User Equipment (UE) technologies used to constrain network slicing

Abstract

The techniques discussed herein facilitate configuring network slices for user equipment (UE) to support constraints on simultaneous operation of slices. An exemplary embodiment is a UE device configured to: transmit a registration request message requesting registration on a set of requested network slices; and receive a registration acceptance message indicating that the UE is registered to a set of allowed network slices, wherein the registration acceptance 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

Background Technology

[0001] Next-generation wireless communication systems, such as 5G or New Radio (NR) networks, enable ubiquitous connectivity and access to information and data sharing globally. 5G networks and network slicing provide a unified, service-based framework that targets common and sometimes conflicting performance standards and serves an extremely diverse range of application domains, from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and others. Generally, NR can include further developments based on 3GPP Long Term Evolution (LTE) advanced technologies and additional enhanced radio access technologies (RATs) to achieve seamless and faster wireless connectivity solutions. Attached Figure Description

[0002] Figure 1 This is a block diagram illustrating the architecture of a system, including the core network (CN) (e.g., fifth-generation (5G) CN (5GC)), based on various aspects.

[0003] Figure 2 This is an illustration showing exemplary components of a device that may be employed according to the various aspects discussed herein.

[0004] Figure 3 This is a diagram illustrating an exemplary interface of a baseband circuit that may be used according to the various aspects discussed herein.

[0005] Figure 4 This is a block diagram illustrating a system based on the various aspects discussed herein, which facilitates network slicing-related configuration for user equipment (UE) subject to constraints of simultaneous slicing use.

[0006] Figure 5 This is an illustration showing an example of a network slice that combines the various aspects discussed in this article.

[0007] Figure 6 A call flowchart illustrating the method for establishing network slices for a UE is shown, combining the various aspects discussed in this article.

[0008] Figure 7 The first exemplary call flow combining simultaneous slice usage constraints is shown based on the various aspects discussed herein.

[0009] Figure 8 A second exemplary call flow combining slice registration with simultaneous slice usage constraints is shown based on the various aspects discussed herein.

[0010] Figure 9An exemplary table is shown based on the various aspects discussed herein, illustrating three examples of allowed slices, showing the slice / service type (SST) value, optional SD value, and compatibility between slices.

[0011] Figure 10 An exemplary table is shown according to the third set of aspects discussed herein, in which compatibility between slices is shown based on explicit indications of slice incompatibility.

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

[0013] Figure 12 An exemplary table is shown according to the third set of aspects discussed herein, in which the compatibility between slices is shown via a slice incompatibility indication based on GSMA identifier constraints.

[0014] Figure 13 An illustration of an exemplary call flow involving the selective establishment of Protocol Data Unit (PDU) sessions by a UE is shown in conjunction with the various aspects discussed herein.

[0015] Figure 14 A diagram illustrating a first example call flow that prioritizes releasing sliced ​​IEs or values ​​is shown, taking into account the various aspects discussed in this article.

[0016] Figure 15 A second exemplary call flow is illustrated, taking into account the various aspects discussed herein, and employing the priority release of slice information elements (IEs) or values.

[0017] Figure 16 A third example call flow diagram is shown, combining the various aspects discussed in this article, employing a priority release of slice IE or value.

[0018] Figure 17 An illustration of an exemplary call flow that implicitly releases a PDU session using the PDU session state IE, in conjunction with the various aspects discussed herein, is shown.

[0019] Figure 18 An illustration of an exemplary call flow for establishing user plane resources using uplink data state is shown, taking into account the various aspects discussed in this article.

[0020] Figure 19 The present paper illustrates an exemplary call flow for locally releasing a PDU session using the PDU session state IE when the UE is not allowed to register for a constrained slice, taking into account the various aspects discussed herein. Detailed Implementation

[0021] This disclosure will now be described with reference to the accompanying drawings, in which similar reference numerals are used throughout to denote similar elements, and the structures and devices shown are not necessarily 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, 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 user equipment with processing capabilities (e.g., a mobile phone or other device configured to communicate via 3GPP RAN, etc.). By way of example, an application running on a server and a server can also be components. One or more components may reside in a process, and components may be located on a single computer and / or distributed among two or more computers. A group of elements or a group of other components may be described herein, wherein the term “group” may be interpreted as “one or more” unless the context otherwise indicates (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 a set S or a “proper subset”, where each element of the proper subset is an element of the set S, but the set S includes at least one element that is not a proper subset of the set S.

[0022] Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored, such as by utilizing modules, for example. Components can communicate via local and / or remote processes, for example, based on 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 throughout a network, such as the Internet, a local area network, a wide area network, or similar networks with other systems via signals).

[0023] For example, a component can be a device with a specific function provided by a mechanical component operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry can be operated by a software application or firmware application executed by one or more processors. The one or more processors can be internal or external to the device and can execute at least a portion of the software or firmware application. As another example, a component can be a device that provides a specific function through an electronic component without a mechanical component; the electronic component may include one or more processors to execute software and / or firmware that at least partially endows the electronic component with that function.

[0024] The use of the term “exemplary” is intended to present the concept in a specific 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 stated or clearly apparent from the context, “X adopts A or B” is intended to mean any natural inclusive arrangement. That is, “X adopts A or B” is satisfied if X adopts A; X adopts B; or X adopts both A and B. Additionally, the articles “a” and “an” used in this application and the appended claims should generally be interpreted as meaning “one or more” unless otherwise stated or clearly apparent from the context to refer to the singular form. 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 included in a manner similar to the term “comprising.” Furthermore, in the context of discussing one or more numbered items (e.g., “first X,” “second X,” etc.), generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0025] As used herein, the term "circuit" may refer to, be part of, or may include: an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or grouped), and / or memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functions. In some aspects, a circuit may be implemented in one or more software or firmware modules, or the functions 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 operate at least partially in hardware.

[0026] The various aspects discussed in this article may involve facilitating wireless communication, and the nature of these communications may vary.

[0027] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 explained to users.

[0028] The aspects described herein can be implemented into a system using any appropriately configured hardware and / or software. Figure 1The architecture of system 100, including core network (CN) 120 (e.g., fifth-generation (5G) CN (5GC)), is shown according to various aspects. System 100 is shown to include: UE 101, which may be the same as or similar to one or more other UEs discussed herein; 3GPP radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, (R)AN 110, which may 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 data network (DN) 103, which may be, for example, operator services, Internet access or third-party services; and fifth-generation core network (5GC) 120. 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 As shown.

[0029] Figure 2 Exemplary components of device 200 according to some aspects are shown. In some aspects, 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 (at least coupled together as shown). The components of the illustrated device 200 may be included in a UE or RAN node. In some aspects, device 200 may include fewer components (e.g., the RAN node may not utilize application circuitry 202, but instead include a processor / controller to process IP data received from a CN such as 5GC 120 or Evolved Packet Core (EPC). In some aspects, device 200 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in device 200, etc.) or input / output (I / O) interfaces. In other respects, the following components may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

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

[0031] Baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 206 and generate baseband signals for the transmit signal path of RF circuitry 206. Baseband circuitry 204 may interact with application circuitry 202 to generate and process baseband signals and control the operation of RF circuitry 206. For example, in some aspects, 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.). Baseband circuitry 204 (e.g., one or more baseband processors 204A-D) may handle various radio control functions that can communicate with one or more radio networks via RF circuitry 206. In other aspects, some or all of the functions of the baseband processors 204A-D may be included in modules stored in memory 204G and may be executed via a central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, and radio frequency shifting. In some aspects, the modulation / demodulation circuitry of the baseband circuitry 204 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some aspects, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. The aspects of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other aspects.

[0032] In some aspects, the baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and in other aspects may include other suitable processing elements. In some aspects, 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, for example, on a system-on-a-chip (SoC).

