Techniques for supporting network slice groups

Abstract

Techniques for supporting a network slice group, such as a network slice simultaneous registration group (NSRRG), in a 5G telecommunications network are disclosed. The disclosed techniques enable robust support for network slice groups that can improve accessibility and efficiency of network slices, reduce incorrect configuration, and provide an extended capability compared to conventional approaches. These techniques may involve one or more of utilizing a communication mode (e.g., an evolved packet core) to enable support for a network slice group over another communication mode (e.g., 5G); managing network slice group information in response to the subscription change; connecting to a network slice in a different group when connected to a network slice in a first group via a plurality of access types (e.g., 3GPP and non-3GPP); managing pending network slices and requested network slices; and synchronizing the user equipment and network registration status for different accesses.

Description

Technical Field

[0001] The present disclosure relates generally to wireless technologies, and more particularly to supporting network slice groups. Background Art

[0002] In telecommunications, 5G is the fifth generation technology standard for broadband cellular networks. Like its predecessor, 5G networks are cellular networks in which the service area is divided into small geographical areas called cells. Mobile devices moving from one cell to another are seamlessly and automatically handed over. The 3rd Generation Partnership Project (3GPP) is an industry consortium that sets standards for 5G. The packet protocols for mobility management (establishing connections between stations and moving between base stations) and session management (connecting to networks and network slices) in 5G are defined in TS24.501. The air interface or access mode is the communication link between two stations in mobile or wireless communication. 5G New Radio (NR) is a standard radio access technology (RAT) developed by 3GPP as the air interface for 5G networks. 5G NR deployments can be configured to utilize aspects of both 5GC and / or 4G LTE EPC networks.

[0003] In addition to increased speed and bandwidth, 5G offers new capabilities compared to 4G, such as network slicing. Network slicing is a network architecture that enables the reuse of virtualized and independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end network customized to meet the diverse requirements of specific applications. Network slicing plays a central role in supporting 5G mobile networks, which are designed to efficiently accommodate a large number of services with very different service level requirements. Summary of the Invention

[0004] Processes, machines, and articles of manufacture are described for supporting network slice groups. It should be understood that the embodiments can be combined in any number of ways without departing from the scope of the present disclosure.

[0005] An embodiment may include receiving an information element via a first communication mode, the information element indicating that a network slice is capable of being deployed on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice; updating a configured network slice list to include the network slice identifier; and registering based on the network slice identifier to utilize the network slice on the second communication mode.

[0006] An embodiment may include receiving an information element at a user equipment (UE) device via a first communication mode, the information element indicating that a network slice can be used for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice and group information corresponding to a network slice group including the network slice; updating a configured network slice list to include the network slice identifier and the group information; and registering based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

[0007] An embodiment may include: receiving a new configured network slice list at a user equipment (UE) device during a UE configuration update process; failing to receive an information element (IE) having new group information associated with the configured network slice list during the UE configuration update process; and deleting old group information in response to receiving the new configured network slice list and failing to receive new group information associated with the configured network slice list during the UE configuration update process.

[0008] An embodiment may include: registering to a first network slice via a first access type, wherein the first network slice is included in a first network slice group; registering to a second network slice via a second access type, wherein the second network slice is included in the first network slice group; determining to register to a third network slice, wherein the third network slice is included in the second network slice group; and generating a registration request for the third network slice, wherein the registration request indicates that the registration request is intentional.

[0009] An implementation may include: determining that registration for a network slice in a pending network slice list is no longer required; initiating a mobility registration process with an access and mobility management function (AMF); and communicating an indication to the AMF during the mobility registration process that registration with the network slice is no longer required.

[0010] An implementation scheme may include: when a user equipment (UE) device is out of coverage of a first access type and a second access type, performing local deregistration on the first access type at the UE device; when the UE device returns to coverage of the first access type or the second access type, initiating a registration process with an access and mobility management function (AMF); and communicating the UE's registration status regarding the first access type or the second access type to the AMF during the registration process.

[0011] Other processes, machines, and articles of manufacture are also described herein, which may be combined in any number of ways without departing from the scope of the present disclosure, such as with the embodiments of the summary. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The present invention is illustrated by way of example and is not limited to the figures of the accompanying drawings in which like reference numerals indicate like elements. To easily identify the discussion of any particular element or action, one or more of the most significant digits in a reference numeral refers to the figure number that first introduces the element.

[0013] Figure 1 An exemplary wireless communication system in accordance with some embodiments is illustrated.

[0014] Figure 2 A base station (BS) in communication with a user equipment (UE) device is illustrated according to some embodiments.

[0015] Figure 3 An exemplary block diagram of a UE according to some embodiments is illustrated.

[0016] Figure 4 An exemplary block diagram of a BS according to some embodiments is illustrated.

[0017] Figure 5 An exemplary block diagram of cellular communication circuitry according to some embodiments is illustrated.

[0018] Figure 6A and Figure 6B Various aspects of network slicing according to some embodiments are illustrated.

[0019] Figure 7 An exemplary block diagram of a network slice list according to some embodiments is illustrated.

[0020] Figure 8 An exemplary operating environment according to some embodiments is illustrated.

[0021] Figure 9 An exemplary block diagram of network messaging is illustrated in accordance with some embodiments.

[0022] Figure 10 An exemplary process diagram for slice group updates according to some embodiments is illustrated.

[0023] Figure 11A and Figure 11B Illustrated is a logic flow of exemplary techniques for supporting network slice groups according to some embodiments.

[0024] Figure 12 Illustrated is a logic flow of exemplary techniques for supporting network slice groups according to some embodiments.

[0025] Figure 13 Illustrated is a logic flow of exemplary techniques for supporting network slice groups according to some embodiments.

[0026] Figure 14 Illustrated is a logic flow of exemplary techniques for supporting network slice groups according to some embodiments.

[0027] Figure 15 Illustrated is a logic flow of exemplary techniques for supporting network slice groups according to some embodiments. DETAILED DESCRIPTION

[0028] Techniques for supporting network slice groups are described. In the following description, numerous specific details are set forth to provide a thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention can be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail to avoid obscuring the understanding of this description.

[0029] Reference in this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present invention. The appearance of the phrase "in one embodiment" in various places in this specification is not necessarily to the same embodiment.

[0030] In the following description and claims, the terms "coupled" and "connected," and their derivatives, may be used. It should be understood that these terms are not intended to be synonymous with each other. "Coupled" is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, cooperate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled to each other.

[0031] The processes depicted in the following figures are performed by processing logic components that include hardware (e.g., circuitry, dedicated logic components, etc.), software (such as software running on a general-purpose computer system or a dedicated machine), or a combination of both. Although the processes are described below as operating in certain sequential order, it should be understood that some of the operations described may be performed in a different order. Furthermore, some operations may be performed in parallel rather than sequentially.

[0032] The terms "server," "client," and "device" are intended to refer generally to data processing systems and not specifically to specific form factors of a server, client, and / or device.

[0033] Generally speaking, the present disclosure describes techniques for supporting network slice groups, such as Network Slice Simultaneous Registration Groups (NSRRGs), in 5G telecommunication networks. The subject matter described herein provides numerous technical advantages. For example, the computer-based techniques of the present disclosure improve the functionality of telecommunication systems compared to conventional approaches because the techniques enable robust support for network slice groups that can improve the accessibility and efficiency of network slices, reduce incorrect configurations, and provide expanded capabilities compared to conventional approaches. Thus, the embodiments disclosed herein may be used to improve the functionality of computers and / or improve the technical fields of telecommunications and / or network slicing.

[0034] In several embodiments, the techniques relate to utilizing one communication mode (e.g., Evolved Packet Core (EPC)) to enable support for network slice groups on another communication mode (e.g., 5G). In various embodiments, the techniques relate to managing network slice group information in response to subscription changes. In many embodiments, the techniques relate to connecting to network slices in a different group when connected to a network slice in a first group via multiple access types (e.g., 3GPP and non-3GPP). In one or more embodiments, the techniques relate to managing pending network slices and requested network slices. In some embodiments, the techniques relate to synchronizing user equipment and network registration states for different accesses. It should be understood that various aspects of telecommunication networks, capabilities, protocols, and procedures related to the techniques described herein and the terminology referenced herein may be found in 3GPP Technical Specifications (TSs), such as TS 24.501, TS 24.301, and TS 24.008.

[0035] Figure 1 A simplified exemplary wireless communication system according to some embodiments is illustrated. Note that Figure 1 The system is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0036] As shown, the example wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B, 106N, etc. via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE) or a UE device. Therefore, user device 106 is referred to as a UE or a UE device.

[0037] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with UEs 106A through 106N.

[0038] The communication area (or coverage area) of a base station may be referred to as a "cell." The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB." Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB."

[0039] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. Specifically, cellular base station 102A may provide UE 106 with various telecommunications capabilities, such as voice, SMS, and / or data services.

[0040] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore provide a network of cells that can provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0041] Thus, although base station 102A may function as Figure 1 106A-N, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be capable of facilitating communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularity of service area size. For example, in Figure 1 The base stations 102A-B illustrated in FIG may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0042] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or "gNB." In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0043] It is noted that the UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). If desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0044] Figure 2 Illustrated in accordance with some embodiments is a user equipment 106 (e.g., one of devices 106A through 106N) in communication with a base station 102. The UE 106 may be a device with cellular communication capabilities, such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0045] The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.

[0046] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, 5G NR, CDMA2000 (1xRTT, 1xEV-DO, HRPD, eHRPD), or LTE using a single shared radio and / or GSM or LTE using a single shared radio. The shared radio may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Generally speaking, the radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive chains and transmit chains using the aforementioned hardware. For example, UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication technologies (such as those discussed above). In various embodiments, the receive and / or transmit chain may include a cascade of electronic components and subunits (e.g., amplifiers, filters, mixers, attenuators, detectors, etc.) for receiving and / or transmitting signals (such as radio frequency signals).

[0047] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0048] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is illustrated. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (such as a laptop computer, a notebook or a portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components can be implemented as a system on a chip (SOC), which can include parts for various purposes. Alternatively, the group of components 300 can be implemented as a separate component or group of components for various purposes. The group of components 300 can be coupled to various other circuits of the communication device 106 (e.g., communicatively; directly or indirectly).

[0049] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, a camera, a keyboard; output devices such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0050] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336, as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338, as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input, multiple-output (MIMO) configuration.

[0051] In some embodiments, as further described below, the cellular communication circuitry 330 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuitry 330 can include a single transmit chain that can switch between radios dedicated to specific RATs. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with both the dedicated receive chain and the shared transmit chain.

[0052] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of a variety of elements, such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0053] The communication device 106 may also include one or more smart cards 345 , such as one or more UICCs (Universal Integrated Circuit Cards) 345 , having SIM (Subscriber Identity Module) functionality.

[0054] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 (the MMU may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as the display circuit 304, the short-range wireless communication circuit 229, the cellular communication circuit 330, the connector I / F 320, and / or the display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0055] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 can be configured to send a request to attach or register to a first network node operating according to a first RAT (e.g., 5G NR, 4G LTE, Bluetooth, Wi-Fi, etc.) and send an indication that the wireless device is capable of maintaining substantially concurrent connections with the first network node and a second network node operating according to a second RAT (e.g., 5G NR, 4G LTE, Bluetooth, Wi-Fi, etc.). The wireless device can also be configured to send a request to attach or register to the second network node. The request can include an indication that the wireless device is capable of maintaining substantially concurrent connections with the first and second network nodes. In addition, the wireless device can be configured to receive an indication that dual connectivity has been established with the first network node and the second network node.

[0056] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for supporting network slice groups. The processor 302 of the communication device 106 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or additionally), the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein.

[0057] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 302.

[0058] Furthermore, as described herein, both the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuitry 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuitry 329. Thus, the cellular communication circuitry 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuitry 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuitry 330. Similarly, the short-range wireless communication circuitry 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuitry 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuitry 329.

[0059] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is illustrated. Note that Figure 4 The base station 102 is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 that may be configured to receive addresses from the processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or to other circuits or devices.

[0060] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the telephone network as described above. Figure 1 and Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0061] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0062] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or a 5G CN core (5G CN) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, UEs capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0063] Base station 102 may include at least one antenna 434, and may include multiple antennas. At least one antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio 430. Antenna 434 communicates with radio 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0064] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some instances, the base station 102 may include multiple radio components that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, the base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multimode radio component capable of performing communications according to any one of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0065] As further described later herein, BS102 may include hardware and software components for implementing or supporting the specific implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS102 may be configured to implement or support part or all of the features described herein.

