Processing slice information with S-NSSAI mapping for UICC

Abstract

A user equipment (UE) is provided for processing slice information having a Single Network Slice Selection Assist Information (S-NSSAI) mapping for a Universal Integrated Circuit Card (UICC) processor. The UE operates by determining whether its baseband processor is busy. Based on the determination that the baseband processor is not busy, the baseband processor transmits a retrieval message to the UE's UICC processor, wherein the retrieval message is transmitted in response to receiving an active command pending message from the UICC processor. The baseband processor receives an active command message from the UICC processor, wherein the active command message corresponds to a request for Single Network Slice Selection Assist Information (S-NSSAI) information corresponding to one or more network slices. Finally, the baseband processor transmits a response message with the S-NSSAI information to the UICC processor.

Description

Cross-references

[0001] This application claims priority to U.S. Non-Provisional Application No. 18 / 926,461, filed October 25, 2024, entitled “HANDLING SLICE INFORMATION WITH S-NSSAI MAPPING FOR UICC,” and U.S. Provisional Application No. 63 / 593,766, filed October 27, 2023, entitled “HANDLING SLICE INFORMATION WITH S-NSSAI MAPPING FOR UICC,” the contents of which are incorporated herein by reference in their entirety. Background Technology Technical Field

[0002] The aspects described herein relate in general to techniques for implementing network slicing in wireless communication systems.

[0003] Related fields

[0004] 5G New Radio (NR) in wireless communications supports a wide range of use cases and applications operating across various bandwidths, as well as diverse sets of User Equipment (UEs) with varying performance and latency requirements. Network slicing is a key architectural concept and technology that enables the creation of multiple virtualized, independent, and logically isolated network instances or slices within a single physical 5G network infrastructure. Each network slice can be customized to meet the specific requirements of different services, applications, or user groups, allowing for efficient resource allocation, optimized performance, and diverse use cases within the network. Summary of the Invention

[0005] Some aspects of this disclosure relate to apparatus and methods for processing slice information having a single network slice selection assist information (S-NSSAI) mapping for a general-purpose integrated circuit card (UICC). For example, some aspects of this disclosure relate to configuring a baseband processor to provide a UICC processor with currently active S-NSSAI mappings, rejected slice information with or without mapping information, configured slice information, and / or allowed slice information.

[0006] Some aspects of this disclosure relate to a UE having a transceiver configured to implement wireless communication with a base station and a baseband processor communicatively coupled to a UICC processor and the transceiver. The baseband processor is configured to determine whether it is in a busy state, which corresponds to UE registration with the network or any other activity. Based on the determination that the baseband processor is not in a busy state, the baseband processor is configured to transmit a retrieval message to the UICC processor, wherein the retrieval message is transmitted in response to receiving an active command pending message from the UICC processor. The baseband processor then receives an active command message from the UICC processor, wherein the active command message corresponds to a request for S-NSSAI-specific information corresponding to one or more network slices. The baseband processor then transmits a response message with the S-NSSAI information to the UICC processor.

[0007] According to some aspects, an active command message is an event list creation command requesting information corresponding to a slice state change event (i.e., the slice state change event is provided as part of an event download slice state information creation command transmitted from the UICC to the terminal). According to some aspects, a response message is an envelope command message including S-NSSAI information (e.g., an event download slice state message), which includes one or more of the following: currently serving s-NSSAI, configured s-NSSAI, rejected s-NSSAI without mapping information, or allowed s-NSSAI with or without mapping information. According to some aspects, an active command message is a provide local information (PLI) command requesting information corresponding to a rejected network slice with S-NSSAI information. According to some aspects, a response message is a terminal response message that includes rejected slice information with mapping information or rejected slice information without mapping information. According to some aspects, a PLI command includes a command qualifier corresponding to the rejected slice information with or without mapping information. According to some aspects, the PLI command includes a command qualifier with a value of seventeen to request rejected slice information. According to some aspects, the first bit of the thirty-seventh byte of the terminal configuration file message indicates support for PLI-rejected slice information. According to some aspects, the active command message is a PLI command requesting information corresponding to a network slice with S-NSSAI mapping. According to some aspects, the response message is a terminal response message that includes rejected slice information with or without mapping information and currently active S-NSSAI mapping information. According to some aspects, the response message is a terminal response message that includes rejected slice information with or without mapping information, and one or more of the following: currently serving S-NSSAI information, allowed S-NSSAI with or without mapping information, or configured slice information.

[0008] The content of this invention is provided for illustrative purposes only, to provide an understanding of the subject matter described herein. Therefore, the features described above are merely illustrative and should not be construed as narrowing the scope or substance of the subject matter of this disclosure. Other features, aspects, and advantages of this disclosure will become apparent from the following detailed description, the accompanying drawings, and the claims. Attached Figure Description

[0009] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the present disclosure and, together with the specification, further serve to explain the principles of the disclosure and enable those skilled in the art to implement and use the disclosure.

[0010] Figure 1An example wireless system is illustrated with an implementation of some aspects of this disclosure for processing slice information having an S-NSSAI mapping for UICC.

[0011] Figure 2 A block diagram of an example system 200 of an electronic device is illustrated, which is an implementation of some aspects of this disclosure for processing technology of slice information having S-NSSAI mapping for UICC.

[0012] Figure 3 An example of a situation is illustrated where, according to some aspects of this disclosure, the baseband processor fails to provide slice status information to the UICC in response to an active command to build an event list.

[0013] Figure 4 Examples of cases are illustrated where, according to some aspects of this disclosure, the baseband processor fails to respond to a PLI active command to provide a rejected slice information to the UICC.

[0014] Figure 5 An example is illustrated where, according to some aspects of this disclosure, the baseband processor provides current slice state information to the UICC in response to an active command to establish an event list.

[0015] Figure 6 An example case is illustrated where, according to some aspects of this disclosure, the baseband processor responds to a Provide Local Information (PLI) active command with a command qualifier to provide rejected slice information to the UICC.

[0016] Figure 7 An example case is illustrated where, according to some aspects of this disclosure, the baseband processor responds to a PLI active command to provide a rejected slice information to the UICC.

[0017] Figure 8 An exemplary terminal configuration file portion is illustrated, according to some aspects of this disclosure, for indicating support for slice information rejected by PLI.

[0018] Figure 9 An exemplary method for processing slice information having S-NSSAI mapping for UICC, performed by a UE according to some aspects of this disclosure, is illustrated.

[0019] Figure 10 It is an example computer system used to implement some aspects or parts thereof.