[0033] In some aspects, baseband circuit 204 can provide communication compatible with one or more radio technologies. For example, in some aspects, baseband circuit 204 can support communication with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN), etc. Aspects in which baseband circuit 204 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuitry.

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

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

[0036] In some respects, the mixer circuit 206a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 206d to generate an RF output signal for the FEM circuit 208. The baseband signal can be provided by the baseband circuit 204 and can be filtered by the filter circuit 206c.

[0037] 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 downconversion and upconversion, 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 suppression (e.g., Hartley image suppression). In some aspects, the mixer circuit 206a of the receive signal path and the mixer circuit 206a may be arranged for direct downconversion and direct upconversion, 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.

[0038] In some aspects, the output baseband signal and the input baseband signal may be analog baseband signals, but the range of aspects is not limited in this respect. In some alternative aspects, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative aspects, RF circuit 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuit 204 may include a digital baseband interface for communicating with RF circuit 206.

[0039] In some dual-mode aspects, separate radio IC circuits can be provided to process signals for each spectrum, but the range of each aspect is not limited in this respect.

[0040] In some respects, synthesizer circuit 206d can be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the range of aspects is not limited in this respect, as other types of frequency synthesizers can be suitable. For example, synthesizer circuit 206d can be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0041] Synthesizer circuit 206d can 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 respects, synthesizer circuit 206d can be a fractional N / N+1 synthesizer.

[0042] In some respects, 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 circuit 204 or the application circuit 202 according to the desired output frequency. In some respects, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by the application circuit 202.

[0043] 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 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 carry output) to provide a fractional division ratio. In some exemplary aspects, the DLL may include cascaded, tunable, delay elements, a phase detector, a charge pump, and a set of D-type flip-flops. In these aspects, the delay elements may be configured to divide the VCO period 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 period.

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

[0045] FEM circuit 208 may include a receive signal path, which 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 RF circuit 206 for further processing. FEM circuit 208 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 206 for transmission through one or more of the one or more antennas 210. In various aspects, amplification via the transmit or receive signal path may be performed only in RF circuit 206, only in FEM circuit 208, or in both RF circuit 206 and FEM circuit 208.

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

[0047] In some respects, the PMC 212 can manage the power supplied to the baseband circuitry 204. Specifically, the PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 212 is typically included when the device 200 is capable of being battery powered, for example, when the device is included in a UE. The PMC 212 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

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

[0049] In some respects, PMC 212 can control or otherwise participate in various power-saving mechanisms of device 200. For example, if device 200 is in the RRC_Connected state, where it remains connected to the RAN node as expected to receive traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 200 can be powered down for short intervals, thereby saving power.

[0050] If there is no data traffic activity during the extended period, device 200 can transition to the RRC_Idle state, in which it disconnects from the network and does not perform operations such as channel quality feedback or handover. 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 off again. Device 200 may not receive data in this state; to receive data, the device can transition back to the RRC_Connected state.

[0051] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0052] The processors of application circuit 202 and baseband circuit 204 can be elements used to execute one or more instances of a protocol stack. For example, the processor of baseband circuit 204 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of application circuit 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 the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0053] Figure 3An exemplary interface for a baseband circuit is shown, based on 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 respectively include a memory interface 304A-304E for sending / receiving data to / from the memory 204G.

[0054] Baseband circuit 204 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 204); application circuit interface 314 (e.g., for sending / receiving data to / from a memory external to baseband circuit 204); and application circuit interface 314 (e.g., for sending / receiving data to / from a memory external to baseband circuit 204). Figure 2 Application circuit 202 (interface for sending / receiving data); RF circuit interface 316 (e.g., for sending / receiving data to / from...). Figure 2 RF circuit 206 (interface for transmitting / receiving data); wireless hardware connection interface 318 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Components (e.g.) Low Energy) Interface for sending / receiving data to / from PMC212 (e.g., an interface for sending / receiving power or control signals to / from PMC212).

[0055] In the 3rd Generation Partnership Project (3GPP) and in this document, a network slice (also referred to herein as a slice) may be referred to as a Single Network Slice Selection Auxiliary Information (S-NSSAI) value, which is uniquely associated with that network slice. A set of S-NSSAIs may be collectively referred to as NSSAIs. Configured NSSAIs (also referred to herein as configured network slices or configured slices, etc.) include NSSAIs configured for the UE, which may be based on factors such as the UE's subscription, the current serving network, etc. Requested NSSAIs (also referred to herein as requested network slices or requested slices, etc.) include NSSAIs provided by the UE to the serving Public Land Mobile Network (PLMN) during registration (the requested NSSAIs are a subset of the UE's configured NSSAIs). Allowed NSSAIs (also referred to herein as allowed network slices, allowed slices, registered NSSAIs, registered network slices, or registered slices, etc.) include NSSAIs provided by the serving PLMN during, for example, the registration process, indicating S-NSSAI values ​​that the UE can use in the serving PLMN of the current registration area (the allowed NSSAIs are a subset of the UE's requested NSSAIs). Rejected NSSAI (also referred to in this document as rejected network slices or rejected slices, etc.) includes NSSAIs that are permanently or temporarily rejected for the current registered region or for the entire PLMN.

[0056] The implementation scheme relates to network slice configuration for UEs constrained by the simultaneous use of network slices. This document discusses various aspects involving network slice registration, establishing and releasing PDU sessions on network slices, and / or activating and releasing user plane resources for PDU sessions on network slices, each of which may potentially be constrained by the simultaneous use of these network slices. The constraints on network slice use discussed herein can 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 concurrently 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, then 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 concurrently active user plane resources for established PDU sessions, etc.).

[0057] refer to Figure 4This diagram illustrates a block diagram of system 400 according to various aspects discussed herein. This system 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 / TRP), an Access and Mobility Management Function (AMF), or another component of a 3GPP (3rd Generation Partnership Project) network (e.g., a 5GC (5th Generation Core Network) component or function, such as a UPF (User Plane Management Function)). This system facilitates network-slicing-related configuration of the UE for simultaneous use under network slicing constraints. System 400 may include a processor 410, communication circuitry 420, and memory 430. Processor 410 (e.g., it may include one or more of 202 and / or 204A-204F, etc.) may include processing circuitry and associated interfaces (e.g., a communication interface for communicating with communication circuitry 420 (e.g., RF circuitry interface 316), a memory interface for communicating with memory 430 (e.g., memory interface 312), etc.). The communication circuitry 420 may include, for example, circuitry for wired and / or wireless connections (e.g., 206 and / or 208), which may include transmitter circuitry (e.g., associated with one or more transmission chains) and / or receiver circuitry (e.g., associated with one or more receiver chains), wherein the transmitter and receiver circuitry may employ common and / or different circuitry elements, or combinations 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 a variety of storage media (e.g., volatile and / or non-volatile according to any of a variety of technologies / constructions, etc.), and may store instructions and / or data associated with one or more of the processor 410 or the communication circuitry 420.

[0058] Specific types of aspects of system 400 (e.g., UE aspects, etc.) can be indicated via subscripts (e.g., system 400). UE Including processor 410 UE 420 Communication Circuit UE and memory 430 UE In some aspects, such as the BS aspect (e.g., System 400) BS ) and network components (e.g., AMF, etc.) (e.g., System 400) AMF Processor 410 BS (etc.), communication circuits (e.g., 420) BS (etc.) and memory (e.g., 430) BSSignaling or message transmissions between different aspects of system 400 (e.g., 4001 and 4002) may be generated by processor 4101, transmitted by communication circuitry 4201 through a suitable interface or reference point (e.g., 3GPP air interfaces 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) may participate in the communication.