[0066] Furthermore, as described herein, processor 404 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0067] Furthermore, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0068] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is illustrated. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of possible cellular communication circuitry. Depending on the embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0069] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335a-335b and 336 as shown. In some embodiments, cellular communication circuitry 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, the cellular communication circuitry 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0070] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0071] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processors 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a DL front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0072] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. Additionally, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0073] As described herein, the modem 510 may include hardware and software components for implementing the above-described features for supporting network slice groups and various other techniques described herein. The processor 512 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or additionally), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement some or all of the feature parts described herein.

[0074] Additionally, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0075] As described herein, the modem 520 may include hardware and software components for implementing the above-described features for supporting network slice groups and various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 522 may be configured to implement some or all of the features described herein. Alternatively (or additionally), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement some or all of the features described herein.

[0076] Furthermore, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0077] Figure 6A and Figure 6B Various aspects of network slicing according to one or more embodiments are illustrated. More specifically, Figure 6A illustrates a network 604 having a plurality of network slices 602a, 602b, 602c, 602d, 602e (collectively referred to as network slices 602); and Figure 6B A plurality of slice groups 606a, 606b, 606c (collectively referred to as slice groups 606) are illustrated. In the illustrated embodiment, slice group 606a includes network slices 602a, 602b, 602c, slice group 606b includes network slices 602a, 602d, and slice group 606c includes network slices 602a, 602b, 602e. Various embodiments described herein may relate to supporting network slicing and network slice groups for use by UEs. The embodiments are not limited in this context.

[0078] A network, such as a telecommunications network (i.e., network 604), may overlay multiple virtual networks (i.e., network slices 602) on a set of shared network and computing resources. Each network slice in network slices 602 may include different characteristics, such as logical topology, security rules, and / or performance characteristics. Typically, different slices are created for different purposes, such as ensuring quality of service (QoS) or isolating traffic for specific users or device classes. For example, network slice 602a may be configured for voice and video, network slice 602b may be configured for the Internet of Things (IoT), network slice 602c may be configured for autonomous vehicles, network slice 602d may be used for factory automation, and network slice 602e may be used for physical infrastructure.

[0079] The network slices utilized by 5G include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). In various embodiments, eMBB can provide mobile data access to dense user sets, highly mobile users, and widely dispersed users. In some embodiments, mMTC can serve a large number of devices in a small area, which are expected to generate small amounts of data (e.g., tens of bytes per second) and can tolerate high latency (e.g., 10 seconds). In many embodiments, URRLC can deliver secure communications with small latency (e.g., <1 millisecond) and high reliability and low or even zero packet loss. In many embodiments, each network slice in the network slice 602 may refer to or include single network slice selection assistance information (S-NSSAI).

[0080] refer to Figure 6B , typically, a UE can use multiple different network slices simultaneously. In various embodiments, slice group 606 defines which network slices can be used by (or provided to) the UE simultaneously. For example, in the illustrated embodiment, the UE can simultaneously utilize network slices 602a, 602b, 602c from slice group 606a, network slices 602a, 602d from slice group 606b, or network slices 602a, 602b, 602e. However, in the illustrated embodiment, the UE cannot simultaneously utilize network slices 602d, 602e or network slices 602c, 602d. It should be understood that any number / combination of network slices and / or network slice groups that the network infrastructure can support can be utilized without departing from the scope of the present disclosure. In many embodiments, each slice group in slice group 606 may refer to or include a network slice simultaneous registration group (NSSRG). The UE may indicate its support for NSSRG in a 5G Mobility Management (5GMM) capability information element (IE).

[0081] Figure 7A set of network slice lists 702 according to one or more embodiments is illustrated. In many embodiments, these slice lists may be used during communication between the UE and the network. In the illustrated embodiment, the network slice list 702 includes a requested network slice list 704, a pending network slice list 706, an allowed network slice list 708, a rejected network slice list 710, and a configured network slice list 712. The requested network slice list 704 may include a set of network slices requested by the UE to be used in the registration request. The pending network slice list 706 may include a set of network slices that have been requested by the UE but cannot be used by the UE because the network's authentication of these slices is pending. The allowed network slice list 708 may include a set of network slices that the network allows the UE to use. In many embodiments, the allowed network slice list 708 only includes network slices from a public slice group. The rejected network slice list 710 may include a set of network slices that are rejected by the network (e.g., due to insufficient resources). The configured network slice list 712 may include a set of network slices to which the UE subscribes. In many embodiments, the configured network slice list 712 is provided by the UE's public land mobile network (PLMN) or home PLMN (HPLMN). One or more network slice lists in the network slice list 702 may include slice group information corresponding to one or more network slices in the included network slices.

[0082] In various embodiments, the requested network slice list 704 may refer to or include a requested NSSAI. In various such embodiments, the requested NSSAI may identify one or more S-NSSAIs and be included by the UE as part of a registration request message communicated to the network regarding the one or more S-NSSAIs.

[0083] In some embodiments, the pending network slice list 706 may refer to or include pending NSSAIs. In some such embodiments, the pending NSSAIs may identify one or more S-NSSAIs that were included in the requested NSSAI network message but have not yet been indicated by the network as allowed or denied and instead have been included in the pending NSSAI list.

[0084] In many embodiments, the allowed network slice list 708 may refer to or include allowed NSSAIs. In many such embodiments, the allowed NSSAIs may identify one or more S-NSSAIs that are included in the requested NSSAI network message and allowed in the registration accept message received by the UE from the network. The allowed NSSAIs may include only S-NSSAIs that share a common group (e.g., NSSRG) and can work together at the same time.

[0085] In several embodiments, the rejected network slice list 710 may refer to or include rejected NSSAIs. In several such embodiments, the rejected NSSAIs may identify one or more S-NSSAIs that were included in the requested NSSAI network message and rejected in the REGISTRATION REJECT message received by the UE from the network.

[0086] In various embodiments, the configured network slice list 712 may refer to or include a configured NSSAI. In various such embodiments, the configured NSSAI may be provided by the HPLMN or the visitor PLMN and stored in the UE. The configured NSSAI may be based on UE subscription and other operator deployment options. The configured NSSAI may include one or more NSSRGs associated with one or more of the included S-NSSAIs.

[0087] The NSSRG defines which S-NSSAIs can be provided to the UE simultaneously in the allowed NSSAIs. If there are no NSSRG restrictions in the UE subscription (e.g., availability at a specific location, congestion-based constraints on available slices, etc.), then all network slices (S-NSSAIs) in the UE subscription can be provided to the UE simultaneously in the allowed NSSAIs. However, if there are NSSRG restrictions in the UE subscription, then each S-NSSAI in the UE subscription has NSSRG information associated with it. In many embodiments, the UE can only use those slices that belong to the same NSSRG in the allowed NSSAIs with the application during PDN connection establishment.

[0088] In various embodiments, the network includes a mobility manager having a function (e.g., an access and mobility management function (AMF) and / or a network slice selection function (NSSF)) that evaluates the S-NSSAI in the received requested NSSAI as part of the registration request message based on the applicable NSSRG information and determines which SMFs can be provided to the UE to work together, thereby enabling the determination of allowed NSSAI and rejected NSSAI. In many embodiments, the allowed NSSAI only includes the S-NSSAI of a shared NSSRG (common slice group). When the AMF provides the configured NSSAI to the UE, it may include NSSRG information for each of the included network slices (i.e., the S-NSSAI in the configured NSSAI).

[0089] When a UE requests slices in the requested NSSAI, it includes only those slices that share a common NSSRG. If the NSSRG information changes in the UE subscription, the user data manager (e.g., Unified Data Management (UDM)) updates the mobility manager (e.g., AMF) with the new NSSRG information. The mobility manager then uses the UE configuration update procedure to update the configured NSSAI and associated NSSRG information in the UE.

[0090] Figure 8 An exemplary operating environment 800 is illustrated in accordance with one or more embodiments. Operating environment 800 includes UE 806, network access 810, network mobility managers 802a, 802b (collectively referred to as network mobility managers 802), network interworking interface 804, and interface 808. In various embodiments, components of operating environment 800 can interoperate to provide support for network slicing and network slice groups. In various such embodiments, support for network slicing and network slice groups can utilize one or more communication modes, access types, networks, etc. The embodiments are not limited in this context.

[0091] In many embodiments, the first communication mode may utilize a network mobility manager 802a, and the second communication mode may utilize a network mobility manager 802b. The first communication mode may refer to S1 mode access 812 using the Evolved Packet Core (EPC) in the Evolved Packet System (EPS), and the second communication mode may refer to N1 mode access 814 (or N2 mode access 818) using the 5G Core Network (CN). Thus, in many embodiments, the network mobility manager 802a may refer to or include a Mobility Management Entity (MME) and / or a Home Selection Service (HSS), and the network mobility manager 802b may refer to or include an AMF and / or a UDM. Additionally, the first communication mode may support 3GPP access 820a, and the second communication mode may support multiple access types, such as 3GPP access 820b and non-3GPP access 816. In the illustrated embodiment, the non-3GPP access 816 may utilize the interface 808 to obtain N2 mode access 818 to the 5G CN. For example, non-3GPP access 816 may refer to Wi-Fi and / or Bluetooth access.

[0092] In various embodiments, the network interworking interface 804 can facilitate the transfer of information (such as status, identifiers, etc.) between different communication modes. For example, as will be discussed in more detail below, a first communication mode can be used to communicate the availability of a network slice on a second communication mode. In some embodiments, network access 810 can represent various radio access technologies (RATs) used by the UE 806 to access the network of the network mobility manager 802a and / or the network mobility manager 802b. For example, the RATs can include one or more of Bluetooth, Wi-Fi, GSM, UMTS, LTE, and 5G NR.

[0093] Figure 9 A network message 902 is illustrated, including multiple information elements (IEs) 904a, 904b, 904c, and 904d (collectively, IEs 904). In various embodiments, various network messages 902, comprised of one or more information elements, may be used for communication between different components (e.g., a UE and a network mobility manager). For example, one or more network messages 902 in one or more formats may be exchanged between one or more UEs and one or more network components to perform one or more procedures, such as a UE configuration update procedure, a connection establishment procedure, a mobility registration procedure, and a registration procedure. In some embodiments, network messages may be simply referred to as messages. It should be understood that network messages 902 and IEs 904 may appear in various formats and carry various information. Generally, various standards and technical specifications define various network messages 902, 902, IEs 904, and procedures, such as 3GPP technical specifications (e.g., TS 24.501, TS 24.301, TS 24.008, etc.). The embodiments are not limited in this context.

[0094] Various embodiments described herein may enable support for network slice groups (e.g., NSSRGs) in S1 mode. In various such embodiments, support may improve transitions from N1 mode to S1 mode and back to N1 mode based on network slice availability. For example, when a UE using NR and connected to a 5G CN attempts to use a network slice, the network (e.g., network mobility manager 802b) may deny the UE's use. This may occur because the current network slice (e.g., S-NSSAI) may not be available for the current PLMN or Standalone Non-Public Network (SNPN) or in the current Tracking Area (TA) or Registration Area. In such cases, the network may return reason code #62 (No Network Slice Available). The S-NSSAI may then be added to a rejected NSSAI list (e.g., rejected network slice list 710).

[0095] In this case, the UE may disable N1 mode (e.g., N1 mode access 814) and attempt to use S1 mode (e.g., S1 mode access 812) by registering to the Evolved Packet System (EPS) using LTE. Subsequently, a network slice (e.g., S-NSSAI) may become available, such as due to less network congestion, the UE moving to a different tracking area, etc. In such a case, when a UE using LTE and connected to the EPS attempts to create a packet data network (PDN) connection, the UE may receive this notification from the network in an extended protocol configuration option (ePCO) IE of the availability of the previously rejected network slice. The UE may then remove the slice from the rejected NSSAI list and place it in the configured NSSAI according to 3GPP TS 24.501.

[0096] However, with the existing technology in S1 mode, the UE can only receive the network slice identifier (e.g., S-NSSAI value) as part of the Protocol Configuration Option (PCO) information element, but cannot receive the corresponding group information (e.g., NSSRG information). However, updating the configured NSSAI with the new S-NSSAI received in S1 mode may result in some of the configured NSSAIs having associated NSSRG values ​​while some do not, resulting in configured NSSAIs with inconsistent NSSRG configurations. However, according to TS 24.501, all S-NSSAIs in the configured NSSAI are expected to have associated NSSRG values.

[0097] Thus, embodiments of the present disclosure are directed to preventing inconsistent NSSRG configurations caused by switching from a first communication mode (e.g., N1 mode) to a second communication mode (e.g., S1 mode) and back to the first communication mode. In some embodiments, this includes when a network slice (S-NSSAI) is provided to a UE in S1 mode for inclusion in a configured network slice list (e.g., configured NSSAI), the network provides corresponding group information (e.g., NSSRG value) for the network slice added to the configured network slice list. In such embodiments, once this is done, the UE can activate the NR RAT, transition to N1 mode, and begin using the network slice with NR in the 5G CN.

