Enhancing slice information and data network name association

By integrating DNN information with slice information and data connection status changes in UICC requests, the proposed solution addresses the lack of association in current systems, ensuring accurate network configuration and billing in wireless communication.

WO2026236305A1PCT designated stage Publication Date: 2026-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/026815
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-06
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Current wireless communication systems lack the ability to provide associated Data Network Name (DNN) information with Single Network Slice Selection Assistance Information (S-NSSAI) when requested by a universal integrated circuit card (UICC), and also fail to include slice information with data connection status changes, leading to potential issues in network connectivity and billing accuracy.

Method used

The proposed solution involves enhancing the UICC to request and receive DNN information along with slice information or data connection status changes, using modified command structures and response formats to include DNN lists in the Provide Local Information (PLI) and Event Download commands.

Benefits of technology

This approach ensures accurate DNN and slice information association, preventing network connectivity failures and enabling precise billing by providing the necessary network configuration details to the UICC.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026026815_12112026_PF_FP_ABST
    Figure US2026026815_12112026_PF_FP_ABST
Patent Text Reader

Abstract

An apparatus configured to generate, for transmission from a universal integrated circuit card (UICC) to a terminal, a command comprising a request for one or more of slice information, a change in slice status, or a change in data connection status and process, by the UICC, a response from the terminal, wherein, when the command requests the slice information or the change in slice status, the response includes associated data network name (DNN) information along with the slice information or the change in slice status and, when the command requests the change in data connection status, the response includes associated slice information along with DNN information specified in the change in data connection status.
Need to check novelty before this filing date? Find Prior Art

Description

Attorney Docket No . 30164 / 104402Ref . No . P71760WO1Enhancing Slice Information and Data Network Name Association Inventors : Stanley M. Mayalil, Arjun Ramesh Shetty, Karthik Bangalore Sathyanarayana, Nitin Kuppelur, Raj kumar Krishnaperumal , Roland Gruber and Vivek G. GuptaBackground

[0001] Wireless communication systems are rapidly growing in usage . Further, wireless communication technology has evolved from voice-only communications to also include the transmission of data, such as Internet and multimedia content . As demand for wireless communication systems grows and new use cases for wireless communication arise, there is a seemingly continual need to develop next generation wireless communication techniques and standards . One such developing concept may include network slicing, which may allow a network operator to create different "network slices" configured to address different wireless communication use cases and scenarios in a customized manner.

[0002] In 5G, a DNN (Data Network Name) may be coupled with a network slice, so as to provide a customized set of network resources for special services . The DNN identifies the external network that a User Equipment (UE) should connect to while establishing a data connection (for example, a Protocol Data Unit (PDU) session) . The data connection may be to a public internet, private enterprise network, specific cloud application, or content delivery network. Based on the DNN, the traffic rules are handled and dedicated Quality of Service (QoS) and slicing is provided for the user for the specific slices . Based on the used DNN and network slice, a PCF (policy charging function) of the network operator may regulate billing for the user .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0003] Knowledge of a DNN associated with a Single Network Slice Selection Assistance Information ( S-NSSAI ) may be beneficial for a universal integrated circuit card (UICC) on the UE . However, currently the associated DNN information cannot be provided in a response to a request for slice information .Thus, there may be a need for a mechanism to provide the DNN associated with the respective served and active slice S-NSSAI .

[0004] In a similar manner, when the UICC requests a data connection status change, the DNN is provided in response to the request, but currently the associated slice is not provided .That is , when the mobile equipment (ME) informs that a data connection status change has occurred, currently no associated slice ( s ) information is provided with the DNN. Accordingly, there may be a need for a mechanism to provide the associated slice ( s ) information together with the DNN in response to a request for a data connection status change .Summary

[0005] Some example embodiments are related to an apparatus having memory coupled to processing circuitry, the processing circuitry configured to generate, for transmission from a universal integrated circuit card (UICC) to a terminal , a command comprising a request for one or more of slice information, a change in slice status , or a change in data connection status and process , by the UICC, a response from the terminal , wherein, when the command requests the slice information or the change in slice status , the response includes associated data network name (DNN) information along with the slice information or the change in slice status and, when theAttorney Docket No . 30164 / 104402Ref . No . P71760WO1command requests the change in data connection status, the response includes associated slice information along with DNN information specified in the change in data connection status .

[0006] Other example embodiments are related to an apparatus having memory coupled to processing circuitry, the processing circuitry configured to process, based on signaling from a universal integrated circuit card (UICC) , a command comprising a request for one or more of slice information, a change in slice status, or a change in data connection status and generate, for transmission from a terminal to the UICC, a response, wherein, when the command requests the slice information or the change in slice status, the response includes associated data network name (DNN) information along with the slice information or the change in slice status and, when the command requests the change in data connection status, the response includes associated slice information along with DNN information specified in the change in data connection status .Brief Description of the Drawings

[0007] Fig. 1 shows an example network arrangement according to various example embodiments .

[0008] Fig. 2 shows an example UE according to various example embodiments .

[0009] Fig. 3 is a table showing an example structure of an example envelope for a data connection status change according to various example embodiments .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0010] Fig. 4 is a flow diagram that shows an example method of requesting currently available slice information according to various example embodiments .

[0011] Fig. 5 is a flow diagram that shows an example method 500 of requesting current slice information if available, and also any further slice status change event according to various example embodiments .

[0012] Fig. 6 is a flow diagram that shows an example method of requesting a data connection status change event according to various example embodiments .

[0013] Fig. 7 is a table that shows an example structure of an example TERMINAL RESPONSE according to various example embodiments .

[0014] Fig. 8A is a table that shows an example structure of an ENVELOPE (EVENT DOWNLOAD) - Slices Status data structure according to various example embodiments .

[0015] Fig. 8B is a table that shows an example structure of an example DNN list data obj ect according to various example embodiments .

[0016] Fig. 8C is a table that shows an example structure of an example DNN data obj ect as set forth in TS . 2 . 501

[0070] clause 9. 11. 2. IB .

[0017] Fig. 9A is a table that shows an example structure of an alternate example DNN list data object according to various example embodiments .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0018] Fig. 9B shows an example byte coding as set forth in 3GPP TS 31.111, clause 8.150 for indicating that mapping is provided for slice information according to various example embodiments .

[0019] Fig. 10 is a table that shows an example structure of an ENVELOPE (EVENT DOWNLOAD) - Data Connection Status Change data structure according to various example embodiments .

[0020] Fig. 11 is a table that shows an example structure of a S-NSSAI value data obj ect according to various example embodiments .Detailed Description

[0021] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals . The example embodiments relate to providing enhanced slice (s) information and DNN association.

[0022] The example embodiments are described with regard to a user equipment (UE) . However, reference to a UE is merely provided for illustrative purposes . The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any electronic component .

[0023] The example embodiments are also described with reference to a 5G New Radio (NR) network. However, the example embodiments may also be implemented in other types of networks,Attorney Docket No . 30164 / 104402Ref . No . P71760WO1including but not limited to LTE networks, future evolutions of the cellular protocol ( 6G networks) , or any other type of network that uses network slice information.

[0024] The example embodiments allow a UICC to obtain knowledge of the Single Network Slice Selection Assistance Information (S-NSSAI ) associated DNN when slice (s) information is requested by the UICC . The example embodiments provide the DNN associated with the respective served and active slice S-NSSAI to the UICC along with the requested slice (s) information. In a similar manner, when the UICC requests a data connection status change, the example embodiments provide the UICC with the associated slice (s) information along with the specified DNN in response to a request for a data connection status change . The example embodiments will be described in greater detail below. Although the description of the example embodiments herein may use the term UICC, the concepts described herein also apply for terminals that have an embedded UICC (eUICC) (e . g. , eSIM profiles when eSIMs / eUICCs are used) .