[0059] In various aspects, one or more of the following—information (e.g., system information, resources associated with signaling, etc.), characteristics, parameters, etc.—may be transmitted via signaling originating from or guided through a base station (e.g., gNB, etc.) (e.g., access stratum (AS) signaling, non-access stratum (NAS) signaling) or other access points (e.g., via processor 410) BS Generated by communication circuit 420 BS Transmission, via communication circuit 420 UE Received, and processed by processor 410 UE The signaling used (processed) is configured to the UE. Depending on the type, characteristics, parameters, etc. of the information, the exact details of the signaling used and / or the operations performed at the UE and / or BS during processing (e.g., signaling structure, PDU / SDU processing, etc.) may vary. However, for convenience, such operations may be referred to herein as generating or processing configuration signaling for UE configuration information / characteristics / parameters / etc., or via similar terms.

[0060] refer to Figure 5 This figure illustrates an example of network slice 500, combining the various aspects discussed in this article. 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 illustrated have specific behaviors related to network slice configuration. UDM 127 can store (e.g., UE 101's) user subscriptions, such as whether the user has purchased a subscription to an HD streaming slice. NSSF 129 can provide logical functionality to assess whether a user is allowed to use a given slice in the current PLMN. PCF 126 can provide the UE with rules to identify which type of traffic is sent via which slice. For all slice-related configurations, AMF 121 can act as a single point of contact with the UE. UE 101 can establish slice-specific sessions and route packets on the appropriate slice.

[0061] The independence of network slicing offers the potential to customize RAN (Radio Access Network) and / or CN (Core Network) configurations based on network slices. From the AS (Access Layer) perspective, slice traffic is part of a separate DRB (Data Radio Bearer). From the NAS (Non-Access Layer) perspective, slice traffic is part of a separate PDU (Protocol Data Unit) session.

[0062] The types of entities that can be involved in the management, leasing, or development of a slice can vary. Slices are owned by network operators but can be subleased to enterprises (e.g., Apple) that can develop use cases to leverage the benefits of the slice. Each slice has its own Service Level Agreement (SLA), which specifies its characteristics, such as the maximum number of concurrent users, aggregate bandwidth, etc.

[0063] Network slicing has a variety of potential commercial use cases. As examples, network slicing can provide: (1) QoS (Quality of Service) management for each service (e.g., uRLLC, eMBB, V2X, etc.); (2) enhanced security implementation (e.g., security applications, enterprise solutions such as corporate email, etc.); (3) differentiated billing (e.g., Apple has slices for FaceTime and can provide FaceTime service with zero data charges and higher QoS, etc.).

[0064] refer to Figure 6This figure illustrates a call flow diagram of method 600 for establishing a network slice for a UE, incorporating the various aspects discussed herein. UE 101 may be pre-configured with a list of network slice selection assistance information (NSSAIs) via carrier feature-specific pre-configuration (referred to as carrier binding (CB)) in the UE SW or via previous registration attempts of UE 101, wherein an NSSAI may include a set of one or more individual NSSAIs (S-NSSAIs), each individual NSSAI being associated with a distinct network slice. As used herein, the configured NSSAIs may include S-NSSAIs provided by the operator and subscribed to by the UE (e.g., UE 101). At 602, UE 101 may transmit a registration request message to the BS (e.g., gNB) of RAN 110, which includes one or more requested NSSAIs (e.g., selected by UE 101 from its configured NSSAIs). At 604, the BS can select AMF 121 based on the requested NSSAI included in the Radio Resource Control (RRC) message, and can send the registration request message to the selected AMF 121. At 608, AMF 121 can send a message to UDM 127 to obtain slice selection subscription data for UE 101. At 610, UDM 127 can check UE 101's subscriptions. At 612, UDM 127 can send the list of subscribed NSSAIs and the default NSSAI for UE 101 to AMF 121. At 614, AMF 121 can 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 to AMF 121 for UE 101 AMF candidates (e.g., if different from AMF 127), configured NSSAIs, allowed NSSAIs (if any), rejected NSSAIs (e.g., those permanently or temporarily rejected for the current registration area or for the entire PLMN), and rejection reasons (if any), as well as pending NSSAIs (if any). At 618, AMF 121 may perform an AMF reallocation procedure as appropriate (e.g., if the AMF candidates at 616 are different from AMF 121 selected at 604). At 620, AMF 121 may send a registration acceptance message to UE 101, which includes any allowed NSSAIs, any rejected NSSAIs and rejection reasons, and the UE configuration for UE 101.At 622, AMF 121 may initiate (e.g., in response to an updated NSSAI message from UE 101) a Network Slice Specific Authentication and Authorization (NSSAA) procedure for any eligible slice. At 624, in response to the NSSAI procedure, AMF 121 may send a configuration update command to UE 101, indicating the allowed NSSAIs (if any) and the denied NSSAIs (if any) and the reasons for denial.

[0065] The 3GPP SA2 (Architecture Working Group 2 (WG2)) has identified constraints 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 defined parameters: value (integer), unit of measurement (NA), example (0: can be used with any network slice; 1: can be used with network slices with the same SST [Slice / Type of Service] 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 class), and label (character attribute / feature).

[0066] The 3GPP Release 15 (Rel-15) and Rel-16 specifications do not allow the implementation of constraints associated with network slicing, as defined in this property.

[0067] The SA2 issue is to investigate: (1) how to implement the constraints associated with network slicing in both roaming and non-roaming scenarios in the UE and the network; (2) how to ensure that the identified implementation scheme does not negatively affect network operations of Rel-15 and Rel-16 5GS deployments; (3) as understood from the GSMA 5GJA NG.116 document (sections 3.4.25 and 3.4.9), for some network slices, the service network may need to separate slice operations due to security isolation and service network configuration, resulting in mutually exclusive slice operations; (4) slice operation constraints may exist in: the service network but not in the home network, or in the home network but not in the service network, or in both the home network and the service network; and (5) the network may deploy non-standardized network slice identifiers, and the issue includes how to deploy slice exclusivity in this case.

[0068] Various implementation schemes may employ the techniques discussed herein that facilitate network slice configurations subject to constraints on the simultaneous use of slices. These techniques encompass three distinct sets of aspects for handling constraints on the simultaneous use of network slices, including various options within those techniques.

[0069] When the UE (e.g., UE 101 and / or includes system 400) UE When a UE (e.g., a UE) subscribes to multiple slices (e.g., these slices may be referred to herein as slices or S-NSSAIs, such as S-NSSAI_1 (or SLICE_1), S-NSSAI_2, S-NSSAI_A, S-NSSAI_B, etc.), various implementation schemes discussed herein may be employed. In various aspects of the implementation schemes 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 an indication of whether the UE supports a new capability of simultaneous slice usage constraints. In response to the registration request message, the NW may send a registration acceptance message (e.g., similar to 620), which may in various aspects indicate the selection of one or more network slices based on the UE's support of simultaneous slice usage constraints.

[0070] refer to Figure 7 The figure illustrates a first exemplary call flow 700 of slice registration incorporating simultaneous slice usage constraints, according to the various aspects discussed herein. At 702, UE 101 may send a registration request message to AMF 121, which includes a requested NSSAI (e.g., similar to 602) and may also include (in various ways) an indication that the UE supports simultaneous slice usage constraints. At 704, AMF may contact UDM 127 to obtain UE subscription information and NSSF 129 to obtain network capabilities for simultaneous slice operation in conjunction with the requested NSSAI. At 706, AMF 121, NSSF 129, PCF 126, and UDM 127 may register UE 101 to at least one (and possibly more, depending on slice compatibility, etc.) of the requested NSSAIs, according to the registration process discussed herein and section 4.2.2.2 of 3GPP Technical Specification (TS) 23.502. At 708, AMF 121 may send a registration acceptance message to the UE, which indicates the allowed NSSAIs (e.g., similar to 620) and also indicates compatibility parameters for each such S-NSSAI (e.g., indicating whether the slice is compatible or incompatible with other slices operating simultaneously, according to the various aspects discussed herein). In some aspects, the registration acceptance message may also indicate compatibility parameters for the S-NSSAIs used for each configuration of the UE.

[0071] In various aspects, the compatibility information (e.g., compatibility parameters, etc.) used for slicing or S-NSSAI, as discussed herein, may indicate to this S-NSSAI which other S-NSSAIs (e.g., configured NSSAIs, requested NSSAIs, or permitted NSSAIs) are compatible or incompatible with this S-NSSAI regarding one or more of the following: (a) compatibility or incompatibility of network slices with simultaneous registrations for the UE; (b) compatibility or incompatibility of network slices with simultaneously established PDU sessions for the UE; (c) compatibility or incompatibility of network slices with simultaneously active user plane resources for established PDU sessions for the UE. In some cases, this indication may be explicit (e.g., S-NSSAI_1 is incompatible with simultaneous registrations with S-NSSAI_2, or is incompatible with S-NSSAI_2 with simultaneously active PDU sessions, etc.). In other cases, the indication can be implicit (e.g., S-NSSAI_1 is compatible with S-NSSAI_3 or S-NSSAI_4 when registered together, but no explicit indication of compatibility / incompatibility is provided for the configured S-NSSAI_2; instead, it implicitly indicates that S-NSSAI_1 is incompatible with S-NSSAI_2 when registered together, etc.).

[0072] refer to Figure 8 The figure illustrates a second exemplary call flow 800 for slice registration incorporating simultaneous slice usage constraints, based on the 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 NSSAI in response to the initial request). At 804, AMF may contact UDM 127 to obtain UE subscription information and contact NSSF 129 to obtain network capabilities for simultaneous slice operation in conjunction with the UE's configured NSSAI, and AMF may store compatibility information.