[0098] As described in more detail below, a first solution to prevent inconsistent NSSRG configuration caused by switching from a first communication mode (e.g., N1 mode) to a second communication mode (e.g., S1 mode) and back to the first communication mode may include: (1) the network provides only S-NSSAI in S1 mode without any NSSRG information; (2) the UE stores the provided S-NSSAI in the configured NSSAI; (3) when transitioning to N1 mode and during a registration procedure, the UE includes the S-NSSAI provided in S1 mode from the configured NSSAI in the requested NSSAI and has the network mobility manager (e.g., AMF) determine the appropriate NSSRG value; and (4) the network mobility manager then updates the NSSRG value and provides the new configured NSSAI to the UE using a UE configuration update procedure by transmitting a CONFIGURATIONUPDATE COMMAND message.

[0099] In various embodiments, this solution may result in TS 24.501 with modifications, including the following regarding initial registration initiation. If an S-NSSAI is neither in the rejected NSSAI nor associated with an S-NSSAI in the rejected NSSAI, the subset of configured NSSAIs provided in the requested NSSAI shall include one or more S-NSSAIs in the configured NSSAIs that are applicable to the current PLMN or SNPN. In addition, if NSSRG information is available, the subset of configured NSSAIs provided in the requested NSSAI shall be associated with at least one common NSSRG value. The UE may also include in the requested NSSAI an S-NSSAI that was added to the configured NSSAI when the UE was in S1 mode and for which an associated NSSRG value is not yet available. If the UE is in the 5G MM-REGISTERED state on another access and already has an allowed NSSAI for the other access, all S-NSSAIs in the requested NSSAI for the current access shall share at least an NSSRG value that is common to all S-NSSAIs of the allowed NSSAIs for the other access. If the UE is simultaneously performing a registration procedure on another access type, the UE shall include an S-NSSAI that shares at least one common NSSRG value on all access types.

[0100] Additionally, in some embodiments, this solution may result in TS 24.501 with modifications, including the following regarding mobility and periodic registration update initiation. If an S-NSSAI is neither in the rejected NSSAI nor associated with an S-NSSAI in the rejected NSSAI, then the subset of configured NSSAIs provided in the requested NSSAI shall consist of one or more S-NSSAIs in the configured NSSAIs that are applicable to the PLMN or SNPN. Furthermore, if NSSRG information is available, then the subset of configured NSSAIs provided in the requested NSSAI shall be associated with at least one common NSSRG value. The UE may also include in the requested NSSAI any S-NSSAI that was added to the configured NSSAI when the UE was in S1 mode and for which an associated NSSRG value is not yet available. If the UE is in the 5GMM-REGISTERED state on another access and already has an allowed NSSAI for the other access, all S-NSSAIs in the requested NSSAI for the current access shall share at least an NSSRG value that is common to all S-NSSAIs of the allowed NSSAIs for the other access. If the UE is simultaneously performing a registration procedure on another access, the UE shall include S-NSSAIs that share at least one common NSSRG value across all access types.

[0101] As described in more detail below, a second solution to prevent inconsistent NSSRG configuration caused by switching from a first communication mode (e.g., N1 mode) to a second communication mode (e.g., S1 mode) and back to the first communication mode may include: (1) when an S-NSSAI is to be added to the configured NSSAI, providing support for NSSRG in the PCO or ePCO, so that the UE indicates support for NSSRG and the network provides NSSRG information; (2) the UE stores NSSRG information associated with the S-NSSAI provided in the PCO or ePCO; and (3) the UE shall store the received NSSRG information in the configured NSSAI together with any S-NSSAI value.

[0102] In many embodiments, support for network slice groups (e.g., NSSRGs) may be provided in the PCO IE. When a network slice (e.g., S-NSSAI) is to be added to a configured network slice list (e.g., configured NSSAI), the UE may indicate support for network slice groups and the network may provide group information (e.g., NSSRG information). In some embodiments, this may be implemented at least in part using an additional parameter list (octets w+1 to za) for the PCO as defined in TS 24.008 with modifications. The additional parameter list is included when special parameters and / or requests (e.g., associated with a PDP context) need to be transmitted between the UE and the network. These parameters and / or requests are not related to a specific configuration protocol and are therefore not encoded as a "packet" contained in the configuration protocol option list. The additional parameter list contains a list of special parameters, each in a separate container. The type of parameter carried in the container is identified by a specific container identifier. In this version of the protocol, the following container identifiers are specified.

[0103] UE to network direction: 004BH (NSSRG support indicator). Network to UE direction: 004BH (NSSRG information indicator). When the container identifier indicates the NSSRG support indicator, the container identifier content field is empty and the length of the container identifier content indicates a length equal to zero. If the container identifier content field is not empty, it should be ignored. This information indicates that the UE supports NSSRG as specified in 3GPP TS 24.501

[167] . When the container identifier indicates the NSSRG information indicator, the container identifier content field contains NSSRG information, followed by a PLMN ID associated with the NSSRG information. The NSSRG information is encoded as specified in subclause 9.11.3.82 of TS 24.501

[167] . In subclause 10.5.5.36, the PLMN ID is encoded as the value of the PLMN identity of the CN operator IE. The use of NSSRG and associated PLMNs is specified in TS 24.501

[167] .

[0104] In various embodiments, the UE shall store the NSSRG information associated with the S-NSSAI provided in the PCO or ePCO. Thus, this solution may result in TS 24.301 with modifications, including the following. Upon receiving the Activate Default EPS Bearer Context Request message, if the S-NSSAI, PLMN ID and NSSRG information associated with the S-NSSAI (if any) are provided in the PCO IE or ePCO IE, the UE may delete the stored S-NSSAI, PLMN ID and NSSRG information associated with the S-NSSAI (if any) and shall store the S-NSSAI, PLMN ID together with the NSSRG information associated with the S-NSSAI provided in the Activate Default EPS Bearer Context Request message, and the associated PLMN ID together with the corresponding PDU Session ID provided by the UE in the PDN Connection Request message. The use of the PDU Session ID and the corresponding S-NSSAI with the associated PLMN ID and NSSRG information is specified in 3GPP TS 24.501

[54] .

[0105] Additionally, the UE may store the received NSSRG information in the configured NSSAI along with any S-NSSAI values. Thus, this solution may result in TS 24.501 with modifications, including the following. If the UE receives an S-NSSAI associated with a PLMN ID and associated NSSRG information from the network during the PDN connection establishment procedure in EPS as specified in 3GPP TS 24.301 or via an ePDG as specified in 3GPP TS 24.302

[16] , the UE may store the received S-NSSAI in the configured NSSAI for the PLMN identified by the PLMN ID associated with the S-NSSAI (if not already included in the configured NSSAI along with the associated NSSRG information).

[0106] Figure 10A process diagram 1000 for slice group update according to some embodiments is illustrated. Process diagram 1000 may relate to preventing inconsistent NSSRG configurations caused by switching from a first communication mode (e.g., N1 mode) to a second communication mode (e.g., S1 mode) and back to the first communication mode. In various embodiments, some aspects of process diagram 1000 may specifically relate to the second solution described above. Process diagram 1000 includes exchanging network messages 1010, 1012, 1014, 1018, 1020, 1024, 1026, 1030, 1032, 1036, 1038 between various components 1002, 1004, 1006, 1008 to perform a plurality of processes 1016, 1022, 1028, 1034, 1040. The various components may include UE 1002, BS 1004, AMF 1006, and MME 1008. The plurality of processes may include a registration process 1016, a mobility registration process 1022, a connection establishment process 1028, a mobility registration process 1034, and a configuration update process 1040. The embodiments are not limited in this context.

[0107] The registration process 1016 may include an exchange of three messages 1010, 1012, and 1014. The first message may include a Registration Request message 1010 transmitted from the UE 1002 to the AMF 1006. The Registration Request message 1010 may include the UE's 5G MM capabilities. In response to the Registration Request message 1010, the AMF 1006 may send a Registration Accept message 1012 to the UE 1002. The Registration Accept message 1012 may include the configured NSSAI and group information (NSSRG). In various embodiments, the AMF 1006 may receive the network slice group configuration and NSSRG information from the subscription information (e.g., via UDM). In response to the Registration Accept message 1012, the UE 1002 may locally store the configured NSSAI and associated NSSRG information. Additionally, the UE 1002 may transmit a Registration Complete message 1014 to the AMF 1006. The registration process 1016 may result in the UE 1002 being registered on the NR RAT.

[0108] The mobility registration process 1022 may include an exchange of two messages 1018, 1020. The first message may include a mobility registration request message 1018 transmitted from the UE 1002 to the AMF 1006. The mobility registration request message 1018 may include the requested NSSAI. In response, and due to network slice unavailability (e.g., due to congestion), the AMF 1006 may transmit a registration reject message 1020 to the UE 1002 indicating the rejected NSSAI and cause (e.g., cause #62). Thereafter, the UE 1002 may disable the NR RAT and perform an LTE attach (switching from N1 mode to S1 mode).

[0109] After LTE attach, a connection establishment procedure 1028 may be performed. The connection establishment procedure 1028 may include an exchange of two messages 1024 and 1026. The first message may include a PDN connection request message 1024 transmitted from the UE 1002 to the MME 1008. In response, and because the previously rejected network slice has become available, the MME 1008 may transmit an activate EPS bearer context request message 1026 to the UE 1002, which indicates the S-NSSAI and NSSRG information via the PCO IE of the activate EPS bearer context request message 1026. In response to the activate EPS bearer context request message 1026, the UE 1002 may store the configured NSSAI in S1 mode / update the configured NSSAI with the S-NSSAI and NSSRG information. Thereafter, the UE 1002 may reactivate the NR RAT, perform 5GS registration, and transition back to N1 mode.

[0110] After transitioning back to N1 mode, a second mobility registration procedure 1034 may be performed. The mobility registration procedure 1034 may include an exchange of two messages 1030, 1032. The first message may include a mobility registration request message 1030 transmitted from the UE 1002 to the AMF 1006, including the requested NSSAI. The UE request may now be accepted because the network slice in the requested NSSAI is available. Therefore, in response to the mobility registration request message 1030, the AMF 1006 may transmit a mobility registration accept message 1032 to the UE 1002. The UE 1002 then receives the allowed NSSAI and may begin using the network slice in NR and performing data transmission.

[0111] Subsequently, a configuration update procedure 1040 may be performed to update the configured NSSAI on the UE 1002. The configuration update procedure 1040 may include an exchange of two messages 1036 and 1038. The first message may include a configuration update command message 1036 with the configured NSSAI and NSSRG information. The configuration update command message 1036 may be transmitted in response to the network updating the configured NSSAI and / or associated NSSRG information. In response to the configuration update command message 1036, the UE 1002 may locally store the updated configured NSSAI and associated NSSRG information in N1 mode and transmit a configuration update complete message 1038 back to the AMF 1006.

[0112] Figure 11A and Figure 11B1. Logic flows for supporting network slicing according to some embodiments are illustrated. More specifically, logic flows 1100a, 1100b may relate to preventing inconsistent NSSRG configurations caused by switching from a first communication mode (e.g., N1 mode) to a second communication mode (e.g., S1 mode) and back to the first communication mode. In various embodiments, some aspects of logic flow 1100a may specifically relate to the first solution described above, and some aspects of logic flow 1100b may specifically relate to the second solution described above.

[0113] refer to Figure 11A , logic flow 1100a may begin at block 1102a. Block 1102a may include receiving, at a user equipment (UE) device via a first communication mode, an information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice. For example, UE 1002 may receive an activate EPS bearer context request message 1026 from 1008 via S1 mode indicating that S-NSSAI is available on N1 mode.

[0114] Continuing to block 1104a, the configured network slice list may be updated to include network slice identifiers. For example, the UE 1002 may update the configured NSSAI to include available S-NSSAI.

[0115] Proceeding to block 1106a, the network slice on the second communication mode may be registered for use based on the network slice identifier. For example, the UE 1002 may transmit a mobility registration request message 1030 with the S-NSSAI included in the requested NSSAI. In many such embodiments, the AMF determines the appropriate NSSRG value and provides the UE with the newly configured NSSAI using the UE configuration update procedure 1040.

[0116] refer to Figure 11B , logic flow 1100b may begin at block 1102b. Block 1102b may include receiving, at a user equipment (UE) device via a first communication mode, an information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice and group information corresponding to a network slice group including the network slice. For example, UE 1002 may receive an activate EPS bearer context request message 1026 from 1008 via S1 mode indicating that an S-NSSAI is available on N1 mode along with corresponding NSSRG information.

[0117] Continuing to block 1104b, the configured network slice list may be updated to include the network slice identifier and group information. For example, the UE 1002 may update the configured NSSAI to include the available S-NSSAI along with the corresponding NSSRG information.

[0118] Proceeding to block 1106b, the network slice on the second communication mode may be registered for use based on the network slice identifier.For example, the UE 1002 may communicate a mobility registration request message 1030 with the S-NSSAI and NSSRG included in the requested NSSAI.

[0119] Figure 12 12. The embodiment of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention. The method of the present invention provides a method for slicing a network slice in accordance with the present invention.

[0120] Logic flow 1200 begins at block 1202. At block 1202, a new configured network slice list may be received at a UE device during a UE configuration update procedure. Proceeding to block 1204, an information element (IE) having new group information associated with the configured network slice list may not be received during the UE configuration update procedure. For example, a configuration update command message 1036 received by the UE 1002 of the configuration update procedure 1040 may not include new group information associated with the configured network slice list.

[0121] Continuing to block 1206, in response to receiving a new configured network slice list and failing to receive new group information associated with the configured network slice list during the UE configuration update procedure, the old group information may be deleted. For example, the UE 1002 may delete the old group information stored locally.

[0122] In various embodiments, Figure 12The described solution may result in TS 24.501 with modifications, including the following regarding generic UE configuration updates accepted by the UE. If the UE receives a new configured NSSAI in a Configuration Update Command message, the UE shall consider the new configured NSSAI for the registered PLMN or SNPN valid and the old configured NSSAI for the registered PLMN or SNPN invalid; otherwise, the UE shall consider the old configured NSSAI for the registered PLMN or SNPN valid. The UE shall store the new configured NSSAI as specified in subclause 4.6.2.2. In addition, if the Configuration Update Command message contains an NSSRG Information IE, the UE shall store the contents of the NSSRG Information IE as specified in subclause 4.6.2.2. If the UE receives a new configured NSSAI in a Configuration Update Command message and does not receive an NSSRG Information IE, the UE shall delete any stored NSSRG information as specified in subclause 4.6.2.2.

[0123] In many embodiments, this solution may result in TS 24.501 with modifications, including the following regarding initial registrations accepted by the network. If the Registration Accept message contains a Configured NSSAI IE with the new configured NSSAI for the current PLMN or SNPN, and optionally contains a mapped S-NSSAI to the configured NSSAI for the current PLMN or SNPN, the UE shall store the contents of the Configured NSSAI IE as specified in subclause 4.6.2.2. Additionally, if the Registration Accept message contains an NSSRG Information IE, the UE shall store the contents of the NSSRG Information IE as specified in subclause 4.6.2.2. If the UE receives a new configured NSSAI in the Registration Accept message and does not receive an NSSRG Information IE, the UE shall delete any stored NSSRG information as specified in subclause 4.6.2.2.

[0124] In several embodiments, this solution may result in TS 24.501 with modifications, including the following regarding network-accepted mobility and periodic registration update initiation. If the Registration Accept message contains a Configured NSSAI IE with the new Configured NSSAI for the current PLMN or SNPN, and optionally contains a mapped S-NSSAI to the Configured NSSAI for the current PLMN or SNPN, the UE shall store the contents of the Configured NSSAI IE as specified in subclause 4.6.2.2. Additionally, if the Registration Accept message contains an NSSRG Information IE, the UE shall store the contents of the NSSRG Information IE as specified in subclause 4.6.2.2. If the UE receives a new Configured NSSAI in the Registration Accept message and does not receive an NSSRG Information IE, the UE shall delete any stored NSSRG information as specified in subclause 4.6.2.2.

[0125] Figure 13 1 (Group A), S-NSSAI 3 (Group B), S-NSSAI 4 (Group B)}; (2) the UE is registered to S-NSSAI 1 via a 3GPP access and to S-NSSAI 2 via a non-3GPP access (both belonging to Group A); and (3) at a later point in time, the UE wants to access services of Group B. However, if the UE transmits a Registration Request with a requested NSSAI indicating S-NSSAI 3 to the 3GPP access, the AMF will reject it because on the other access, the UE already has an allowed S-NSSAI with Group A.

