WO2025240348A1

WO2025240348A1 - Partial single network slice selection assistance information handling

Info

Publication number: WO2025240348A1
Application number: PCT/US2025/028943
Authority: WO
Inventors: Stanley M. Mayalil; Arjun Ramesh Shetty; Rajkumar KRISHNAPERUMAL; Vivek G. Gupta; Rajeev Verma; Haijing Hu
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2024-05-16
Filing date: 2025-05-12
Publication date: 2025-11-20
Anticipated expiration: 2026-11-16

Abstract

A UE, baseband processor, and network device are described. The baseband processor can receive, from the network device, a control message including partial network slice selection assistance information (NSSAI). The baseband processor may then provide, to a universal integrated circuit card (UICC) of the UE, a message that includes a portion of the partial NSSAI. The baseband processor may then provide, to the UICC, an indication that there are one or more remaining portions of the partial NSSAI. In some examples, the baseband processor then proceeds to provide the one or more additional messages that include the one or more remaining portions of the partial NSSAI.

Description

PARTIAL SINGLE NETWORK SLICE SELECTION ASSISTANCE INFORMATION

HANDLING

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Cooperation Treaty patent application claims priority to Indian Patent Application No. 202411038501, filed May 16, 2024, and titled “Partial Single Network Slice Selection Assistance Information Handling,” the contents of which are incorporated herein by reference as if fully disclosed herein in its entirety.

TECHNICAL FIELD

[0002] This application relates generally to wireless communication systems, including systems, apparatuses, and methods for partial single network slice selection assistance information (s-NSSAI) handling.

BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between a network device (e.g., a base station, a radio head, etc.) and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G), 3GPP new radio (NR) (e.g., 5G), and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0004] As contemplated by the 3GPP, different wireless communication systems standards and protocols can use various radio access networks (RANs) for communicating between a network device of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or Next-Generation Radio Access Network (NG-RAN).

[0005] Each RAN may use one or more radio access technologies (RATs) to perform communication between the network device and the UE. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3 GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). Tn certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

[0006] A network device used by a RAN may correspond to that RAN. One example of an E- UTRAN network device is an E-UTRAN Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN network device is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0007] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC), while NG-RAN may utilize a 5G Core Network (5GC).

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. [0009] FIG. 1 shows an example wireless communication system, according to one or more aspects described herein.

[0010] FIG. 2 shows an example signal flow, according to one or more aspects described herein.

[0011] FIG. 3 shows an example signal flow, according to one or more aspects described herein.

[0012] FIG. 4 shows an example signal flow, according to one or more aspects described herein.

[0013] FIG. 5 shows an example signal flow, according to one or more aspects described herein.

[0014] FIG. 6 shows an example signal flow, according to one or more aspects described herein.

[0015] FIG. 7 shows an example signal flow, according to one or more aspects described herein.

[0016] FIG. 7 shows an example method of wireless communication at a user equipment (UE), according to one or more aspects described herein. [0017] FIG. 8 illustrates an example architecture of a wireless communication system, according to one or more aspects described herein.

[0018] FIG. 9 illustrates an example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein.

DETAILED DESCRIPTION

[0019] Various embodiments are described with regard to a processor (e.g., baseband processor), wireless device (e.g., a user equipment (UE)), or a network device. However, reference to a processor, wireless device, or network device is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component or device that may establish a wireless connection and is configured with the hardware, software, and/or firmware to exchange information and data over the wireless connection. Therefore, the processors, wireless devices, and network devices described herein are used to represent any appropriate electronic components or devices.

[0020] Network slicing in a wireless communications system such as 5G/NR refers to the capability of creating multiple virtual network instances or “slices” within a single physical network infrastructure. Each slice may operate as an independent end-to-end network tailored to specific requirements such as latency, bandwidth, security, and reliability. These slices are logically isolated from one another and can be customized to cater to the diverse needs of various applications, services, or user groups. In some examples, network slicing may be used to support multiple use cases simultaneously, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency (URLLC) communications, or massive machine-type communications (mMTC). For instance, one slice might prioritize high-speed internet access for consumers, while another slice might prioritize low-latency connections for critical industrial automation applications.

[0021] Network slice selection assistance information (NSSAI) in wireless communication system is used for network slicing. NSSAI provides the necessary parameters and identifiers that enable network elements to determine the appropriate network slice for a particular service or application. These parameters include characteristics like latency, throughput, security requirements, and other quality-of-service considerations. By utilizing NSSAI, network elements can efficiently match user demands with the most suitable network slice, ensuring optimal performance and resource utilization. Partial NSSAI refers to a subset of NSSAI parameters available in a set of tracking areas (TAs) of a registration area (RA) provided by the network to assist in selecting an appropriate network slice for a specific service or application, which may be used by the UE. For example, in some cases, not all parameters may be needed to determine the best slice for a particular use case. As such, partial NSSAI may include only necessary parameters (e.g., a subset of the parameters) relevant to the service requirements, such as latency, throughput, or security levels. Partial NSSAI information when provided by network delivers one or more S- NSSAIs in a set of TA of a registration area from the network to the UE, and may include the partially allowed NSSAI, and/or the partially rejected NSSAI. [0022] During the initial connection setup process, a UE may receive a full NSSAI, including comprehensive information about available network slices (for example, allowed NSS AT, rejected NSSAI, partially allowed, partially rejected, configured NSSAI), which indicates their characteristics, capabilities, and quality-of-service attributes. This allows the UE to make an informed decision about which slice to connect to based on its specific requirements and service demands. However, after the initial connection establishment, the UE may receive updated NSSAI information, for example partial NSSAI, in scenarios where only specific parameters or attributes need to be updated or modified. The partial NSSAI may be either partially allowed/rejected or both, and provides a subset of the information required for slice selection, streamlining the communication process between the UE and the network while still enabling efficient slice management and resource allocation.

[0023] A UE or other mobile device may use a subscriber identity module (SIM) card to store information about a user of the UE. A SIM card is typically a small, portable memory chip that stores information about the user. For example, a SIM card typically has a seventeen-digit code that designates the country code of origin, the operate (e.g., a mobile network operator (MNO)), and a user ID. Rather than a physical card to be changed out or installed for different deployments, an eSIM (embedded SIM) may be embedded directly into a UE, such as a smartphone or Internet of Things (loT) device, rather than being a physical, removable card. An eSIM refers generally to remote SIM provisioning according to the Global System for Mobile Communications Association (GSMA). The eSIM is designed in part to replace traditional physical SIM cards. One advantage of eSIM technology is flexibility, as eSIM technology allows users to remotely provision and manage the user’s mobile subscriptions without the need for a physical SIM card swap. This capability may particularly be beneficial for devices with constrained physical space, such as smartwatches or connected loT devices.

[0024] In some cases, a universal integrated circuit card (UICC), such as an embedded universal integrated circuit card (eUICC), can be used. An eUICC is an embedded component that incorporates both the functionality of a traditional SIM card and an additional layer of programmability for managing multiple mobile subscriptions. An eUICC may be a removable or a non-removable UICC, and enables the remote and/or local management of profiles in a secure way. An eUICC may have or store multiple “eSIM profiles,” which may also be referred to herein as simply a “profile.”