[0020] This disclosure is described with reference to the accompanying drawings. In the drawings, the same reference numerals generally indicate the same or similarly functional elements. Additionally, the leftmost numeral of the reference numeral usually appears first in the drawing to which that reference numeral is located. Detailed Implementation

[0021] 5G NR use cases include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). These use cases cover a wide range of applications with highly varying requirements. For example, eMBB is designed to meet the high capacity required for high user density scenarios, mMTC services are characterized by a large number of sensors or connected devices that typically send small amounts of non-latency-sensitive data, and URLLC services refer to services expected to have exceptionally low latency and extremely high reliability.

[0022] Network slicing provides a solution for meeting the requirements of all use cases using a common physical network infrastructure. The network infrastructure is divided into multiple network slices to cater to the diverse requirements of various applications and services. 5G NR defines individual Network Slice Selection Auxiliary Information (S-NSSAI) to uniquely identify a network slice. S-NSSAI consists of two fields: Slice Service Type (SST) and Service Differentiator (SD). SST defines the expected behavior of the network slice based on specific characteristics and services, while SD is an optional field.

[0023] Currently, Rel 17 CT6 of the 3GPP specification does not specify instructions to the Universal Subscriber Identification Module (USIM) applet for: (1) allowed and / or denied slices when there is a proactive-command-pending message corresponding to the event download slice status request from the baseband delay; (2) allowed and / or denied slices when the timing of the proactive-command-pending message from the USIM corresponding to the event download slice status request is after the slice has been established; and (3) denied slice information via the terminal response with or without mapping information when the slice information is denied via a Provide Local Information (PLI) command request from a terminal that may not support the event download process.

[0024] To address the aforementioned technical problems, embodiments of this disclosure provide techniques for handling slice information with S-NSSAI mappings for UICC. Some aspects of this disclosure relate to configuring a baseband processor to provide a UICC processor with currently active S-NSSAI information even when the baseband processor delays transmitting a fetch command and / or when the UICC processor delays transmitting an active command pending message to the baseband processor. This currently active S-NSSAI information may include current service information, allowed information, and rejected slice information with or without mapping information. Embodiments of this disclosure also describe extending the provision of Local Information (PLI) active command responses to provide the UICC processor 106 with rejected slice information with or without mapping information.

[0025] Figure 1 An example wireless system 100 is illustrated with an implementation of some aspects of this disclosure for processing slice information having an S-NSSAI mapping for a UICC. The example wireless system 100 is provided for illustrative purposes only and is not intended to limit the disclosed aspects. The wireless system 100 includes, but is not limited to, a base station 108 and a user equipment (UE) 102. The UE 102 includes a baseband processor 104 and a Universal Integrated Circuit Card (UICC) processor 106. Furthermore, a Universal Subscriber Identity Module (USIM) application (commonly referred to as a “SIM card”) is implemented in the UICC of the UE 102. The UICC securely stores UE-specific credentials required for network authentication of the user. Additionally, the UICC card enables the UE 102 to access the appropriate network slice based on service requirements. The baseband processor 104 performs baseband signal processing (e.g., encoding, modulation, data frame formatting, control signaling, etc.), which is typically necessary for performing wireless communication with the BS 108 according to one or more 3GPP standards.

[0026] Depending on some aspects, base station 108 can be a fixed station or a mobile station. Base station 108 can be referred to as a cellular Internet of Things (IoT) base station, evolved Node B (eNB), next-generation Node B (gNB), 5G Node B (NB), or some other equivalent term. In some examples, base station 108 can be interconnected to other base stations or network nodes in the network via various types of backhaul interfaces such as direct physical connections, virtual networks, etc. (not shown).

[0027] Depending on some aspects, UE 102 may be configured to operate based on a wide variety of wireless communication technologies. These technologies may include, but are not limited to, technologies based on 3GPP standards. UE 102 may be stationary or mobile. UE 102 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a desktop computer, a cordless phone, a wireless local loop station, a wireless sensor, a tablet computer, a camera, a video surveillance camera, a gaming device, a netbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component, a smart meter, industrial manufacturing equipment, a GPS device, an Internet of Things (IoT) device, a machine-type communication (MTC) device, an evolved or enhanced machine-type communication (eMTC) device, or any other suitable device configured to communicate via a wireless medium. For example, MTC and eMTC devices may include robots, drones, location tags, etc. Furthermore, UE 102 may be an augmented reality device, a virtual reality device, a mixed reality device, etc.

[0028] According to some aspects, UE 102 may be able to communicate with one or more base stations of radio system 100. According to some aspects, radio system 100 may utilize one or more radio access technologies (RATs) and may have overlapping coverage from one or more RATs. According to some aspects, base station 108 may be part of a next-generation RAN (NG-RAN). According to some aspects, base station 108 is an NR base station. The NR radio access network (RAN) includes NR base stations and a new radio core network (CN). The NR base station may be a next-generation node B (gNB). UE 102 may access external networks via the NR base station and the NR CN.

[0029] According to some aspects, UE 102 accesses multiple network slices via base station 108. Network slices are defined within a Public Land Mobile Network (PLMN) and include resources from both the access network (e.g., NG-RAN) and the core network. A network slice is identified by its S-NSSAI, where S-NSSAI is a concatenation of an 8-bit SST and a 24-bit slice distinguisher. Furthermore, a set of one or more S-NSSAIs is referred to as an NSSAI. 3GPP has defined several categories of NSSAIs, including configured NSSAIs, allowed NSSAIs, requested NSSAIs, and rejected NSSAIs.

[0030] A configured NSSAI is a set of S-NSSAIs available within a specific PLMN. The PLMN can configure UE 102 using one or more configured NSSAIs, and UE 102 can use a configured NSSAI as its default NSSAI. A configured NSSAI can include up to sixteen S-NSSAIs. An allowed NSSAI is a set of S-NSSAIs that the core network has authorized for UE 102. Up to eight network slices can exist within an allowed NSSAI, and therefore UE 102 can be served by up to eight network slices. Furthermore, using all eight network slices will require the UE to establish eight PDU sessions. A requested NSSAI is a set of S-NSSAIs that UE 102 preferably accesses. A requested NSSAI can be a configured or allowed NSSAI, or a combination thereof. UE 102 provides the requested NSSAI to base station 108 in a Radio Resource Control (RRC) establishment completion message.

[0031] A rejected NSSAI is a set of S-NSSAIs for which UE 102 should not attempt to access. 3GPP defines the following NSSAIs: rejected NSSAIs for the current PLMN or Independent Non-Public Network (SNPN); rejected NSSAIs for the current registered area; rejected NSSAIs for failed or revoked NSSAIs; rejected NSSAIs for reaching the maximum number of UEs; alternative NSSAIs; and partially rejected NSSAIs. Depending on some aspects, UE 102 may receive a rejected NSSAI information element that identifies one or more rejected S-NSSAIs. Each rejected S-NSSAI includes an S-NSSAI and an associated reason value.