[0025] Fig. 1 shows an example network arrangement 100 according to various example embodiments . The example network arrangement 100 includes a UE 110. The UE 110 may be any type of electronic component that is configured to communicate via a network, e . g. , mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (loT) devices, etc . An actual network arrangement may include any number of UEs being used by any number of users . Thus, the example of one UE 110 is merely provided for illustrative purposes . The example networkAttorney Docket No . 30164 / 104402Ref . No . P71760WO1arrangement 100 al so includes a UE 112 . The UE 112 may be functionally equivalent to the UE 110 .

[0026] The UEs 110 and 112 may be conf igured to communicate with one or more networks . In the example o f the network arrangement 100 , the network with which the UEs 110 and 112 may wireles s ly communicate i s a 5G NR radio acces s network ( RAN) 120 . However , the UE 110 may al so communicate with other types o f networks ( e . g . , 5G cloud RAN, a next generation RAN (NG-RAN) , a legacy cel lular network, etc . ) and the UE 110 may al so communicate with networks over a wired connection . Regarding the example embodiments , the UEs 110 and 112 may establ i sh a connection with the 5G NR RAN 120 . There fore , the UE 110 may have a 5G NR chipset to communicate with the NR RAN 120 . The UEs 110 and 112 may communicate with the one or more networks .

[0027] The 5G NR RAN 120 may be portions o f a cel lular network that may be deployed by a network carrier ( e . g . , Veri zon, AT &T , T-Mobile , etc . ) . The RAN 120 may include cel ls or base stations that are configured to send and receive traf f ic from UEs that are equipped with the appropriate cel lular chip set . In thi s example , the 5G NR RAN 120 includes the gNB 120A. However , re ference to a gNB i s merely provided for i l lustrative purposes , any appropriate base station or cel l may be deployed ( e . g . , Node Bs , eNodeBs , HeNBs , eNBs , gNBs , gNodeBs , macrocell s , microcel l s , small cell s , femtocell s , etc . ) .

[0028] Any association procedure may be performed for the UEs 110 and 112 to connect to the 5G NR RAN 120 . For example , as di scus sed above , the 5G NR RAN 120 may be associated with a particular network carrier where the UE 110 and / or the userAttorney Docket No . 30164 / 104402Ref . No . P71760WO1thereo f has a contract and credential information ( e . g . , stored on a S IM card) . Upon detecting the presence o f the 5G NR RAN 120 , the UE 110 may transmit the corresponding credential information to as sociate with the 5G NR RAN 120 . More speci f ically, the UEs 110 and 112 may as sociate with a speci fic cel l ( e . g . , gNB 120A) .

[0029] The network arrangement 100 al so includes a cel lular core network 130 , the Internet 140 , an I P Multimedia Subsystem ( IMS ) 150 , and a network services backbone 160 . The cellular core network 130 manages the traf f ic that f lows between the cel lular network and the Internet 140 . The IMS 150 may be general ly described as an architecture for del ivering multimedia services to the UEs 110 and 112 us ing the IP protocol . The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UEs 110 and 112 . The network services backbone 1 60 is in communication either directly or indirectly with the Internet 140 and the cel lular core network 130 . The network services backbone 1 60 may be generally described as a set of components ( e . g . , servers , network storage arrangements , etc . ) that implement a suite o f services that may be used to extend the functionalities o f the UE 110 in communication with the various networks .

[0030] Fig . 2 shows an example UE 110 according to various example embodiments . The UE 110 wi l l be described with regard to the network arrangement 100 o f Fig . 1 . The UE 110 may represent any electronic device and may include a proces sor 205 , a memory arrangement 210 , a display device 215 , an input / output ( I / O ) device 220 , a transceiver 225 , and other components 230 . The other components 230 may include , for example , an audio inputAttorney Docket No . 30164 / 104402Ref . No . P71760WO1device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, sensors to detect conditions of the UE 110, etc . A UICC 240 may also be included in the UE 110. In one embodiment, the UICC 240 may be a hardware component embedded into the UE 110 (eUICC) configured to store a number of carrier profiles .

[0031] The processor 205 may be configured to execute a plurality of engines for the UE 110. For example, the engines may include a Slice Information and Associated DNN Engine 235 for performing operations related to providing a DNN associated with the respective served and active slice S-NSSAI to the UICC along with requested slice (s) information and providing the UICC with the associated slice (s) information along with the DNN in response to a request for a data connection status change .