[0025] The UE (e.g., a baseband processor of the UE) may receive communication from the network regarding information for managing partial NSSAI, such as new, deleted, and partially allowed/rejected NSSAI (including single NSSAI specific to the TA of the registration area). As used herein, partially rejected NSSAI may indicate the S-NSSAI(s) are rejected by the network in some TAs but not all TAs of the registration area. Each S-NSSAT in the partially rejected NSSAI is associated with a list of TAs where the S-NSSAI is rejected. As used herein, partially allowed NSSAI may indicate the S-NSSAI(s) is allowed by the network in some TAs but not all TAs of the registration area. Each S-NSSAI in the partially allowed NSSAI is associated with a list of TAs where the S-NSSAI is rejected. The UICC needs to communicate with the UE (e.g., the baseband processor) regarding such partial NSSAI. However, current approaches are deficient.

[0026] In one example, when a network intends to delete previously-provided partially allowed and/or partially rejected NSSAI, for example via a registration procedure with the UE or a configuration update command (CUC) procedure, there may not be a mechanism to provide this information to the UICC. As such, the UICC may have to deal with stale information that was previously obtained, and may rely on the invalid or stale information. The network (e.g., the access management function (AMF) may set the length of partial NSSAI contents to 0 if there are no S- NSSAIs to deliver in a set of tracking areas of a registration area and, the UE may delete any existing stored partially allowed NSSAI for the current registration area or partially rejected NSSAI for the current registration area in response. However, the UICC may not be able to get this information that is also needed for by the UICC (e.g., for UICC applets). Similarly, there is absent, according to present techniques, a mechanism to provide allowed and/or rejected slice information to the UICC. These challenges may exist both in the case of a provide local information (PLI) case, and an event download slice status case.

[0027] In another example, a network may provide a partially allo wed/rejec ted NSSAI via the registration procedure or CUC procedure. The data size of the partially allo wed/rejec ted NSSAI can vary depending on the network configuration and can go beyond the limit allowed by one envelope. For example, the partial NSSAI information element that the UE receives from the network can have a minimum length of 3 octets and a maximum length of 808 octets. Because of this length, the UICC cannot be provided with the full set of information according to current approaches. An application protocol data unit (APDU), such as a terminal response APDU (e.g., in the case of a provide local information (PLI) - slice information signaling) or envelope APDU (e.g., in the case of an event download slice status signaling), may be limited to a certain number of bytes, such as 255 bytes. As such, as further described herein, an APDU, such as the proactive command PLI or envelope command, may be revised (modified, updated, extended) to allow additional data beyond existing size limitations. For example, as further described herein, messages such as an APDU may indicate that there is pending data for the UICC, such that the UICC may receive and/or request more information that is then provided by the UE (e.g., a baseband processor of the UE).

[0028] In another example, even if a complete list of S-NSSAI information is received at the UE side (including partial, allowed, rejected NSSAI), the NSSAI information is accommodated within a single message (e.g., an envelope). According to current techniques, in the case of multiple NSSAI information (even when available on the UE side), UE may not be able to provide to the UICC within a single envelope due to limitation imposed on the single message. In some examples, as further described herein, a bit mapping (e.g., in “Slice status coding 8.150”) may be updated to simplify UICC signaling in many use cases like multiple registrations with two UICC or dual registration with single UICC.

[0029] In yet other examples, a UE may receive both allowed slice and partially allowed slice information from a network. In the case of PLI signaling, there may not be a mechanism to provide information to the UICC when an allowed slice is requested. Certain UEs may provide the available served slices information, along with the allowed slice info, others may only provide available served slices information along with partially allowed slice. In some cases, the same issue may arise when PLI - rejected slice/partially rejected slice is requested. Also, the ordering of provided s-NSSAI information within a type-length-value (TLV) message may be ambiguous or otherwise unclear in communications between a UE and UICC. For example, one or more of served slices TLV, rejected slices TLV, or allowed slices TLV may be included in signaling with an unclear order.

[0030] Techniques for improved UE (e.g., baseband processor) to UICC signaling are described. The UE can receive, from the network device, a control message including partial NSSAI. The UE can then provide (e.g., from the baseband processor to a UICC) a message that includes a portion of the partial NSSAI. The UE can also provide to the UICC an indication that there are one or more remaining portions of the partial NSSAI. In some examples, the UE then proceed to provide to the UICC the one or more additional messages that include the one or more remaining portions of the partial NSSAI.

[0031] FIG. 1 shows an example wireless communications system 100, according to one or more aspects described herein. In one or more embodiments, wireless communications system 100 supports one or more aspects of partial s-NSSAI handling, as further described herein.

[0032] Wireless communications system 100 includes a UE 102 and a network device 104. The network device 104 may be in communication with an AMF 106, and other core network components (not shown) of the wireless communications system 100. In one or more embodiments, UE 102 includes a baseband processor 114 and is associated with a universal SIM (USIM), such as a UICC 1 16. In some embodiment, UICC 116 is an eUICC.

[0033] As further described herein, the AMF 106 may provide (transmit, output, convey, communicate) to the UE 102 with partial NSSAI 122 via network device 104. In order for the UE 102 to provide the partial NSSAI to the UICC 116, the UE 102 provides a first portion 124 of the partial NSSAI to UICC 116 as well as an indication 126 of remaining portions of partial NSSAI. For example, the indication 126 may represent partial NSSAI that the UE 102 received from the network device 104, but did not deliver to the UICC 116 with the first portion 124 of the partial NSSAI.

[0034] With the partial NSSAI, the UICC can utilize slice information received from a network to facilitate the establishment and management of connections to specific network slices. The partial NSSAI 122 received from the network device 104 typically contains parameters such as slice identifiers, characteristics, and quality-of-service (QoS) attributes. When the UICC 116 receives the partial NSSAI (e.g., via the first portion 124 and, in some examples, the remaining portions of the partial NSSAI), the UICC 116 may evaluate the received slice information to determine a network slice (e.g., the most suitable network slice) for the current service or application requirements. The UICC 116 may consider one or more factors including latency, throughput, security levels, and other QoS parameters specified in the slice information. Following slice selection, the UICC 116 may initiate an authentication and authorization process with the network, which may include verifying a user’s credentials and permissions to access the selected slice. If access is granted, a connection to the selected network slice is established, and the UE 102 may communicate with the network device 104 in a protocol data unit (PDU) session 128. The network (e.g., via network device 104) may allocate resources and configure the connection parameters with the UE 102 according to the slice requirements.

[0035] For a UE 102 (including UICC 116) having an established connection with the network via network device 104, the UICC may need to monitor the slice information to ensure continued optimal performance of the connection to ensure that the application, or a user if UE 102 can access the desired services with the appropriate levels of performance and quality.

[0036] FIG. 2 shows an example signal flow 200, according to one or more aspects described herein. In one or more embodiments, example signal flow 200 supports one or more aspects of partial s-NSSAI handling, as further described herein. Example signal flow 200 may include one or more aspect further described herein, for example with reference to the wireless communications system 100. [0037] In some examples, previously-provided partially allowed NSSAI or partially rejected NSSAT may need to be deleted. The UE 102, via baseband processor 1 14, may transmit (provide, output, convey, communicate) a message (e.g., a TLV message) to the UICC 116 that indicates a length of zero to indicate that previously-provided partial NSSAI (e.g., partially allowed and/or partially rejected NSSAI) is no longer valid.

[0038] At 202, the UE 102 may power up, including powering up the baseband processor 114 and UICC 116. At 204, USIM initialization is performed between the UICC 116 and baseband processor 114. A terminal profile 206 may be provided to the UICC 1 16 during USIM initialization. The terminal profile includes the list of card application toolkit (CAT) capabilities, or USIM application toolkit (USAT) facilities supported by a mobile equipment (ME) (e.g., UE 102), and is transmitted to the applications present on the UICC. The UE 102 may then perform UE registration with a network device 104, including receiving a registration accept message 208 from the network.

[0039] At 210, the baseband processor 114 receives a proactive command pending (which may be an example of a CAT message indicating that the pending proactive command available for baseband processor 114 to FETCH). At 212, the baseband processor 114 responds with a fetch function. At 214, the UICC 116 transmits (sends, provides) a proactive command: PLI for slice information, or PLI rejected slice information. The baseband processor 114 may then provide a terminal response message 216 that can also include the partially allowed and/or partially rejected slice information in response.

[0040] Sometime later, the UE 102 may receive from the network device 104 an indication that the previously-provided slice information is to be deleted. For examples, network device 104 may transmit to the UE 102 a CUC 218 that has a partial NSSAI information element present, including a length indication indicating that the length of the content is zero. In the CUC 218, if the partial NSSAI TLV, length of contents is indicated as 0, then this is a special indication to indicate any information previously provided (e.g., partially allowed or partially rejected S-NSSAI) for the current registration area is no longer valid and can be removed by the UE 102. This indication is provided to ensure that the UICC 1 16 will not have stale data. A similar approach can be extended to allowed and rejected slices information (in addition to partially allowed or partially rejected) previously provided (with/without mapping).

[0041] At 220, the baseband processor 114 receives a proactive command pending. At 222, the baseband processor 114 responds with a fetch function. At 224, the UICC 116 transmits (sends, provides) a proactive command: PLI for slice information, or PLI rejected slice information. The baseband processor 114 may then provide a terminal response message 226 in response, with the partially allowed and/or partially rejected slice information empty, and including an indication that the length is zero, to indicate that the partially allowed and/or partially rejected slice information is no longer valid.

[0042] Although the example signal flow 200 is shown and described with reference to the PLI case, signal flow 200 may also be applied in the event download case. For example, in the event download case, an envelope may contain the same partial S-NSSAI allo wed/rejec ted slice information TLV, with a length indicated as 0 to indicate that the prior information (e.g., provided for this partial case) is no longer valid.

[0043] Different data objects may be used in the example signal flow 200 (e.g., for terminal response message 226), to indicate the length of 0, and thus that the partially allowed and/or partially rejected slice information is no longer valid. The data object of rejected slices information with S-NSSAI mapping can include a length field set to 0 to indicate any information previously provided is no longer valid. The data object of rejected slices information (e.g., without S-NSSAI mapping) can include a length field set to 0 to indicate any information previously provided is no longer valid. The data object of partial NSSAI (e.g., containing a subset of tracking areas or the current registration area for each S-NSSAI partially supported) can include a length field set to 0 to indicate any information previously provided for the current registration area is no longer valid.

[0044] FIG. 3 shows an example signal flow 300, according to one or more aspects described herein. In one or more embodiments, example signal flow 300 supports one or more aspects of partial s-NSSAI handling, as further described herein. Example signal flow 300 may include one or more aspects further described herein, for example with reference to the wireless communications system 100 and/or the signal flow 200.

[0045] At 302, the UE 102 may power up, including powering up the baseband processor 114 and UICC 116. At 304, USIM initialization is performed between the UICC 116 and baseband processor 1 14. A terminal profile 306 may be provided to the UICC 116. In some embodiments, the terminal profile 306 may include an indication that the UE 102 (e.g., including the baseband processor 114) is capable of providing a “full list” of partial slice rejected/allowed information, or supports consecutive commands with these information.

[0046] The UE 102 may then perform UE registration with a network device 104, including transmitting a registration request 308, receiving a registration accept 310, and transmitting a registration complete 312. In one or more examples, the registration request 308 may include a requested NSSAI and requested mapped NSSAI. In one or more examples, the registration accept 310 may indicate the allowed, configured, and/or rejected NSSAI, and include partially rejected slices information, and/or partially allowed slices information (each with/without respective mapped s-NSSAI information). Following UE registration, the UE 102 may establish a PDU session 314 with a data network name (DNN) and s-NSSAT.

[0047] At 316, the baseband processor 114 receives a proactive command pending indication. At 318, the baseband processor 114 responds with a fetch function. At 320, the UICC 116 transmits (sends, provides) a proactive command: PLI for slice information, or PLI rejected slice information. The baseband processor 114 may then provide a terminal response message 322 in response.

[0048] According to current techniques, there may be no ability for the UE 102 to provide a full list of partially allowed and/or partially rejected slice information, although such information may be available at the UE 102. For example, the terminal response length (e.g., of the terminal response message 322) may be inadequate. As such, the information regarding the full list of partially allowed and/or partially rejected slice information may be available to the baseband processor 114 of the UE 102, but may not be able to be provided to the UICC 116 according to current techniques. In one or more embodiments, the terminal response message 322 may include an indication regarding remaining information about the partially allowed and/or partially rejected slice information. For example, if the UICC 116 subsequently requests for pending data via one or more proactive commands for pending data (e.g., similar to proactive command 316 for pending data).

[0049] Although described with reference the registration accept 310, a CUC may additionally, or alternatively, indicate the allowed, configured, and/or rejected NSSAI, and include partially rejected slices information, and/or partially allowed slices information (each with/without respective mapped s-NSSAI information).

[0050] FIG. 4 shows an example signal flow 400, according to one or more aspects described herein. In one or more embodiments, example signal flow 400 supports one or more aspects of partial s-NSSAI handling, as further described herein. Example signal flow 400 may include one or more aspects further described herein, for example with reference to the wireless communications system 100, example, signal flow 200, and/or example signal flow 300. As further described, example signal flow 400 includes signaling between a baseband processor 114 and a UICC 116 in an example where the UE 102 (e.g., the baseband processor 114 of UE 102) may discard remaining data (e.g., about the partially allowed and/or partially rejected slices), and indicate to the UICC 116 that the information provided is partial information, and more data is available.

[0051] At 402, the baseband processor 114 receives a proactive command =pending indication. At 404, the baseband processor 114 responds with a fetch function. At 406, the UICC 116 transmits (sends, provides) a proactive command: PLI for slice information. 402, 404, and 406 may be examples of 316, 318, and 320, respectively, of the example signal flow 300.

[0052] The baseband processor 114 may then provide a terminal response message 408 in response to the proactive command at 406. The terminal response message 408 contains a portion of the requested data (e.g., a first portion of the partial NSSAI), but is incomplete. The terminal response message 408 also includes an indication that there are one or more remaining portions of the partial NSSAI. In some examples, the terminal response message 408 indicates the quantity of partial NSSAI remaining (e.g., indicate YY# of remaining data available with a TLV “more data”). The remaining partial NSSAI information may be then discarded on the baseband processor side (e.g., the UICC 116 terminates with 90 00, and further data may be discarded).

[0053] In some examples, the proactive command: PLI for slice information at 406 may include a “more data” data object. The “more data” data object may apply when the Command Qualifier in Command details is set to indicate either “slices information” or “rejected slices information.” The “more data” data object may be included if the UE 102 has indicated that (i) the UE 102 supports successive partially allowed or partially rejected slice via the respective Terminal Profile setting, and (ii) that the UE 102 has indicated in a prior Terminal Response that the UE 102 has more partial slice information available. The “more data” data object is included to request to the UE 102 to provide the remaining partial slice or slices information that is available.

[0054] In some examples, “more data” may be requested immediately in successive commands, or may be at a later time, but the UE 102 (e.g., the baseband processor 1 14) may not have any further slice information to send to the UICC 116. In such case, the UE 102 (e.g., the baseband processor 114) may send (transmit, provide) to the UICC 116 a terminal response message with a general result indicating that the terminal is currently unable to process the command, and additional information with the result indicating that no specific cause can be given.

[0055] FIG. 5 shows an example signal flow 500, according to one or more aspects described herein. In one or more embodiments, example signal flow 500 supports one or more aspects of partial s-NSSAI handling, as further described herein. Example signal flow 500 may include one or more aspects further described herein, for example with reference to the wireless communications system 100, example, signal flow 200, example signal flow 300 and/or example signal flow 400. As further described, example signal flow 500 includes signaling between a baseband processor 114 and a UICC 116 in an example where the UE 102 (e.g., the baseband processor 114 of UE 102) may indicate to the UICC 116 that the information provided is partial information, and more data is available, then provide the remaining data (e.g., about the partially allowed and/or partially rejected slices) in one or more terminal response messages. [0056] At 502, the baseband processor 114 receives a proactive command pending indication. At 504, the baseband processor 1 14 responds with a fetch function. At 506, the UICC 1 16 transmits (sends, provides) a proactive command: PLI for slice information. 502, 504, and 506 may be examples of 316, 318, and 320, respectively, of the example signal flow 300.

[0057] The baseband processor 114 may then provide a terminal response message 508 in response to the proactive command at 506. The terminal response message 508 contains a portion of the requested data (e.g., a first portion of the partial NSSAI), but is incomplete. The terminal response message 508 also includes an indication that there are one or more remaining portions of the partial NSSAI. In some examples, the terminal response message 508 continues the proactive session (e.g., with 91XX).

[0058] The procedures of the example signal flow 500 that include 502, 504, 506, and 508 may repeat for each of the additional portions of the one or more remaining portions of the partial NSSAI, for example until a last portion of the one or more remaining portions is met. For example, 502, 504, 506, and 508 may repeat, with the terminal response message 508 each time including an indication that there are one or more remaining portions of the partial NSSAI. For the terminal response message 516 where the final information is provided (e.g., a final portion of the one or more remaining portions of the partial NSSAI), the MORE DATA TLV may be absent. Alternatively, the MORE DATA TLV may include a length indicated as 0.

[0059] For the provision of the final information, responsive to the terminal response message 508, at 510, the UICC 1 16 transmits and the baseband processor 114 receives a proactive command pending indication (e.g., with 91XX). At 512, the baseband processor 114 responds with a fetch function. At 514, the UICC 116 transmits (sends, provides) a proactive command: PLI for slice information. The baseband processor 114 may then provide a terminal response message 516 in response to the proactive command at 514. The terminal response message 516 contains the final portion of the requested data (e.g., a last portion of the one or more remaining portions of the partial NSSAI).

[0060] In some examples, the proactive command: PLI for slice information at 406 may include a “more data” data object. The “more data” data object may apply when the Command Qualifier in Command details is set to indicate either “slices information” or “rejected slices information.” The “more data” data object may be included if the UE 102 has indicated that (i) the UE 102 supports successive partially allowed or partially rejected slice via the respective Terminal Profile setting, and (ii) that the UE 102 has indicated in a prior Terminal Response that the UE 102 has more partial slice information available. The “more data” data object is included to request to the UE 102 to provide the remaining partially supported slice or slices information that is available. [0061] In some examples, “more data” may be requested, but the UE 102 (e.g., the baseband processor 1 14) may not have any further slice information to send to the UICC 1 16. In such case, the UE 102 (e.g., the baseband processor 114) may send (transmit, provide) to the UICC 116 a terminal response message with a general result indicating that the terminal is currently unable to process the command, and additional information with the result indicating that no specific cause can be given.

[0062] In some examples, proactive command 506 (or proactive command 514 in the case of the last portion of partially allowed S-NSSAI) includes the “more data” TLV as part of the request. In such case, the terminal response message 508 (or terminal response message 516 in the case of the last portion of partially allowed S-NSSAI) may contain the remaining partially allowed S- NSSAI information up to the limit of the size of the APDU of the terminal response message. If no slice information is available, the respective data object may have a length of zero.

[0063] In some examples, the “more data” data object may indicate that more data is expected, and specify the indexing of the buffer size in bytes. A first byte may be a more data tag. A second byte may be used to indicate a length, were if the length indicates 0, then it indicates that no more data is expected or available and data index is either absent to coded with zeros (e.g., “00 00”). A third and fourth byte may be for a data index. The data index may indicate the last data index. The data index is coded on two bytes to represent indexing of the buffer size in byte(s). When used in a PLI, then the index is the number of bytes already received (which may include both header and data). When used in the terminal response (e.g., terminal response message 508, terminal response message 516), the data index represents the remaining bytes available to send from the UE 102 (e.g., baseband processor 1 14) to the UICC 116.

[0064] In some examples, if “more data” is requested when used in the PLI, but the UE 102 (e.g., baseband processor 1 14) does not have additional information to send in a terminal response, then the UE 102 (e.g., baseband processor 1 14) may reject the PLI command from the UICC 116 with a general result indicating “terminal currently unable to process command,” and additional information with the result “no specific cause can be given.”

[0065] FIG. 6 shows an example signal flow 600, according to one or more aspects described herein. In one or more embodiments, example signal flow 600 supports one or more aspects of partial s-NSSAI handling, as further described herein. Example signal flow 500 may include one or more aspects further described herein, for example with reference to the wireless communications system 100, example, signal flow 200, example signal flow 300, example signal flow 400, and/or example signal flow 500. As further described, example signal flow 500 includes signaling between a baseband processor 114 and a UICC 116 in an example where the UE 102 (e.g., the baseband processor 114 of UE 102) may indicate to the UICC 116 that the information provided is partial information, and more data is available, then provide the remaining data (e.g., about the partially allowed and/or partially rejected slices) in one or more envelopes.

[0066] At 602, the UE 102 may power up, including powering up the baseband processor 114 and UICC 116. At 604, USIM initialization is performed between the UICC 116 and baseband processor 114. A terminal profile 606 may be provided to the UICC 116. In some embodiments, the terminal profile 606 may include an indication that the UE 102 (e.g., including the baseband processor 1 14) is capable of providing a “full list” of partial slice rejected/allowed information, or supports consecutive commands with these information.

[0067] The UE 102 may then perform UE registration with a network device 104, including transmitting a registration request 608, receiving a registration accept 610, and transmitting a registration complete 614. In one or more examples, the registration request 608 may include a requested NSSAI and requested mapped NSSAI. In one or more examples, the registration accept 610 may indicate the allowed, configured, and/or rejected NSSAI, and include partially rejected slices information, and/or partially allowed slices information (each with/without respective mapped s-NSSAI information). Following UE registration, the UE 102 may establish a PDU session 618 with a DNN and s-NSSAI.

[0068] In some examples, the UE 102 may transmit a proactive command 612 for pending data. At 614, the baseband processor 114 responds with a fetch function.

[0069] At 612, the baseband processor 114 receives a proactive command pending indication. At 616, the baseband processor 114 responds with a fetch function.

[0070] In some cases, the UE 102 may support and receive a slice status change event as part of proactive command 620 (e.g., SET UP EVENT LIST: EVENT DOWNLOAD command). In the case of a slice status change event, when the UE 102 detects a change or already has the required slice information, an envelope 624 may be sent to the UICC 116 with available slice information. The envelope 624 may include available slice information (e.g., partially supported/partially rejected slice information for specific tracking area as received from network). In some examples, information that can be provided may be limited to be less than 255 bytes per envelope. However, multiple envelopes may be provided, including at least one subsequent envelope 626. Each subsequent envelope 626 may contain partial NSSAI (e.g., list of partial S- NSSAIs allowed or rejected per subset of tracking area(s)). In some examples, the partial NSSAI may be ordered in envelopes how the partial NSSAI was received from network device 104. The final envelope 626 may contain an indication of a last envelope to indicate that the envelope 626 is the last envelope with the final list of information available. [0071] In some examples, an envelope 624 and envelope 626 (which may be examples of ENVELOPE (EVENT DOWNLOAD - slices status)) may include a “last envelope” TLV (parameter, data). If one envelope (e.g., a first of the envelope 624) is not sufficient to transmit all the information (e.g., for providing the partial S-NSSAI) then information may be split into several envelopes). The final envelope (e.g., envelope 626) is indicated by containing the “last envelope” TLV. In some examples, a byte may be used in the last envelope TLV as a “last envelope tag” to indicate that the conveyed partial NSSAI is the final data.

[0072] In other examples, the last envelope indication may be a conveyed by the partial NSSAI TLV (parameter, data) of envelope 626 (which may be an example of ENVELOPE (EVENT DOWNLOAD - slices status)). The partial NSSAI data object may include a length field, which may be one byte, that indicates the last envelope by having the length indicated as 0.

[0073] In some embodiments, in the case of the “event download slice status” at 620, when the “slice status change event” is triggered, the respective partial NSSAI information to be delivered may be optimized (modified, reformatted). For example, a “slice status change event” may occur when the UE 102 detects any changes in any S-NSSAI status, including any partially allowed or partially rejected slice list, served slice information, allowed slices information, or rejected slices information. In some examples, the partial NSSAI information can be combined (e.g., concatenated) into one envelope by indicating the correct (corresponding quantity of) bits in the slice status (ENVELOPE (EVENT DOWNLOAD - slices status)). In other examples, the partial NSSAI information can be combined (e.g., concatenated) into two or more envelopes that are fewer in quantity than would otherwise be needed for the partial NSSAI information (e.g., combined into relatively fewer envelopes).

[0074] In some examples, after concatenation (combination), the total data length is less than the maximum length of a single envelope, then only one envelope is needed. Otherwise, multiple envelopes (including with combined (concatenated)) information may be used, for example as described with reference to envelope 624 through envelope 626, to carry the remaining data after concatenation.

[0075] In some examples (e.g., in the case of a PLI request to the UE 102), the UE 102 may have both allowed NSSAI and partially allowed NSSAI information. Similarly, in other examples, the (e.g., in the case of a PLI request to the UE 102 to provide rejected slice information), the UE 102 may have both rejected NSSAI and partially rejected NSSAI information. When there are both allowed slice, and partially allowed slice information at UE 102 (received from the network device 104), and when the UICC 116 sends PLI (list of slice information), it may be unclear what information is to be provided. In some examples, it may be unclear whether the UE 102 is to provide only the served plus allowed slices, or provide a served plus subset of partially allowed slices.

[0076] The PLI data object may include a more data field (more data TLV). The “more data” data object may apply when the Command Qualifier in Command details is set to indicate either “slices information” or “rejected slices information.” The “more data” data object may be included if the UE 102 has indicated (i) support for “successive partially allowed or partially rejected slice” via the respective Terminal Profile setting, and (ii) UE 102 has indicated in prior Terminal Response that it has more partial slice information available. In some examples, the “more data” data object may be included to request to the UE 102 to provide the remaining partially supported slice(s) information that is available. In some examples, if “more data” is requested, and the UE 102 has nothing more to send then the UE 102 (e.g., baseband processor 114) rejects the command by sending TERMINAL RESPONSE with general result “Terminal currently unable to process command” and additional information with result “No specific cause can be given.”

[0077] Where the UICC 1 16 has requested the List of slice(s) information, the TERMINAL RESPONSE can contain the serving public land mobile network (PLMN) served S-NSSAI list, along with (i) either the slices information data object listing all slice(s) information without S- NSSAI mapping data object (if S-NSSAI mapping information is not available) or the list of slice(s) information with S-NSSAI mapping data object listing all available mapping information, (ii) if the S-NSSAI is supported only on a subset of Tracking Area(s) of the current Registration Area, the tracking area identity list where the S-NSSAI is supported shall be available, up to the limit of the TERMINAL RESPONSE APDU command size. If the “more data” TLV is part of this request then TERMINAL RESPONSE shall contain the remaining S-NSSAI information, up to the limit of the TERMINAL RESPONSE APDU. If no slice information is available, the respective data object shall have length zero.

[0078] Where the UICC has requested via Provide local information for the closed access group (CAG) information list, the TERMINAL RESPONSE shall contain the CAG information list and the corresponding CAG human-readable network name per CAG ID (if available in the broadcasted information to the UE 102) of the detected CAG cells (if class “ag” is supported) along with “more data TLV” to provide full level of information to UICC if requested via successive commands. In the case CAG Cell Selection event, If the CAG Cell Selection event is part of the current event list (as set up by the last SET UP EVENT LIST command, “LAST ENVELOPE” indication may be used to indicate the last envelope from UE.

[0079] Where the UICC has requested the list of rejected slice(s), then TERMINAL RESPONSE shall contain (i) either the list of rejected slice(s) information with S-NSSAI mapping information (if S-NSSAI mapping information is available) or rejected slice(s) information without S-NSSAI mapping information (if S-NSSAI mapping information is not available), (ii) if the S-NSSAI is rejected only on a subset of Tracking Area(s) of the current Registration Area, the tracking area identity list where the S-NSSAI is rejected shall be available, up to the limit of the TERMINAL RESPONSE APDU command size. If “more data” TLV is part of this request then TERMINAL RESPONSE shall contain the remaining S-NSSAI information, up to the limit of the TERMINAL RESPONSE APDU. If no rejected slice information is available, the respective data object shall have length zero.

[0080] In or more examples described herein, rather than the “Envelope Event download Slice status” extended to have the “Last envelope TLV” as discussed herein (e.g., with reference to example signal flow 600) or the “Provide Local info (slice information)” and corresponding “Terminal Response” enhanced to have “MORE DATA” TLV as discussed herein (e.g., with reference to example signal flow 300, signal flow 400, or signal flow 500), the “Partial NS SAI” TLV itself can also be extended to have “Last Envelope TLV,” or alternatively a “final data/end of data” or “more data TLV”, or “truncated data” indication. In some examples, this final data indication can be present in only the final Partial NSSAI TLV to indicate the final information available. In other examples, this final data indication can be present on every intermediate Partial NSSAI TLV with a bit to indicate this information accordingly to represent “not final data.” In some instances, the final data indication can be used to specify the buffer index of sent/received/pending data.

[0081] In some examples described herein, the ordering of S-NSSAI within a “served slice TLV” is in the same order as the slices that were activated on the side of the UE 102. However, for other TLV’s (e.g., allowed slices, partial NSSAI, rejected slices), the ordering of S-NSSAI is in the same order the S-NSSAI were received from network via the network device 104. In other examples, the S-NSSAI are provided in no particular order.

[0082] In some examples described herein, the AMF (e.g., AMF 106) can provide different slice information simultaneously (e.g., provide roaming number (PRN), provisioning of authentication data over the non-access stratum (NAS) (PAN), rejected, allowed). When the AMF 106 provides both the partially allowed NSSAI and the partially rejected NSSAI to the UE 102, each S-NSSAI is either in the partially allowed NSSAI or in the partially rejected NSSAI, but may not be both. The number of S-NSSAIs included in the partially allowed NSSAI or the partially rejected NSSAI may not exceed seven in some examples. The number of S-NSSAI stored in the partially allowed NSSAI and the allowed NSSAI may not exceed eight, in some examples. The partially allowed NSSAI may only be applicable to 3GPP access and is applicable for the registration area. The partially rejected NSSAI may only be applicable to 3GPP access and is applicable for the registration area. When the AMF 106 provides the partially allowed NSSAI and Partially rejected NSSAI to UE 102, each NSSAI may be either be in Partially allowed NSSAIs, or Partially rejected S-NSSAI but not both. As such, in some examples, both partially allowed and partially rejected S-NSSAI are possible.

[0083] In some examples described herein, the AMF 106 updates the allowed NSSAI, the partially allowed NSSAI and the rejected NSSAI using the generic UE configuration update procedure after the network slice-specific authentication and authorization procedure is completed. As such, allowed plus partially allowed plus rejected NSSAI is possible.

[0084] In some examples described herein, if the UE 102 supports the partial network slice and includes the S-NSSAI(s) in the requested NSSAI, and if the partially allowed NSSAI, the partially rejected NSSAI, or both are changed, the AMF 106 can provide the new partially allowed NSSAI, the new partially rejected NSSAI, or both to the UE 102. As such, partially allowed plus partially rejected NSSAI is possible.

[0085] In some examples described herein, during PDU session establishment, in order to enable PDU transmission in a network slice, the UE 102 may request establishment of a PDU session in a network slice towards a data network (DN) which is associated with an S-NSSAI and a DNN if there is no established PDU session adequate for the PDU transmission. The S-NSSAI included is part of allowed NSSAI of the serving PLMN or standalone non-public networks (SNPN), which is an S-NSSAI value valid in the serving PLMN or SNPN, and in roaming scenarios the mapped S-NSSAI is also included for the PDU session if available. The UE 102 determines whether to establish a new PDU session or use one of the established PDU session(s) based on the S-NSSAIs, if any, or based on local configuration of UE 102.

[0086] In some examples described herein, the utilization of partial network slices during session management may be according to the following description. In some examples, if the S- NSSAI is included in the partially allowed NSSAI and: (a) if the current tracking area identity (TAI) is in the list of TAs for which the S-NSSAI is allowed, the UE can initiate the UE-requested PDU session establishment procedure for the S-NSSAI; or (b) if the current TAI is not in the list of TAs for which the S-NSSAI is allowed, the UE may not initiate the UE-requested PDU session establishment procedure for the S-NSSAI.

[0087] In other examples described herein, if an existing PDU session is established for the S- NSSAI included in the partially allowed NSSAI and: (a) if the current TAI is changed and the current TAI is in the list of TAs for which the S-NSSAI is allowed, the UE can initiate the service request procedure to re-establish the user plane resources for the established PDU session or the UE can initiate UL NAS TRANSPORT messages carrying control plane user data or the session management function (SMF) can send control plane user data to the UE; or (b) if the current TAI is changed and the current TAI is not in the list of TAs for which the S -NS SAI is allowed, the SMF and the UE may not maintain a 5G system architecture (5GSM) contexts for the established PDU session. The UE 102 may not initiate UL NAS TRANSPORT messages carrying control plane user data and the SMF may not send control plane user data to the UE.

[0088] In some examples described herein, a generic UE configuration update procedure may be initiated by the network. For example, the AMF 106 may initiate the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND (CUC) message to the UE 102. In one example, if the UE 102 supports partial network slice and the AMF 106 needs to update the partially allowed NSSAI, partially rejected NSSAI or both, then the AMF 106 may include the Partially allowed NSSAI IE, the Partially rejected NSSAI IE or both, in the CONFIGURATION UPDATE COMMAND message.

[0089] FIG. 7 shows an example method 700 of wireless communication by a UE, according to one or more aspects described herein. In some cases, the UE may be the wireless device 902 or UE 102. In some cases, the method 700 may be performed by a baseband processor of the UE. In some embodiments, the baseband processor may include one or more processor cores, and memory that is coupled to the processor core(s). The memory may store instructions that, when executed by the processor core(s), causes the baseband processor to perform the operations of the method 700. As the baseband processor performs the operations of the method 700, the baseband processor may also cause other components of the UE to perform, or discontinue, various operations.

[0090] At 702, the method 700 includes receiving partial NSSAI. In some embodiments, the method 700 includes receiving a control message, transmitted from a network device, that includes partial NSSAI.

[0091] At 704, the method 700 includes providing a portion of the partial NSSAI to the UICC. In some embodiments, the method 700 includes providing, to a UICC of the UE, a message that includes a portion of the partial NSSAI.

[0092] At 706, the method 700 includes indicating to the UICC that the UE has additional partial NSSAI. In some embodiments, the method 700 includes providing, to the UICC, an indication that there are one or more remaining portions of the partial NSSAI.

[0093] In one or more embodiments, the method further includes transmitting, to the UICC, a type-length-value of zero that indicates that a previously-provided partial NSSAI is no longer valid. [0094] In one or more embodiments, the method further includes transmitting, to the UICC, a terminal profile message indicating that the UE is capable of providing the partial NSSAT over a plurality of messages.

[0095] In one or more embodiments, the method further includes discarding the one or more remaining portions of the partial NS SAI.

[0096] In one or more embodiments, the method further includes transmitting, to the UICC, one or more additional messages that include the one or more remaining portions of the partial NS SAI. In some embodiments, the message and the one or more additional messages are envelope messages, and a last message of the one or more additional messages includes an indication of a last envelope message.

[0097] In one or more embodiments, the method further includes receiving, from the UICC and responsive to the indication that there are one or more remaining portions of the partial NSSAI, a request for the one or more remaining portions of the partial NSSAI.

[0098] In some embodiments, the indication that there are one or more remaining portions of the partial NSSAI includes a quantity value.

[0099] In some embodiments, the indication that there are one or more remaining portions of the partial NSSAI is included in a terminal response message.

[0100] In one or more embodiments, the method further includes combining a plurality of served, allowed, rejected, NSSAI into a single envelope message, where the indication that there are one or more remaining portions of the partial NSSAI is included in the length.

[0101] In one or more embodiments, the method further includes providing, to the UICC, an indication of a capability to combine a plurality of other NSSAI information (for example served slice, allowed slice, rejected slice) along with partial NSSAI within a single message.

[0102] The method 700 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.

[0103] Embodiments contemplated herein include one or more non-transitory computer- readable media storing instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 700. In the context of method 700, this non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein). [0104] Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the method 700. Tn the context of method 700, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE).