[0073] 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 can register with each other simultaneously, but none of them can register with S-NSSAI_D simultaneously; (b) S-NSSAI_A and S-NSSAI_B can have PDU sessions that are active simultaneously with each other, but neither of them can have a PDU session that is active simultaneously with S-NSSAI_C; and (c) S-NSSAI_A and S-NSSAI_B can have user plane resources that are established simultaneously with each other.

[0074] Table 1: Exemplary Slice Compatibility Information Provided to the UE

[0075]

[0076] In the example in Table 1, although simultaneous registration of S-NSSAI-A, S-NSSAI-B, and S-NSSAI-C is allowed (i.e., all three S-NSSAIs can be part of a list of allowed NSSAIs received simultaneously from the network), the UE is allowed to establish PDU sessions simultaneously and have active user plane resources for PDU sessions 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 either released or have not yet been established.

[0077] Similarly, as seen in this example, uRLLC slice S-NSSAI-D is not allowed to register simultaneously with another configured NSSAI. Therefore, if a UE wishes to access S-NSSAI-D, it can first initiate a mobility or periodic registration process with the network using an NSSAI configured to include a request for S-NSSAI-D. The UE can also ensure that PDU sessions associated with incompatible slices are implicitly released and indicated to the network via the PDU session state IE in the registration request, or explicitly released via a PDU session release request.

[0078] 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, depending on slice compatibility, etc.) of the initially requested NSSAIs, in accordance with the registration process discussed herein and section 4.2.2.2 of 3GPP Technical Specification (TS) 23.502. At 808, AMF 121 may send a registration acceptance message to the UE, indicating slice compatibility information for each configured S-NSSAI of the UE (and may also indicate one or more S-NSSAIs registered as allowed NSSAIs at 806).

[0079] At 810, the UE may send a periodic or mobility registration request to the AMF including the requested NSSAIs (e.g., S-NSSAI_A, S-NSSAI_B, and S-NSSAI_C). In various respects, the requested NSSAIs 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 NSSAIs (however, for example, one or more S-NSSAIs may be rejected for reasons other than slice incompatibility). At 814, the AMF may send a registration acceptance 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, such as...). Figure 8 (As shown).

[0080] In conjunction with various aspects of the exemplary call flow 800, 802 to 808 may occur once during the initial registration with the PLMN, while 810 to 816 (or similar actions) may potentially occur multiple times when the UE sends periodic and / or mobility registration requests (e.g., NSSAI with potentially varying requests and permitted NSSAI).

[0081] In the first group, NW can create a list of allowed NSSAIs based on the requested NSSAI, similar to... Figure 6 616-620 in the table. However, in addition, each S-NSSAI in the allowed NSSAIs may include a list of compatible S-NSSAIs, which defines the slices that can work concurrently with the S-NSSAI. References Figure 9 The figure illustrates an exemplary table based on the various aspects discussed herein, showing examples of three allowed slices, illustrating the SST value, optional SD value, and compatibility between slices. In the first set of aspects, when the UE indicates support for simultaneous slice use constraints, the NW will not reject S-NSSAI due to slice incompatibility issues (however, the NW may still reject S-NSSAI for other reasons (e.g., quota unavailability, NSAAA failure, etc.)). Additionally, if the UE does not support support for simultaneous slice use constraints, the network is free to reject slices due to slice incompatibility issues (e.g., for 3GPP Rel-16 UEs, etc.).

[0082] In the second group, each S-NSSAI in the list of NSSAIs used for UE configuration can indicate a list of compatible S-NSSAIs that can work concurrently with it (e.g., such as...). Figure 9(As shown). AMF ensures that all S-NSSAIs listed in the compatible NSSAI list are part of the configured NSSAI list. Based on UE priority policies (e.g., which set of slices the user / UE is interested in), the UE can initiate a new registration process, indicating the requested NSSAI (e.g., such as...). Figure 7-8 (As shown). 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.

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