[0032] The above referenced engine being an application (e . g. , a program) executed by the processor 205 is only an example . The functionality associated with the engines may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e . g. , an integrated circuit with or without firmware . For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications . In addition, in some UEs, the functionality described for the processor 205 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0033] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to show data to a user while the I / O device 220 may be a hardware component that enables the user to enter inputs . The display device 215 and the I / O device 220 may be separate components or integrated together such as a touchscreen. The transceiver 225 may be a hardware component configured to establish a connection with the 5G-NR RAN 120. Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e . g. , set of consecutive frequencies) . The transceiver 225 includes circuitry configured to transmit and / or receive signals (e . g. , control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein. The processor 205 may be operably coupled to the transceiver 225 and configured to receive from and / or transmit signals to the transceiver 225. The processor 205 may be configured to encode and / or decode signals (e . g. , signaling from a base station of a network) for implementing any one of the methods described herein.

[0034] In 5G, a DNN (Data Network Name) may be coupled with a network slice, so as to provide a customized set of network resource for special services . The DNN identifies the external network that User Equipment (UE) should connect to while establishing a data connection (for example, a Protocol Data Unit (PDU) session) . The data connection may be to a public internet, private enterprise network, specific cloud application, or content delivery network. Based on the DNN, the traffic rules are handled and dedicated Quality of Service (QoS)Attorney Docket No . 30164 / 104402Ref . No . P71760WO1and slicing is provided for the user for the specific slices . Based on the used DNN and network slice, a PCF (policy charging function) on the network operator may regulate billing for the user .

[0035] Knowledge of the S-NSSAI associated DNN may be beneficial for UICC . However, currently the associated information cannot be provided. For example, in one issue, when the UICC requests slice (s) information, the slice (s) information is provided, but currently the DNN association is not provided. Likewise, when the mobile equipment (ME) informs the UICC of slicing information changes (served slices, allowed slices, configured slices, and / or rej ected slices) , the DNN association is not provided. In a second issue, when the UICC requests a data connection status change, the DNN is provided, but currently the associated slice is not provided. That is, when the ME informs that a data connection status change has occurred, currently no associated slice (s) information is provided .

[0036] It is proposed herein that with respect to the first issue mentioned above, when the UICC requests the terminal (ME) to provide the current slice information or any changes in slice information (i . e . , the serving slice for the currently active PDU session, along with the allowed slice / partial slices as received from the registered network, or the rejected slice from the network) , the terminal provides the requested and available slice information together with the associated DNN information. However, currently there is no way to provide the DNN associated with the respective served and active slice S-NSSAI . ProvidingAttorney Docket No . 30164 / 104402Ref . No . P71760WO1the associated DNN may be more beneficial and meaningful to the UICC, in certain use cases .

[0037] For example, one use case might be when a Bearer Independent Protocol (BIP) Session is requested by the UICC (via an OPEN channel command) to the terminal . Currently, the Open channel command specifies the Access Point Name (APN) or the DNN, a bearer type, and / or the Radio Access Technology to use for the terminal . However, the UICC has no information about the S-NSSAI associated with this APN / DNN . This may cause a serious issue since the BIP will fail for this requested DNN if the DNN' s associated slice is part of the rej ected slice list in the current registered network . Another use case might be for an USIM where there is an Elementary File for the UE Route Selection Policy (EF_URSP File ) . I f an EF_URSP has a misconfigured association e . g . , DNN : S-NSSAI routing policy (be due to a wrong configuration or due to any future network topology changes ) , there is currently no way to reconfigure the EF URSP routing policy rules . A third use might be where the indication of the DNN associated with the S-NSSAI may be used by the UICC for metering applications , so operators may be aware of allowed, rej ected, and / or partially supported new slice configurations that are currently deployed and used by a subscriber .

[0038] With respect to the second issue mentioned above, when the UICC requests the terminal (ME ) to inform the UICC about any data connection status change, the terminal provides the Envelope : Data Connection Status Change whenever there is a data connection status change detected by the ME . The terminal includes the tag length values (TLVs ) defined in 3GPP TS 31 . 111Attorney Docket No . 30164 / 104402Ref . No . P71760WO1clause 7.5.25.2, in this Envelope, with the information seen in Fig. 3. Fig. 3 is a table showing an example structure of an example Envelope for a data connection status change according to various example embodiments . However, as seen in the Envelope in Fig. 3, currently there is no way to provide, in the Envelope, the S-NSSAI with the specified PDU session (associated with the Network Access Name / DNN) .

[0039] With respect to the first issue mentioned above, where the UICC requests slice (s) information, the slice (s) information is provided, or where the ME informs of slicing information changes (served slices, allowed slices, configured slices, and / or rejected slices) , and the DNN association is not provided, this may further be seen when looking at Figs . 4 and 5. Fig. 4 is a flow diagram that shows an example method 400 of requesting currently available slice information according to various example embodiments . Fig. 5 is a flow diagram that shows an example method 500 of requesting current slice information if available, and also any further slice status change event according to various example embodiments .

[0040] The method 400 of Fig. 4 may take place in a system where there is a UE 401 (which may be similar to UE 110 or UE 112 in Fig. 1 ) including a baseband processor 402 and a UICC 404, and a NG-RAN 406, which may be similar to 5G NG-RAN 120 in Fig. 1. In method 400 of Fig. 4, the ME will power up (410) and the UICC 404 will send an initialization message to the baseband processor 402 (420) , which will start a registration process with the NG-RAN 406 (425) . The baseband processor 402 may also be referred to as the terminal herein. When the UICC 404 initializes, the ME indicates to the UICC 404 the features that the terminal supports, via the coding within 'Terminal Profile' ,Attorney Docket No . 30164 / 104402Ref . No . P71760WO1such as the support of Provide Local Information ( PLI ) -s l ice ( s ) information, PLI-rej ected sl ice ( s ) information, and Event- s lice status change ) . The regi stration may include a regi stration request ( 430 ) from the baseband processor 402 with the requested NSSAI and mapped NSSAI . The NG-RAN 406 may respond with a Registration Accept ( 440 ) , which may include one or more o f an al lowed NSSAI ( s ) , partial ly al lowed or rej ected NSSAI ( s ) , rej ected NSSAI ( s ) , conf igured NSSAI ( s ) , pending NSSAI ( s ) , alternative NSSAI ( s ) , and / or On Demand NSAAI ( s ) . The baseband proces sor 402 of the UE may then send a message to the NG-RAN 406 indicating that regi stration i s complete ( 450 ) . Further , a PDU ses s ion i s establi shed with DNN and S-NSSAI ( 460 ) .

[0041] The UICC 404 may i s sue a Pending Proactive command to the terminal ( e . g . , for requesting s l ice information ) ( 470 ) , and a FETCH command may be sent by the terminal in response ( 475 ) . Further , a proactive command PLI-s l ice ( s ) information may be sent from the UICC 404 to the terminal ( 480 ) , and a terminal response may be sent back to the UICC 404 containing the fol lowing ( requested) information as avai lable : [ Served S l ices information + Allowed s l ices information ( and Partial ly Al lowed S l ice ( s ) information ) i f avai lable ] ( 490 ) . Note that no as sociated DNN li st is currently provided when the served S-NSSAI i s provided .

[0042] Re ferring to Fig . 5 , the method 500 may take place in a system where there i s a UE 501 (which may be s imi lar to UE 110 or UE 112 in Fig . 1 ) including a baseband proces sor 502 and a UICC 504 , and a NG-RAN 506 , which may be s imi lar to 5G NG-RAN 120 in Fig . 1 . In the method 500 , the ME will power up ( 510 ) and the UICC 504 will continue with initial i zation based on the mes sage from / to the baseband proces sor 502 ( 520 ) , which wi l lAttorney Docket No . 30164 / 104402Ref . No . P71760WO1start a regi stration process with the NG-RAN ( 525 ) . The baseband may al so be re ferred to as the terminal herein . When the UICC 504 initial i zes , the ME indicates to the UICC 504 the features that the terminal supports , via the coding within ' Terminal Pro fi le ' , such as the support o f PLI - sl ice ( s ) information, PLI -rej ected sl ice ( s ) information, and Event- s lice status change ) . The regi stration may include a regi stration reguest ( 530 ) from the baseband proces sor 502 to the NG-RAN 506 with the requested NSSAI and mapped NSSAI . The NG-RAN 506 may respond to the baseband processor 502 with a Regi stration Accept ( 540 ) , which may include one or more o f an allowed NSSAI ( s ) , partially al lowed or rej ected NSSAI ( s ) , rej ected NSSAI ( s ) , conf igured NSSAI ( s ) , pending NSSAI ( s ) , alternative NSSAI ( s ) , and / or On Demand NSAAI ( s ) . The baseband proces sor 502 o f the UE may then send a message to the NG-RAN 506 indicating that regi stration i s complete ( 550 ) . Further , a PDU ses s ion i s establ ished with DNN and S-NSSAI ( 560 ) .

[0043] The UICC 504 may i s sue a Pending Proactive command to the terminal ( e . g . , for requesting a sl ice status change ( 570 ) ) , and a FETCH command may be sent by the terminal in response ( 575 ) . Further , a proactive command may be sent from the UICC 504 to the terminal ( 580 ) , where a ' SET UP EVENT LI ST : with -S l ice status change event is l i sted as part o f the current event l i st ' information requested from the terminal , and a terminal response may be sent back to the UICC 504 with the requested information ( 585 ) . I f the Sl ices Status Change event i s part o f the current event l i st ( as set up by the last SET UP EVENT LIST command, see ETS I TS 102 223

[0032] ) , then, when the ME detects a change in any S-NSSAI status ( i . e . , the S-NSSAI is added to or removed from Rej ected S-NSSAI , Allowed NSSAI , Served S-NSSAI ,Attorney Docket No . 30164 / 104402Ref . No . P71760WO1partial ly al lowed, or partial ly rej ected s lice ( s ) l i st ) , the ME shall inform the UICC 504 that a change in S-NSSAI status has occurred, us ing ENVELOPE (EVENT DOWNLOAD - Sl ices status ) as de f ined below ( 590 ) . I f the s l ices status is already avai lable in the UE 501 when the UICC supplies an event l i st for S l ices Status Change event , then the ME shal l immediately send the ENVELOPE (EVENT DOWNLOAD - S l ices Status ) , providing the current S l ices Status . I f the S-NSSAI i s supported only on a subset of Tracking Area ( s ) o f the current Regi stration Area, the tracking area identity list where the S-NSSAI is supported shal l be available . Note that no associated DNN l i st i s currently provided when the served S-NSSAI i s provided .