[0105] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 700. In the context of method 700, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein).

[0106] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 700.

[0107] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the method 700. In the context of method 700, the processor may be a processor of a UE (such as a processor(s) 904 of a wireless device 902 that is a UE, as described herein), and the instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein).

[0108] FIG. 8 illustrates an example architecture of a wireless communication system, according to embodiments described herein. The following description is provided for an example wireless communication system 800 that operates in conjunction with the LTE system standards or specifications and/or 5G or NR system standards or specifications, as provided by 3GPP technical specifications.

[0109] As shown, the wireless communication system 800 includes UE 802 and UE 804 (although any number of UEs may be used). In this example, the UE 802 and the UE 804 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0110] The UE 802 and UE 804 may be configured to communicatively couple with a RAN 806. In embodiments, the RAN 806 may be NG-RAN, E-UTRAN, etc. The UE 802 and UE 804 utilize connections (or channels) (shown as connection 808 and connection 810, respectively) with the RAN 806, each of which comprises a physical communications interface. The RAN 806 can include one or more network devices, such as base station 812 and base station 814, that enable the connection 808 and connection 810. [0111] In this example, the connection 808 and connection 810 are air interfaces to enable such communicative coupling and may be consistent with RAT(s) used by the RAN 806, such as, for example, an LTE and/or NR.