[0084] In the third group, the UE can include a new information element (IE) indicating support for simultaneous slicing using constraints in (e.g., Figure 7-8 The registration request (etc.) indicates awareness of slice constraints.

[0085] Additionally, AMF can be used in (for example, Figure 7-8 The registration acceptance includes a new IE indicating slice compatibility. The slice compatibility IE can indicate slice compatibility or incompatibility among all slices subscribed to by the UE. To provide this information, the Serving AMF can: (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 these constraints, and according to the GST attribute provided by the network slice provider, send the slice compatibility IE to the UE.

[0086] In various implementations, the slice compatibility IE may also include information about AMF reassignment (e.g., via indication, for each pair of incompatible slices, whether they are served by the same AMF or by different AMFs, etc.). AMF reassignment information may be based on service network configurations regarding how the serving network selects service-independent slices.

[0087] In the third group, the UE may send a registration request with the requested S-NSSAI (e.g., such as...). Figure 7-8As shown in SLICE_A and SLICE_B, it may also include an indication supporting constraint-based slice activation. In response, the AMF may send a registration acceptance with permitted S-NSSAI (e.g., as shown in the image). Figure 7-8 As shown in the figure, it may include allowing the use of incompatible slices at the same time, and may also include specifying which slices are allowed to be used at the same time in Slice Compatibility IE.

[0088] In the third aspect, when any PDU session is initiated and a slice is activated, the UE follows the slice compatibility rules set in the slice compatibility IE. The rules in the slice compatibility IE are specific to the serving network only, and the registration process on a new network can generate new slice constraint rules for the UE.

[0089] In the third group, there are several options for addressing potential registration issues for UEs on incompatible slices.

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

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

[0092] The first option addresses the slices entering NSSAA. After successful NSSAA, the UE can move these slices to the "Allowed List," but still use the information provided in the "Slice Compatibility IE" to activate the PDU session on the compatible slice.

[0093] In the second option, the UE is allowed to register simultaneously for the constrained slice and establish a simultaneous PDU session on the constrained slice, but there are no concurrently active user plane resources on the constrained slice.

[0094] An example of the second option is a scenario where the UE already has an active PDU session (e.g., created on SLICE_A), and SLICE_A and SLICE_B are available in the permitted NSSAI. However, (depending on the slice compatibility IE) the UE can establish simultaneous PDU sessions on both slices, but only one slice can have an active user plane resource. If a new PDU session for SLICE_B requires the user plane resource to be active, the UE can (a) use the "PDU Session State IE" in a service request or registration request to begin releasing the currently active user plane resource on SLICE_A, or (b) wait to release the user plane resource on SLICE_A before establishing the user plane resource on SLICE_B. To activate the user plane resource on SLICE_B, the UE can include the "Uplink Data State" IE in the registration request or service request. In various aspects, the UE can check slice compatibility before triggering a service request or registration request to request user plane resources on other slices.

[0095] In the third option, UE registration for constrained slices is not allowed. An example of this third option is a scenario where the UE sends a registration request with a requested S-NSSAI (e.g., SLICE_A, SLICE_B) and an indication supporting constraint-based slice activation, and the AMF sends a registration acceptance with only allowed S-NSSAIs for SLICE_A, where the registration acceptance also includes a slice compatibility IE specifying which slices are allowed to be used simultaneously. After a 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 for the slice with SLICE_B as the requested slice, and locally deactivates / releases all PDU sessions using SLICE_A, indicating this to the network by including a PDU session state IE and indicating that the PDU session ID corresponding to SLICE_A is inactive.

[0096] In conjunction with the third option, when SLICE_B is activated, the UE can omit the 5G S-Temporary Mobile Subscriber Identity (5G S-TMSI) associated with the AMF used for SLICE_A in the message transmission to the BS (e.g., gNB) during the RRC connection establishment process, preventing the BS from selecting the same AMF again. For example, if the UE has already 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 simultaneously due to being served by different AMFs, then if the network has initially activated SLICE_A and the UE now wants to activate SLICE_B, the UE omits the 5G S-TMSI in the message transmission to the BS (e.g., gNB). By omitting the 5G S-TMSI, the UE prevents the BS from selecting the same AMF again to activate SLICE_B. These aspects provide a solution for scenarios where the UE triggers a PDU session after registration acceptance with an allowed S_NSSAI consisting of SLICE_B. For slices with NSAA that already exist in the allowed list, omitting 5G S-TMSI can trigger registration via the appropriate AMF.

[0097] Additionally, the technology associated with the third option may involve AMF selection performed by the BS (e.g., gNB). When the requested slice information is received in NSSAI inclusion mode in the RRC CONNECTION ESTABLISHMENT, the BS may select the appropriate AMF based on the first slice indicated by the UE in the RRC CONNECTION ESTABLISHMENT when switching between independent slices that involve registration to different AMFs.

[0098] In various aspects of the third option, a fallback timer can be used in conjunction with slice selection. In some scenarios, applications running incompatible slices (e.g., SLICE_A or SLICE_B) may be activated as needed within the UE. These applications could potentially cause the network to continuously switch between different constrained slices through re-registration procedures or PDU session deactivation and reactivation. To limit rapid switching between slices, in various aspects, the network may (e.g., during registration acceptance or PDU session establishment acceptance) provide a fallback timer so that the UE can only activate mutually constrained slices after the fallback timer has expired.

[0099] As an example scenario involving a fallback 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 simultaneously due to being served by different AMFs. The AMF provides a fallback timer in the registration acceptance, which instructs the UE that it cannot activate SLICE_B until the fallback timer expires. Similarly, this can be applied to scenarios where SLICE_A and SLICE_B are both sent in an allowed NSSAI, but exist in a slice compatibility IE indicating that SLICE_A and SLICE_B cannot have concurrently active PDU sessions. In this scenario, the AMF can instruct the UE that it cannot activate a PDU session on SLICE_B until the constraint fallback timer expires.

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

[0101] Furthermore, in conjunction with the third aspect, a technique can be employed whereby the network can dynamically modify slice constraint information when the UDM detects a change in the subscribed NSSAI or a change in slice configuration by the network slice provider. As an example scenario, if the UE has already 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 simultaneously due to different AMF services, then if the network has initially activated SLICE_A and the UDM detects a change in the NSSAI that indicates the UE should no longer subscribe to SLICE_B, the AMF can instruct the UE to remove SLICE_B from the slice constraint IE. These techniques can be implemented via an AMF-triggered 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 detected changes in the subscribed NSSAI or slice configuration, etc.).

[0102] refer to Figure 10 The figure illustrates an exemplary table based on the third set of aspects discussed herein, where compatibility between slices is shown based on explicit indications of slice incompatibility. Figure 10 The lower right table shows an example of slices for UE configuration of the serving 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 combined with which slices provide, and whether 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 simultaneously with all other registered slices.

[0103] refer to Figure 11 The figure illustrates an exemplary table based on the third set of aspects discussed herein, in which compatibility between slices is shown via an indication of SST-based slice incompatibility. Figure 11 The lower right table shows an example of slices for UE configuration of the serving 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 can be combined with the information provided by those slices, and whether slices incompatible with SST are served by the same AMF. Although Figure 11 An SST-based example is provided, but similar techniques can be used in conjunction with SD-based incompatibility indicators.

[0104] refer to Figure 12 The figure illustrates an exemplary table according to the third set of aspects discussed herein, where slice compatibility is shown via slice incompatibility indications based on GSMA identifier constraints. The slices configured by the UE for serving the network can be... Figure 10 and Figure 11 The same as in [the previous sentence]. Figure 12 The lower table shows the exclusion types indicated by combining the above discussion and the GST examples provided by the GSMA. Figure 12 The upper table shows exemplary incompatibility information provided by the configured slices, as well as incompatible slice constraints and exclusion types. Figure 10 and 11 Similarly, the lack of indicated constraints between slices implicitly suggests that the UE can operate on those slices simultaneously.

[0105] Figure 13-19 An exemplary call flowchart is shown in conjunction with the first, second, and third groups of aspects. In various implementations, (e.g., according to...) Figure 7 or Figure 8 After registration, such as combining Figure 13-19 The techniques discussed may be used for one or more of the following: (a) changing the permitted network slices for the UE (e.g., adding and / or removing registered network slices based on the application or service to be adopted); (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 PDU sessions on a registered network slice (e.g., a network slice with active PDU sessions).

[0106] refer to Figure 13This figure illustrates an exemplary call flow 1300 involving a UE selectively establishing a PDU session, in conjunction with the various aspects discussed herein. Flow 1300 can be used in an exemplary scenario where the network has already allowed the UE to register an incompatible slice, and the UE decides to selectively establish a PDU session on a slice incompatible with the slice having an active PDU session. In flow 1300, an active PDU session exists for S-NSSAI_1 for UE 101. At 1302, the user of UE 101 can initiate a new application or service served by S-NSSAI_2. At 1304, the UE, wanting to initiate a PDU session for S-NSSAI_2, checks and determines that S-NSSAI_1 and S-NSSAI_2 cannot operate simultaneously (e.g., as indicated by the AMF via registration acceptance, in the configured NSSAI list, in slice compatibility IE, etc.). At 1306, the UE can send a PDU session release request for S-NSSAI_1 to the AMF. At 1308, a PDU session release procedure can be performed for S-NSSAI_1. This procedure may include: at 1310, the AMF sends and the UE receives a PDU session release command, indicating that the PDU session has been 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 by the UE. If so, at 1316, a PDU establishment procedure can be performed for S-NSSAI_2, and at 1318, the AMF may send a PDU session establishment acceptance message to the UE, indicating S-NSSAI_2 and the PDU session ID. At 1320, the PDU session is active for S-NSSAI_2.

[0107] In various implementations, a technique can be employed whereby the UE can indicate that the requested PDU session is a priority PDU session for the UE relative to other PDU sessions. In implementations employing such a technique, the UE can send a PDU session establishment request with an allowed NSSAI, and this request may include a priority release slice IE that notifies the network that this is a priority PDU session for the UE. According to this implementation, if the IE exists or is set to 1, the NW can release active PDU sessions with S-NSSAI incompatible with the S-NSSAI for its requested PDU session, and if the IE does not exist or is set to 0, then if any PDU session with S-NSSAI incompatible with the S-NSSAI for its requested PDU session is active, the NW can reject that PDU session.

[0108] In implementations employing these technologies, when a UE wants to establish a PDU session for S-NSSAI, the UE can check if any active PDU sessions exist in the incompatible slice. If they exist, then if the application / service belonging to that S-NSSAI is in the foreground, the UE can set "Prioritize Slice Release" to 1 (or include the IE, depending on the implementation), and if the request is for a background application / service, no PDU session establishment request is initiated. If they do not exist, the UE can set "Prioritize Slice Release" to 0 (or omit the IE, depending on the implementation). Figure 14-16 An exemplary call flow for techniques associated with priority release slices is shown.

[0109] refer to Figure 14 This figure illustrates a first exemplary call flow 1400 employing a priority release slice IE or value, in conjunction with the 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 for S-NSSAI_2 is set to 1, at 1406, a PDU session release procedure may be performed for S-NSSAI_1 (e.g., according to 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 can 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 can 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.

[0110] refer to Figure 15This figure illustrates a second exemplary call flow 1500 employing a priority release slice IE or value, in conjunction with the 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., according to 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 point 1510, there are concurrent PDU sessions for both S-NSSAI_1 and S-NSSAI_2.

[0111] refer to Figure 16 This figure illustrates a third exemplary call flow 1600 employing a priority release slice IE or value, in conjunction with the 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, at 1606, the AMF sends a PDU session establishment rejection message to the UE indicating S-NSSAI_2, and call flow 1600 ends. However, if they can operate simultaneously, at 1608, a PDU session 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 point 1610, the AMF can send a PDU session establishment accept message to the UE for S-NSSAI_2, indicating the PDU session ID of the established PDU session. At point 1612, there are PDU sessions that are active simultaneously for both S-NSSAI_1 and S-NSSAI_2.

[0112] refer to Figure 17This figure illustrates an exemplary call flow 1700 that implicitly releases a PDU session using the PDU session state IE, in conjunction with the various aspects discussed herein. In 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, checking and determining that S-NSSAI_A and S-NSSAI_B cannot operate simultaneously. At 1704, the UE sends either a service request or a registration request to the AMF, including the PDU session state IE. At 1706, in response to the PDU session state IE, the network can perform a PDU session release procedure for all PDU session IDs not included in the PDU session state IE of the service request or registration request. At 1708, the AMF can send either a service acceptance or registration acceptance message to the UE, including the "PDU session state" IE (depending on the message in 1704). 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 an incompatible PDU session has been released, the UE can send a PDU session establishment request to the AMF indicating S-NSSAI_B. At 1712, the AMF can check and determine that the UE is capable of operating on S-NSSAI_B. At 1714, a PDU establishment procedure can be performed for S-NSSAI_B. At 1716, the AMF can send a PDU session establishment acceptance message to the UE, indicating S-NSSAI_B and the PDU session ID for the PDU session established for it. At 1718, the PDU session is active for S-NSSAI_B.

[0113] refer to Figure 18 This figure illustrates an exemplary call flow 1800 for establishing user plane resources using uplink data state, in conjunction with the various aspects discussed herein. In call flow 1800, the PDU session is active for both S-NSSAI_A and S-NSSAI_B, but only S-NSSAI_A has an allocated active user plane resource (i.e., an active data radio bearer (DRB)). At 1802, the UE may determine the user plane resource for initiating the PDU session active on S-NSSAI_B. The UE checks and determines that S-NSSAI_A and S-NSSAI_B cannot simultaneously activate user plane resources. The UE may wait until the user plane resource for S-NSSAI_A is released, or may initiate a service request including the PDU session state to implicitly release the SLICE_APDU session (e.g., as in...). Figure 17(Or 19, etc.). Once the user plane resources for S-NSSAI_A are released, at 1804, the UE can send a service request or registration request to the AMF, including the uplink state for S-NSSAI_B. At 1806, in response to the uplink state, user plane resources can be established for the PDU sessions active on S-NSSAI_B.

[0114] refer to Figure 19 This figure, in conjunction with the various aspects discussed herein, illustrates an exemplary call flow 1900 of locally releasing a PDU session using the PDU session state IE when the UE is not allowed to register for a restricted slice. At 1902, the UE may (e.g., via a BS such as a gNB) transmit a registration request message to the next-generation (NG) radio access network (RAN), which includes a requested NSSAI (e.g., in...). Figure 19In the example, S-NSSAI_A and S-NSSAI_B are used, and the simultaneous slice usage constraint is indicated. At 1904, the NG RAN can select an AMF based on the requested NSSAI in the RRC message, and at 1906, it can send the registration request message to the selected AMF. At 1908, the AMF can 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 scenarios where S-NSSAI_A and S-NSSAI_B are incompatible, the registration process can be performed for S-NSSAI_A but not for S-NSSAI_B. At 1912, the AMF can send a registration acceptance message to the UE indicating that the allowed NSSAIs only include 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, an active PDU session exists 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 new registration due to incompatibility (e.g., for scenarios employing the third option of the third group aspect). At 1918, the UE may send a second registration request message to the NG RAN, indicating the requested NSSAI including S-NSSAI_B, and the PDU session state IE, thereby triggering the 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 slice operation. At 1926, a registration procedure can be performed for S-NSSAI_B, and at 1928, the AMF selected at 1920 can send a second registration acceptance message to the UE indicating that the newly allowed NSSAI only includes compatible slices, as well as a new slice restriction IE associated with the allowed NSSAI.

[0115] Additional Examples

[0116] Embodiments herein may include subjects such as methods, components for performing actions or blocks of the method, and at least one machine-readable medium including 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 actions of a method, apparatus, or system for concurrent communication using various communication technologies according to the described aspects and examples.

[0117] Example 1 is a user equipment (UE) device including a processor configured to perform operations including: transmitting an initial registration request message including an indication that the UE has the capability to support simultaneous slice usage constraints; receiving a first registration acceptance message indicating slice compatibility information for each of a set 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 set of configured network slices are compatible with the configured network slice for simultaneous operation by the UE; transmitting 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 receiving an additional registration acceptance 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.

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

[0119] Example 3 includes the subject matter of any variation of any of Examples 1-2, wherein the set of allowed network slices includes one or more of the following: the largest subset of the network slices requested in the set, wherein the network slices are each compatible with each other for simultaneous operation by the UE, or the first network slice in the set of requested network slices and any other requested network slice 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 the priority information of the first network slice.

[0120] Example 4 includes the subject of any variation of any of Examples 1-3, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein slice compatibility information indicates that the first network slice and the second network slice are incompatible for concurrently active PDU (Protocol Data Unit) sessions.

[0121] Example 5 includes any variation of the subject matter of Example 4, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: 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 the second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0122] Example 6 includes the subject matter of any variation of any of Examples 4-5, 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, 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.

[0123] Example 7 includes the subject matter of any variation of any of Examples 4-6, wherein when the UE has an active PDU session on the first network slice, the operation further includes: transmitting 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 the second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0124] Example 8 includes the subject matter of any variation of any of Examples 4-7, wherein when the UE has an active PDU session on the first network slice, the operation also includes activating the second network slice via a non-3GPP access technology.

[0125] Example 9 includes the subject matter of any variation of any of Examples 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 acceptance 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.

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

[0127] Example 11 is a user equipment (UE) device including a processor configured to perform operations including: 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 acceptance 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 acceptance 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.

[0128] Example 12 includes the subject of any variation of Example 11, wherein the registration accept message indicates slice compatibility information for each network slice in the set of network slices for the UE, wherein the slice compatibility information for each network slice indicates whether the network slices of other configurations in the set of network slices are compatible with the network slice of that configuration for simultaneous operation by the UE.

[0129] Example 13 includes the subject matter of any variation of any of Examples 11-12, wherein, when the slice compatibility information of each allowed network slice in the group of allowed network slices indicates that another allowed network slice in the group 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 other allowed network slice are associated with the same Access and Mobility Management Function (AMF) or different AMFs.

[0130] Example 14 includes the subject matter of any variation of any of Examples 11-13, wherein the requested network slices include 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 allowed network slices include the first network slice but not the second network slice.

[0131] Example 15 includes the subject of any variation of any of Example 14, wherein a registration accept message indication timer is provided, and the UE may request registration to a second network slice after the timer expires.

[0132] Example 16 includes the subject matter of any variation of any of Examples 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 for requesting registration on the second network slice and implicitly releasing the active PDU session on the first network slice; and receiving a second registration acceptance message indicating that the UE is registered to the second network slice.

[0133] Example 17 includes the subject of any variation of any of Examples 11-16, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein slice compatibility information indicates that the first network slice and the second network slice are incompatible for concurrently active PDU (Protocol Data Unit) sessions.

[0134] Example 18 includes the subject matter of any variation of Example 17, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: 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 the second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0135] Example 19 includes the subject matter of any variation of any of Examples 17-18, 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, 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.

[0136] Example 20 includes the subject matter of any variation of any of Examples 17-19, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: transmitting 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 the second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0137] Example 21 includes the subject matter of any variation of Examples 17-20, wherein, when the UE has an active PDU session on the first network slice, the operation also includes activating the second network slice via a non-3GPP access technology.