[0126] To avoid this problem using existing techniques, the UE must redundantly (and therefore inefficiently) perform an explicit deregistration on the other access and then attempt to connect to the preferred slice on the current access. This results in unnecessary delays and additional signaling. Again, when the service is completed, and if the UE wants to move back, the same sequence must be repeated. This is because the current AMF cannot determine whether the UE is requesting slices belonging to a new group that does not match the other access, or whether this is an intentional request from the UE. If the UE can indicate that this is an intentional request and that the group on the other access needs to be covered, the network can implicitly deregister the UE on the other access and also indicate this in the Registration Accept using existing mechanisms.

[0127] To overcome this limitation, embodiments of the present disclosure may utilize one of the following solutions. The first solution introduces a new IE in the registration request message that allows the slice configuration to be overridden. In some embodiments, the new IE may include parameters (e.g., bits) for 3GPP access and parameters (e.g., bits) for non-3GPP access. If the parameter is set to 1 for 3GPP access, the slice configuration on the 3GPP access is overridden when registering through a non-3GPP access slice. If the parameter is set to 1 for non-3GPP access, the slice configuration on the non-3GPP access is overridden when registering through a 3GPP access. Therefore, the IE may include a first part for overriding registration on a first access type (e.g., 3GPP) and a second part for overriding registration on a second access type (e.g., non-3GPP).

[0128] Another solution may include the following scenario. The UE has an allowed NSSAI as S-NSSAI1 on 3GPP and an allowed NSSAI as S-NSSAI2 on non-3GPP, both of which belong to group A. The UE now wants to access services of S-NSSAI3 belonging to group B via 3GPP access. Under the existing technology, if the UE initiates registration on S-NSSAI3 via 3GPP access, the UE is not allowed to initiate the registration, and even if the UE attempts to request S-NSSAI3, the network will not accept the registration.

[0129] There are several techniques that can be utilized to address this issue. In the first technique, a new IE can be utilized that explicitly indicates the group the UE wants to request to be removed from. The UE will include the S-NSSAI3 in the requested NSSAI in the registration request. Additionally, the UE should include a new IE that indicates the NSSRG ID of the S-NSSAI that the UE wants to remove from the existing allowed NSSAIs on both accesses. When the network receives this IE, the network should remove all S-NSSAIs associated with the included NSSRGID from the allowed NSSAIs. If there are no other S-NSSAIs associated with any other groups that are currently in the allowed NSSAIs, the network should consider the UE deregistered on both accesses and should process the received registration request as an initial registration. Alternatively, the network may choose to process the received registration request as a mobility registration and only consider the UE deregistered on the other access for the same scenario.

[0130] In the second technique, if the network receives a requested NSSAI with an S-NSSAI belonging to a group different from the group associated with the current allowed NSSAI, and if within the requested NSSAI, all S-NSSAIs belong to the same NSSRG, the network shall consider this to be an intentional request by the UE for a group change, rather than a misconfiguration case. The AMF shall process the new requested NSSAI and shall treat the existing allowed NSSAI as no longer part of the requested NSSAI, and therefore shall not infer a conflict in the NSSRG. Additionally, the AMF shall remove all S-NSSAIs from the allowed NSSAI on the other access and shall consider the UE to be deregistered.

[0131] In the third technique, for the scenario considered, the UE shall first initiate deregistration for the non-3GPP access on the 3GPP access, or perform deregistration for both accesses simultaneously. Subsequently, the UE shall initiate registration on the 3GPP access using the new requested NSSAI. When the UE is registered on only one access, if the new requested NSSAI has an S-NSSAI belonging to the same group but a different NSSRG than the existing allowed NSSAI, the AMF shall not infer an error but shall treat this as a use case where the UE wants to access an S-NSSAI belonging to a different group. In this case, the AMF shall locally release the PDU sessions belonging to the S-NSSAI present in the old allowed NSSAI, which has a different NSSRG group than the one the UE is requesting in the requested NSSAI.

[0132] Return Reference Figure 13 , logic flow 1300 begins at block 1302. At block 1302, a first network slice may be registered via a first access type, wherein the first network slice is included in a first network slice group. For example, network slice A included in group 1 may be registered via a 3GPP access type. Continuing at block 1304, a second network slice may be registered via a second access type, wherein the second network slice is included in the first network slice group. For example, network slice B included in group 1 may be registered via a non-3GPP access type.

[0133] Proceeding to block 1306, a determination may be made to register with a third network slice, wherein the third network slice is included in the second network slice group. For example, a determination may be made to register with network slice C in group 2. At block 1308, a registration request may be generated for the third network slice, the registration request indicating that the registration request is intentional. For example, a value of the Overlay Slice Configuration IE may be set to 1 to indicate that the registration request is intentional.

[0134] Figure 14A logic flow 1400 for supporting network slicing according to some embodiments is illustrated. More specifically, the logic flow 1400 may involve handling network slice group restrictions for pending network slices. This issue may arise in the following scenarios: (1) during authentication (NSSAA) of a slice, if authentication is pending, a specific slice (S-NSSAI) may be placed in a pending NSSAI list; (2) the NSSRG restriction applies to all S-NSSAIs included in a requested NSSAI; and (3) if the UE is still interested in the S-NSSAI of the pending NSSAI, the UE should treat the S-NSSAI in the pending NSSAI as the S-NSSAI requested by the UE, and therefore the UE considers the S-NSSAI in the pending NSSAI that the UE is still interested in in order to apply the NSSRG restriction. However, for the case when the UE is no longer interested in the S-NSSAI in the pending NSSAI, there is no mechanism to remove the S-NSSAI from the pending NSSAI.

[0135] Therefore, if the UE wants to discard the pending NSSAI, the network requires an explicit indication from the UE that the UE is no longer interested in the pending NSSAI. A number of techniques can be utilized to address this issue.

[0136] In one technique, if the UE has stored a pending NSSAI and the UE is no longer interested in the S-NSSAI of the pending NSSAI, the UE removes the S-NSSAI that it is no longer interested in from the pending NSSAI list. The UE initiates a mobility registration procedure by transmitting a Registration Request message containing a Discarded NSSAI information element set to the S-NSSAI of the pending NSSAI that the UE is no longer interested in. The S-NSSAI in the pending NSSAI and the requested NSSAI should be associated with at least one common NSSRG value. If the AMF receives the Discarded NSSAI in the Registration Request message, the AMF removes the S-NSSAI present in the Discarded NSSAI from the pending NSSAI list and aborts any ongoing NSSAA procedure corresponding to the Discarded NSSAI.

[0137] Alternatively, in the second technique, if the UE has stored the pending NSSAI and does not intend to register any S-NSSAI for the pending NSSAI, the UE may apply the NSSRG restriction (of the requested NSSAI) that excludes the S-NSSAI for the pending NSSAI. The AMF may assume that the UE intends to implicitly ignore the S-NSSAI included in the pending NSSAI.

[0138] In a third technique, parameters (e.g., bits) for 3GPP access and parameters (e.g., bits) for non-3GPP access may be introduced to the Cover Pending NSSAI IE. In this technique, the new IE indicates to the AMF which requested S-NSSAI(s) the UE wants to proceed with. Any S-NSSAI not included in the requested NSSAI is ignored, and the network immediately aborts any ongoing NSSAA procedure. If this parameter is set to 1 for 3GPP access, slice configurations not included in the requested NSSAI are ignored for both 3GPP access and non-3GPP access when registering over 3GPP access. The contention situation at both the UE and network sides is handled so that any received message related to the NSSAA procedure after the corresponding S-NSSAI is no longer of interest to the UE, and the receiving entity shall then discard the NSSAA related message.

[0139] Return Reference Figure 14 , logic flow 1400 begins at block 1402. At block 1402, it may be determined that registration for a network slice in the pending network slice list is no longer required. For example, it may be determined that registration for network slice A is no longer required, such as because access to network slice A is no longer required due to a change in circumstances (e.g., multimedia connectivity is no longer required due to an application being closed).

[0140] Proceeding to block 1404, a mobility registration procedure can be initiated with an access and mobility management function (AMF). For example, the mobility registration procedure 1022 can be initiated. Continuing to block 1406, during the mobility registration procedure, an indication that registration with the network slice is no longer required can be communicated to the AMF. For example, a bit can be set in an IE to indicate that registration with the network slice is no longer required.

[0141] Figure 15 Illustrated is a logic flow 1500 for supporting network slicing in accordance with some embodiments. More specifically, the logic flow 1500 may relate to a network rejection based on a loss of synchronization between the UE and the network for a network slice group. This problem may arise in a scenario where a UE is out of coverage of two accesses on the same PLMN and the UE must perform a local deregistration on one of these accesses. The UE then returns to coverage and initiates registration for a new group and receives a Registration Accept indicating that the UE is registered on both accesses. In the context of NSSRG, this may result in a Registration Reject because the network believes that the UE is mistakenly requesting a new group when it is already registered for another group via another access. Therefore, the UE must indicate to the network that it is no longer registered on the other access, such as using an IE. The embodiments are not limited to this context.