[0112] In some embodiments, the UE 802 and UE 804 may also directly exchange communication data via a sidelink interface 816. The UE 804 is shown to be configured to access an access point (shown as AP 818) via connection 820. By way of example, the connection 820 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 818 may comprise a Wi-Fi® router. In this example, the AP 818 may be connected to another network (for example, the Internet) without going through a CN 824.

[0113] In embodiments, the UE 802 and UE 804 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 812 and/or the base station 814 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0114] In some embodiments, all or parts of the base station 812 or base station 814 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 812 or base station 814 may be configured to communicate with one another via interface 822. In embodiments where the wireless communication system 800 is an LTE system (e.g., when the CN 824 is an EPC), the interface 822 may be an X2 interface. The X2 interface may be defined between two or more network devices of a RAN (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 800 is an NR system (e.g., when CN 824 is a 5GC), the interface 822 may be an Xn interface. The Xn interface is defined between two or more network devices of a RAN (e.g., two or more gNBs and the like) that connect to the 5GC, between a base station 812 (e.g., a gNB) connecting to the 5GC and an eNB, and/or between two eNBs connecting to the 5GC (e.g., CN 824).

[0115] The RAN 806 is shown to be communicatively coupled to the CN 824. The CN 824 may comprise one or more network elements 826, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 802 and UE 804) who are connected to the CN 824 via the RAN 806. The components of the CN 824 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0116] In embodiments, the CN 824 may be an EPC, and the RAN 806 may be connected with the CN 824 via an S I interface 828. In embodiments, the SI interface 828 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 812 or base station 814 and a serving gateway (S-GW), and the Sl-MME interface, which is a signaling interface between the base station 812 or base station 814 and mobility management entities (MMEs).