[0032] According to some aspects, an active UICC (i.e., a UICC capable of issuing active commands) includes a toolkit applet that uses an active command pending message to notify baseband processor 104 that it wishes to transmit an active command. Baseband processor 104 can transmit a fetch command to UICC processor 106, and in response to receiving a fetch command, UICC processor 106 transmits an active command to baseband processor 104. Baseband processor 104 processes the active command and uses an encapsulation command or terminal response to transmit a response to UICC processor 106. Active commands transmitted from UICC processor 106 to baseband processor can include an event list creation command and a provide local information (PLI) command. Using the event list creation command, the UICC provides a list of events for which it wishes the baseband processor to provide details of when those events occurred (e.g., specific event scheduling, slice creation, slice status changes). The UICC uses the PLI command to request baseband processor 104 to pass local information to the UICC, such as network slice information and / or mobile country and network codes of the network on which the user has registered, and this information is transmitted from the network to the baseband processor.

[0033] When baseband processor 104 is busy, it delays transmitting a fetch command to UICC processor 106 in response to an active command pending message. Therefore, baseband processor 104 may not be able to provide the UICC processor 106 with the current active S-NSSAI mapping in response to an event download slice status active command transmitted by UICC processor 106. According to some aspects, embodiments of this document describe enhancing the event download process (e.g., the event download slice status change process) to configure baseband processor 104 to provide the UICC processor 106 with the current active S-NSSAI even when baseband processor 104 delays transmitting the fetch command. This current active S-NSSAI may include current service slice information, allowed slice information, and rejected slice information with or without mapping information. Furthermore, when S-NSSAI is rejected by the network, baseband processor 104 may not be able to provide the UICC with information about the rejected slice in the terminal response. Current standard specifications do not support providing rejected slice information and / or pre-configured slice information in response to PLI active commands. According to some aspects, the implementation of this document describes extended PLI active commands and corresponding terminal responses to provide UICC processor 106 with rejection slice information with or without mapping information.

[0034] Figure 2A block diagram illustrating an example system 200 of an electronic device for processing slice information having or not having corresponding S-NSSAI mappings for UICC, according to implementations of some aspects of this disclosure, is provided. System 200 may represent UE 102 of system 100. System 200 includes a baseband processor 210, a UICC processor 230, one or more transceivers 220a to 220n, a communication infrastructure 240, a memory 250, an operating system 252, an application 254, and an antenna 260. The illustrated system is provided as an exemplary part of system 200, and system 200 may include other circuitry and subsystems. Furthermore, although system 200 is illustrated as separate components, aspects of this disclosure may include any combination of these components, fewer components, or more components.

[0035] Memory 250 may include random access memory (RAM) and / or cache, and may include control logic (e.g., computer software) and / or data. Memory 250 may include other storage devices or memories, such as, but not limited to, hard disk drives and / or removable storage devices / cells. According to some examples, operating system 252 may be stored in memory 250. Operating system 252 can manage data transfer from memory 250 and / or one or more applications 254 to baseband processor 210 and / or one or more transceivers 220a to 220n. In some examples, operating system 252 holds one or more network protocol stacks (e.g., Internet Protocol stack, cellular protocol stack, etc.) that may include multiple logical layers. At the corresponding layer of the protocol stack, operating system 252 includes control mechanisms and data structures to perform the functions associated with that layer.

[0036] According to some examples, application 254 may be stored in memory 250. Application 254 may include applications used by users of wireless system 200 (e.g., user applications). Applications in application 254 may include, but are not limited to, applications such as, but not limited to, wireless streaming, video streaming, remote control, and / or other user applications.

[0037] System 200 may also include communication infrastructure 240. Communication infrastructure 240 provides communication between, for example, baseband processor 210, one or more transceivers 220a to 220n, and memory 250. In some implementations, communication infrastructure 240 may be a bus. Baseband processor 210 and UICC processor 230 operate together with computer instructions stored in memory 250, enabling system 200 of system 100 to implement techniques for processing slice information having S-NSSAI mappings for UICC. Alternatively, baseband processor 210 may be "hard-coded" to implement techniques for processing slice information having S-NSSAI mappings for UICC, as described herein.

[0038] One or more transceivers 220a to 220n transmit and receive communication signals according to some aspects of a technique for enhancing the user experience in low-data use cases with WUS enabled, and may be coupled to antenna 260. Antenna 260 may include one or more antennas that may be the same or different types. One or more transceivers 220a to 220n allow system 200 to communicate with other devices that may be wired and / or wireless. In some examples, one or more transceivers 220a-220n may include processors, controllers, radio components, sockets, plugs, amplifiers, filters, buffers, and similar circuitry / devices for connecting to and communicating over a network. According to some examples, one or more transceivers 220a to 220n may include one or more circuitry for connecting to and communicating over a wired and / or wireless network.

[0039] According to some aspects, one or more transceivers 220a-220n may include a cellular subsystem, a WLAN subsystem, and / or Bluetooth. ™ The subsystems, each comprising its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some specific implementations, one or more transceivers 220a to 220n may include more or fewer systems for communicating with other devices.

[0040] In some examples, one or more transceivers 220a to 220n may include one or more circuits (including a WLAN transceiver) for enabling connectivity and communication via a WLAN network (such as, but not limited to, networks based on the standards described in IEEE 802.11). Additionally or alternatively, one or more transceivers 220a to 220n may include circuits for enabling connectivity and communication via, for example, Bluetooth. ™ Protocol, Bluetooth ™ Low power protocol or Bluetooth ™ One or more circuits for low-power remote protocol connectivity and communication (including Bluetooth) ™ (Transceiver). For example, transceiver 220n may include Bluetooth. ™ Transceiver.

[0041] Additionally, one or more transceivers 220a to 220n may include one or more circuits (including cellular transceivers) for connecting to and communicating over cellular networks such as 5G NR. For example, one or more transceivers 220a-220n may be configured to operate according to one or more of Rel-15, Rel-16, Rel-17 or other versions of 3GPP standards.

[0042] Figure 3An example of a situation is illustrated where, according to some aspects of this disclosure, the baseband processor fails to provide slice status information to the UICC in response to an active command to build an event list.