[0142] Logic flow 1500 begins at block 1502. At block 1502, when a user equipment (UE) device is out of coverage of a first access type and a second access type, a local deregistration from the first access type may be performed at the UE device. Continuing to block 1504, when the UE device returns to coverage of the first access type or the second access type, a registration procedure with an access and mobility management function (AMF) may be initiated. Continuing to block 1506, during the registration procedure, the UE's registration status for the first access type or the second access type may be communicated to the AMF, such as using an IE.

[0143] The part of the above content can be realized by utilizing a logic circuit such as a dedicated logic circuit or utilizing a microcontroller or other form of processing core for executing program code instructions.Thus, program code such as machine executable instructions can be utilized to execute the process taught by the above discussion, and the machine executable instructions make the machine execute these instructions to perform certain functions.In this context, "machine" can be a machine that converts an intermediate form (or "abstract") instruction into an instruction specific to a processor (for example, an abstract execution environment such as a "virtual machine" (for example, a Java virtual machine), an interpreter, a common language runtime, a high-level language virtual machine, etc.), and / or an electronic circuit that is arranged on a semiconductor chip (for example, a "logic circuit" realized using a transistor), and the electronic circuit is designed to execute instructions, and the processor is such as a general-purpose processor and / or a special-purpose processor.The process taught by the above discussion can also be executed by (as a substitute of a machine or in combination with a machine) an electronic circuit, and the electronic circuit is designed to execute a process (or a part thereof) without executing program code.

[0144] The present invention also relates to an apparatus for performing the operations described herein. The apparatus may be specially constructed for the required purpose, or may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored on a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, and magneto-optical disks, read-only memory (ROM), RAM, EPROM, EEPROM, magnetic or optical cards, or any type of medium suitable for storing electronic instructions, and each coupled to a computer system bus.

[0145] A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, machine-readable media include read-only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; and the like.

[0146] Articles of manufacture can be used to store program code. Articles of manufacture storing program code can be implemented as, but not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic, or other)), optical disks, CD-ROMs, DVD ROMs, EPROMs, EEPROMs, magnetic or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code can also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) via a data signal contained in a propagation medium (e.g., via a communication link (e.g., a network connection)).

[0147] Various example implementations are described herein.

[0148] Embodiment 1 is a computer-implemented method, comprising: receiving an information element via a first communication mode, the information element indicating that a network slice can be used for deployment on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice; updating a configured network slice list to include the network slice identifier; and registering based on the network slice identifier to utilize the network slice on the second communication mode.

[0149] Embodiment 2 is a computer-implemented method according to embodiment 1, which may optionally include: registering based on the network slice identifier to utilize the network slice on the second communication mode includes: providing a requested network slice list including the network slice identifier to an access and mobility management function (AMF); and receiving a new configured network slice list from the AMF, wherein the new configured network slice list includes the network slice identifier and group information corresponding to the network slice group including the network slice.

[0150] Embodiment 3 is a computer-implemented method according to embodiment 2, and the computer-implemented method may optionally include: the newly configured network slice list is received via the UE configuration update process.

[0151] Embodiment 4 is a computer-implemented method according to embodiment 3, and the computer-implemented method may optionally include: the new configured network slice list is received in a configuration update command message during the UE configuration update process.

[0152] Embodiment 5 is a computer-implemented method according to embodiment 2, and the computer-implemented method may optionally include: the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

[0153] Embodiment 6 is a computer-implemented method according to embodiment 5, and the computer-implemented method may optionally include: each network slice in the network slice group is simultaneously supported by the second communication mode.

[0154] Embodiment 7 is a computer-implemented method according to embodiment 6, which may optionally include: each network slice in the configured network slice list is included in the network slice group.

[0155] Embodiment 8 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: the first communication mode lacks support for 5G network slicing, and the second communication mode supports 5G network slicing.

[0156] Embodiment 9 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: the first communication mode utilizes an evolved packet core (EPC), and the second communication mode utilizes a 5G core network.

[0157] Embodiment 10 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI includes one or more S-NSSAIs and associated slice group information.

[0158] Embodiment 11 is a computer-implemented method according to embodiment 10, which may optionally include: updating the configured network slice list to include the network slice identifier, including: updating the configured NSSAI to include the S-NSSAI, wherein the NSSAI is updated to include the S-NSSAI without associated slice group information.

[0159] Embodiment 12 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: the information element includes the network slice identifier and group information corresponding to the network slice group including the network slice, and the computer-implemented method also includes: updating the configured network slice list to include the network slice identifier and the group information; and registering based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

[0160] Embodiment 13 is a computer-implemented method according to embodiment 12, which may optionally include: the network slice identifier and the network slice group are included in an extended protocol configuration option (ePCO) part of the information element.

[0161] Embodiment 14 is a computer-implemented method according to embodiment 12, and the computer-implemented method may optionally include: the configured network slice list includes configured slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

[0162] Embodiment 15 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: updating the configured network slice list to include the network slice identifier and the group information, including: updating the configured NSSAI to include the S-NSSAI and the value associated with the NSSRG.

[0163] Embodiment 16 is a computer-implemented method according to embodiment 1, which may optionally include receiving the information element during a packet data network (PDN) connection establishment procedure.

[0164] Embodiment 17 is a user equipment (UE), the UE comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 1 to 16.

[0165] Embodiment 18 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 1 to 16.

[0166] Embodiment 19 is a computer-implemented method, comprising: sending an information element to a user equipment (UE) via a first communication mode, the information element indicating that a network slice can be used for deployment on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice, wherein the information element causes the UE to update a configured network slice list to include the network slice identifier; receiving the configured network slice list including the network slice identifier from the UE; and registering the UE using the configured network slice list including the network slice identifier to utilize the network slice on the second communication mode.

[0167] Embodiment 20 is a computer-implemented method according to embodiment 19, which may optionally include: registering the UE using the configured network slice list including the network slice identifier to utilize the network slice on the second communication mode includes: relaying the requested network slice list including the network slice identifier received from the UE to an access and mobility management function (AMF); receiving a new configured network slice list from the AMF, wherein the new configured network slice list includes the network slice identifier and group information corresponding to the network slice group including the network slice; and sending the new configured network slice list to the UE.

[0168] Embodiment 21 is a computer-implemented method according to embodiment 20, and the computer-implemented method may optionally include: the new configured network slice list is received via a UE configuration update process.

[0169] Embodiment 22 is a computer-implemented method according to embodiment 21, and the computer-implemented method may optionally include: the new configured network slice list is received in a configuration update command message during the UE configuration update process.

[0170] Embodiment 23 is a computer-implemented method according to embodiment 20, and the computer-implemented method may optionally include: the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

[0171] Embodiment 24 is a computer-implemented method according to embodiment 23, and the computer-implemented method may optionally include: each network slice in the network slice group is simultaneously supported by the second communication mode.

[0172] Embodiment 25 is a computer-implemented method according to embodiment 24, which may optionally include: each network slice in the configured network slice list is included in the network slice group.

[0173] Embodiment 26 is a computer-implemented method according to embodiment 19, which may optionally include: the first communication mode lacks support for 5G network slicing, and the second communication mode supports 5G network slicing.

[0174] Embodiment 27 is a computer-implemented method according to embodiment 19, which may optionally include: the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

[0175] Embodiment 28 is a computer-implemented method according to embodiment 19, and the computer-implemented method may optionally include: the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI includes one or more S-NSSAIs and associated slice group information.

[0176] Embodiment 29 is a computer-implemented method according to embodiment 28, which may optionally include: causing the UE to update the configured network slice list to include the network slice identifier, including: causing the UE to update the configured NSSAI to include the S-NSSAI without associated slice group information.

[0177] Embodiment 30 is a computer-implemented method according to embodiment 19, which may optionally include: the information element includes the network slice identifier and group information corresponding to the network slice group including the network slice, and the one or more processors are further configured to perform operations including: causing the UE to update the configured network slice list to include the network slice identifier and the group information; and registering the UE using the configured network slice list including the network slice identifier and the group information to utilize the network slice on the second communication mode.

[0178] Embodiment 31 is a computer-implemented method according to embodiment 30, which may optionally include: the network slice identifier and the network slice group are included in an extended protocol configuration option (ePCO) part of the information element.

[0179] Embodiment 32 is a computer-implemented method according to embodiment 30, and the computer-implemented method may optionally include: the configured network slice list includes configured slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

[0180] Embodiment 33 is a computer-implemented method according to embodiment 32, and the computer-implemented method may optionally include: causing the UE to update the configured network slice list to include the network slice identifier and the group information, including: updating the configured NSSAI to include the S-NSSAI and the value associated with the NSSRG.

[0181] Embodiment 34 is a computer-implemented method according to embodiment 19, which may optionally include: the information element is sent to the UE during a packet data network (PDN) connection establishment procedure.

[0182] Embodiment 35 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 19 to 34.

[0183] Embodiment 36 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 19 to 34.

[0184] Embodiment 37 is a computer-implemented method, comprising: receiving an information element at a user equipment (UE) device via a first communication mode, the information element indicating that a network slice can be used for deployment on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice and group information corresponding to a network slice group including the network slice; updating a configured network slice list to include the network slice identifier and the group information; and registering based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

[0185] Embodiment 38 is a computer-implemented method according to embodiment 37, and the computer-implemented method may optionally include: each network slice in the network slice group is simultaneously supported by the second communication mode.

[0186] Embodiment 39 is a computer-implemented method according to embodiment 38, which may optionally include: each network slice in the configured network slice list is included in the network slice group.

[0187] Embodiment 40 is a computer-implemented method according to embodiment 37, which may optionally include: the first communication mode lacks support for 5G network slicing, and the second communication mode supports 5G network slicing.

[0188] Embodiment 41 is a computer-implemented method according to embodiment 37, which may optionally include: the first communication mode utilizes an evolved packet core and the second communication mode utilizes a 5G core network.

[0189] Embodiment 42 is a computer-implemented method according to embodiment 37, and the computer-implemented method may optionally include: the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI).

[0190] Embodiment 43 is a computer-implemented method according to embodiment 42, and the computer-implemented method may optionally include: updating the configured network slice list to include the network slice identifier and the group information, including: updating the configured NSSAI to include the S-NSSAI.

[0191] Embodiment 44 is a computer-implemented method according to embodiment 42, and the computer-implemented method may optionally include: the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

[0192] Embodiment 45 is a computer-implemented method according to embodiment 44, which may optionally include: updating the configured network slice list to include the network slice identifier and the group information, including: updating the configured NSSAI to include the S-NSSAI and the value associated with the NSSRG.

[0193] Embodiment 46 is a computer-implemented method according to embodiment 37, which may optionally include: the information element is received during a packet data network (PDN) connection establishment procedure.

[0194] Embodiment 47 is a computer-implemented method according to embodiment 37, which may optionally include: the network slice identifier and the network slice group are included in an extended protocol configuration option (ePCO) part of the information element.

[0195] Embodiment 48 is a user equipment (UE), the UE comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 37 to 47.

[0196] Embodiment 49 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 37 to 47.

[0197] Embodiment 50 is a computer-implemented method, comprising: sending an information element to a user equipment (UE) device via a first communication mode, the information element indicating that a network slice can be used for deployment on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice and group information corresponding to a network slice group including the network slice, and the information element causes the UE to update a configured network slice list to include the network slice identifier and the group information; receiving the configured network slice list including the network slice identifier from the UE; and registering the UE using the configured network slice list including the network slice identifier and the group information to utilize the network slice on the second communication mode.

[0198] Embodiment 51 is a computer-implemented method according to embodiment 50, and the computer-implemented method may optionally include: each network slice in the network slice group is simultaneously supported by the second communication mode.

[0199] Embodiment 52 is a computer-implemented method according to embodiment 51, and the computer-implemented method may optionally include: each network slice in the configured network slice list is included in the network slice group.

[0200] Embodiment 53 is a computer-implemented method according to embodiment 50, which may optionally include: the first communication mode lacks support for 5G network slicing, and the second communication mode supports 5G network slicing.

[0201] Embodiment 54 is a computer-implemented method according to embodiment 50, which may optionally include: the first communication mode utilizes an evolved packet core and the second communication mode utilizes a 5G core network.

[0202] Embodiment 55 is a computer-implemented method according to embodiment 50, and the computer-implemented method may optionally include: the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI).

[0203] Embodiment 56 is a computer-implemented method according to embodiment 55, and the computer-implemented method may optionally include: causing the UE to update the configured network slice list to include the network slice identifier and the group information, including: updating the configured NSSAI to include the S-NSSAI.

[0204] Embodiment 57 is a computer-implemented method according to embodiment 55, and the computer-implemented method may optionally include: the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

[0205] Embodiment 58 is a computer-implemented method according to embodiment 57, which may optionally include: causing the UE to update the configured network slice list to include the network slice identifier and the group information, including: updating the configured NSSAI to include the S-NSSAI and the value associated with the NSSRG.