[0117] In embodiments, the CN 824 may be a 5GC, and the RAN 806 may be connected with the CN 824 via an NG interface 828. In embodiments, the NG interface 828 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 812 or base station 814 and a user plane function (UPF), and the S I control plane (NG-C) interface, which is a signaling interface between the base station 812 or base station 814 and access and mobility management functions (AMFs).

[0118] Generally, an application server 830 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 824 (e.g., packet switched data services). The application server 830 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 802 and UE 804 via the CN 824. The application server 830 may communicate with the CN 824 through an IP communications interface 832.

[0119] FIG. 9 illustrates an example system 900 for performing signaling 938 between a wireless device 902 and a network device 920, according to embodiments described herein. The system 900 may be a portion of a wireless communication system as herein described. The wireless device 902 may be, for example, a UE of a wireless communication system. The network device 920 may be, for example, a base station (e.g., an eNB or a gNB) or a radio head of a wireless communication system.

[0120] The wireless device 902 may include one or more processor(s) 904. The processor(s) 904 may execute instructions such that various operations of the wireless device 902 are performed, as described herein. The processor(s) 904 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. [0121] The wireless device 902 may include a memory 906. The memory 906 may be a non- transitory computer-readable storage medium that stores instructions 908 (which may include, for example, the instructions being executed by the processor(s) 904). The instructions 908 may also be referred to as program code or a computer program. The memory 906 may also store data used by, and results computed by, the processor(s) 904.