[0043] According to some aspects, the UICC 106 of UE 102 is an active type UICC, and the baseband processor 104 supports active commands. According to some aspects, when UE 102 is powered on at 302, it triggers the initialization of USIM 304. As part of the USIM initialization process, at 308, the UICC processor 106 transmits an active command pending message to the baseband processor 104. According to some aspects, the active command pending message 308 may be an active command requesting information corresponding to a slice state change event to establish an event list. An active command to establish an event list is a command that provides details about the serving slice, allowed slice, and / or denied slice to the baseband processor 104 whenever the baseband processor 104 detects any change in the S-NSSAI state. For example, the s-NSSAI state may change whenever the network provides the UE with a new allowed, configured, or denied s-NSSAI. The active command pending message may include a status response code 91 xx, where xx indicates the length of the response data (e.g., an active command) from the UICC. When a pending active command message is received, the baseband processor 104 can send an extraction command to the UICC processor 106 to obtain information corresponding to the active command.

[0044] Depending on some aspects, baseband processor 104 may delay transmitting the retrieval command to UICC processor 106, as shown in 310. For example, baseband 104 may be busy performing UE registration 310 and PDU session establishment 312 with BS 108, and therefore delay transmitting the retrieval command to UICC processor 106. During UE registration 310 with BS 108, baseband processor 104 transmits a registration request 310a to BS 108 with the requested NSSAI and the requested mapped NSSAI. Subsequently, BS 108 transmits a registration acceptance message 310b to baseband processor 104 with a list of allowed NSSAIs, configured NSSAIs, and rejected NSSAIs. Baseband processor 104 then transmits a registration completion message 310c to BS 108 to complete the registration process. Once the registration process is complete, at 312, baseband processor 104 performs PDU session establishment to establish a PDU session associated with the S-NSSAI having a Data Network Name (DNN).

[0045] Still referencing Figure 3Once the PDU session establishment 312 is complete, the baseband processor 310 exits the busy state and sends an extraction command 316 to the UICC processor 106. The UICC processor 106 receives the extraction command and sends an active command 318 to the baseband processor 104 requesting an event list creation command corresponding to a slice state change event. According to some aspects, in response to the active command 318 requesting an event list creation command corresponding to a slice state change event, the baseband processor 104 is expected to provide the UICC processor 106 with currently available S-NSSAI information. However, since the baseband processor 104 has already established a network slice, it may not be able to send an encapsulation command to the UICC processor 106 providing current slice information, which may include currently serving slice information, allowed slice information, and rejected slice information with or without mapping information. According to some aspects, the baseband processor 104 may not monitor the slice state after a successful PDU session establishment. Therefore, in response to the received active command 318 to establish an event list corresponding to the request and slice state change event, the baseband processor 104 does not provide the current active S-NSSAI mapping to the UICC processor 106 at 320.

[0046] According to some aspects, the embodiments provided herein describe an enhanced event download process (e.g., an event download slice state change process) to configure baseband processor 104 to provide the UICC processor 106 with the current activity S-NSSAI even when baseband processor 104 is busy registering and therefore delays the transmission of the fetch command in response to receiving an active command pending message from UICC processor 106 requesting an active command to establish an event list corresponding to a slice state change event. The current activity S-NSSAI may include current service slice information, allowed slice information, and rejected slice information with or without mapping information.

[0047] Depending on the circumstances, if the timing of the pending active command message itself occurs after a slice has been established, the slice information may not be provided to the UICC processor 106 even if the baseband processor 104 issues an immediate fetch command to the UICC processor 106. For example, if the pending active command message 314 is transmitted to the baseband processor 104 after a slice has been established, the slice information may not be provided to the UICC 106. Even if the baseband processor 104 immediately transmits the fetch command 316, and the UICC further transmits the establishment event list active command 318 requesting information corresponding to the slice state change event, the baseband processor 104 may still be unable to provide the slice information to the UICC processor 106.

[0048] Depending on some aspects, the UICC processor 106 delays transmitting a pending active command message to the baseband processor 104. The UICC processor 106 triggers the active command pending message as part of the USIM initialization process. However, the UICC processor 106 may transmit the active command pending message to the baseband processor 104 after completing UE registration 310 and PDU session establishment 312. The baseband processor 104 then transmits a fetch command 316 to the UICC processor 106 and receives an active command 318 from the UICC processor 106 requesting information corresponding to slice state change events to establish an event list. However, the baseband processor 104 may not be able to provide the UICC processor 106 with currently available S-NSSAI information in response to the active command 318 requesting information corresponding to slice state change events because the baseband processor 104 has already established one or more network slices.

[0049] According to some aspects, embodiments of this document describe an enhanced event download process (e.g., an event download slice state change process) to configure baseband processor 104 to provide UICC processor 106 with a current active S-NSSAI even when UICC processor 106 delays transmitting an active command pending message to baseband processor 104. The current active S-NSSAI may include current service slice information, allowed slice information, and rejected slice information with or without mapping information.

[0050] Figure 4 Examples of cases are illustrated where, according to some aspects of this disclosure, the baseband processor fails to provide rejected slice information to the UICC in response to the Provide Local Information (PLI) active command.

[0051] According to some aspects, the UICC of UE 102 is an active type UICC, and the baseband processor 104 (e.g., the terminal of UE 104) may not support some active commands. According to some aspects, the baseband processor 104 may or may not support event download active commands from the UICC processor 106. However, the baseband processor 104 may support PLI active commands. According to some aspects, when UE 102 is powered on at 402, it triggers the initialization of USIM 404. The baseband processor 104 then performs UE registration 406 and PDU session establishment 408. During UE registration 406 with BS 108, the baseband processor 104 transmits a registration request 406a to BS 108 with a requested NSSAI or a mapped NSSAI. BS 108 transmits a registration acceptance message 406b to the baseband processor 104 with a list of allowed NSSAIs, configured NSSAIs, and rejected NSSAIs (with or without corresponding mapping information). The baseband processor 104 then sends a registration completion message 406c to the BS 108 to complete the registration process. Once the registration process is complete, the baseband processor 104 executes PDU session establishment 408, whereby the UE 102 can establish a PDU session associated with the S-NSSAI with the DNN.

[0052] According to some aspects, the UICC processor 106 transmits an active command pending message 410 to the baseband processor 104, wherein the active command pending message may correspond to a PLI command for slice information. A PLI command for slice information with S-NSSAI mapping is a command that provides details about the slice with S-NSSAI mapping to the baseband processor 104. Upon receiving the active command pending message, the baseband processor 104 transmits a fetch command 316 to the UICC processor 106 and receives a PLI active command 414 for slice information transmitted from the UICC processor 106.