[0138] Example 22 includes the subject matter of any variation of any of Examples 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 acceptance 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.

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

[0140] Example 24 is an Access and Mobility Management Function (AMF) including a processor configured to perform operations including: receiving an initial registration request message including an indication that a User Equipment (UE) has the capability to support simultaneous slice usage constraints; generating a first registration acceptance message for transmission, the first registration acceptance message indicating slice compatibility information for each of a set 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 set of configured network slices are compatible with the configured network slices for simultaneous operation by the UE; 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; 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 an additional registration acceptance message for transmission indicating that the UE is registered to the set of allowed network slices.

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

[0142] Example 26 includes the subject matter of any variation of any of Examples 24-25, wherein the set of allowed network slices includes one or more of the following: the largest subset of the network slices requested in the set, 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 slice in the set of requested network slices that is 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.

[0143] Example 27 includes the subject matter of any variation of any of Examples 24-26, wherein the operation further includes: receiving subscription information about the UE associated with the network slices requested in the group from the Unified Data Management (UDM); receiving network capability information about network slices that simultaneously operate the group of requests from the 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.

[0144] Example 28 includes the subject matter of any variation of any of Examples 24-27, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein slice compatibility information indicates that the first network slice and the second network slice are incompatible for concurrently active PDU (Protocol Data Unit) sessions.