[0122] The wireless device 902 may include one or more transceiver(s) 910 (also collectively referred to as a transceiver 910) that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna(s) 912 of the wireless device 902 to facilitate signaling (e.g., the signaling 938) to and/or from the wireless device 902 with other devices (e.g., the network device 920) according to corresponding RATs.

[0123] The wireless device 902 may include one or more antenna(s) 912 (e.g., one, two, four, eight, or more). For embodiments with multiple antenna(s) 912, the wireless device 902 may leverage the spatial diversity of such multiple antenna(s) 912 to send and/or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 902 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 902 that multiplexes the data streams across the antenna(s) 912 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Some embodiments may use single user MIMO (SU-M1MO) methods (where the data streams are all directed to a single receiver) and/or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0124] In some embodiments having multiple antennas, the wireless device 902 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 912 are relatively adjusted such that the (joint) transmission of the antenna(s) 912 can be directed (this is sometimes referred to as beam steering).

[0125] The wireless device 902 may include one or more interface(s) 914. The interface(s) 914 may be used to provide input to or output from the wireless device 902. For example, a wireless device 902 that is a UE may include interface(s) 914 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 910/antenna(s) 912 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0126] The wireless device 902 may include partial NSSAI manager 916. The partial NSSAI manager 916 may be implemented via hardware, software, or combinations thereof. For example, the partial NSSAI manager 916 may be implemented as a processor, circuit, and/or instructions 908 stored in the memory 906 and executed by the processor(s) 904. In some examples, the partial NSSAI manager 916 may be integrated within the processor(s) 904 and/or the transceiver(s) 910. For example, the partial NSSAI manager 916 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 904 or the transceiver(s) 910.