[0044] With respect to the second is sue mentioned above , where the UICC reguests a data connection status change , and the DNN i s provided, but the associated s lice is currently not provided, thi s may further be seen when looking at Fig . 6 . Fig .6 i s a f low diagram that shows an example method 600 o f requesting a data connection status change event according to various example embodiments .

[0045] The method 600 o f Fig . 6 may take place in a system where there i s a UE 601 (which may be s imi lar to UE 110 or UE 112 in Fig . 1 ) including a baseband proces sor 602 and a UICC 604 , and a NG-RAN 606 , which may be s imi lar to 5G NG-RAN 120 in Fig . 1 . Referring to Fig . 6 , in the method 600 , the ME wi l l power up ( 610 ) and the UICC 604 wi l l continue with initial i zation based on the mes sage from / to the baseband proces sor 602 ( 620 ) , which wi l l start a registration proces s with the NG-RAN 606 ( 625 ) . The baseband may al so be re ferred to as the terminal herein . When the UICC 604 initiali zes , the MEAttorney Docket No . 30164 / 104402Ref . No . P71760WO1indicates to the UICC 604 the features that the terminal supports , via the coding within ' Terminal Pro f i le ' , such as the support o f PLI -sl ice ( s ) information, PLI -rej ected s l ice ( s ) information, and Event- s l ice status change ) . The regi stration may include a regi stration request ( 630 ) from the baseband proces sor 602 to the NG-RAN 606 with the requested NSSAI and mapped NSSAI . The NG-RAN 606 may respond with a Regi stration Accept ( 640 ) , which may include one or more o f an al lowed NSSAI ( s ) , conf igured NSSAI ( s ) , and / or rej ected NSAAI ( s ) . The baseband processor 602 o f the UE 601 may then send a mes sage to the NG-RAN 606 indicating that regi stration i s complete ( 650 ) . Further , a PDU ses s ion i s established with DNN and S-NSSAI ( 660 ) .

[0046] The UICC 604 may i s sue a Pending Proactive command to the terminal ( e . g . , requesting a data connection status change ( 670 ) ) , and a FETCH command may be sent by the terminal in response ( 675 ) . Further , a proactive command may be sent from the UICC 604 to the terminal ( 680 ) , where a ' SET UP EVENT LI ST : with - data connection status change event is l i sted as part o f the current event l i st ' information requested from the terminal , and a terminal response may be sent back to the UICC with the requested information ( 685 ) . I f the Data Connection Status Change event i s part of the current event list ( as set up by the last SET UP EVENT LI ST command, see clause 8 . 25 of 31 . 111 ) , then, upon detection by the ME of a change in the data connection status , the terminal shal l inform the UICC 604 that thi s event has occurred, by us ing the ENVELOPE ( EVENT DOWNLOAD - Data Connection Status Change ) command ( 690 ) . Note that no as sociated S-NSSAI i s currently provided .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0047] In order to address the above discussed issues, in a first aspect of the example embodiments, it is proposed that when the UICC requests the terminal (ME) to provide the current slice information or any changes in slice information (i . e . , the serving slice for the currently active PDU session, along with the allowed slice / partial slices as received from the registered network, or the rej ected slice from the network) , the terminal provides the requested and available slice information together with the associated DNN information.

[0048] Currently, a Provide Local Information command (such as defined in 3GPP TS 31.111 clause 6.4.15) command requests the ME to send current local information to the UICC . At present, when the list of slice (s) information is requested, the serving public land mobile network (PLMN) served S-NSSAIs list, along with an Allowed S-NSSAIs list, shall be returned. When Allowed S-NSSAIs mapping information is available with slice (s) information, the list of PLMN Allowed S-NSSAIs with S-NSSAI mapping shall be returned. When Allowed S-NSSAIs mapping information is not available with slice (s) information, the list of PLMN Allowed S-NSSAIs shall be provided without S-NSSAI mapping. When 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 returned. It is hereby proposed that for the PLI command from the UICC requesting ME for the list of slice (s) information, when the S-NSSAIs of active (served) PDU sessions of serving PLMN are included in the response, the corresponding DNN shall also be included in an ordered list . Also, when served S-NSSAIs are included, the corresponding DNN shall also be included in an ordered list .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0049] In addition, with respect to 3GPP TS 31 . 111 section 6 . 8 . 7 Local Information, it i s proposed that the TERMINAL RESPONSE should al so include the as sociated DNN list . That is , where the UICC has requested the l i st of s lice ( s ) information, the TERMINAL RESPONSE may contain the serving PLMN served S-NSSAI s and the as sociated DNN l ist , along with ( i ) either the s l ices information data obj ect listing al l avai lable s lice ( s ) information without S-NSSAI mapping data obj ect ( i f S-NSSAI mapping information is not avai lable ) or the l i st o f s lice ( s ) information with S-NSSAI mapping data obj ect l i sting all available mapping information, ( ii ) i f the S-NSSAI i s supported inly on a subset o f Tracking Area ( s ) o f the current Registration Area, the tracking area identity l i st where the S-NSSAI i s supported shal l be avai lable . I f the ME has more data in the buf fer to be sent to the UICC and complete data cannot be included within a s ingle response , the TERMINAL RESPONSE shall contain the 'More Data' data obj ect . I f 'More data ' obj ect is part o f the request , then the TERMINAL RESPONSE shal l contain only the as sociated data obj ect ( e . g . , 'partial NSSAI ' data ) .

[0050] In order to al low for the inclus ion o f the associated DNN l i st into the response with the served S-NSSAI i s provided, it may be necessary to make changes to the TERMINAL RESPONSE and ENVELOPE (EVENT DOWNLOAD ) - S l ices Status data structures .

[0051] Fig . 7 i s a table 700 that shows an example structure o f an example TERMINAL RESPONSE according to various example embodiments . The table 700 in Fig . 7 may show a structure s imilar to the structure o f TERMINAL RESPONSE in 3GPP TS 31 . 111 section 6 . 8 . 0 , with the di f ference being the addition of a newAttorney Docket No . 30164 / 104402Ref . No . P71760WO18 . yyy data obj ect in Local Information for the associated DNN l i st to be included in the Local Information being provided in response to a PROVIDE LOCAL INFORMAT ION proactive command .

[0052] Fig . 8A i s a table 800 that shows an example structure o f an ENVELOPE ( EVENT DOWNLOAD ) - S l ices Status data structure according to various example embodiments . The table 800 may show a structure s imilar to the structure in 3GPP TS 31 . 111 section 7 . 5 . 27 . 2 , where the command header may be speci f ied inTS . 31 . 101

[0013] . The di f ference is the addition o f a DNN l i st as a data obj ect 8 . xx in the command parameters / data . The added DNN l i st data obj ect 8 . xx may contain a DNN as sociated with the S l ices information ( served) . The l i sting o f DNN shal l be in the l i sted in the same order as the as sociated S-NSSAI s in S l ices information ( served) data obj ect .

[0053] There may be multiple options for the structure o f the new proposed DNN l i st data obj ect 8 . yyy . Fig . 8B i s a table 850 that shows an example structure of an example DNN l i st data obj ect according to various example embodiments . In the embodiment o f Fig . 8B, the DNN list data obj ect does not have a length in the DNN l i st and redundant DNNs may be skipped . The DNN l i st data obj ect in Fig . 8B may contain a l i st o f DNNs . In one embodiment , the li st o f DNNs may be as de f ined in 3GPPTS . 24 . 501