[0053] According to some aspects, in response to receiving a PLI active command 414 from the UICC processor 106 for slice information with S-NSSAI mapping, the baseband processor 104 transmits information corresponding to the allowed slices with S-NSSAI mapping. However, if any S-NSSAI is rejected (i.e., rejected in the current registered region or in the PLMN), the baseband processor 104 may not be able to provide information about the rejected slice in the terminal response 416. Rejected slice information with or without mapping information may not be provided because current standard specifications do not support providing rejected slice information in response to a PLI active command. Furthermore, current standard specifications do not support providing information corresponding to configured slices to the UICC processor 106. According to some aspects, embodiments herein describe extending the PLI active command and corresponding response to provide the UICC processor 106 with rejected slice information with or without mapping information and / or configured slice information.

[0054] Figure 5 Examples are illustrated in which, according to some aspects of this disclosure, the baseband processor actively provides the UICC with current slice state information in response to an active command that requests an event list corresponding to a slice state change event.

[0055] According to some aspects, when UE 102 is powered on at 502, it triggers the initialization of USIM 504. As part of the USIM initialization process, UICC processor 106 transmits an active command pending message 506 to baseband processor 104. Active command pending message 506 may correspond to an active command requesting the establishment of an event list corresponding to a slice state change event. Upon receiving an active command pending message, baseband processor 104 may transmit a fetch command to obtain the information corresponding to the active command.

[0056] According to some aspects, the baseband processor 104 may delay transmitting the retrieval command to the UICC processor 106. For example, the baseband processor 104 may be busy performing UE registration 508 and PDU session establishment 510, and may delay transmitting the retrieval command to the UICC processor 106. According to some aspects, during UE registration 508 with BS 108, the baseband processor 104 transmits a registration request 508a to BS 108. BS 108 then transmits a registration acceptance message 508b, and the baseband processor 104 transmits a registration completion message 508c to BS 108 to complete the registration process. Once the registration process is complete, the baseband processor 104 performs PDU session establishment 510, in which UE 102 establishes a PDU session associated with an S-NSSAI having a Data Network Name (DNN).

[0057] According to some aspects, the baseband processor 104 may be in a busy state due to UE registration 508 and PDU session establishment 510, and it may delay transmitting the fetch command to the UICC processor 106. According to some aspects, once the PDU session is established, the baseband processor 104 exits the busy state and transmits the fetch command 514 to the UICC processor 106. The UICC processor receives the fetch command and transmits an active command 516 to the baseband processor 104 requesting the establishment of an event list corresponding to the slice state change event.

[0058] According to some aspects, the event download process (e.g., the event download slice state change process) is enhanced so that even when the baseband processor 104 delays the transmission of the retrieval command in response to receiving an active command (e.g., an active command requesting the establishment of an event list corresponding to the slice state change event), the baseband processor 104 provides the UICC processor 106 with the currently active S-NSSAI mapping. Therefore, the baseband processor 104 transmits an encapsulation command 518 with the current slice information to the UICC processor 106, and even when the baseband processor 104 transmits the retrieval command after UE registration 508 and PDU session establishment 510, the baseband processor 104 provides the UICC with all currently available S-NSSAI information (e.g., rejected S-NSSAIs, allowed S-NSSAIs, and a list of S-NSSAIs for services with or without mapping information). The S-NSSAI information provided to the UICC processor 106 may include information corresponding to one or more of the following: current service slices with or without mapping, allowed slices with or without mapping, denied slices with or without mapping, or configured slices.

[0059] Still referencing Figure 5 When the baseband processor 104 is busy, the UICC processor 106 delays sending a pending active command message to the baseband processor. As part of the subsequent USIM initialization process, the UICC processor 106 triggers a pending active command message. However, after completing UE registration 508 and PDU session establishment 510, the UICC processor 106 sends a pending active command message 512 to the baseband processor 104. The baseband processor 104 then sends a fetch command 514 to the UICC processor 106 and receives an establishment event list active command 516 from the UICC processor 106 requesting information corresponding to slice state change events. Depending on some aspects, the baseband processor 104 then sends an encapsulation command 518 with current slice information to the UICC processor 106.

[0060] According to some aspects, if the slice state change event is part of a current event established as by an active command to establish an event list, then when the baseband processor (e.g., ME) detects a change in any S-NSSAI state from the network (including S-NSSAIs to rejected S-NSSAIs, allowed S-NSSAIs, or S-NSSAIs removed from the list of S-NSSAIs for a service), the baseband processor will use the encapsulated event to download the slice state to notify the UICC that the change has occurred. If the slice state is already available in the UE when the UICC provides an event list for the slice state change event, the baseband processor will immediately transmit the encapsulated event to download the slice state. According to some aspects, the encapsulation command 518 may also include the NSSAIs of the current service with or without mapping information, and the configured slice information available at the baseband processor 104.

[0061] Figure 6 Examples of cases are illustrated, in which a baseband processor, in response to a Provide Local Information (PLI) active command with a command qualifier, provides the UICC with rejection information, either with or without mapping information.

[0062] According to some aspects, baseband processor 104 may not support event download active commands. However, baseband processor 104 may support PLI active commands. When UE 102 is powered on at 602, it triggers the initialization of USIM 604. According to some aspects, after USIM initialization 604, the UE performs registration 606 with BS 108. During UE registration 606, baseband processor 104 transmits registration request 606a to BS 108. BS 108 then transmits registration accept message 606b, and baseband processor 104 subsequently transmits registration complete message 606c to BS 108 to complete the registration process. Once the registration process is complete, baseband processor 104 performs PDU session establishment 608, in which UE 102 establishes a PDU session associated with S-NSSAI having a Data Network Name (DNN).

[0063] According to some aspects, the UICC processor 106 transmits an active command pending message 610 to the baseband processor 104, wherein the pending active command message 610 may correspond to a PLI command for rejected slice information (with or without mapping information). Upon receiving the active command pending message 610, the baseband processor 104 transmits a fetch command 612 to the UICC processor 106. Upon receiving the fetch command 612, the UICC processor 106 transmits an active command PLI 614 to the baseband processor 104 for the rejected slice information (with or without mapping information).

[0064] According to some aspects, the active command PLI 614 may include a new command qualifier (e.g., an indicator label) to indicate that the UICC processor 106 can handle a list of rejected slice information with or without mapping information. According to some aspects, the thirty-seventh byte of the terminal information (e.g., bit 1 of the thirty-seventh byte) may be used to indicate support for slice information rejected by the PLI with or without mapping information. According to some aspects, the terminal information may be included in the active command PLI. According to some aspects, the active command PLI 614 may include a command qualifier with a value of seventeen to request rejected slice information with or without mapping information. Other bytes and values ​​may be used, as those skilled in the art will understand.