[0206] Embodiment 59 is a computer-implemented method according to embodiment 50, which may optionally include: the information element is received during a packet data network (PDN) connection establishment procedure.

[0207] Embodiment 60 is a computer-implemented method according to embodiment 50, which may optionally include: the network slice identifier and the network slice group are included in an extended protocol configuration option (ePCO) part of the information element.

[0208] Embodiment 61 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 50 to 60.

[0209] Embodiment 62 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 50 to 60.

[0210] Embodiment 63 is a computer-implemented method comprising: receiving, at a user equipment (UE) device, a new configured network slice list during a UE configuration update process; failing to receive an information element (IE) having new group information associated with the configured network slice list during the UE configuration update process; and deleting old group information in response to receiving the new configured network slice list and failing to receive the new group information associated with the configured network slice list during the UE configuration update process.

[0211] Embodiment 64 is a computer-implemented method according to embodiment 63, and the computer-implemented method may optionally include: the new configured network slice list is received in a configuration update command message.

[0212] Embodiment 65 is a computer-implemented method according to embodiment 63, and the computer-implemented method may optionally include: the newly configured network slice list is received in a registration acceptance message.

[0213] Embodiment 66 is a computer-implemented method according to embodiment 63, and the computer-implemented method may optionally include: failure to receive new group information associated with the configured network slice list during the UE configuration update process includes: failure to receive network slice simultaneous registration group (NSSRG) information IE.

[0214] Embodiment 67 is a computer-implemented method according to embodiment 63, and the computer-implemented method may optionally include: deleting old group information includes: deleting network slice simultaneous registration group (NSSRG) information stored on the UE.

[0215] Embodiment 68 is a user equipment (UE), the UE comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 63 to 67.

[0216] Embodiment 69 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a computer-implemented method according to any one of embodiments 63 to 67.

[0217] Embodiment 70 is a computer-implemented method comprising: sending a new configured network slice list to a user equipment (UE) during a UE configuration update process; failing to send an information element (IE) having new group information associated with the configured network slice list to the UE during the UE configuration update process; and causing the UE to delete old group information in response to sending the new configured network slice list to the UE and failing to send the new group information associated with the configured network slice list to the UE during the UE configuration update process.

[0218] Example 71 is a computer-implemented method according to Example 70, which may optionally include: the newly configured network slice list is sent in a configuration update command message.

[0219] Embodiment 72 is a computer-implemented method according to embodiment 70, and the computer-implemented method may optionally include: the newly configured network slice list is sent in a registration acceptance message.

[0220] Embodiment 73 is a computer-implemented method according to embodiment 70, and the computer-implemented method may optionally include: failing to send new group information associated with the configured network slice list to the UE during the UE configuration update process includes: failing to send the network slice simultaneous registration group (NSSRG) information IE to the UE.

[0221] Embodiment 74 is a computer-implemented method according to embodiment 70, and the computer-implemented method may optionally include: causing the UE to delete old group information, including: causing the UE to delete the network slice simultaneous registration group (NSSRG) information stored on the UE.

[0222] Embodiment 75 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 70 to 74.

[0223] Embodiment 76 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a computer-implemented method according to any one of embodiments 70 to 74.

[0224] Embodiment 77 is a computer-implemented method comprising: registering to a first network slice via a first access type, wherein the first network slice is included in a first network slice group; registering to a second network slice via a second access type, wherein the second network slice is included in the first network slice group; determining to register to a third network slice, wherein the third network slice is included in the second network slice group; and generating a registration request for the third network slice, wherein the registration request indicates that the registration request is intentional.

[0225] Embodiment 78 is a computer-implemented method according to embodiment 77, which may optionally include: the first access type includes 3GPP access, and the second access type includes non-3GPP access.

[0226] Embodiment 79 is a computer-implemented method according to embodiment 77, which may optionally include: the registration request indicating that the registration request is intentional via an overlay slice configuration information element (IE).

[0227] Embodiment 80 is a computer-implemented method according to embodiment 79, and the computer-implemented method may optionally include: the coverage slice configuration IE includes a part for covering registration on the first access type and a part for covering registration on the second access type.

[0228] Embodiment 81 is a computer-implemented method according to embodiment 79, which may optionally include: the registration request for the third network slice is for the first access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the second access type for network slice groups other than the second network slice group including the third network slice.

[0229] Embodiment 82 is a computer-implemented method according to embodiment 79, which may optionally include: the registration request for the third network slice is for the second access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the first access type for network slice groups other than the second network slice group including the third network slice.

[0230] Embodiment 83 is a user equipment (UE), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 77 to 82.

[0231] Embodiment 84 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a computer-implemented method according to any one of embodiments 77 to 82.

[0232] Embodiment 85 is a computer-implemented method comprising one or more processors configured to perform operations comprising: registering a user equipment (UE) to a first network slice via a first access type, wherein the first network slice is included in a first network slice group; registering the UE to a second network slice via a second access type, wherein the second network slice is included in the first network slice group; and in response to the UE determining to register to a third network slice included in the second network slice group, receiving a registration request for the third network slice from the UE, wherein the registration request indicates that the registration request is intentional.

[0233] Embodiment 86 is a computer-implemented method according to embodiment 85, which may optionally include: the first access type includes 3GPP access, and the second access type includes non-3GPP access.

[0234] Embodiment 87 is a computer-implemented method according to embodiment 85, which may optionally include: the registration request indicating that the registration request is intentional via an overlay slice configuration information element (IE).

[0235] Embodiment 88 is a computer-implemented method according to embodiment 87, and the computer-implemented method may optionally include: the coverage slice configuration IE includes a part for covering registration on the first access type and a part for covering registration on the second access type.

[0236] Embodiment 89 is a computer-implemented method according to embodiment 87, which may optionally include: the registration request for the third network slice is for the first access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the second access type for network slice groups other than the second network slice group including the third network slice.

[0237] Embodiment 90 is a computer-implemented method according to embodiment 87, which may optionally include: the registration request for the third network slice is for the second access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the first access type for network slice groups other than the second network slice group including the third network slice.

[0238] Embodiment 91 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 85 to 90.

[0239] Embodiment 92 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a computer-implemented method according to any one of embodiments 85 to 90.

[0240] Embodiment 93 is a computer-implemented method comprising: determining that registration for a network slice in a pending network slice list is no longer required; initiating a mobility registration process with an access and mobility management function (AMF); and communicating an indication to the AMF during the mobility registration process that registration with the network slice is no longer required.

[0241] Embodiment 94 is a computer-implemented method according to embodiment 93, which may optionally include: the indication that registration with the network slice is no longer required is included in the registration request message.

[0242] Embodiment 95 is a computer-implemented method according to embodiment 94, which may optionally include: the indication that registration with the network slice is no longer required is included in a discard information element (IE).

[0243] Embodiment 96 is a computer-implemented method according to embodiment 95, which may optionally include: the pending network slice list includes pending network slice selection information (NSSAI), and the network slice corresponds to a single NSSAI (S-NSSAI) in the pending NSSAI.

[0244] Embodiment 97 is a computer-implemented method according to embodiment 69, which may optionally include: discarding IE includes discarding NSSAI IE.

[0245] Embodiment 98 is a user equipment (UE), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 93 to 97.

[0246] Embodiment 99 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a computer-implemented method according to any one of embodiments 93 to 97.

[0247] Embodiment 100 is a computer-implemented method comprising: in response to a user equipment (UE) determining that registration for a network slice in a pending network slice list is no longer required, relaying the initiation of a mobility registration process from the UE to an access and mobility management function (AMF); and relaying an indication from the UE to the AMF during the mobility registration process that registration with the network slice is no longer required, so that the AMF removes the network slice from the pending network slice list.

[0248] Embodiment 101 is a computer-implemented method according to embodiment 100, which may optionally include: the indication that registration with the network slice is no longer required is included in the registration request message.

[0249] Embodiment 102 is a computer-implemented method according to embodiment 101, which may optionally include: the indication that registration with the network slice is no longer required is included in a discard information element (IE).

[0250] Embodiment 103 is a computer-implemented method according to embodiment 102, and the computer-implemented method may optionally include: the pending network slice list includes pending network slice selection information (NSSAI), and the network slice corresponds to a single NSSAI (S-NSSAI) in the pending NSSAI.

[0251] Embodiment 104 is a computer-implemented method according to embodiment 103, which may optionally include: discarding the IE includes discarding the NSSAI IE.

[0252] Embodiment 105 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 100 to 104.

[0253] Embodiment 106 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 100 to 104.

[0254] Embodiment 107 is a computer-implemented method comprising: when a user equipment (UE) is out of coverage of a first access type and a second access type, performing a local deregistration at the UE on the first access type; when the UE returns to coverage of the first access type or the second access type, initiating a registration process with an access and mobility management function (AMF); and communicating the registration status of the UE regarding the first access type or the second access type to the AMF during the registration process.

[0255] Embodiment 108 is a computer-implemented method according to embodiment 107, which may optionally include: the communication of the UE's registration status regarding the first access type or the second access type includes: indicating that the UE has deregistered from the first access type.

[0256] Embodiment 109 is a computer-implemented method according to embodiment 107, which may optionally include: communicating the registration status of the UE regarding the first access type or the second access type includes: indicating that the UE is only registered to the second access type.

[0257] Embodiment 110 is a user equipment (UE) comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 107 to 109.

[0258] Embodiment 111 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 107 to 109.

[0259] Embodiment 112 is a computer-implemented method comprising: in response to a user equipment (UE) locally deregistering on a first access type and a second access type when the UE is out of coverage of the first access type and the second access type, relaying the initiation of a registration process from the UE to an access and mobility management function (AMF) when the UE returns to coverage of the first access type or the second access type; and relaying the UE's registration status with respect to the first access type or the second access type from the UE to the AMF during the registration process.

[0260] Embodiment 113 is a computer-implemented method according to embodiment 112, which may optionally include: relaying the UE's registration status regarding the first access type or the second access type includes: indicating that the UE has deregistered from the first access type.

[0261] Example 114 is the computer-implemented method of Example 112, which may optionally include relaying the UE's registration status with respect to the first access type or the second access type including indicating that the UE is registered only to the second access type.

[0262] Embodiment 115 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 112 to 114.

[0263] Embodiment 116 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 112 to 114.

[0264] The foregoing detailed description has been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the tools used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm, as used here and generally, refers to a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulation of physical quantities. Typically, but not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient, primarily for common sense, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0265] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise specifically stated, it will be apparent from the foregoing discussion that discussions throughout this specification using terms such as "select," "determine," "receive," "form," "group," "aggregate," "generate," "remove," and the like will be understood to refer to actions and processes on a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the computer system's registers and memories and converts it into other data similarly represented as physical quantities in the computer system's memories or registers or other such information storage, transmission, or display devices.

[0266] The process presented herein and display are not inherently relevant to any particular computer or other device. According to the teaching content of this paper, various general-purpose systems can be used together with program, or can prove that it is convenient to construct the more special-purpose device for carrying out described operation. According to the description below, the required structure for various these systems will be apparent. In addition, the present invention is not described with reference to any specific programming language. Should be appreciated that multiple programming languages ​​can be used for realizing the teaching content of the present invention as described herein.

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

[0268] The foregoing discussion describes only some exemplary embodiments of the present invention. Those skilled in the art will readily recognize from these discussions, drawings and claims that various modifications can be made without departing from the spirit and scope of the present invention.

Claims

1. A user equipment (UE), the UE comprising one or more processors configured to perform operations including: receiving, via the first communication mode, an information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice; Updating the configured network slice list to include the network slice identifier; as well as Registering is performed based on the network slice identifier to utilize the network slice on the second communication mode.

2. The UE of claim 1 , wherein registering based on the network slice identifier to utilize the network slice on the second communication mode comprises: providing an access and mobility management function (AMF) with the requested network slice list including the network slice identifier; as well as A newly configured network slice list is received from the AMF, wherein the newly configured network slice list includes the network slice identifier and group information corresponding to the network slice group including the network slice.

3. The UE according to claim 2, wherein the new configured network slice list is received via a UE configuration update process.

4. The UE of claim 3, wherein the new configured network slice list is received in a configuration update command message during the UE configuration update procedure.

5. The UE of claim 2, wherein the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

6. The UE according to claim 5, wherein each network slice in the network slice group is simultaneously supported by the second communication mode.

7. The UE according to claim 6, wherein each network slice in the configured network slice list is included in the network slice group.

8. The UE of claim 1 , wherein the first communication mode lacks support for 5G network slicing, and the second communication mode supports 5G network slicing.

9. The UE of claim 1 , wherein the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

10. The UE according to claim 1, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI includes one or more S-NSSAIs and associated slice group information.

11. The UE of claim 10, wherein updating the configured network slice list to include the network slice identifier comprises: The configured NSSAI is updated to include the S-NSSAI, wherein the NSSAI is updated to include the S-NSSAI without associated slice group information.