[0070] . The DNN l i st data obj ect in Fig . 8B may al so contain a DNN entry li st . The DNN entry l ist may contain at least one DNN entry ( ' Tag 80 ' ) . The order of DNN entries may be the same order in which the as sociated S-NSSAI ( s ) are li sted in S l ices information ( served) data obj ect ( clause 8 . 145 ) . I f , for a served S-NSSAI , more than one PDU ses s ion i s active , only the DNN of one PDU ses s ion may be included . For a DNN entry n, the contents are the DNN of the PDU ses s ion as sociated with the n-thAttorney Docket No . 30164 / 104402Ref . No . P71760WO1element o f the Serving PLMN served S-NSSAI li st , and coding of the DNN i s as speci f ied as octet 2 to octet n o f the DNN information element ( de f ined in TS . 24 . 501

[0070] clause 9 . 11 . 2 . IB , as seen in Fig . 8C ) . Fig . 8C i s a table 875 that shows an example structure o f an example DNN data obj ect as set forth in TS . 2 . 501

[0070] clause 9 . 11 . 2 . IB . In some embodiments , there may be a need to truncate the DNN entry l ist truncation shown here in Fig . 8B .

[0054] Fig . 9A i s a table 900 that shows an example structure o f an alternate example DNN l i st data obj ect according to various example embodiments . In the embodiment o f Fig . 9A, the DNN l i st data obj ect has a length in the DNN l i st and there is an option to truncate the DNN l ist . The DNN l i st data obj ect in Fig . 9A may contain a l i st o f DNNs . In one embodiment , the li st o f DNNs may be as de fined in TS . 24 . 501

[0070] . The DNN l i st data obj ect in Fig . 9A may al so contain a DNN entry l ist . The DNN entry l i st may contain at least one DNN entry ( ' Tag 80 ' ) . The DNN entry l i st may contain at least one DNN entry ( ' Tag 80 ' ) . The order o f DNN entries may be the order in which the as sociated S-NSSAI ( s ) are li sted in S lices information ( served) data obj ect ( clause 8 . 145 ) . In case the DNN entry l i st exceeds the indicated length, the remaining DNN entries may not be provided due to truncation . For a length o f a n-th DNN entry, the contents are the length o f the nth DNN entry and for the DNN entry n, the contents are the DNN o f the PDU ses sion associated with the n-th element o f the Serving PLMN served S-NSSAI l i st , and coding o f the DNN i s as speci f ied as octet 2 to octet n of the DNN information element ( de fined in TS . 24 . 501

[0070] clause 9 . 11 . 2 . IB . In some embodiments , there may be a need to truncate the DNN entry list truncation shown in Fig . 9A .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0055] Some embodiments may also indicate within a sl ice status TLV that ' as sociated served + dnn mapping is provided' by the ME . Thi s indication may be done by us ing a byte coding XX in s l ice status , as seen in Fig . 9B . Fig . 9B shows an example byte coding 950 as set forth in 3GPP TS 31 . 111 , clause 8 . 150 for indicating that mapping i s provided for the s l ice information according to various example embodiments . In case the length o f DNN entries exceeds that which can be provided by the Terminal to the UICC [ i . e . , due to which the resulting APDU from ME exceeds 255 Bytes ] , then DNN truncation may be required . In such cases , a truncation flag may be speci fied to indicate accordingly that not al l DNNs may be provided . In such cases , some implementations may decide to s kip the DNN list and not provide the DNN l i st to the UICC .

[0056] In some cases , there may be one S-NSSAI used by multiple DNNs . In such cases , there are multiple options . In a f irst option, the DNN l i st as sociation may not be provided . In a second option, only one as sociated DNN i s provided in the l i st , but an additional f lag may be used to indicate that only one as sociated DNN i s provided, so as to maintain as sociation .

[0057] Us ing the proposed TERMINAL RESPONSE in Fig . 7 , the proposed Envelope s l ices status in Fig . 8A, and / or one o f the proposed DNN l ist data obj ects in Fig . 8B or Fig . 9A, a UICC may be provided with a DNN l i st when it requests s l ice ( s ) information and / or when the UICC requests being informed o f a s l ice status change event . Thus , us ing the techniques and methods described above with respect to Figs . 7 - 9B, going back to Fig . 4 , when the UICC 404 sends a proactive command PLI -Attorney Docket No . 30164 / 104402Ref . No . P71760WO1s l ice ( s ) information requesting sl ice ( s ) inf ormation ( 470- 480 ) , the terminal response sent back to the UICC 404 may contain the as sociated DNN li st in addition to the fol lowing sl ice ( s ) information : [ Served S l ices information + Allowed s l ices information ( and Partial ly Al lowed S l ice ( s ) information) i f available ] ( 490 ) .

[0058] Li kewise , referring back to Fig . 5 , us ing the techniques and methods di scus sed above with respect to Figs . 7 -9B , when the UICC 504 i s sues a Proactive command requesting a s l ice status change event ( 570- 580 ) , and a terminal response i s sent back to the UICC 504 with the requested information ( 585 ) , i f the S l ices Status Change event i s part o f the current event l i st and a change i s detected in any S-NSSAI status ( i . e . , the S-NSSAI i s added to or removed from Rej ected S-NSSAI , Al lowed NSSAI , Served S-NSSAI , partially al lowed, or partial ly rej ected sl ice ( s ) l i st ) , the ME shal l inform the UICC 504 that a change in S-NSSAI status has occurred, us ing ENVELOPE (EVENT DOWNLOAD - S l ices status ) ( 590 ) . The information provided to the UICC wi l l include the as sociated DNN li st .

[0059] In a second aspect o f the example embodiments , it is proposed that when " Data connection status change" i s part o f the Proactive command ( SET UP EVENT LIST ) : from the UICC, and there i s a change to the current data connection ( PDU Ses s ion) , then the terminal wi ll include the as sociated S-NSSAI value for the speci fied DNN . Thi s S-NSSAI wi l l be included i f it i s present when S-NSSAI information element i s avai lable and may be as sociated with the speci f ied DNN . The S-NSSAI data obj ect may contain the S-NSSAI TLV from the S-NSSAI information in the PDU SESS ION ESTABLISHMENT ACCEPT ( see Table 8 . 3 . 2 . 1 . 1 ) , PDU SESS ION MODI FICAT ION COMMAND ( see Table 8 . 3 . 9 . 1 . 1 ) , as speci f ied in TSAttorney Docket No . 30164 / 104402Ref . No . P71760WO124 .501

[0070] . In some embodiments, the S-NSSAI information available from PDU SESSION RELEASE COMMAND may also be used .

[0060] In addition, a new Tag Length Value ( TLV) (with new tag value ) may be defined since there is currently no TLV to specify an individual S-NSSAI value within the Envelope command for Data connection status change . The specified S-NSSAI may either be a mapped configuration, or a non-mapped configuration . The Length of the S-NSSAI Byte 2 may indicate the presence or absence of the S-NSSAI value .

[0061] In order to allow for the inclusion of an associated S-NSSAI value for the specified DNN into the response, it may be necessary to make changes to the data structure for the ENVELOPE (EVENT DOWNLOAD - Data Connection Status change ) data structure . Fig . 10 is a table 1000 that shows an example structure of an ENVELOPE (EVENT DOWNLOAD - Data Connection Status Change) data structure according to various example embodiments . The table 1000 may show a structure similar to the structure in 7 . 5.25.2 , where the command header may be specified in TS . 31 . 101