[0065] Still referencing Figure 6 In response to receiving an active command PLI 614 from the UICC processor 106 regarding rejected slice information with or without mapping information, the baseband processor 104 transmits a terminal response 616 containing information corresponding to the rejected slice information with or without mapping information. If the rejected slice information with or without mapping information is available at the baseband processor 104, the baseband processor 104 includes the rejected slice information with or without mapping information in the terminal response 616. However, if the rejected slice information with or without mapping information is not available at the baseband processor 104, the response length is indicated by a zero value in the terminal response 616.

[0066] UICC processor 106 can transmit an active command PLI 618 with configured slice information and / or new command qualifiers. Baseband processor 104 can respond with a terminal response 620 containing the configured slice information (if available at baseband processor 104). However, if the configured slice information is not available at baseband processor 104, the response length is indicated by a zero value in the terminal response 620.

[0067] Alternatively or additionally, the UICC processor 106 may transmit an active command PLI with new tags and / or new command qualifiers for permitted slice information. The baseband processor 104 may respond using a terminal response with permitted slice information (if available at the baseband processor 106). However, if permitted slice information is not available at the baseband processor 104, the response length is indicated by a zero value in the terminal response.

[0068] According to some aspects, a PLI command with new qualifiers for rejected slice information with or without mapping information provides the UICC processor 106 with the flexibility to request rejected slice information with or without mapping information, independent of the allowed slice information from the baseband processor 104. Furthermore, the PLI command with new qualifiers for rejected slice information with or without mapping information enables the baseband processor 104 to transmit terminal responses smaller than 255 bytes.

[0069] Figure 7 Examples of cases are illustrated whereby, according to some aspects of this disclosure, the baseband processor responds to a Provide Local Information (PLI) active command to provide the UICC with or without rejection slice information, whether or not it has mapping information.

[0070] Depending on some aspects, baseband processor 104 may not support the event download process and related active commands. However, baseband processor 104 can support PLI active commands. At 702, UE 102 is powered on, and after USIM initialization 704, the UE performs registration with BS 108 706. Baseband processor 104 transmits a registration request 706a to BS 108. BS 108 then transmits a registration acceptance message 706b, and baseband processor 104 subsequently transmits a registration completion message 706c to NG-RAN to complete the registration process. Once the registration process is complete, baseband processor 104 performs PDU session establishment 708.

[0071] According to some aspects, the UICC processor 106 transmits an active command pending message 710 to the baseband processor 104. The pending active command message 710 may correspond to a PLI command for slice information. Upon receiving the active command pending message 710, the baseband processor 104 transmits a fetch command 712 to the UICC processor 106. Next, upon receiving the fetch command 712, the UICC processor 106 transmits an active command PLI 714 to the baseband processor 104 to request slice information.

[0072] Still referencing Figure 7The baseband processor 104 then transmits a terminal response 716 with a list of rejected slices, which may or may not have S-NSSAI mapping information (if available). According to some aspects, the PLI command response is extended to include additional information such as a list of rejected slices with S-NSSAI mapping and a list of available currently serving S-NSSAIs. According to some aspects, when receiving active command PLI slice information, the baseband processor 104 is expected to respond using the rejected slice information with or without mapping information and the slice information with S-NSSAI mapping. According to some aspects, the terminal response 716 may include information corresponding to configured slices and / or allowed slices with or without S-NSSAI mapping at UE 102, as well as serving slice information with S-NSSAI mapping.

[0073] According to some aspects, in order to deal with such Figures 5 to 7 The illustrated slice information with S-NSSAI mapping for UICC may include the following amendments in 3GPP TS 131.11:

[0074] Clause 5.2: A new bit in the terminal configuration file used to indicate support for providing local information (support for slice information indicating rejection with or without mapping information). Support for providing local information, and slice information with or without mapping information.

[0075] Clause 6.4.15: In PLI—Add a list of rejected slice information. When a request is made for a list of rejected slice information with or without mapping information, the list of rejected slice information is returned.

[0076] Clause 6.8: Include rejected slice information in the terminal response, and therefore increase the command header length of the terminal response accordingly. Rejected slice information (only required in response to providing local information (list of rejected slice information in the active command))

[0077] Clause 6.8.7: Local information updates to include rejected S-NSSAI mapping information. If the UICC has already requested a list of rejected slices, the terminal response should include the list of rejected slices until the terminal responds to the APDU command size limit. If no rejected slice information is available, the corresponding data object should have a length of zero.

[0078] Clause 7.5.27.1: An additional condition has been added that allows the baseband to provide requested slice information if the UE later retrieves an active command. If the slice state is already available in the UE when the UICC provides the establishment event list: If there is an event list for slice state change events (i.e., an active command requesting an establishment event list corresponding to a slice state change event), the baseband should immediately transmit the encapsulation (event download—slice state).

[0079] Clause 8.6: Command Details—Additional values ​​for PLI command qualifiers reserved for handling S-NSSAI commands that refuse to comply.

[0080] Clause 8.151: Pursuant to Clause 9.11.3.46 of TS 24.501, the rejected slice does not have mapping information (the rejected S-NSSAI encoding is based on...). Figure 9 .11.3.46.2—Starting from octet 2), therefore this clause was corrected to remove the mapping information.

[0081] Clause 9.3: In accordance with the amended Clause 8.151, the name “Rejected Slice Information Label” has been corrected to avoid the use of the term “mapping information”.

[0082] Figure 8 An exemplary terminal profile portion according to some aspects of this disclosure is illustrated for indicating support for slice information rejected by a PLI, whether or not it has mapping information. According to some aspects, the thirty-seventh byte of the terminal information is used to indicate support for slice information rejected by a PLI. According to some aspects, bit b1 802 indicates support for slice information rejected by a PLI. According to some aspects, an active command PLI includes a command qualifier having a value of seventeen to request rejected slice information, whether or not it has mapping information. This disclosure is not limited to the thirty-seventh byte or the value 17; other bytes and values ​​may be used, as those skilled in the art will understand.

[0083] Figure 9 An exemplary method 900, performed by a UE according to some aspects of this disclosure, for processing slice information having S-NSSAI mapping for UICC, is illustrated. For convenience and not limitation, further details may be provided. Figures 1 to 8 To describe the components Figure 9 ,For example, Figure 9 The functions can be performed by UE 102. For example, baseband processor 104 can be combined with... Figure 2 Other components perform or enable execution Figure 9 The function. Method 900 can also be derived from... Figure 2 System 200 and / or Figure 10The method is executed by computer system 1000. However, method 900 is not limited to the specific aspects depicted in the figures, and other systems can be used to execute the method, as those skilled in the art will understand. It should be understood that not all operations may be necessary, and these operations may not be performed according to... Figure 9 Perform them in the same order as shown.