12. The UE of claim 1 , wherein the information element comprises the network slice identifier and group information corresponding to a network slice group including the network slice, and the one or more processors are further configured to perform operations comprising: updating the configured network slice list to include the network slice identifier and the group information; and Registering is performed based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

13. The UE of claim 12, wherein the network slice identifier and the network slice group are included in an extended protocol configuration option (ePCO) portion of the information element.

14. The UE of claim 12, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

15. The UE according to claim 14, wherein updating the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

16. The UE of claim 1, wherein the information element is received during a packet data network (PDN) connection establishment procedure.

17. A computer-implemented method, comprising: receiving, via the first communication mode, an information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice; Updating the configured network slice list to include the network slice identifier; as well as Registering is performed based on the network slice identifier to utilize the network slice on the second communication mode.

18. The computer-implemented method of claim 17, wherein registering to utilize the network slice on the second communication mode based on the network slice identifier comprises: providing an access and mobility management function (AMF) with the requested network slice list including the network slice identifier; as well as A newly configured network slice list is received from the AMF, wherein the newly configured network slice list includes the network slice identifier and group information corresponding to the network slice group including the network slice.

19. A computer-implemented method according to claim 18, wherein the new configured network slice list is received via a UE configuration update process.

20. The computer-implemented method of claim 19, wherein the new configured network slice list is received in a configuration update command message during the UE configuration update procedure.

21. The computer-implemented method of claim 18, wherein the network slice group comprises a Network Slice Simultaneous Registration Group (NSSRG), and the group information comprises a value associated with the NSSRG.

22. The computer-implemented method of claim 21 , wherein each network slice in the group of network slices is simultaneously supported by the second communication mode.

23. A computer-implemented method according to claim 22, wherein each network slice in the configured network slice list is included in the network slice group.

24. The computer-implemented method of claim 17, wherein the first communication mode lacks support for 5G network slicing and the second communication mode supports 5G network slicing.

25. The computer-implemented method of claim 17, wherein the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

26. A computer-implemented method according to claim 17, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI includes one or more S-NSSAIs and associated slice group information.

27. The computer-implemented method of claim 26, wherein updating the configured network slice list to include the network slice identifier comprises: The configured NSSAI is updated to include the S-NSSAI, wherein the NSSAI is updated to include the S-NSSAI without associated slice group information.

28. The computer-implemented method of claim 17, wherein the information element comprises the network slice identifier and group information corresponding to a network slice group including the network slice, and the computer-implemented method further comprises: Updating the configured network slice list to include the network slice identifier and the group information; as well as Registering is performed based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

29. The computer-implemented method of claim 28, wherein the network slice identifier and the network slice group are included in an extended protocol configuration options (ePCO) portion of the information element.

30. The computer-implemented method of claim 28, wherein the configured network slice list comprises configured network slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

31. The computer-implemented method of claim 30, wherein updating the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

32. The computer-implemented method of claim 17, wherein the information element is received during a packet data network (PDN) connection establishment procedure.

33. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a method comprising: receiving, via the first communication mode, an information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice; Updating the configured network slice list to include the network slice identifier; as well as Registering is performed based on the network slice identifier to utilize the network slice on the second communication mode.

34. The non-transitory machine-readable medium of claim 33, wherein registering to utilize the network slice on the second communication mode based on the network slice identifier comprises: providing an access and mobility management function (AMF) with the requested network slice list including the network slice identifier; as well as A newly configured network slice list is received from the AMF, wherein the newly configured network slice list includes the network slice identifier and group information corresponding to the network slice group including the network slice.

35. The non-transitory machine-readable medium of claim 34, wherein the new configured network slice list is received via a UE configuration update process.

36. The non-transitory machine-readable medium of claim 35, wherein the new configured network slice list is received in a configuration update command message during the UE configuration update procedure.

37. The non-transitory machine-readable medium of claim 34, wherein the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

38. The non-transitory machine-readable medium of claim 37, wherein each network slice in the group of network slices is simultaneously supported by the second communication mode.

39. The non-transitory machine-readable medium of claim 38, wherein each network slice in the configured network slice list is included in the network slice group.

40. The non-transitory machine-readable medium of claim 33, wherein the first communication mode lacks support for 5G network slicing and the second communication mode supports 5G network slicing.

41. The non-transitory machine-readable medium of claim 33, wherein the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

42. The non-transitory machine-readable medium of claim 33, wherein the configured network slice list comprises configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI comprises one or more S-NSSAIs and associated slice group information.

43. The non-transitory machine-readable medium of claim 42, wherein updating the configured network slice list to include the network slice identifier comprises: The configured NSSAI is updated to include the S-NSSAI, wherein the NSSAI is updated to include the S-NSSAI without associated slice group information.

44. The non-transitory machine-readable medium of claim 33, wherein the information element comprises the network slice identifier and group information corresponding to a network slice group including the network slice, and the non-transitory machine-readable medium has instructions for causing one or more processing units to perform the method, the method further comprising: Updating the configured network slice list to include the network slice identifier and the group information; as well as Registering is performed based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

45. The non-transitory machine-readable medium of claim 44, wherein the network slice identifier and the network slice group are included in an extended protocol configuration options (ePCO) portion of the information element.

46. ​​The non-transitory machine-readable medium of claim 44, wherein the configured network slice list comprises configured network slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

47. The non-transitory machine-readable medium of claim 46, wherein updating the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

48. The non-transitory machine-readable medium of claim 33, wherein the information element is received during a packet data network (PDN) connection establishment procedure.

49. A base station (BS), the BS comprising one or more processors configured to perform operations comprising: sending an information element to a user equipment (UE) via a first communication mode, the information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice, wherein the information element causes the UE to update a configured network slice list to include the network slice identifier; receiving, from the UE, the configured network slice list including the network slice identifier; as well as Registering the UE using the configured network slice list including the network slice identifier to utilize the network slice on the second communication mode.

50. The BS of claim 49, wherein registering the UE to utilize the network slice on the second communication mode using the configured network slice list including the network slice identifier comprises: relaying the requested network slice list including the network slice identifier received from the UE to an access and mobility management function (AMF); receiving a newly configured network slice list from the AMF, wherein the newly configured network slice list includes the network slice identifier and group information corresponding to a network slice group including the network slice; as well as Send the newly configured network slice list to the UE.

51. The BS of claim 50, wherein the new configured network slice list is received via a UE configuration update process.

52. The BS of claim 51 , wherein the new configured network slice list is received in a configuration update command message during the UE configuration update procedure.

53. The BS of claim 50, wherein the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

54. The BS of claim 53, wherein each network slice in the network slice group is simultaneously supported by the second communication mode.

55. The BS of claim 54, wherein each network slice in the configured network slice list is included in the network slice group.

56. The BS of claim 49, wherein the first communication mode lacks support for 5G network slicing, and the second communication mode supports 5G network slicing.

57. The BS of claim 49, wherein the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

58. The BS of claim 49, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI includes one or more S-NSSAIs and associated slice group information.

59. The BS of claim 58, wherein causing the UE to update the configured network slice list to include the network slice identifier comprises: causing the UE to update the configured NSSAI to include the S-NSSAI without associated slice group information.

60. The BS of claim 49, wherein the information element comprises the network slice identifier and group information corresponding to a network slice group including the network slice, and the one or more processors are further configured to perform operations comprising: causing the UE to update the configured network slice list to include the network slice identifier and the group information; and Register the UE using the configured network slice list including the network slice identifier and the group information to utilize the network slice on the second communication mode.

61. The BS of claim 60, wherein the network slice identifier and the network slice group are included in an extended protocol configuration option (ePCO) portion of the information element.

62. The BS of claim 60, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

63. The BS of claim 62, wherein causing the UE to update the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

64. The BS of claim 49, wherein the information element is sent to the UE during a packet data network (PDN) connection establishment procedure.

65. A computer-implemented method, comprising: sending an information element to a user equipment (UE) via a first communication mode, the information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice, wherein the information element causes the UE to update a configured network slice list to include the network slice identifier; receiving, from the UE, the configured network slice list including the network slice identifier; as well as Registering the UE using the configured network slice list including the network slice identifier to utilize the network slice on the second communication mode.

66. The computer-implemented method of claim 65, wherein registering the UE to utilize the network slice on the second communication mode using the configured network slice list including the network slice identifier comprises: relaying the requested network slice list including the network slice identifier received from the UE to an access and mobility management function (AMF); receiving a newly configured network slice list from the AMF, wherein the newly configured network slice list includes the network slice identifier and group information corresponding to a network slice group including the network slice; as well as Send the newly configured network slice list to the UE.

67. A computer-implemented method according to claim 66, wherein the new configured network slice list is received via a UE configuration update process.

68. The BS of claim 67, wherein the new configured network slice list is received in a configuration update command message during the UE configuration update procedure.

69. A computer-implemented method according to claim 66, wherein the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

70. The computer-implemented method of claim 69, wherein each network slice in the group of network slices is simultaneously supported by the second communication mode.

71. A computer-implemented method according to claim 70, wherein each network slice in the configured network slice list is included in the network slice group.

72. The computer-implemented method of claim 65, wherein the first communication mode lacks support for 5G network slicing and the second communication mode supports 5G network slicing.

73. The computer-implemented method of claim 65, wherein the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

74. A computer-implemented method according to claim 65, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI includes one or more S-NSSAIs and associated slice group information.

75. The computer-implemented method of claim 74, wherein causing the UE to update the configured network slice list to include the network slice identifier comprises: causing the UE to update the configured NSSAI to include the S-NSSAI without associated slice group information.

76. The computer-implemented method of claim 65, wherein the information element comprises the network slice identifier and group information corresponding to a network slice group including the network slice, and the computer-implemented method further comprises: causing the UE to update the configured network slice list to include the network slice identifier and the group information; as well as Register the UE using the configured network slice list including the network slice identifier and the group information to utilize the network slice on the second communication mode.

77. A computer-implemented method according to claim 76, wherein the network slice identifier and the network slice group are included in an extended protocol configuration options (ePCO) portion of the information element.

78. A computer-implemented method according to claim 76, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

79. The computer-implemented method of claim 78, wherein causing the UE to update the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

80. The computer-implemented method of claim 65, wherein the information element is sent to the UE during a packet data network (PDN) connection establishment procedure.

81. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a method comprising: sending an information element to a user equipment (UE) via a first communication mode, the information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice, wherein the information element causes the UE to update a configured network slice list to include the network slice identifier; receiving, from the UE, the configured network slice list including the network slice identifier; as well as Registering the UE using the configured network slice list including the network slice identifier to utilize the network slice on the second communication mode.

82. The non-transitory machine-readable medium of claim 81 , wherein registering the UE to utilize the network slice on the second communication mode using the configured network slice list including the network slice identifier comprises: relaying the requested network slice list including the network slice identifier received from the UE to an access and mobility management function (AMF); receiving a newly configured network slice list from the AMF, wherein the newly configured network slice list includes the network slice identifier and group information corresponding to a network slice group including the network slice; as well as Send the newly configured network slice list to the UE.

83. A non-transitory machine-readable medium according to claim 82, wherein the new configured network slice list is received via a UE configuration update process.

84. A non-transitory machine-readable medium according to claim 8.3, wherein the new configured network slice list is received in a configuration update command message during the UE configuration update process.

85. The non-transitory machine-readable medium of claim 82, wherein the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

86. The non-transitory machine-readable medium of claim 85, wherein each network slice in the group of network slices is simultaneously supported by the second communication mode.

87. A non-transitory machine-readable medium according to claim 86, wherein each network slice in the configured network slice list is included in the network slice group.

88. The non-transitory machine-readable medium of claim 81 , wherein the first communication mode lacks support for 5G network slicing and the second communication mode supports 5G network slicing.

89. The non-transitory machine-readable medium of claim 81 , wherein the first communication mode utilizes an evolved packet core (EPC) and the second communication mode utilizes a 5G core network.

90. The non-transitory machine-readable medium of claim 81 , wherein the configured network slice list comprises configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI), and the configured NSSAI comprises one or more S-NSSAIs and associated slice group information.

91. The non-transitory machine-readable medium of claim 90, wherein causing the UE to update the configured network slice list to include the network slice identifier comprises: causing the UE to update the configured NSSAI to include the S-NSSAI without associated slice group information.

92. The non-transitory machine-readable medium of claim 81 , wherein the information element comprises the network slice identifier and group information corresponding to a network slice group including the network slice, and the non-transitory machine-readable medium has instructions for causing one or more processing units to perform the method, the method further comprising: causing the UE to update the configured network slice list to include the network slice identifier and the group information; as well as Register the UE using the configured network slice list including the network slice identifier and the group information to utilize the network slice on the second communication mode.