[0013] .The difference is the addition of a S-NSSAI value as a data obj ect 8 . xxx in the command parameters / data, as seen at the bottom of the table 1000 in Fig . 10 .

[0062] A new Tag Length Value ( TLV) (with new Tag value ) is also proposed, as there is no new TLV currently to specify an individual S-NSSAI value . Fig . 11 is a table 1100 that shows an example structure of an S-NSSAI value data obj ect 8 . xxx according to various example embodiments . The data obj ect 8 . xxx may contain a S-NSSAI as defined in TS . 24 . 501

[0070] . The specified S-NSSAI may either be a mapped configuration, or a non-mapped configuration . The contents of S-NSSAI byte 2 is the Length ofAttorney Docket No . 30164 / 104402Ref . No . P71760WO1S-NSSAI value byte and the Length of S-NSSAI Byte 2 indicates the presence or absence of the S-NSSAI value . The S-NSSAI bytes (bytes 3 to 3+n) is coded as for the S-NSSAI information element as in TS . 24 . 501

[0070] clause 9. 11 .2 . 8 starting from octet 2 in figure 9. 11 .2 . 8 . 1 .

[0063] Note that if the UICC is relying on this data particularly to manage and update the entries in an Elementary File (EF) , such as EF URSP (UE Route Selection Policy) , the applet needs to ensure the data available (S-NSSAI and associated DNN) is from a trusted network . This may be done by ensuring and preferring the information obtained from an authenticated Home / Roam network that uses Subscription Concealed Identifier ( SUCI ) protection during identification (over any information if available from networks that have not been authenticated or failed registration or that uses no Protection scheme (null SUCI ) ) . This ensures the UICC may trust the data before the applet proceeds to update the EF URSP to avoid any new misconfiguration .

[0064] Using the techniques and methods discussed above with respect to Figs . 10 and 11 , when a "Data connection status change" is part of the Proactive command ( SET UP EVENT LIST ) : from the UICC, and there is a change to the current data connection ( PDU Session) , then the terminal will include the associated S-NSSAI value for the specified DNN when information is sent to the UICC from the terminal . Thus, referring back to Fig . 6, when the UICC 604 may issue a Proactive command to the terminal reguesting to know when a data connection status changes ( 670- 680 ) , and a terminal response is sent back to the UICC with the requested information ( 685 ) , if the DataAttorney Docket No . 30164 / 104402Ref . No . P71760WO1Connection Status Change event is part of the current event list then the terminal may inform the UICC 604 that this event has occurred, by using the ENVELOPE (EVENT DOWNLOAD - Data Connection Status Change ) command ( 690 ) . The associated S-NSSAI value along with the specified DNN will be sent to the UICC from the terminal .

[0065] There may be other possible implementations using the general concepts and techniques disclosed herein . For example, in another embodiment, the DNN may be associated not with served S-NSSAI ( s ) . Instead, the DNN may be associated with the allowed S-NSSAI in the allowed slices information, with or without mapping . In another embodiment, the DNN may be associated with the configured S-NSSAI in the configured S-NSSAI information . In another embodiment, the DNN may be associated with the S-NSSAI in the rej ected slices information, with or without mapping .

[0066] In another embodiment, the associated DNN may be provided with the S-NSSAI in slice information ( served S-NSSAI , allowed S-NSSAI , or configured S-NSSAI ) only if the UICC specially requests the associated DNN information as well . The UICC may "explicitly" request the DNN association by indicating it 'explicitly' while sending a proactive command to the terminal . For example, for PLI - slices information, a new proactive command might be for PLI - slices information with DNN association . For Event download - slice status , a new command might be for Event download - slice status with DNN association .

[0067] In another embodiment, a terminal may indicate the support of the above described features explicitly using a dedicated bit and extending the Terminal Profile (TP) . The TP is provided to the UICC during SIM initialization after the UE isAttorney Docket No . 30164 / 104402Ref . No . P71760WO1powered up . Detai l s of a current structure of coding o f the TP that may be suitable for use i s in 3GPP TS 31 . 111 , clause 5 . 2 .

[0068] Li st of Abbreviations and Acronyms :Requested NSSAI : NSSAI provided by the UE to the Serving PLMN during regi stration .Al lowed NSSAI : Indicating the S-NSSAI s values that UE could use in the Serving PLMN in the current Regi stration Area .Served S-NSSAI : Indicating the S-NSSAI value that i s used in the active PDU Ses sion .Rej ected sNSSAI : The Access and Mobi l ity ManagementFunction (AMF) shal l al so provide the l i st of Rej ected S-NSSAI s , each o f them with the appropriate rej ection cause value .Rej ected NSSAI for the current PLMN or standalone non-publ ic network ( SNPN) , rej ected NSSAI for the current regi stration area, rej ected NSSAI for the failed or revoked NSSAA or rej ected NSSAI for the maximum number o f UEs reached .Rej ected NSSAI for the current PLMN or SNPN : A set o f S-NSSAI ( s ) which was included in the requested NSSAI by the UE and i s sent by the AMF with the rej ection cause " S-NSSAI not avai lable in the current PLMN or SNPN" .Rej ected NSSAI for the current regi stration area : A set o f S-NSSAI ( s ) which was included in the requested NSSAI by the UE and i s sent by the AMF with the rej ection cause " S-NSSAI not available in the current regi stration area" .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1Rej ected NSSAI for the failed or revoked NSSAA : A set of S-NSSAI ( s ) which is sent by the AMF with the rej ection cause " S-NSSAI not avai lable due to the fai led or revoked network s l icespeci f ic authentication and authori zation" .Rej ected NSSAI for the maximum number of UEs reached : A set of S-NSSAI ( s ) which was included in the requested NSSAI by the UE and i s sent by the AMF with the rej ection cause " S-NSSAI not available due to maximum number of UEs reached" .Alternative NSSAI : A l i st of mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI .Mapped S-NSSAI : An S-NSSAI in the subscribed S-NSSAI s for the home publ ic land mobile network ( HPLMN) or the subscribed SNPN, to which an SNSSAI o f the regi stered PLMN ( in case o f a roaming scenario ) or the registered non-subscribed SNPN is mapped .On-demand NSSAI : A l ist o f on-demand S-NSSAI ( s ) and optionally s l ice deregi stration inactivity timer per on demand S-NSSAI .On-demand S-NSSAI : An S-NSSAI included in the configured NSSAI that the UE supporting network slice usage control i s al lowed to request only when this S-NSSAI is used by the UE to establ i sh a PDU ses s ion for user data transmis s ion .Partial ly rej ected NSSAI : Indicating the S-NSSAI ( s ) i s rej ected by the network in some TA ( s ) but not al l TAs o f the regi stration area . Each S-NSSAI in the partially rej ected NSSAI i s as sociated with a l i st o f TAs where the S-NSSAI is rej ected .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1NSSAI : Network Slice Selection Assistance InformationS-NSSAI : Single Network Slice Selection Assistance InformationDNN : Data Network Name .APN : Access Point Name .Examples

[0069] In a first example, a method, comprising generating, for transmission from a universal integrated circuit card (UICC) to a terminal , a command comprising a request for one or more of slice information, a change in slice status, or a change in data connection status and processing, by the UICC, a response from the terminal , wherein, when the command requests the slice information or the change in slice status , the response includes associated data network name (DNN) information along with the slice information or the change in slice status and, when the command requests the change in data connection status , the response includes associated slice information along with DNN information specified in the change in data connection status .