[0084] At 902, the baseband processor 104 determines whether it is in a busy state corresponding to the UE 102's registration with the network. Depending on some aspects, the baseband processor 104 may be in a busy state due to performing UE registration and PDU session establishment, and may delay transmitting the fetch command to the UICC processor 106. Alternatively or additionally, the baseband processor 104 may be in a busy state due to performing any activity that may require the baseband processor 104 to delay transmitting an immediate fetch message to the UICC processor 106. If the baseband processor 104 is not in a busy state, the method proceeds to 904.

[0085] At 904, based on the determination that baseband processor 104 is not in a busy state, baseband processor 104 transmits a fetch message to UICC processor 106. The fetch message is transmitted in response to receiving an active command pending message from UICC processor 106. According to some aspects, the UICC of UE 102 is an active type UICC, and baseband processor 104 can support active commands. When a UICC has an active request to be transmitted to baseband processor 104, it first transmits an active command pending message to baseband processor 104. Upon receiving the active command pending message, baseband processor 104 transmits a fetch command to obtain information corresponding to the active command. However, in some aspects, baseband processor 104 only transmits the fetch command to UICC processor 106 when baseband processor 106 is not in a busy state.

[0086] At 906, the baseband processor 104 receives an active command message from the UICC processor 106. This active command message corresponds to a request for Select Auxiliary Information (S-NSSAI) mapping information for a single network slice corresponding to one or more network slices. According to some aspects, the active command message may be an active command requesting the establishment of an event list corresponding to a slice state change event. According to some aspects, the active command message may be a Provide Local Information (PLI) command requesting information corresponding to a rejected network slice with S-NSSAI mapping. According to some aspects, the active command message may be a PLI command requesting information corresponding to a network slice with S-NSSAI mapping.

[0087] According to some aspects, proactive PLI commands may include new command qualifiers (e.g., indicator labels) to handle a list of rejected slice information with or without mapping information. According to some aspects, the 37th byte of the terminal information may be used to indicate support for slice information rejected by the PLI with or without mapping information. Furthermore, proactive PLI commands may include a command qualifier with a value of 17 to request rejected slice information with or without mapping information.

[0088] At 908, the baseband processor 104 transmits a response message containing S-NSSAI mapping information to the UICC processor 106. According to some aspects, the response message may be a terminal response message including rejected slice information with S-NSSAI mapping. Alternatively, the response message may be an encapsulated command message including currently active S-NSSAI mapping information. Alternatively, the response message may be a terminal response message including rejected slice information with S-NSSAI mapping and currently active S-NSSAI mapping information.

[0089] According to some aspects, upon receiving an active command PLI for slice information with S-NSSAI mapping, the baseband processor 104 transmits a terminal response containing a list of rejected slices with S-NSSAI mapping and a list of currently served S-NSSAIs (if available). According to some aspects, the response to the active PLI command (e.g., a terminal response from the baseband processor 104) is extended to include current slice information, such as serving slice information, configured slice information, rejected slice information, and / or allowed slices with or without mapping information. According to some aspects, when receiving active command PLI slice information, the baseband processor 104 is expected to respond using rejected slice information with or without mapping information and slice information with S-NSSAI mapping. According to some aspects, the baseband processor 104 transmits a terminal message to the UICC processor 106 containing configured slice information (if available at the baseband processor 104). However, if the configured slice information is not available at the baseband processor 104, the response length is indicated by a zero value in the terminal response. According to some aspects, the baseband processor 104 transmits a terminal message to the UICC processor 106, which contains information corresponding to an allowed slice with mapping (if available at the baseband processor 104). However, if the allowed slice information is not available at the baseband processor 104, the response length is indicated by a zero value in the terminal response.

[0090] Various aspects may, for example, use one or more computer systems (such as...) Figure 10The computer system 1000 shown herein is used to implement this functionality. The computer system 1000 can be any well-known computer capable of performing the functions described herein, such as... Figure 1 UE 102. Computer system 1000 includes one or more processors (also referred to as central processing units or CPUs), such as processor 1004. Processor 1004 is connected to communication infrastructure 10010 (e.g., a bus). Computer system 1000 also includes user input / output devices 1003, such as monitors, keyboards, pointing devices, etc., that communicate with communication infrastructure 1006 via user input / output interface 1002. Computer system 1000 also includes main memory or primary memory 1006, such as random access memory (RAM). Main memory 1008 may include one or more levels of cache. Main memory 1008 already stores control logic (e.g., computer software) and / or data.

[0091] The computer system 1000 may also include one or more secondary storage devices or memories 1010. Secondary storage 1010 may include, for example, a hard disk drive 1012 and / or a removable storage device or drive 1014. The removable storage drive 1014 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and / or any other storage device / drive.

[0092] Removable storage drive 1014 can interact with removable storage unit 1018. Removable storage unit 1018 includes a computer-usable or readable storage device on which computer software (control logic) and / or data are stored. Removable storage unit 1018 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disk, and / or any other computer data storage device. Removable storage drive 1014 reads from and / or writes to removable storage unit 1018 in a well-known manner.

[0093] According to some aspects, secondary storage 1010 may include other components, tools, or other methods for allowing computer system 1000 to access computer programs and / or other instructions and / or data. Such components, tools, or other methods may include, for example, removable storage unit 1022 and interface 1020. Examples of removable storage unit 1022 and interface 1020 may include a program box and box interface (such as an interface present in video game devices), a removable memory chip (such as EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0094] Computer system 1000 may also include a communication or network interface 1024. Communication interface 1024 enables computer system 1000 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 1028). For example, communication interface 1024 may allow computer system 1000 to communicate with remote device 1028 via communication path 1026, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic and / or data may be sent to and from computer system 1000 via communication path 1026.

[0095] The operations described in the foregoing aspects can be implemented in various configurations and architectures. Therefore, some or all of the operations described in the foregoing aspects can be performed in hardware, software, or both. In some aspects, tangible, non-transitory devices or articles of art include tangible, non-transitory computer-usable or readable media on which control logic (software) is stored, also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 1000, main memory 1008, secondary storage 1010, and removable storage units 1018 and 1022, and tangible articles embodying any combination thereof. Such control logic, when executed by one or more data processing devices (such as computer system 1000), causes such data processing devices to operate as described herein.

[0096] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 10 The aspects of this disclosure may be implemented and used with data processing devices, computer systems, and / or computer architectures other than those shown herein. Specifically, the aspects may operate in conjunction with specific implementations of software, hardware, and / or operating systems other than those described herein.