[0145] Example 29 includes the subject matter of any variation of Example 28, wherein, when the UE has an active PDU session on a first network slice, the operation further includes: 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.

[0146] Example 30 includes the subject matter of any variation of Examples 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.

[0147] Example 31 includes the subject matter of any variation of any of Examples 28-30, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: receiving a service request or a registration request, the request 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 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.

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

[0149] Example 33 includes the subject matter of any variation of any of Examples 24-32, wherein 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 be operated simultaneously 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.

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

[0151] Example 35 is an Access and Mobility Management Function (AMF) including a processor configured to perform operations including: receiving 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; 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 acceptance message for transmission, the registration acceptance message indicating that the UE is registered to the set of allowed network slices, wherein the registration acceptance 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.

[0152] Example 36 includes the subject matter of any variation of Example 35, wherein the registration accept message indicates slice compatibility information for each of the network slices in the set of network slices for the UE, wherein the slice compatibility information for each network slice indicates whether the network slices of other configurations in the set of network slices are compatible with the network slice of that configuration for simultaneous operation by the UE.

[0153] Example 37 includes the subject matter of any variation of any of Examples 35-36, wherein, when the slice compatibility information of each allowed network slice in the group of allowed network slices indicates that another allowed network slice in the group 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 other allowed network slice are associated with the same Access and Mobility Management Function (AMF) or different AMFs.

[0154] Example 38 includes the subject matter of any variation of any of Examples 35-37, wherein the requested network slices include 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 allowed network slices include the first network slice but not the second network slice.

[0155] Example 39 includes the subject matter of any variation of any of Example 38, wherein a registration accept message indication timer is provided, and the UE may request registration to a second network slice after the timer expires.

[0156] Example 40 includes the subject matter of any variation of any of Examples 38-39, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: 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 state 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 acceptance message indicating that the UE is registered to the second network slice.

[0157] Example 41 includes the subject matter of any variation of any of Examples 35-40, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein slice compatibility information indicates that the first network slice and the second network slice are incompatible for concurrently active PDU (Protocol Data Unit) sessions.

[0158] Example 42 includes the subject matter of any variation of Example 41, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: 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 generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0159] Example 43 includes the subject matter of any variation of Examples 41-42, 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 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.

[0160] Example 44 includes the subject matter of any variation of Examples 41-43, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: receiving a service request or a registration request, the request 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 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.

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

[0162] Example 46 includes the subject matter of any variation of any of Examples 35-45, wherein 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 be operated simultaneously 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.

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

[0164] Example 48 includes an apparatus that includes means for performing any of the operations described in Examples 1-47.

[0165] Example 49 includes a machine-readable medium storing instructions for execution by a processor to perform any of the operations described in Examples 1-47.

[0166] Example 50 includes an apparatus comprising: a memory interface; and processing circuitry configured to perform any of the operations described in Examples 1-47.

[0167] Example 51 includes a user equipment (UE) configured to perform any of the operations described in Examples 1-23.

[0168] Example 52 includes an Access and Mobility Management Function (AMF) configured to perform any of the operations described in Examples 24-47.

[0169] The above description of exemplary aspects of the subject matter of this disclosure, including those described in the specification summary, is not intended to be exhaustive or to limit the disclosed aspects to their precise forms. While specific aspects and embodiments have been described herein for illustrative purposes, various modifications may be contemplated within the scope of such aspects and embodiments, as will be appreciated by those skilled in the art.

[0170] 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 substitute functions of the disclosed subject matter without departing from the described aspects. Therefore, the disclosed subject matter should not be limited to any single aspect described herein, but should be interpreted in accordance with the breadth and scope of the appended claims.

[0171] In particular, regarding the various functions performed by the aforementioned components or structures (components, devices, circuits, systems, etc.), unless otherwise stated, the terminology used to describe such components (including references to "component") is intended to correspond to any component or structure that performs the specified function of the said component (e.g., functionally equivalent), even if it is not structurally equivalent to the disclosed structure that performs the function in the exemplary embodiments shown herein. Furthermore, while certain features have been disclosed with respect to only one of the plurality of embodiments, it may be desirable and advantageous for any given or particular application to combine such features with one or more other features of other embodiments.

Claims