[0070] In a second example, the method of the first example, wherein the DNN information includes a list of DNNs in an ordered list .

[0071] In a third example, the method of the first example, wherein the command from the UICC is a Provide Local Information ( PLI ) command requesting slice information and the response from the terminal includes one or more of served slice ( s ) information, allowed slice ( s ) information, or partially allowedAttorney Docket No . 30164 / 104402Ref . No . P71760WO1slice ( s ) information together with the associated DNN information .

[0072] In a fourth example, the method of the third example, wherein one or more Single Network Slice Selection Assistance Information ( S-NSSAIs ) of active Protocol Data Unit ( PDU) sessions of one or more serving public land mobile networks ( PLMNs ) are included in the slice information provided to the UICC, and the DNN information includes a list of DNNs in an ordered list .

[0073] In a fifth example, the method of the first example, wherein, when a list of slice ( s ) information is included in the request, the response from the terminal includes a serving public land mobile network ( PLMN) served Single Network Slice Selection Assistance Information ( S-NSSAIs ) list, an allowed S-NSSAIs list, and when allowed S-NSSAIs mapping information is available with slice ( s ) information, a list of PLMN allowed S-NSSAIs with S-NSSAI mapping .

[0074] In a sixth example, the method of the first example, wherein the command from the UICC includes a SET UP EVENT LIST with a slice status change event listed as part of a current event list and the response from the terminal includes an ENVELOPE (EVENT DOWNLOAD - Slices status ) which indicates that a change in Single Network Slice Selection Assistance Information ( S-NSSAI ) status has occurred, along with the associated DNN information .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0075] In a seventh example, the method of the sixth example, wherein the response from the terminal includes a current slice status .

[0076] In an eighth example, the method of the sixth example, wherein the response is sent from the terminal when a change in any S-NSSAI status is detected, the change including one or more of a S-NSSAI being added to or removed from a rejected S-NSSAI list, an allowed NSSAI list, a served S-NSSAI list, a partially allowed slice (s) list, or a partially rej ected slice (s) list .

[0077] In a ninth example, the method of the sixth example, wherein the response from the terminal includes an ENVELOPE (EVENT DOWNLOAD - Slices Status) data structure that includes a DNN list as a data obj ect a command parameters / data field.

[0078] In a tenth example, the method of the ninth example, wherein the DNN list has DNNs listed in an order that corresponds to an order of associated S-NSSAIs in a served slices information data object .

[0079] In an eleventh example, the method of the ninth example, wherein the ENVELOPE (EVENT DOWNLOAD - Slices Status) data structure includes a slice status tag length value (TLV) that that mapping is provided for the slice information.

[0080] In a twelfth example, the method of the eleventh example, wherein, when a length of DNN entries exceeds a DNN threshold, the ENVELOPE (EVENT DOWNLOAD - Slices Status) data structure includes a truncation flag configured to indicate that not all DNNs are provided.Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0081] In a thirteenth example, the method of the first example, wherein the response from the terminal includes an associated DNN list data obj ect in a Local Information field of a TERMINAL RESPONSE data structure .

[0082] In a fourteenth example, the method of the thirteenth example, wherein the associated DNN list data object includes a DNN list without a length and redundant DNNs are not included in the DNN list .

[0083] In a fifteenth example, the method of the fourteenth example, wherein the associated DNN list data object includes a DNN entry list .

[0084] In a sixteenth example, the method of the fifteenth example, wherein an order of DNN entries corresponds to an order in which associated S-NSSAI (s) are listed in a served slices information data object .

[0085] In a seventeenth example, the method of the fifteenth example, wherein, for a served S-NSSAI, when more than one PDU session is active, only a DNN of one PDU session is included in the DNN entry list .

[0086] In an eighteenth example, the method of the thirteenth example, wherein the associated DNN list data object includes a DNN list having a DNN entry list, the associated DNN list data object also including a length of the DNN list .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0087] In a nineteenth example, the method of the eighteenth example, wherein, when the DNN entry list exceeds the length, any remaining DNN entries are not included due to truncation .

[0088] In a twentieth example, the method of the first example, wherein, when the slice information includes one or more Single Network Slice Selection Assistance Information (S-NSSAIs ) and one of the S-NSSAIs is used by multiple DNNs, the response from the terminal either does not include the associated DNN information or an additional flag is included in the response to indicate that only one associated DNN is provided .

[0089] In a twenty first example, the method of the first example, wherein the command requests a change in data connection status , and the response includes associated slice information along with DNN information specified in the change in data connection status .

[0090] In a twenty second example, the method of the twenty first example, wherein the command is a SET UP EVENT LIST command, wherein the response is sent from the terminal when there is a change to a current data connection, and wherein the response includes an associated S-NSSAI value for a specified DNN when a S-NSSAI information element is available and allowed to be associated with the specified DNN.

[0091] In a twenty third example, the method of the twenty second example, wherein the response includes a S-NSSAI data obj ect having a S-NSSAI tag length value ( TLV) .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0092] In a twenty fourth example, the method of the twenty third example, wherein the S-NSSAI TLV is included within an ENVELOPE (EVENT DOWNLOAD - Data Connection Status Change) data structure used to respond to a request for a data connection status change .

[0093] In a twenty fifth example, the method of the twenty fourth example, wherein a length of a byte in the S-NSSAI TLV indicates a presence or absence of the associated S-NSSAI value .

[0094] In a twenty sixth example, the method of the twenty fourth example, wherein a specified S-NSSAI is either a mapped configuration or a non-mapped configuration.

[0095] In a twenty seventh example, the method of the first example, wherein the command includes a request for allowed Single Network Slice Selection Assistance Information (S-NSSAIs) and the response from the terminal includes DNN information for DNNs associated with allowed S-NSSAIs .

[0096] In a twenty eighth example, the method of the first example, wherein the command includes a request for configured Single Network Slice Selection Assistance Information (S-NSSAIs) and the response from the terminal includes DNN information for DNNs associated with configured S-NSSAIs .

[0097] In a twenty ninth example, the method of the first example, wherein the command includes a request for rejected Single Network Slice Selection Assistance Information (S-NSSAIs) and the response from the terminal includes DNN information for DNNs associated with rej ected S-NSSAIs .Attorney Docket No . 30164 / 104402Ref . No . P71760WO1

[0098] In a thirtieth example , the method o f the f irst example , wherein the response from the terminal includes as sociated DNN information only when the command expl icitly requests the associated DNN information .

[0099] In a thirty f irst example , the method of the f irst example , wherein the process ing circuitry is further conf igured to regi ster with a next generation Radio Acces s Network (NG-RAN) prior to transmitting the command, wherein the proces s ing circuitry i s conf igured to transmit a regi stration request with requested Network S l ice Selection As s istance Information (NSSAI ) and mapped NSSAI to the NG-RAN .

[0100] In a thirty second example , the method of the thirty f irst example , wherein the process ing circuitry is configured to receive , from the NG-RAN, a registration accept mes sage compri s ing one or more o f an al lowed NSSAI ( s ) , partial ly al lowed or rej ected NSSAI ( s ) , rej ected NSSAI ( s ) , conf igured NSSAI ( s ) , pending NSSAI ( s ) , alternative NSSAI ( s ) , or On Demand NSAAI ( s ) .

[0101] In a thirty third example , the method of the f irst example , wherein when the UICC initiali zes , the proces sing circuitry i s conf igured to receive a mes sage indicating features that the terminal supports , wherein the features comprise one or more o f Provide Local Information ( PLI ) - s l ice ( s ) information, PLI -rej ected s lice ( s ) information, or an event- s lice status change .