[0127] The partial NSSAI manager 916 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-9, from a wireless device or UE perspective. The partial NSSAI manager 916 may be configured to, for example, perform receiving, from a network device, a control message including partial NSSAI; providing, to a UICC of the UE, a message that includes a portion of the partial NSSAI; and providing, to the UICC, an indication that there are one or more remaining portions of the partial NSSAI.

[0128] The network device 920 may include one or more processor(s) 922. The processor(s) 922 may execute instructions such that various operations of the network device 920 are performed, as described herein. The processor(s) 922 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0129] The network device 920 may include a memory 924. The memory 924 may be a non- transitory computer-readable storage medium that stores instructions 926 (which may include, for example, the instructions being executed by the processor(s) 922). The instructions 926 may also be referred to as program code or a computer program. The memory 924 may also store data used by, and results computed by, the processor(s) 922.

[0130] The network device 920 may include one or more transceiver(s) 928 (also collectively referred to as a transceiver 928) that may include RF transmitter and/or receiver circuitry that use the antenna(s) 930 of the network device 920 to facilitate signaling (e.g., the signaling 938) to and/or from the network device 920 with other devices (e.g., the wireless device 902) according to corresponding RATs. [0131] The network device 920 may include one or more antenna(s) 930 (e.g., one, two, four, or more). Tn embodiments having multiple antenna(s) 930, the network device 920 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0132] The network device 920 may include one or more interface(s) 932. The interface(s) 932 may be used to provide input to or output from the network device 920. For example, a network device 920 of a RAN (e.g., a base station, a radio head, etc.) may include interface(s) 932 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 928/antenna(s) 930 already described) that enables the network device 920 to communicate with other equipment in a network, and/or that enables the network device 920 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the network device 920 or other equipment operably connected thereto.