1. A user equipment (UE) device, the UE device including transceiver circuitry and a processor coupled to a memory, the processor being configured to perform operations including the following when executing instructions stored in the memory: An initial registration request message is transmitted via the transceiver circuit, the initial registration request message including an indication that the UE has the ability to support simultaneous slice usage constraints; Receive a first registration acceptance message, the first registration acceptance message indicating slice compatibility information for each of the network slices in a set of configured network slices for the UE, wherein the slice compatibility information for each configured network slice indicates whether the network slices of other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous registration; An additional registration request message is transmitted via the transceiver circuitry, 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 network slices configured in the set, and wherein the set of requested network slices is compatible for simultaneous registration according to the slice compatibility information. as well as Receive an additional registration acceptance message, which indicates that the UE is registered to the network slice requested by the group.

2. The UE device according to claim 1, wherein the operation further includes: The network slice requested by the group is selected based on the slice compatibility information of each network slice in the network slices configured for the group, such that each requested network slice in the group is compatible with the other requested network slices in the group for simultaneous registration.

3. The UE device according to any one of claims 1-2, wherein the network slice requested by the group 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 concurrently active PDU protocol data unit sessions.

4. The UE device according to claim 3, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: Transmit a PDU session release request associated with the active PDU session on the first network slice via the transceiver circuit; Transmit a PDU session establishment request associated with the second network slice via the transceiver circuit; and Receive PDU session establishment acceptance associated with the second network slice.

5. The UE device according to claim 3, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: Transmit a PDU session establishment request associated with the second network slice via the transceiver circuitry, wherein the PDU session establishment request includes a priority indication identifier; Receive a PDU session release command associated with the first network slice; and Receive PDU session establishment acceptance associated with the second network slice.

6. The UE device according to claim 3, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: The transceiver circuit transmits either 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 the implicit release of the active PDU session on the first network slice. Transmit a PDU session establishment request associated with the second network slice via the transceiver circuit; and Receive PDU session establishment acceptance associated with the second network slice.

7. The UE device according to claim 3, wherein, When the UE has an active PDU session on the first network slice, the operation also includes activating the second network slice via a non-3GPP access technology.

8. The UE device according to any one of claims 1-2, wherein the group-requested network slice comprises 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: Transmit a PDU session establishment request associated with the second network slice via the transceiver circuit; Receive PDU session establishment acceptance associated with the second network slice; and Simultaneously maintain the active PDU session on the first network slice and the active PDU session on the second network slice.

9. The UE device according to claim 8, wherein the operation further comprises: When the UE does not have active user plane resources on the first network slice, it transmits either a service request or a registration request via the transceiver circuit, the request including an uplink data state information element (IE) to trigger the establishment of user plane resources associated with the active PDU session on the second network slice.

10. A user equipment (UE) device, the UE device including transceiver circuitry and a processor coupled to a memory, the processor being configured to perform operations including the following when executing instructions stored in the memory: The transceiver circuit transmits a registration request message, which requests 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 A registration acceptance message is received, 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 network slices requested in the set, and wherein the registration acceptance 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 allowed network slices in the set of allowed network slices are compatible with the allowed network slice for simultaneous registration.

11. The UE device of claim 10, wherein the registration acceptance message indicates slice compatibility information for each configured network slice in the group-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-configured network slices are compatible with the configured network slice for simultaneous registration.

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

13. The UE device according to any one of claims 10-12, wherein the group-requested network slice 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 registration, and wherein the group-allowed network slice includes the first network slice but does not include the second network slice.

14. The UE device of claim 13, wherein the registration accept message indicates a timer, and wherein the UE may request registration to the second network slice after the timer expires.

15. The UE device according to claim 13, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: A second registration request message is transmitted via the transceiver circuit. This second registration request message requests registration on the second network slice and implicitly releases the active PDU session on the first network slice. Receive a second registration acceptance message, which indicates that the UE is registered to the second network slice.

16. The UE device according to any one of claims 10-12, wherein the group 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 concurrently active PDU protocol data unit sessions.

17. The UE device according to claim 16, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: Transmit a PDU session release request associated with the active PDU session on the first network slice via the transceiver circuit; Transmit a PDU session establishment request associated with the second network slice via the transceiver circuit; and Receive PDU session establishment acceptance associated with the second network slice.

18. The UE device according to claim 16, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: Transmit a PDU session establishment request associated with the second network slice via the transceiver circuitry, wherein the PDU session establishment request includes a priority indication identifier; Receive a PDU session release command associated with the first network slice; and Receive PDU session establishment acceptance associated with the second network slice.

19. The UE device according to claim 16, wherein, When the UE has an active PDU session on the first network slice, the operation further includes: The transceiver circuit transmits either 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 the implicit release of the active PDU session on the first network slice. Transmit a PDU session establishment request associated with the second network slice via the transceiver circuit; and Receive PDU session establishment acceptance associated with the second network slice.

20. The UE device according to claim 16, wherein, When the UE has an active PDU session on the first network slice, the operation also includes activating the second network slice via a non-3GPP access technology.

21. The UE device according to any one of claims 10-12, wherein the network slices allowed by the group include 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: Transmit a PDU session establishment request associated with the second network slice via the transceiver circuit; Receive PDU session establishment acceptance associated with the second network slice; and Simultaneously maintain the active PDU session on the first network slice and the active PDU session on the second network slice.

22. The UE device of claim 21, wherein the operation further comprises: When the UE does not have active user plane resources on the first network slice, it transmits either a service request or a registration request via the transceiver circuit, the request including an uplink data state information element (IE) to trigger the establishment of user plane resources associated with the active PDU session on the second network slice.

23. A method to be executed by a user equipment (UE), comprising: Transmit 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; Receive a first registration acceptance message, the first registration acceptance message indicating slice compatibility information for each of the network slices in a set of configured network slices for the UE, wherein the slice compatibility information for each configured network slice indicates whether the network slices of other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous registration; An additional registration request message is transmitted to request registration on a set of requested network slices, wherein the set of requested network slices is a subset of the network slices configured in the set, and wherein the set of requested network slices is compatible for simultaneous registration according to the slice compatibility information. as well as Receive an additional registration acceptance message, which indicates that the UE is registered to the network slice requested by the group.

24. The method of claim 23, further comprising: The network slice requested by the group is selected based on the slice compatibility information of each network slice in the network slices configured for the group, such that each requested network slice in the group is compatible with the other requested network slices in the group for simultaneous registration.

25. The method according to any one of claims 23-24, wherein the network slice requested by the group 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 concurrently active PDU protocol data unit sessions.

26. The method of claim 25, wherein, When the UE has an active PDU session on the first network slice, the method further includes: Issue a PDU session release request associated with the active PDU session on the first network slice; Send a PDU session establishment request associated with the second network slice; and Receive PDU session establishment acceptance associated with the second network slice.

27. The method according to claim 25, wherein, When the UE has an active PDU session on the first network slice, the method further includes: A PDU session establishment request associated with the second network slice is transmitted, wherein the PDU session establishment request includes a priority indication identifier; Receive a PDU session release command associated with the first network slice; and Receive PDU session establishment acceptance associated with the second network slice.

28. The method according to claim 25, wherein, When the UE has an active PDU session on the first network slice, the method further includes activating the second network slice via a non-3GPP access technology.

29. The method according to any one of claims 23-24, wherein the requested network slice comprises 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 method further includes: Send a PDU session establishment request associated with the second network slice; Receive PDU session establishment acceptance associated with the second network slice; and Simultaneously maintain the active PDU session on the first network slice and the active PDU session on the second network slice.

30. The method of claim 28, further comprising: When the UE does not have active user plane resources on the first network slice, it transmits either a service request or a registration request, the request including an uplink data state information element (IE) to trigger the establishment of user plane resources associated with the active PDU session on the second network slice.

Images