[0102] In a thirty fourth example , the method of the thirty third example , wherein the terminal indicates support ofAttorney Docket No . 30164 / 104402Ref . No . P71760WO1features explicitly using a dedicated bit and extending a Terminal Profile (TP) , where the TP is provided to the UICC during initialization.

[0103] In a thirty fifth example, one or more processors configured to perform any of the methods of the first through thirty fourth examples .

[0104] In a thirty sixth example, a user equipment (UE) configured to perform any of the methods of the first through thirty fourth examples .

[0105] In a thirty seventh example, a method, comprising processing, based on signaling from a universal integrated circuit card (UICC) , a command comprising a request for one or more of slice information, a change in slice status, or a change in data connection status and generating, for transmission from a terminal to the UICC, a response, wherein, when the command requests the slice information or the change in slice status, the response includes associated data network name (DNN) information along with the slice information or the change in slice status and, when the command requests the change in data connection status, the response includes associated slice information along with DNN information specified in the change in data connection status .

[0106] In a thirty eighth example, one or more processors configured to perform the method of the thirty seventh example .

[0107] Those skilled in the art will understand that the above-described example embodiments may be implemented in anyAttorney Docket No . 30164 / 104402Ref . No . P71760WO1suitable software or hardware configuration or combination thereof . An example hardware platform for implementing the example embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc . The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor .

[0108] Although this application described various embodiments each having different features in various combinations, those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not specifically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments .

[0109] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users . In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users .

[0110] It will be apparent to those skilled in the art that various modifications may be made in the present disclosure,Attorney Docket No . 30164 / 104402Ref . No . P71760WO1without departing from the spirit or the scope of the disclosure . Thus, it is intended that the present disclosure cover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent .

Claims

Attorney Docket No . 30164 / 104402Ref . No . P71760WO1What is claimed:1 . An apparatus comprising memory coupled to processing circuitry, the processing circuitry configured to :generate, for transmission from a universal integrated circuit card (UICC) to a terminal, a command comprising a reguest for one or more of slice information, a change in slice status , or a change in data connection status ; andprocess , by the UICC, a response from the terminal, wherein :when the command requests the slice information or the change in slice status, the response includes associated data network name (DNN) information along with the slice information or the change in slice status ; andwhen the command requests the change in data connection status, the response includes associated slice information along with DNN information specified in the change in data connection status .2 . The apparatus of claim 1 , wherein the DNN information includes a list of DNNs in an ordered list .3 . The apparatus of claim 1 , wherein the command from the UICC is a Provide Local Information (PLI ) command requesting slice information and the response from the terminal includes one or more of served slice ( s ) information, allowed slice ( s ) information, or partially allowed slice ( s ) information together with the associated DNN information .4 . The apparatus of claim 3 , wherein one or more Single Network Slice Selection Assistance Information ( S-NSSAIs ) of active Protocol Data Unit (PDU) sessions of one or more servingAttorney Docket No . 30164 / 104402Ref . No . P71760WO1public land mobile networks ( PLMNs ) are included in the slice information provided to the UICC, and the DNN information includes a list of DNNs in an ordered list .

5. The apparatus of claim 1 , wherein, when a list of slice ( s ) information is included in the request, the response from the terminal includes a serving public land mobile network ( PLMN) served Single Network Slice Selection Assistance Information ( S-NSSAIs ) list, an allowed S-NSSAIs list, and when allowed S-NSSAIs mapping information is available with slice ( s ) information, a list of PLMN allowed S-NSSAIs with S-NSSAI mapping .

6. The apparatus of claim 1 , wherein the command from the UICC includes a SET UP EVENT LIST with a slice status change event listed as part of a current event list and the response from the terminal includes an ENVELOPE (EVENT DOWNLOAD - Slices status ) which indicates that a change in Single Network Slice Selection Assistance Information ( S-NSSAI ) status has occurred, along with the associated DNN information .7 . The apparatus of claim 6, wherein the response is sent from the terminal when a change in any S-NSSAI status is detected, the change including one or more of a S-NSSAI being added to or removed from a rej ected S-NSSAI list, an allowed NSSAI list, a served S-NSSAI list, a partially allowed slice ( s ) list, or a partially rej ected slice ( s ) list .8 . The apparatus of claim 6, wherein the response from the terminal includes an ENVELOPE (EVENT DOWNLOAD - Slices Status )Attorney Docket No . 30164 / 104402Ref . No . P71760WO1data structure that includes a DNN list as a data obj ect a command parameters / data field.

9. The apparatus of claim 1, wherein the response from the terminal includes an associated DNN list data object in a Local Information field of a TERMINAL RESPONSE data structure .

10. The apparatus of claim 9, wherein the associated DNN list data obj ect includes a DNN list without a length and redundant DNNs are not included in the DNN list .

11. The apparatus of claim 9, wherein the associated DNN list data obj ect includes a DNN list having a DNN entry list, the associated DNN list data obj ect also including a length of the DNN list .

12. The apparatus of claim 1, wherein, when the slice information includes one or more Single Network Slice Selection Assistance Information (S-NSSAIs) and one of the S-NSSAIs is used by multiple DNNs, the response from the terminal either does not include the associated DNN information or an additional flag is included in the response to indicate that only one associated DNN is provided.

13. The apparatus of claim 1, wherein the command requests a change in data connection status, and the response includes associated slice information along with DNN information specified in the change in data connection status .

14. The apparatus of claim 13, wherein the command is a SET UP EVENT LIST command, wherein the response is sent from theAttorney Docket No . 30164 / 104402Ref . No . P71760WO1terminal when there is a change to a current data connection, and wherein the response includes an associated S-NSSAI value for a specified DNN when a S-NSSAI information element is available and allowed to be associated with the specified DNN.

15. The apparatus of claim 1, wherein the command includes a request for allowed Single Network Slice Selection Assistance Information (S-NSSAIs) and the response from the terminal includes DNN information for DNNs associated with allowed S-NSSAIs .

16. The apparatus of claim 1, wherein the command includes a request for configured Single Network Slice Selection Assistance Information (S-NSSAIs) and the response from the terminal includes DNN information for DNNs associated with configured S-NSSAIs .

17. The apparatus of claim 1, wherein the command includes a request for rejected Single Network Slice Selection Assistance Information (S-NSSAIs) and the response from the terminal includes DNN information for DNNs associated with rej ected S-NSSAIs .

18. The apparatus of claim 1, wherein the response from the terminal includes associated DNN information only when the command explicitly requests the associated DNN information.

19. The apparatus of claim 1, wherein the processing circuitry is further configured to register with a next generation Radio Access Network (NG-RAN) prior to transmitting the command, wherein the processing circuitry is configured to transmit aAttorney Docket No . 30164 / 104402Ref . No . P71760WO1registration request with requested Network Slice Selection Assistance Information (NSSAI ) and mapped NSSAI to the NG-RAN.20 . An apparatus comprising memory coupled to processing circuitry, the processing circuitry configured to :process , based on signaling from a universal integrated circuit card (UICC) , a command comprising a request for one or more of slice information, a change in slice status , or a change in data connection status ; andgenerate, for transmission from a terminal to the UICC, a response, wherein :when the command requests the slice information or the change in slice status, the response includes associated data network name (DNN) information along with the slice information or the change in slice status ; andwhen the command requests the change in data connection status, the response includes associated slice information along with DNN information specified in the change in data connection status .