[0097] It should be understood that the detailed description section, rather than the summary and abstract section, is intended to interpret the claims. The summary and abstract section may set forth one or more, but not all, exemplary aspects of this disclosure as contemplated by the inventors, and is therefore not intended to limit this disclosure or the appended claims in any way.

[0098] Although this disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that this disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, the aspects are not limited to the software, hardware, firmware, and / or entities illustrated in the figures and / or described herein. Furthermore, the aspects (whether explicitly described herein or not) have significant utility in fields and applications beyond those described herein.

[0099] This document has described aspects using functional building blocks that exemplify specific implementations of functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative aspects may perform functional blocks, steps, operations, methods, etc., in a different order than that described herein.

[0100] References to “an aspect,” “aspect,” “an example,” “example,” or similar phrases herein indicate that the aspect described may include a particular feature, structure, or characteristic, but each aspect may not necessarily include that particular feature, structure, or characteristic. Furthermore, such wording does not necessarily refer to the same aspect. Additionally, when a particular feature, structure, or characteristic is described in conjunction with an aspect, whether or not it is explicitly mentioned or described herein, the combination of those features, structures, or characteristics with other aspects is within the knowledge of a person skilled in the art.

[0101] The breadth and scope of this disclosure should not be limited by any of the exemplary aspects described above, but should be defined solely by the following claims and their equivalents.

[0102] This disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with robust privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to privacy policies and measures that are recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable entity purposes and should not be shared or sold outside of these legitimate purposes. Furthermore, such collection / sharing should only occur upon receipt of informed consent from the user. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to such personal information data comply with the privacy policies and procedures of those other entities. Furthermore, such entities may be subject to third-party assessments to demonstrate their compliance with widely accepted privacy policies and privacy practices. Moreover, policies and measures should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including considerations of specific jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Transfer and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: A transceiver configured to enable wireless communication; Universal Integrated Circuit Card (UICC) processor; and A baseband processor, communicatively coupled to the UICC processor and the transceiver, wherein the baseband processor is configured to: Determine whether the baseband processor is in a busy state; Based on the determination that the baseband processor is not in the busy state, an extraction message is transmitted to the UICC processor, wherein the extraction message is transmitted in response to receiving an active command pending message from the UICC processor; The UICC processor receives an active command message, wherein the active command message corresponds to a request for selectable auxiliary information (S-NSSAI) information for a single network slice corresponding to one or more network slices; as well as A response message containing the S-NSSAI information is transmitted to the UICC processor.

2. The UE according to claim 1, wherein the active command message is an active command requesting the establishment of an event list corresponding to the slice state change event.

3. The UE according to claim 2, wherein the response message is an encapsulated command message including the S-NSSAI information, the S-NSSAI information including one or more of the following: current service S-NSSAI, configured S-NSSAI, rejected S-NSSAI with or without mapping information, or allowed S-NSSAI with or without mapping information.

4. The UE according to claim 1, wherein the active command message is a Provide Local Information (PLI) command that requests or rejects information corresponding to network slices.

5. The UE according to claim 4, wherein the response message is a terminal response message including rejected slice information with mapping information or rejected slice information without mapping information.

6. The UE of claim 4, wherein the PLI command includes a command qualifier corresponding to the rejected slice information.

7. The UE of claim 4, wherein the PLI command includes a command qualifier having a value of seventeen to request rejection of slice information.

8. The UE according to claim 1, wherein the baseband processor is further configured to: A terminal profile message is transmitted to the UICC processor, wherein the first bit of the thirty-seventh byte of the terminal profile message indicates support for slice information rejected by the PLI.

9. A method of operating user equipment (UE), the method comprising: Determine whether the UE's baseband processor is in a busy state; Based on the determination that the baseband processor is not in the busy state, the baseband processor transmits an extraction message to the UE's Universal Integrated Circuit Card (UICC) processor, wherein the extraction message is transmitted in response to receiving an active command pending message from the UICC processor; The baseband processor receives an active command message from the UICC processor, wherein the active command message corresponds to a request for selecting auxiliary information (S-NSSAI) mapping information for a single network slice corresponding to one or more network slices; as well as A response message containing the S-NSSAI mapping information is transmitted to the UICC processor.

10. The method according to claim 9, wherein the active command message is an active command requesting the establishment of an event list corresponding to the slice state change event.

11. The method of claim 10, wherein the response message is an encapsulated command message including the S-NSSAI information, the S-NSSAI information including one or more of the following: current service S-NSSAI, configured S-NSSAI, rejected S-NSSAI with or without mapping information, or allowed S-NSSAI with or without mapping information.

12. The method of claim 9, wherein the active command message is a Provide Local Information (PLI) command that requests or rejects information corresponding to network slices.

13. The method of claim 12, wherein the response message is a terminal response message including rejected slice information with mapping information or rejected slice information without mapping information.

14. The method of claim 12, wherein the PLI command includes a command qualifier having a value of seventeen to request rejection of slice information.

15. The method according to claim 9, further comprising: A terminal profile message is transmitted to the UICC processor, wherein the first bit of the thirty-seventh byte of the terminal profile message indicates support for slice information rejected by the PLI.

16. A non-transitory computer-readable medium (CRM) having instructions stored thereon, the instructions causing the user equipment (UE) to perform operations including the following when executed by a processor: Determine whether the UE's baseband processor is in a busy state; Based on the determination that the baseband processor is not in the busy state, the baseband processor transmits an extraction message to the UE's Universal Integrated Circuit Card (UICC), wherein the extraction message is transmitted in response to receiving an Active Command Pending message from the UICC processor; The baseband processor receives an active command message from the UICC processor, wherein the active command message corresponds to a request for selecting auxiliary information (S-NSSAI) mapping information for a single network slice corresponding to one or more network slices; as well as A response message containing the S-NSSAI mapping information is transmitted to the UICC processor.

17. The non-transient CRM according to claim 16, wherein the active command message is an active command requesting the creation of an event list corresponding to a slice state change event.

18. The non-transient CRM of claim 17, wherein the response message is an encapsulated command message including the S-NSSAI information, the S-NSSAI information including one or more of the following: current service S-NSSAI, configured S-NSSAI, rejected S-NSSAI with or without mapping information, or permitted S-NSSAI with or without mapping information.

19. The non-transient CRM of claim 16, wherein the active command message is a Provide Local Information (PLI) command that requests or rejects information corresponding to network slices.

20. The non-transient CRM of claim 19, wherein the response message is a terminal response message, the terminal response message including rejected slice information with and / or without mapping information, and one or more of the following: current service S-NSSAI information, allowed S-NSSAI with or without mapping information, or configured slice information.

Images