[0133] The network device 920 may include at least one partial NSSAI manager 934. The partial NSSAI manager 934 may be implemented via hardware, software, or combinations thereof. For example, the partial NSSAI manager 934 may be implemented as a processor, circuit, and/or instructions 926 stored in the memory 924 and executed by the processor(s) 922. In some examples, the partial NSSAI manager 934 may be integrated within the processor(s) 922 and/or the transceiver(s) 928. For example, the partial NSSAI manager 934 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 922 or the transceiver(s) 928.

[0134] The partial NSSAI manager 934 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-9, from a network device perspective. The partial NSSAI manager 934 may be configured to, for example, perform managing partial NSSAI for a UE; and transmitting a control message including partial NSSAI for the UE.

[0135] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein. For example, a baseband processor (or processor) as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, network device, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0136] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form described. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0137] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special -purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

[0138] The systems described herein pertain to specific embodiments but are provided as examples. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0139] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein but may be modified within the scope and equivalents of the appended claims.

Claims

1. A baseband processor comprising a memory and configured to: receive a control message, transmitted from a network device, that includes partial network slice selection assistance information (NSSAI); transmit, to a universal integrated circuit card (UICC), a message that includes a portion of the partial NSSAI; and transmit, to the UICC, an indication that there are one or more remaining portions of the partial NSSAI.

2. The baseband processor of claim 1, further configured to: transmit, to the UICC, a type-length-value of zero that indicates that a previously- provided partial NSSAI is no longer valid.

3. The baseband processor of claim 1 , further configured to: transmit, to the UICC, a terminal profile message indicating that the baseband processor is capable of providing the partial NSSAI over a plurality of messages.

4. The baseband processor of claim 1, further configured to: discard the one or more remaining portions of the partial NSSAI.

5. The baseband processor of claim 1 , further configured to: transmit, to the UICC, one or more additional messages that include the one or more remaining portions of the partial NSSAI.

6. The baseband processor of claim 5, wherein the message and the one or more additional messages are envelope messages, and a last message of the one or more additional messages comprises an indication of a last envelope message.

7. The baseband processor of claim 1, further configured to: receive, from the UICC and responsive to the indication that there are one or more remaining portions of the partial NSSAI, a request for the one or more remaining portions of the partial NSSAI.

8. The baseband processor of claim 1 , wherein the indication that there are one or more remaining portions of the partial NSSAI includes a quantity value.

9. The baseband processor of claim 1 , wherein the indication that there are one or more remaining portions of the partial NSSAT is included in a terminal response message.

10. The baseband processor of claim 1 , further configured to: combine a plurality of served, allowed, rejected, partial NSSAI into a single envelope message; and determine a length of the single envelope message, wherein the indication that there are one or more remaining portions of the NSSAI is included in the length.

11. The baseband processor of claim 1 , further configured to: transmit, to the UICC, an indication of a capability to combine a plurality of other NSSAI information along with partial NSSAI within a single message.

12. A method of wireless communication at a user equipment (UE), comprising: receiving a control message, transmitted from a network device, that includes partial network slice selection assistance information (NSSAI); providing, to a universal integrated circuit card (UICC) of the UE, a message that includes a portion of the partial NSSAI; and providing, to the UICC, an indication that there are one or more remaining portions of the partial NSSAI.

13. The method of claim 12, further comprising: transmitting, to the UICC, a type-length-value of zero that indicates that a previously- provided partial NSSAI is no longer valid.

14. The method of claim 12, further comprising: transmitting, to the UICC, a terminal profile message indicating that the UE is capable of providing the partial NSSAI over a plurality of messages.

15. The method of claim 12, further comprising: discarding the one or more remaining portions of the partial NSSAI.

16. The method of claim 12, further comprising: transmitting, to the UICC, one or more additional messages that include the one or more remaining portions of the partial NSSAI.

17. The method of claim 16, wherein the message and the one or more additional messages are envelope messages, and a last message of the one or more additional messages comprises an indication of a last envelope message.

18. The method of claim 12, further comprising: receiving, from the UICC and responsive to the indication that there are one or more remaining portions of the partial NSSAI, a request for the one or more remaining portions of the partial NSSAI.

19. The method of claim 12, wherein the indication that there are one or more remaining portions of the partial NSSAI includes a quantity value.

20. A user equipment (UE), comprising: a processor; memory; and a universal integrated circuit card (UICC), wherein the processor is configured to cause the UE to: receive a control message, transmitted from a network device, that includes partial network slice selection assistance information (NSSAI); provide, to the UICC, a message that includes a portion of the partial NSSAI; and provide, to the UICC, an indication that there are one or more remaining portions of the partial NSSAI.