93. The non-transitory machine-readable medium of claim 92, wherein the network slice identifier and the network slice group are included in an extended protocol configuration options (ePCO) portion of the information element.

94. The non-transitory machine-readable medium of claim 92, wherein the configured network slice list comprises configured network slice selection assistance information (NSSAI), the network slice identifier is included in a single NSSAI (S-NSSAI), the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

95. The non-transitory machine-readable medium of claim 94, wherein causing the UE to update the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

96. The non-transitory machine-readable medium of claim 81, wherein the information element is sent to the UE during a packet data network (PDN) connection establishment procedure.

97. A computer-implemented method, the computer-implemented method comprising: receiving, at a user equipment (UE) device via a first communication mode, an information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice and group information corresponding to a network slice group including the network slice; Updating the configured network slice list to include the network slice identifier and the group information; as well as Registering is performed based on the network slice identifier and the group information to utilize the network slice on the second communication mode.

98. The computer-implemented method of claim 97, wherein each network slice in the group of network slices is simultaneously supported by the second communication mode.

99. A computer-implemented method according to claim 98, wherein each network slice in the configured network slice list is included in the network slice group.

100. The computer-implemented method of claim 97, wherein the first communication mode lacks support for 5G network slicing and the second communication mode supports 5G network slicing.

101. The computer-implemented method of claim 97, wherein the first communication mode utilizes an evolved packet core and the second communication mode utilizes a 5G core network.

102. A computer-implemented method according to claim 97, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI).

103. The computer-implemented method of claim 102, wherein updating the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI.

104. The computer-implemented method of claim 102, wherein the network slice group comprises a network slice simultaneous registration group (NSSRG), and the group information comprises a value associated with the NSSRG.

105. The computer-implemented method of claim 104, wherein updating the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

106. The computer-implemented method of claim 97, wherein the information element is received during a packet data network (PDN) connection establishment procedure.

107. The computer-implemented method of claim 97, wherein the network slice identifier and the network slice group are included in an extended protocol configuration options (ePCO) portion of the information element.

108. A user equipment (UE) comprising one or more processors configured to perform the computer-implemented method of any one of claims 97 to 107.

109. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 97 to 107.

110. A computer-implemented method, the computer-implemented method comprising: sending, at a user equipment (UE) device via a first communication mode, an information element to a user equipment (UE), the information element indicating that a network slice is available for provisioning on a second communication mode, wherein the information element includes a network slice identifier corresponding to the network slice and group information corresponding to a network slice group including the network slice, and the information element causes the UE to update a configured network slice list to include the network slice identifier and the group information; receiving, from the UE, the configured network slice list including the network slice identifier; as well as Register the UE using the configured network slice list including the network slice identifier and the group information to utilize the network slice on the second communication mode.

111. The computer-implemented method of claim 110, wherein each network slice in the group of network slices is simultaneously supported by the second communication mode.

112. A computer-implemented method according to claim 111, wherein each network slice in the configured network slice list is included in the network slice group.

113. The computer-implemented method of claim 110, wherein the first communication mode lacks support for 5G network slicing and the second communication mode supports 5G network slicing.

114. The computer-implemented method of claim 110, wherein the first communication mode utilizes an evolved packet core and the second communication mode utilizes a 5G core network.

115. A computer-implemented method according to claim 110, wherein the configured network slice list includes configured network slice selection assistance information (NSSAI), and the network slice identifier is included in a single NSSAI (S-NSSAI).

116. The computer-implemented method of claim 115, wherein causing the UE to update the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI.

117. A computer-implemented method according to claim 115, wherein the network slice group includes a network slice simultaneous registration group (NSSRG), and the group information includes a value associated with the NSSRG.

118. The computer-implemented method of claim 117, wherein causing the UE to update the configured network slice list to include the network slice identifier and the group information comprises: The configured NSSAI is updated to include the S-NSSAI and the value associated with the NSSRG.

119. The computer-implemented method of claim 110, wherein the information element is received during a packet data network (PDN) connection establishment procedure.

120. The computer-implemented method of claim 110, wherein the network slice identifier and the network slice group are included in an extended protocol configuration options (ePCO) portion of the information element.

121. A base station (BS), the BS comprising one or more processors configured to perform the computer-implemented method according to any one of claims 110 to 120.

122. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 110 to 120.

123. A computer-implemented method, the computer-implemented method comprising: receiving, at a user equipment (UE) device, a new configured network slice list during a UE configuration update procedure; failing to receive an information element (IE) with new group information associated with the configured network slice list during the UE configuration update procedure; as well as In response to receiving the new configured network slice list and failing to receive the new group information associated with the configured network slice list during the UE configuration update process, deleting the old group information.

124. A computer-implemented method according to claim 123, wherein the new configured network slice list is received in a configuration update command message.

125. A computer-implemented method according to claim 123, wherein the new configured network slice list is received in a registration accept message.

126. The computer-implemented method of claim 123, wherein failing to receive new group information associated with the configured network slice list during the UE configuration update procedure comprises: Failed to receive Network Slice Simultaneous Registration Group (NSSRG) Information IE.

127. The computer-implemented method of claim 123, wherein deleting old group information comprises: Delete the network slice simultaneous registration group (NSSRG) information stored on the UE.

128. A user equipment (UE) comprising one or more processors configured to perform the computer-implemented method of any one of claims 123 to 127.

129. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 123 to 127.

130. A computer-implemented method, the computer-implemented method comprising: Sending a new configured network slice list to a user equipment (UE) during a UE configuration update procedure; failing to send an information element (IE) having new group information associated with the configured network slice list to the UE during the UE configuration update procedure; as well as In response to sending the new configured network slice list to the UE and failing to send the new group information associated with the configured network slice list to the UE during the UE configuration update process, the UE deletes the old group information.

131. A computer-implemented method according to claim 130, wherein the new configured network slice list is sent in a configuration update command message.

132. A computer-implemented method according to claim 130, wherein the new configured network slice list is sent in a registration acceptance message.

133. The computer-implemented method of claim 130, wherein failing to send new group information associated with the configured network slice list to the UE during the UE configuration update procedure comprises: Failed to send the Network Slice Simultaneous Registration Group (NSSRG) Information IE to the UE.

134. The computer-implemented method of claim 130, wherein causing the UE to delete old group information comprises: Cause the UE to delete the network slice simultaneous registration group (NSSRG) information stored on the UE.

135. A base station (BS), the BS comprising one or more processors configured to perform the computer-implemented method of any one of claims 130 to 134.

136. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 130 to 134.

137. A computer-implemented method, the computer-implemented method comprising: registering to a first network slice via a first access type, wherein the first network slice is included in a first network slice group; registering to a second network slice via a second access type, wherein the second network slice is included in the first network slice group; Determining to register to a third network slice, wherein the third network slice is included in the second network slice group; as well as Generating a registration request for the third network slice, wherein the registration request indicates that the registration request is intentional.

138. The computer-implemented method of claim 137, wherein the first access type comprises 3GPP access and the second access type comprises non-3GPP access.

139. A computer-implemented method according to claim 137, wherein the registration request indicates that the registration request is intentional via an overlay slice configuration information element (IE).

140. A computer-implemented method according to claim 139, wherein the overlay slice configuration IE includes a portion for overlaying registrations on the first access type and a portion for overlaying registrations on the second access type.

141. A computer-implemented method according to claim 139, wherein the registration request for the third network slice is for the first access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the second access type for network slice groups other than the second network slice group including the third network slice.

142. A computer-implemented method according to claim 139, wherein the registration request for the third network slice is for the second access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the first access type for network slice groups other than the second network slice group including the third network slice.

143. A user equipment (UE) comprising one or more processors configured to perform the computer-implemented method of any one of claims 137 to 142.

144. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 137 to 142.

145. A computer-implemented method comprising one or more processors configured to perform operations comprising: registering a user equipment (UE) to a first network slice via a first access type, wherein the first network slice is included in a first network slice group; registering the UE to a second network slice via a second access type, wherein the second network slice is included in the first network slice group; as well as In response to the UE determining to register to a third network slice included in the second network slice group, a registration request for the third network slice is received from the UE, wherein the registration request indicates that the registration request is intentional.

146. The computer-implemented method of claim 145, wherein the first access type comprises 3GPP access and the second access type comprises non-3GPP access.

147. A computer-implemented method according to claim 145, wherein the registration request indicates that the registration request is intentional via an overlay slice configuration information element (IE).

148. A computer-implemented method according to claim 147, wherein the overlay slice configuration IE includes a portion for overlaying registrations on the first access type and a portion for overlaying registrations on the second access type.

149. A computer-implemented method according to claim 147, wherein the registration request for the third network slice is for the first access type, and the overlay slice configuration IE indicates an access slice configuration overlay on the second access type for network slice groups other than the second network slice group including the third network slice.

150. A computer-implemented method according to claim 147, wherein the registration request for the third network slice is for the second access type, and the overlay slice configuration IE indicates an overlay of the access slice configuration on the first access type for network slice groups other than the second network slice group including the third network slice.

151. A base station (BS), the BS comprising one or more processors configured to perform the computer-implemented method of any one of claims 145 to 150.

152. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 145 to 150.

153. A computer-implemented method, the computer-implemented method comprising: Determining that registration for a network slice in the pending network slice list is no longer required; Initiate the mobility registration process with the Access and Mobility Management Function (AMF); as well as During the mobility registration procedure, an indication is communicated to the AMF that registration with the network slice is no longer required.

154. A computer-implemented method according to claim 153, wherein the indication that registration with the network slice is no longer required is included in a registration request message.

155. A computer-implemented method according to claim 154, wherein the indication that registration with the network slice is no longer required is included in a discard information element (IE).

156. A computer-implemented method according to claim 155, wherein the pending network slice list includes pending network slice selection information (NSSAI), and the network slice corresponds to a single NSSAI (S-NSSAI) in the pending NSSAI.

157. The computer-implemented method of claim 156, wherein the discarding IE comprises discarding an NSSAI IE.

158. A user equipment (UE) comprising one or more processors configured to perform the computer-implemented method of any one of claims 153 to 157.

159. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 153 to 157.

160. A computer-implemented method, the computer-implemented method comprising: In response to a user equipment (UE) determining that registration for a network slice in the pending network slice list is no longer required, relaying initiation of a mobility registration procedure from the UE to an access and mobility management function (AMF); as well as During the mobility registration procedure, an indication is relayed from the UE to the AMF that registration with the network slice is no longer required, so that the AMF removes the network slice from the pending network slice list.

161. A computer-implemented method according to claim 160, wherein the indication that registration with the network slice is no longer required is included in a registration request message.

162. A computer-implemented method according to claim 161, wherein the indication that registration with the network slice is no longer required is included in a discard information element (IE).

163. A computer-implemented method according to claim 162, wherein the pending network slice list includes pending network slice selection information (NSSAI), and the network slice corresponds to a single NSSAI (S-NSSAI) in the pending NSSAI.

164. The computer-implemented method of claim 163, wherein the discarding IE comprises discarding an NSSAI IE.

165. A base station (BS), the BS comprising one or more processors configured to perform the computer-implemented method of any one of claims 160 to 164.

166. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 160 to 164.

167. A computer-implemented method, the computer-implemented method comprising: performing, at a user equipment (UE), local deregistration on the first access type when the UE is out of coverage of the first access type and the second access type; When the UE returns to the coverage of the first access type or the second access type, initiating a registration procedure with an access and mobility management function (AMF); as well as and communicating a registration status of the UE regarding the first access type or the second access type to the AMF during the registration procedure.

168. The computer-implemented method of claim 167, wherein the communication of the UE's registration status regarding the first access type or the second access type comprises: Indicating that the UE has deregistered from the first access type.

169. The computer-implemented method of claim 167, wherein the communication of the UE's registration status regarding the first access type or the second access type comprises: Instructing the UE to register only with the second access type.

170. A user equipment (UE) comprising one or more processors configured to perform the computer-implemented method of any one of claims 167 to 169.

171. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 167 to 169.

172. A computer-implemented method, the computer-implemented method comprising: In response to a local deregistration of a user equipment (UE) on a first access type and a second access type when the UE is out of coverage of the first access type and the second access type, relaying initiation of a registration procedure from the UE to an access and mobility management function (AMF) when the UE returns to coverage of the first access type or the second access type; as well as Relaying a registration status of the UE for the first access type or the second access type from the UE to the AMF during the registration procedure.

173. The computer-implemented method of claim 172, wherein relaying the UE's registration status for the first access type or the second access type comprises: Indicating that the UE has deregistered from the first access type.

174. The computer-implemented method of claim 172, wherein relaying the UE's registration status for the first access type or the second access type comprises: Instructing the UE to register only with the second access type.

175. A base station (BS), the BS comprising one or more processors configured to perform the computer-implemented method of any one of claims 172 to 174.

176. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 172 to 174.

Images