Radio access technology (RAT) restriction for a non-terrestrial network (NTN)

Abstract

This disclosure provides systems, methods, and apparatuses implemented by user equipment (UE) (102) for wireless communication. The UE camps on a cell of a radio access network (RAN) using a first radio access technology (RAT). A mobile equipment (ME) (122) of the UE communicates, to a universal integrated circuit card (UICC) (125) of the UE, RAT restriction information (119) associated with at least the first RAT and the RAN.

Description

Docket No. 14730881400PCTRADIO ACCESS TECHNOLOGY (RAT) RESTRICTION FOR A NON-TERRESTRIAL NETWORK (NTN)RELATED APPLICATION

[0001] This application claims the priority benefit of U.S. Provisional Patent Application Serial No. 63 / 755,570, filed February 7, 2025, entitled “RADIO ACCESS TECHNOLOGY (RAT) RESTRICTION FOR A NON-TERRESTRIAL NETWORK (NTN),” the entire contents of which are hereby incorporated by reference herein.TECHNICAL FIELD

[0002] This disclosure relates generally to wireless communication and some aspects relate to a radio access technology (RAT) restriction for a non-terrestrial network (NTN) where the RAT restriction potentially impacts communication from a universal integrated circuit card (UICC).BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] A wireless communication system includes one or more network entities (such as base stations) that enable communication for a mobile communication device (referred to as a user equipment (UE)). Network entities operate one or more cells and collectively form a radio access network (RAN). A RAN can be classified as a terrestrial network (TN) or a non-terrestrial network (NTN). An NTN refers to a network, or segment of networks, using radio frequency (RF) resources on board an NTN node, such as spaceborne vehicles or airborne vehicles. For simplicity, the discussion below refers to all such apparatuses as satellites or NTN nodes. A RAN implements a radio access technology (RAT), such as those specified by the 3rd Generation Partnership Project (3GPP) wireless standards. Example RATs include General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access (E-UTRA), and 3GPP Fifth Generation New Radio (5G NR). A RAN type can also refer to the RAT, such as a GSM / EDGE access network (GERAN), UMTS terrestrial radio access network (UTRAN), evolved universal terrestrial radioDocket No. 14730881400PCTaccess network (E-UTRAN) (i.e., implementing LTE), or next-generation radio access network (NG-RAN) (i.e., implementing 5G NR). When using an NTN, the RAT can be modified slightly to refer to NTN counterparts, such as “Satellite E-UTRAN” or “Satellite NG-RAN.” The 3GPP is developing a technology referred to as “Enhancement of controlling RAT utilization” (ECRATU) to enable a core network (or the operator) to provide information on allowed, notallowed, or restricted RATs in a public land mobile network (PLMN). A UE may disable or refrain from using a RAT marked as not-allowed.

[0005] A UE includes several components, such as a mobile equipment (ME) (also referred to as a modem), an application processor (AP), and a universal integrated circuit card (UICC). The UICC stores subscription information that enables the modem to access a core network. A UICC can include an embedded processor, memory, and other components. A UICC can also be referred to as a universal subscriber identity module (USIM), enhanced UICC, SIM, eSIM, or other terms. A UICC can initiate a data connection (also referred to as a proactive session) via the modem and use the proactive session to obtain over-the-air (OTA) updates from a network node.BRIEF SUMMARY

[0006] The systems, methods, and apparatuses of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0007] One innovative aspect of the subject matter described in this disclosure can be implemented as a method of a mobile equipment (ME) of a user equipment (UE) for wireless communication. The method includes camping on a cell of a radio access network (RAN) using a first radio access technology (RAT), and communicating, to a universal integrated circuit card (UICC) of the UE, RAT restriction information associated with at least the first RAT and the RAN.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method of a UICC of a UE for wireless communication. The method includes communicating, to an ME of the UE, a command associated with a proactive UICC session while the ME is using a first RAT of a RAN, and receiving, from the ME, RAT restriction information associated with at least the first RAT and the RAN.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus for use in a UE. The apparatus includes a communication interface,Docket No. 14730881400PCTand a processing system configured to control the communication interface to implement any one of the above-described methods.

[0010] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0011] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Like reference numbers and designations in the various drawings indicate like elements. Note that the relative dimensions of the figures may not be drawn to scale. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0013] FIG. 1 shows an example wireless communication system in which a user equipment (UE) has a universal integrated circuit card (UICC) that can trigger a mobile equipment (ME) of the UE to establish a packet data network (PDN) connection for a proactive session, in which the ME can inform the UICC about a radio access technology (RAT) restriction for a non-terrestrial network (NTN).

[0014] FIG. 2A shows an example scenario in which a UE moves from a coverage area of a terrestrial network (TN) cell to a coverage area of an NTN cell, or vice versa.

[0015] FIG. 2B shows an example wireless communication system in which the UE might attempt to access an Operations, Administration, Maintenance and Provisioning (OAM&P) network node via an NTN infrastructure.

[0016] FIG. 3 shows a message flow diagram in which a UICC can cause excessive power usage and / or signaling resource consumption by repeatedly requesting a proactive UICC session when the UE is camping on an NTN cell using a restricted RAT.

[0017] FIG. 4A shows a message flow diagram in which a UICC is a legacy subscriber identity module (SIM) and the UICC disregards a message from the ME that indicates an NTN RAT that is unknown to the legacy SIM.

[0018] FIG. 4B shows a message flow diagram in which a UICC is a legacy SIM and the UICC does not recognize a distinction between a RAT in an NTN versus the same RAT in a TN.Docket No. 14730881400PCT

[0019] FIG. 5 shows a message flow diagram in which a UICC attempts to initiate proactive UICC sessions in various RATs when the UICC is initially not aware of RAT restrictions.

[0020] FIG. 6 shows a message flow diagram in which the ME can provide additional RAT restriction information to the UICC as part of a terminal response of a proactive UICC session procedure.

[0021] FIG. 7 shows a message flow diagram in which the ME can preemptively provide additional RAT restriction information to the UICC to prevent proactive UICC session procedures when the ME is aware of RAT restrictions.

[0022] FIG. 8A shows a first example table of values for a message from the ME to the UICC to indicate RAT restriction information.

[0023] FIG. 8B shows a second example table of values for a message from the ME to the UICC to indicate RAT restriction information.

[0024] FIG. 8C shows a third example table of values for a message from the ME to the UICC to indicate RAT restriction information.

[0025] FIG. 8D shows an example bitmap for a message from the ME to the UICC to indicate RAT restriction information.

[0026] FIG. 9A shows a message flow diagram in which an ME preemptively informs the UICC about an emergency scenario to prevent the UICC from initiating a proactive UICC session.

[0027] FIG. 9B shows a message flow diagram in which an ME informs the UICC about an emergency scenario as part of a terminal response of a proactive UICC session procedure.

[0028] FIG. 10 shows a flow diagram of example operations of an ME for communicating RAT restriction information to a UICC.

[0029] FIG. 11 shows a flow diagram of example operations of a UICC for receiving RAT restriction information from an ME.

[0030] FIG. 12 shows a block diagram illustrating an example user equipment.

[0031] FIG. 13 shows a block diagram of an example wireless communication system showing hardware features and communication interfaces.DETAILED DESCRIPTION

[0032] The following description is directed to certain implementations for the purpose of describing innovative aspects of this disclosure. However, a person having ordinary skill in theDocket No. 14730881400PCTart will readily recognize that the teachings herein can be applied in a multitude of different ways. Some of the examples in this disclosure are based on wireless communication according to the 3rdGeneration Partnership Project (3GPP) wireless standards, such as the 4th generation (4G) Long Term Evolution (LTE) and 5thgeneration (5G) New Radio (NR) standards. However, the described implementations can be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 or 802.16 wireless standards, or other known signals that are used to communicate within a wireless, cellular, or internet of things (loT) network, such as a system utilizing 4G, 5G, sixth generation (6G), WiFi, or future radio technology.

[0033] A user equipment (UE) can have a modem part and a universal integrated circuit card (UICC) part. In this disclosure, the modem part is referred to as a mobile equipment (ME). The term “ME” can be replaced with any other terms (such as modem, modem part / component / module, network interface card, or radio access interface, among other examples) that refer to a UE component that accesses a radio access network (RAN). The term UICC can be replaced with any other terms (such as universal subscriber identity module (USIM), physical USIM card, a USIM profile stored in a USIM chip embedded in the UE, subscriber identity module (SIM), eSIM, smart card, or subscriber module, among other examples) that refer to a UE component that can initiate a proactive session via the ME to obtain data from a network node. A UICC communicates proactive UICC commands (such as an Open Channel command) to trigger the ME to take an action. Example proactive UICC commands include the Open Channel command, Send Data command, and Receive Data command. For example, the UICC can communicate the Open Channel command to the ME to cause the ME to establish a packet data network (PDN) connectivity that the UICC will use to obtain over-the-air (OTA) updates or other subscriber / provisioning data.

[0034] Normally, the ME may open an evolved packet system (EPS) session to establish a PDN connection when the ME receives an Open Channel command from the UICC. If the ME cannot open the PDN connection as requested, the ME communicates a terminal response such as the “Access Technology unable to process command” terminal response (sometimes referred to an error code “3B” or “3B terminal response” referring to the type of terminal response). The techniques of this disclosure can apply to any terminal response from the ME to the UICC. Examples include the “Access Technology unable to process command” (code “3B”) terminalDocket No. 14730881400PCTresponse, a “ME currently unable to process command” (code “20”) terminal response, or a “Command beyond MEs capabilities” (code “30”) terminal response, among other examples. For brevity and consistency, the examples of this disclosure refer to the “Access technology unable to process command.” The “Access Technology unable to process command” can indicate a variety of failures, such as a failure due to network constraints. Absent the techniques of this disclosure, the “Access Technology unable to process command” is insufficient to inform the UICC about a radio access technology (RAT) restriction, such as a RAT restriction based on the UE using a RAT of a non-terrestrial network (NTN). The UICC might consume additional power or signaling overhead by continuing to initiate the proactive session when the UE is in a restricted RAT. Alternatively, or additionally, the “Access Technology unable to process command” terminal response might cause the UICC to refrain from re-attempting the proactive session when the UE is in a non-restricted RAT (e.g., the same RAT but of a TN instead of an NTN).

[0035] This disclosure provides systems, methods, and apparatuses for implementing a RAT restriction. According to aspects of this disclosure, an ME can provide RAT restriction information to the UICC. RAT restriction information can refer to one or more NTN RATs which the UE is not allowed to access, or which the UICC is not allowed to use, for a proactive UICC session. A core network can impose a RAT restriction based on a user subscription, a roaming agreement, or other reason. The RAT restriction can be UE-specific and / or network-specific. Typically, the ME can become aware of the RAT restriction based on a non access stratum (NAS) message (such as during a network registration) or an access stratum (AS) message (such as a radio resource control (RRC) message or system information block (SIB)). However, the UICC currently does not have a mechanism to become aware of RAT restrictions, particularly as they might apply to various NTN RATs (also referred to as Satellite RATs).

[0036] In aspects of this disclosure, the ME can include RAT restriction information in a terminal response to a UICC. In some implementations, the RAT restriction information can refer to the currently-used RAT. Alternatively, or additionally, the RAT restriction information can include “additional RAT restriction information” that refers to more than one RAT. For example, the additional RAT restriction information can refer to a group of RATs, such as any RAT associated with an NTN. In some aspects, the additional RAT restriction information can refer to one or more specific NTN RAT(s), in addition to the currently used RAT. The additional RAT restriction information can indicate a second NTN RAT that the ME is aware has beenDocket No. 14730881400PCTrestricted for the UE. In some aspects, the additional RAT restriction information can include a bitmap to indicate, for various RATs, whether each RAT is restricted or not restricted.

[0037] The UICC can use the RAT restriction information to prevent (i.e., block) itself from initiating a proactive session when the UE is using a restricted RAT. In some implementations, the ME communicates an access technology indication to the UICC whenever the UE changes to a different RAT. The UICC can determine whether to initiate the proactive session based on the current access technology and the RAT restriction information. Furthermore, because the “Access Technology unable to process command” terminal response can include the RAT restriction information, the UICC can become aware that an ongoing proactive session procedure has failed due to a RAT restriction rather than some other network constraint. The UICC can determine whether to reinitiate an unsuccessful proactive session procedure if the network constraint was for a reason other than the RAT restriction and can refrain from reinitiating the unsuccessful proactive session procedure that failed due to the RAT restriction.

[0038] In some aspects, a UE is using a particular RAT based on an emergency scenario. When the UE is in the emergency scenario, it is undesirable for the UICC to perform data transfer for non-emergency data in a proactive session. The ME can inform the UICC about the emergency scenario (such as in a terminal response or other ME-to-UICC message) to prevent the UICC from initiating a proactive session during the emergency scenario. The definition of an emergency scenario can be any situation in which the UICC should not perform a proactive session procedure. In some implementations, the emergency scenario refers to the UE using a satellite connection, such as when a terrestrial network is unavailable. In some implementations, the emergency scenario can be based on an emergency-type application using the ME for emergency data access.

[0039] Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. A RAT restriction can prevent the UICC from attempting a proactive session when the UE is using a satellite RAT that has low data speed and / or high latency that is not suitable for an OTA update of the UICC. Limiting the OTA updates via the satellite RAT can improve user satisfaction and UE performance. By restricting the proactive UICC sessions (including UICC and ME processing), the UE can enjoy power saving and more efficient use of processor resources. By refraining from initiating proactive session procedures that will predictably fail in a restricted RAT, the UICC can more efficiently handle OTA updates when the UE is using a non-restricted RAT. InDocket No. 14730881400PCTsome aspects, the techniques of this disclosure can reduce radio frequency signaling / overhead / congestion in an NTN cell where bandwidth might be limited.

[0040] Although the examples refer to UICC, similar technologies can apply to other UE components that can communicate with the ME to initiate packet data network (PDN) connectivity for non-application data (such as Operations, Administration, Maintenance and Provisioning (OAM&P) information). While examples of this disclosure refer to an Open Data command and terminal response, the techniques can apply to other proactive UICC procedures or messages. Furthermore, the ME can convey the additional RAT restriction information in any type of terminal response or other ME-to-UICC terminal communication.

[0041] FIG. 1 shows an example wireless communication system 100 in which a UE 102 has a UICC 125 that can trigger a ME 122 of the UE to establish a PDN connection for a proactive session. In accordance with aspects of this disclosure, the ME 122 can inform the UICC about a RAT restriction 119 for an NTN. An NTN extends or augments the service capability of a wireless communication system. An NTN refers to a network, or segment of networks, using radio frequency (RF) resources on board an NTN node 101 (such as a spaceborne vehicle or an airborne vehicle). An NTN node 101 can belong to one of several types based on altitude, orbit, and beam footprint size. FIG. 1 shows an NTN node 101 as a satellite 104. A satellite 104 can support a transparent or a regenerative (with on board processing) payload architecture. For a transparent payload implementation, a satellite 104 can apply RF filtering and frequency conversion and amplification, and not change the waveform signal. For a regenerative payload implementation, a satellite 104 can apply RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and coding / modulation.

[0042] An NTN gateway 108 (sometimes also referred to as a “sat-gateway” or “GW”) communicatively couples the satellite 104 to ground components of the example wireless communication system 100 (such as a ground NTN BS 106', a CN 110, or other data network resource). In some deployments, the NTN node 101 (e.g., satellite 104) can perform some or all functions of a base station (shown as BS 106). The BS 106 can be included on-board the satellite 104 or can be partially or wholly located on the ground (shown as ground NTN BS 106'). In this disclosure, the term BS 106 can refer to either or both of the BS 106' on the ground (when present) or the BS 106 (when onboard the satellite 104). The satellite 104, the NTN gateway 108, and the BS 106 form part of a RAN (sometimes referred to as an NTN RAN). In some implementations, the radio access technology for the NTN RAN is based on 5G NR.Docket No. 14730881400PCTAlternatively, the radio access technology for the NTN RAN can use an Evolved Universal Terrestrial Radio Access (E-UTRA) air interface for 4G LTE, or another radio access technology such as narrowband Internet of Things (NB-IoT), among other examples. Any number of RANs can be communicatively coupled to the CN 110. The CN 110 can be implemented as an evolved packet core (EPC), a fifth generation (5G) core (5GC), or a sixth generation (6G) core.

[0043] In this disclosure, the NTN node 101 can refer to the satellite 104, the BS 106, or collectively to the satellite 104 and the BS 106, such that the phrases or reference numbers can be interchangeable. When the UE 102 is within a coverage area of the satellite 104, the UE 102 can establish a radio connection to the satellite 104 via an NTN cell (not shown). The NTN cell refers to a coverage area in which the satellite 104 operates as part of a radio network. The radio network can be associated with a footprint on the surface of the Earth or could be deployed in air, space, a spaceship, or other planetary objects. In terms of the satellite moving pattern, there are three types of service links that are supported in NTN:• Earth-fixed: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., the case of Geostationary Earth Orbit or Geosynchronous Orbit (GEO / GSO) satellites)• Quasi-Earth-fixed: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e g., the case of Low Earth Orbit or Medium Earth Orbit (LEO / MEO) satellites capable of using steerable beams), or • Earth-moving: provisioned by beam(s) whose coverage area slides over the Earth surface (e.g., the case of LEO / MEO satellites using fixed or non-steerable beams).

[0044] With LEO / MEO satellites, the satellite 104 can provide either quasi-Earth-fixed cell coverage or Earth-moving cell coverage. With GEO / GSO satellites, the satellite 104 can provide Earth fixed cell coverage.

[0045] The radio connection between the UE 102 and the satellite 104 can also be referred to as service link 103. The satellite 104 communicates the UE traffic to the CN 110 via a feeder link 107 that communicatively couples the satellite 104 to the NTN gateway 108. The UE can enter a radio resource connection (RRC) connected (RRC CONNECTED) state in the access stratum (AS) which includes the service link 103 and the feeder link 107. The UE can also enter an RRC idle (RRC IDLE) state, which refers to a state where the radio connection is released or not yet established. An RRC inactive (RRC INACTIVE) state refers to a state where the radio connection is suspended. The RRC states refer to the states of radio connections in the AS, whereDocket No. 14730881400PCTthe NTN RAN provides AS connections. In order to access core network services, the UE 102 and the CN 110 communicate NAS messages. For example, the UE 102 can communicate a network registration request or other uplink NAS messages to the CN 110 via the NTN). The CN 110 determines whether to accept or reject the network registration based on user subscription information. The CN 110 provides the network registration accept / reject or other downlink NAS messages to the UE 102 via the NTN RAN.

[0046] The CN 110 includes various network functions for subscription, mobility management, and service management. For example, EPS mobility management (EMM) NAS procedures enable the CN 110 to manage mobility and connection states in LTE networks. In an EMM idle (EMM-Idle) state, the UE 102 does not have an active signaling connection with the CN 110. The UE 102 conserves power by implementing discontinuing radio transmissions and relies on periodic tracking area updates to inform the network of its location. In the EMM-Idle state, the UE 102 monitors a paging channel for indications that the CN 110 has mobile-terminated (MT) traffic (e.g., MT calls or data). If the UE 102 receives a paging indication or has mobile-originated (MO) traffic to send, the UE 102 initiates a NAS connection by sending a Service Request message. The Service Request message is part of a service request procedure to establish a signaling connection with the CN 110. For example, the UE 102 sends the Service Request message to a Mobility Management Entity (MME) of the CN 110. Although the examples of this disclosure describe some concepts in terms of an EPC, the concepts can also be applied to a 5GC (where an Access and Mobility Function (AMF) can perform similar functions as the MME in an EPC). The MME / AMF verifies the UE's identity and executes authentication and authorization checks. If these checks are successful, the MME / AMF instructs the NTN RAN to establish the connection, allowing the LTE 102 to transition to the EMM-Connected state.

[0047] The UE 102 can include an application processor (AP 121), a ME 122 and a UICC 125, among other components (not shown). The AP 121 can communicate data with a packet data network using the ME 122. The ME 122 can include a receiver, transmitter, transmitter, or other components for managing network communication. For example, the ME 122 can implement a NAS layer, RRC layer, and physical (PHY) layer for communicating with the network, while the AP 121 can implement upper layers (such as an application layer). Although shown as separate components, in some implementations, the UE 102 includes hardware that implements the features of both the AP 121 and the ME 122. Alternatively, the AP 121 can be implemented by a first component and the ME 122 can be implemented by a second component. TheDocket No. 14730881400PCTcomponent(s) that implement the AP 121 and / or the ME 122 can be part of a chip or other type of integrated circuit.

[0048] The UICC 125 stores subscription information. A legacy SIM card was typically a passive memory element. However, as SIM cards have evolved (and now called a UICC), they have increasing capabilities. For example, the UICC 125 typically is a powered chip with a processor that can implement some protocol features. The UICC 125 and the ME 122 can communicate via a UICC-ME interface 123 within the UE 102. As described above, the UICC 125 can request a proactive session to obtain over-the-air updates from an OAM&P server 115. As further described with reference to FIG. 3, the UICC 125 can initiate a proactive session (also referred to as a proactive UICC session) by communicating an Open Channel command to the ME 122. The ME 122 may attempt to establish a PDN session 150 via the RAN.

[0049] In the example of FIG. 1, the RAN is an NTN RAN that includes a satellite 104. The limited bandwidth and delay associated with satellite access may be unsuitable for an OTA update from the OAM&P server 115. Furthermore, as shown in block 130, the CN 110 can impose a RAT restriction based on the RAT of the RAN. For example, the CN 110 may restrict NTN access to limited types of traffic or services. Alternatively, or additionally, the CN 110 can restrict NTN access for particular UEs, such as based on a user subscription, roaming agreement between the UE home network operator and the satellite operator, or other reasons. The 3GPP is developing enhancements to a RAT restriction feature referred to as “controlling RAT utilization” (CRATU). Some enhancements are motivated by a desire to impose RAT restrictions for NTN access.

[0050] The ME 122 may become aware of a problem accessing the NTN RAN based on RRC or NAS messaging. For example, the ME 122 can detect a RAT restriction 119 based on contents of a message, such as a reject message from the CN 110. However, absent the techniques of this disclosure, the UICC 125 may be unaware of the RAT restriction 119. The UICC 125 may continually or repeatedly communicate Open Channel commands to the ME 122 in an attempt to establish a PDN session, as further described with reference to FIG. 3. This can unnecessarily consume power and resources within the UE 102. Some potential solutions (as described with reference to FIG. 4A through FIG. 5) can prevent repeated attempts to initiate the proactive session. However, some of the potential solutions are needlessly overly restrictive or can cause barring at a broad level. In accordance with aspects of this disclosure, the ME 122 can communicate RAT restriction information 180 to the UICC 125. The UICC 125 can use the RATDocket No. 14730881400PCTrestriction information 180 and information about the current access technology of the RAN to determine whether to initiate a proactive session 140. A potential technical advantage is power saving. Furthermore, the RAT restriction information 180 can provide more granular control of the UICC 125 utilization of a RAN based on a RAT restriction 119 imposed by the CN 110.

[0051] FIG. 2A shows a block diagram 200A of an example scenario in which a UE moves from a coverage area of a terrestrial network (TN) cell to a coverage area of an NTN cell, or vice versa. The example of FIG. 2A includes a UE 102, BS 206, and satellite 104. BS 206 manages TN cell 219 and satellite 104 manages NTN cell 209. In this example, at time ti, UE 102 initially is in the coverage area of the TN cell 219. At time t2, the UE 102 moves 221 out of the coverage area of the TN cell 219 and into a coverage area of NTN cell 209. The UE 102 may perform an NTN search (i.e., searching an NTN cell) in response to detecting out of TN coverage. In some aspects, the UE 102 may refrain from performing an NTN search when detecting out of TN coverage and perform an NTN search in response to activating an NTN communication (e.g., activating an NTN application of the UE 102 or initiating sending a message).

[0052] FIG.2B shows an example wireless communication system 200B in which the UE might attempt to access an OAM&P network node via an NTN infrastructure. The example of FIG. 2B includes the UE 102, satellite 104 (optionally implementing the BS 106), NTN gateway 108 (optionally implementing BS 106'), CN 110, and OAM&P server 115. The satellite 104 and the NTN gateway 108 are part of an NTN infrastructure 205 that can be managed by OAM&P system 115. The techniques of the disclosure are generally described in the context of the UE 102 establishing a PDN connectivity with the CN 110 for sending and receiving data via the NTN gateway 108 and CN 110 to a data network 218. In some aspects, the UE can initiate PDN connectivity to the OAM&P server 115. The techniques of the disclosure can be readily applied when establishing PDN connectivity with the OAM&P system 115 to reduce power consumption and resource usage associated with control signaling and data transfer in the same manner as discussed with respect to establishing PDN connectivity with the CN 110.

[0053] FIG. 3 shows a message flow diagram 300 in which a UICC can cause excessive power usage and / or signaling resource consumption by repeatedly requesting a proactive UICC session when the UE is camping on an NTN cell using a restricted RAT. At block 332, the UE 102 is camping in a satellite E-UTRAN cell maintained by BS 106 of satellite 104. While camped in the satellite E-UTRAN cell, the ME 122 communicates an access technology indication 334 to the UICC 125 indicating that the access technology for the cell is satellite E-UTRAN.Docket No. 14730881400PCT

[0054] In the example of FIG. 3, the UICC 125 initiates a proactive session. The UICC 125 communicates an Open Channel command 342 to the ME 122 to initiate the proactive session. The Open Channel command requests that the ME 122 is to open a communication channel for a PDN session with a PDN (not shown) via the BS 106. In some examples, the ME 122 transmits a PDN request 345 to a core network via the BS 106 to establish the communication connection. In some examples, the core network transmits a PDN connectivity rejection 346 to the ME 122 indicating that the UE is not allowed to use the NTN cell (or the satellite RAT type) for the PDU session. For example, the PDN connectivity rejection 346 can be one way in which the ME 122 learns of a RAT restriction associated with the Satellite E-UTRAN RAT. Other ways of learning the RAT restriction are possible, such as a system information message, RRC message, or NAS message. Based on the PDN connectivity rejection 346, the ME 122, communicates a terminal response 348 to the UICC 125. In some aspects, the terminal response 348 indicates that the "access technology is unable to process the command" (e.g., a 3B terminal response message).

[0055] In the example of FIG. 3, the UICC 125 is unaware of the RAT restriction. At block 350, the UICC 125 might continually retry establishing the proactive session. The UICC 125 communicates a subsequent Open Channel command 342 to the ME 122. In some implementations, the ME 122 might reattempt the PDN request 345 and receive the PDN connectivity rejection 346. Alternatively, the ME 122 may refrain from transmitting the PDN request 345 and instead proceed directly to communicating the “Access Technology unable to process command” terminal response 348 to the UICC 125. In either scenario, the power consumed by the UICC 125 and the ME 122 is unnecessary and excessive since the PDN connectivity cannot be established while the ME 122 is using the restricted RAT. The repeated cycle of communications 342, 345, 346, and 348 can cause excessive power consumption 352, resource waste, and processing overhead on the UE 102.

[0056] FIG. 4A shows a message flow diagram 400A in which a UICC is a legacy SIM and the UICC disregards a message from the ME that indicates an NTN RAT that is unknown to the legacy SIM. The example of FIG. 4A includes UE 102, BS 206, and BS 106 implemented by satellite 104. The example of FIG. 4A is similar to the example of FIG. 3, with the difference being that UICC 125 is a legacy SIM that does not support an NTN RAT.

[0057] At block 422, the UE 102 is camping in an LTE cell managed by BS 206. The ME 122 communicates an access technology indication 424 to the UICC 125 indicating that the access technology is LTE. Later, at block 332, the UE camps in the satellite E-UTRAN cell managedDocket No. 14730881400PCTby BS 106 of satellite 104. The ME 122 communicates an access technology indication 334 to the UICC 125 indicating that the RAT is satellite E-UTRAN. However, because the legacy SIM might not recognize the satellite E-UTRAN as a valid RAT type, the legacy SIM might not process the access technology indication 334 properly. Shown at block 435, the UICC 125 (a legacy SIM in this scenario) does not support the satellite E-UTRAN RAT and disregards the access technology indication 334. Alternatively, the legacy SIM might store the access technology as an unknown RAT.

[0058] In the example of FIG. 4A, the UE 102 repeats the cycle of communications 342, 345, 346, and 348 in the same way as described with respect to FIG. 3. After receiving the terminal response 348, at block 449, the UICC 125 determines to drop the unknown RAT and instead use the latest reported RAT from the processed access technology indication 424 (LTE in this example). The legacy SIM may reattempt to establish the proactive session and cause similar excessive power consumption as was described with respect to FIG. 3.

[0059] Although the PDN connectivity rejection 346 is one technique for the ME 122 to become aware of a RAT restriction, other ways are possible. For example, the BS 106 may transmit UE RAT restriction information 438 to the UE 102 informing the ME 122 about the RAT restriction. In that scenario, the ME 122 may omit the PDN request 345 and the PDN connectivity rejection 346 because the ME 122 knows that it is using a RAT (satellite E-UTRAN) that is in the UE RAT restriction information 438. However, the ME 122 still communicates the terminal response 348 and the UICC 125 may reattempt the proactive session.

[0060] FIG. 4B shows a message flow diagram 400B in which a UICC is a legacy SIM and the UICC does not recognize a distinction between a RAT in an NTN versus the same RAT in a TN. The example shown in FIG. 4B is similar to the example of FIG. 4A with the difference being that the UICC 125 in FIG. 4B does not recognize a distinction between the “Satellite E-UTRAN” RAT in an NTN and the “E-UTRAN” (i.e., LTE) RAT in a TN.

[0061] The example of FIG. 4B begins in the same way as the example of FIG. 4A up to the first instance of terminal response 348 indicating the access technology is unable to process the command. Based on receiving the terminal response 348 indicating “Access technology unable to process command,” the UICC 125 determines to block further proactive sessions for the E-UTRAN (i.e., LTE) RAT. At block 460, the UICC 125 blocks further proactive sessions for all E-UTRAN cells (including a TN cell using the E-UTRAN RAT). This could result in overbarring, such as when the ME 122 later camps (block 472) on a TN BS 206 using the E-Docket No. 14730881400PCTUTRAN RAT. The ME 122 transmits an access technology indication 474 indicating that the current access technology is E-UTRAN (i.e., LTE). The UICC 125 blocks 461 further proactive sessions for LTE without realizing that the ME 122 is now camping on a TN cell that might be suitable for the PDN session.

[0062] FIG. 5 shows a message flow diagram 500 in which a UICC attempts to initiate proactive UICC sessions in various RATs when the UICC is initially not aware of RAT restrictions.

[0063] At block 332, the UE 102 is camping in the satellite E-UTRAN cell managed by BS 106 of satellite 104. In some implementations, the BS 106 transmits UE RAT utilization restriction indication(s) 538 to the ME 122. In this example, the UE RAT utilization restriction indication(s) 538 can indicate multiple RATs that are restricted, such as the Satellite E-UTRAN RAT and the Satellite NG-RAN RAT.

[0064] FIG. 5 shows a first attempted update procedure 540A. In some examples, the ME 122 communicates an access technology indication 534 to UICC 125 before or during the first attempted update procedure 540A. The access technology indication 534 indicates the current access technology is Satellite E-UTRAN. The first attempted update procedure includes messages 342, 345, 346, and 348, as described with reference to FIG. 3. At block 561, the UICC 125 blocks proactive sessions for satellite E-UTRAN after receiving the terminal response 348 indicating “Access technology unable to process command.”

[0065] Later, at block 532, the UE 102 camps in the satellite NG-RAN cell managed by BS 506 of satellite 504. The ME 122 communicates an access technology indication 534 to the UICC 125 that indicates the access technology is satellite NG-RAN. Because the UICC 125 blocked Satellite E-UTRAN (and did not block the Satellite NG-RAN RAT), the UICC 125 may initiate a second attempted update procedure 540B. The UICC 125 communicates an Open Channel command 542 to the ME 122. The ME 122 communicates a terminal response 548 to the UICC 125 indicating "Access technology unable to process command.” In some implementations, the ME 122 may transmit a PDN request 545 to the core network and receive a PDN connectivity rejection 546. However, the more likely scenario is that the ME 122 omits the PDN request 545 (and thus also the PDN connectivity rejection 546 response) because the ME 122 is already aware of the RAT restriction based on the UE RAT utilization restriction indication(s) 538.

[0066] Ending the second attempted update procedure 540B, the ME 122 communicates a terminal response 548 (again indicating Access technology unable to process command) to theDocket No. 14730881400PCTUICC 125. At block 562, the UICC 125 blocks proactive sessions for satellite NG-RAN based on the terminal response 548.

[0067] Additional example attempted update procedures might be performed each time the ME 122 camps on a cell using a different RAT. These unsuccessful attempted update procedures could be avoided by the ME 122 informing the UICC 125 of the RAT restriction for multiple RATs based on the UE RAT utilization restriction indication(s) 538.

[0068] FIG. 5 shows an example of a successful third attempted update procedure 540C. At block 472, the UE 102 camps in an LTE cell managed by TNBS 206. The ME 122 communicates an access technology indication 574 that indicates the current access technology is LTE. In the third attempted update procedure 540C, the UICC 125 communicates an Open Channel command 592 to the ME 122. The ME 122 transmits a PDN request to the CN 110 via the TN BS 206 and receives a PDN accept message from the CN 110, thereby establishing PDN connectivity 595. The UICC 125 can then continue with the proactive session 597 via the PDN connection.

[0069] FIG. 6 shows a message flow diagram 600 in which the ME can provide additional RAT restriction information to the UICC as part of a terminal response of a proactive UICC session procedure. The example message flow 600 of FIG. 6 begins in the same way as the example message flow 500 of FIG. 5 with the UE camping in the satellite E-UTRAN cell managed by BS 106 of satellite 104 (block 332).

[0070] In the example of FIG. 6, after the PDN connectivity rejection 346 is received from the BS 106, the ME 122 communicates a terminal response 648. The terminal response 648 might be a “Access technology unable to process command” message that includes additional RAT restriction information. For example, the terminal response 648 can include additional RAT restriction information that is not limited to just the Satellite E-UTRAN RAT of the current cell but also the Satellite NG-RAN RAT because the UE RAT utilization restriction indication(s) 538 indicated both of those RATs were restricted for the UE. Alternatively, the additional RAT restriction information can indicate that all “Satellite” (or NTN) RATs are restricted. In some implementations, if the current access technology is not allowed to use for the UE (see, e.g., 3GPP Technical Specification (TS) 24.501), or the current access technology is Satellite E-UTRAN or Satellite NG-RAN, then the ME sends the TERMINAL RESPONSE (Access Technology unable to process command) immediately. The operation is aborted.

[0071] At block 680, the UICC 125 blocks proactive sessions (e g., refrains from sending an Open Channel command) based on the additional RAT restriction information received inDocket No. 14730881400PCTmessage 648. In other words, the UICC 125 will not communicate an Open Channel command to the ME 122 after the ME 122 camps on a satellite NG-RAN cell (block 532) and communicates the access technology indication 534 indicating satellite NG-RAN RAT. In contrast to the example of FIG. 5, the UICC 125 does not reattempt the proactive session with the NG-RAN cell managed by BS 506 because the UICC 125 blocked proactive session creation based on additional RAT information received at block 680. The UICC 125 is thus able to save power and control signaling resources 681 by preventing the repeated attempts to establish a proactive session.

[0072] At block 472, the UE 102 camps in an LTE cell managed by the BS 206. Like the example of FIG. 5, the ME 122 can successfully establish PDN connectivity 595 because the UICC 125 does not block TN based RATs.

[0073] FTG. 7 shows a message flow diagram 700 in which the ME can preemptively provide additional RAT restriction information to the UICC to prevent proactive UICC session procedures when the ME is aware of RAT restrictions. In this example, the UE is camping in NTN cell 732 (e.g., Satellite E-UTRAN or Satellite NG-RAN). The example message flow of FIG. 7 is similar to that shown in FIG. 6. The difference in the example of FIG. 7 is that the ME 122 communicates an access technology indication 734 indicating the current access technology and additional RAT restriction information prior to the UICC 125 attempting to establish a proactive session. For example, the ME 122 can communicate the access technology indication 734 with additional RAT restriction information based on receiving the UE RAT utilization restriction indication(s) 538. At block 680, the UICC 125 blocks proactive sessions based on the access technology and the additional RAT restriction information without communicating an open channel command to the ME 122. Like the example of FIG. 6, the UICC 125 is able to save power and control signaling resources 681 by preventing attempts to establish a proactive session that would predictably fail based on the current access technology and the RAT restriction.

[0074] Later, when the UE 102 camps on an LTE cell managed by BS 206, the ME 122 can successfully establish PDN connectivity 595 because the UICC 125 does not block TN based RATs.

[0075] FIG. 8A through FIG. 8C show example codes and meanings for RAT restriction information that the ME 122 can communicate to the UICC 125. The example codes and meanings can be used with any ME-to-UICC communication, including the “Access technology unable to process command,” an access technology indication upon camping on a new accessDocket No. 14730881400PCTtechnology, or using a new ME-to-UICC message, among other examples. The examples of FIG.8A through FIG. 8C are provided for illustrative purposes and other codes or related RATs can be devised for other implementations.

[0076] FIG. 8A shows a first example table 800a of values for a message from the ME to the UICC to indicate RAT restriction information. The example table 800a includes a column for codes that can be provided in the message and a column indicating the meaning of the code. In this example, the code indicates the affected technology. Below is a reference of example codes and the corresponding RAT:• 00 NR• 01 NR-NTN• 02 E-UTRA• 03 E-UTRA NTN

[0077] An “Access technology unable to process command” terminal response can include the code to provide information about the current RAT and another restricted RAT. For example, the code “01” can mean that NR-NTN and current access technology are both restricted.

[0078] FIG. 8B shows a second example table 800b of values for a message from the ME to the UICC to indicate RAT restriction information. The example table 800b includes a column for codes that can be provided in the message and a column indicating the meaning of the code. Like the example of FIG. 8A, the code indicates the affected technology. Below is a reference of example codes and the corresponding RAT:• 00 current access technology (default)• 01 NR• 02 NR-NTN• 03 E-UTRA• 04 E-UTRA NTN• 05 UTRA• 06 General Packet Radio Service (GPRS)

[0079] For example, the ME can communicate code “01” to indicate that NR-NTN is restricted. If the ME does not indicate a specific value or indicates “00”, the communication can indicate that the current access technology is restricted, which can also be used with a legacy SIM that might not recognize the RAT restriction information based on these later-developed codes.Docket No. 14730881400PCT

[0080] FIG. 8C shows a third example table of values for a message from the ME to the UICC to indicate RAT restriction information. The example table 800c includes a column for codes that can be provided in the message and a column indicating the meaning of the code. Like the example of FIG. 8A and FIG. 8B, the code indicates the affected technology. As an example, a code of ‘00’ indicates that satellite mode (e.g., both Satellite NR and Satellite LTE) are restricted. Below is a reference of example codes and the corresponding RAT:• 00 Satellite• 01 E-UTRA• 02 LTE

[0081] FIG. 8D shows an example bitmap 800d for a message from the ME to the UICC to indicate RAT restriction information. The example bitmap 800d is a field of bits, where the fields in the bitmap correspond to different RATs. A field can have a value of 0 or 1, where 0 indicates the RAT corresponding to the field is not restricted and a value of 1 indicates the RAT corresponding to the field is restricted (or vice versa). A potential technical advantage of this approach is that the ME can provide more granular RAT restriction information and indicate RAT restrictions for multiple RATs.

[0082] FIG. 9A shows a message flow diagram 900A in which an ME preemptively informs the UICC about an emergency scenario to prevent the UICC from initiating a proactive UICC session. At block 935, the UE 102 is in emergency data connection with BS 106 of satellite 104. In some examples, the ME 122 communicates an indication of the emergency state 957 to the UICC 125 prior to the UICC 125 initiating a proactive session (e.g., prior to the UICC 125 communicating an open channel command). At block 960, the UICC 125 can block proactive session initiation based on the emergency state.

[0083] FIG. 9B shows a message flow diagram 900B in which an ME informs the UICC about an emergency scenario as part of a terminal response of a proactive UICC session procedure. At block 935, the UE 102 is in emergency data connection with BS 106 of satellite 104. The UICC 125 communicates an open channel command 342 to the ME 122. The ME 122 does not attempt to establish PDN connectivity due to the emergency data connection. Instead, at block 943, the ME 122 determines to block non-emergency requests such as the open channel command. The ME 122 communicates a terminal response 948 indicating that the access technology is unable to process the command. Additionally, or alternatively, the terminal response includes anDocket No. 14730881400PCTindication of the emergency. At block 960, the UICC 125 can block proactive session initiation based on the emergency state.

[0084] FIG. 10 shows a flow diagram 1000 of example operations of an ME a UE for communicating RAT restriction information to a UICC. In block 1032, and as described above with respect to FIG. 3, block 332, the UE camps on a cell of a RAN using a first RAT. In block 1048, and as described above with respect to FIG. 6, element 648, the ME communicates, to a UICC of the UE, RAT restriction information associated with at least the first RAT and the RAN.

[0085] FIG. 11 shows a flow diagram 1100 of example operations of a UICC of a UE for receiving RAT restriction information from an ME. In block 1132, and as described above with respect to FIG. 3, block 332, the UICC communicates, to an ME, a command associated with a proactive UICC session while the ME is using a first RAT of a RAN. In block 1148, and as described above with respect to FIG. 6, element 648, the UICC receives, from the ME, RAT restriction information associated with at least the first RAT and the RAN.

[0086] FIG. 12 is a block diagram illustrating an example UE 1202. Note that the depicted hardware configurations represent the processing components and communication components of a UE 1202 (such as the UE 102 described herein). The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like.

[0087] The UE 1202 includes antennas 1211 A, a radio frequency front end (RF front end) 121 IB, and radio-frequency transceivers (e.g., an LTE transceiver 1203A and a 5G NR transceiver 1203B) for communicating with a network entity (such as an NTN node). The RF front end 121 IB includes one or more modems configured for the corresponding RAT(s) employed (for example, 5G NR, one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), signal processors, and the like. In the example illustrated in FIG. 12, the RF front end 121 IB of the UE 1202 may couple or connect the LTE transceiver 1203 A, and the 5G NR transceiver 1203B to the antennas 1211 A to facilitate various types of wireless communication. The RF front end 121 IB operates, in effect, as a physical (PHY) transceiver interface to conduct and process signaling between the one or more processor(s) 1203C and antennas 1211 A so as to facilitate various types of wireless communication.

[0088] The antennas 1211 A of the UE 1202 may include an array of multiple antennas that may be tuned to one or more frequency bands associated with a corresponding RAT. The antennas 1211 A and the RF front end 121 IB may be tuned to, and / or be tunable to, one or more frequencyDocket No. 14730881400PCTbands defined by the 3 GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 1203A, and / or the 5G NR transceiver 1203B. Additionally, the antennas 1211 A, the RF front end 121 IB, the LTE transceiver 1203 A, and / or the 5G NR transceiver 1203B may be configured to support beamforming for the transmission and reception of communications with an NTN node (e.g., the BS 106 and satellite 104). By way of example and not limitation, the antennas 1211A and the RF front end 121 IB may be implemented for operation in subgigahertz bands, sub-6 GHz bands, and / or above 6 GHz bands that are defined by the 3GPP LTE and 5GNR communication standards.

[0089] The UE 1202 also includes processor(s) 1203C and computer-readable storage media (CRM) 1203D. The processor(s) 1203C may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASIC), and the like. To illustrate, the processor(s) 1203C may include an application processor (AP) utilized by the UE 1202 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor of the RF front end 121 IB.

[0090] CRM 1203D may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), Flash memory, solid-state drive (SSD) or other mass-storage devices, and the like useable to store one or more sets of executable software instructions and associated data that manipulate the one or more processor(s) 1203C and other components of the UE 1202 to perform the various functions described herein and attributed to the UE 1202. The sets of executable software instructions include, for example, an operating system (OS) and various drivers (not shown), and various software applications (not shown), which are executable by processor(s) 1203C to enable user-plane communication, control-plane signaling, and user interaction with the UE 1202.

[0091] The UE 1202 includes ME 122 and UICC 125. The ME 122 can implement a NAS layer 1208, an RRC layer 1204, and a PHY / MAC layer 1203 for communicating with corresponding layers implemented in a base station.

[0092] In accordance with aspects of this disclosure, the UE 1202 includes a RAT restriction information module 1280. The RAT restriction information module 1280 can include information (including code and / or data) facilitating message communication and message content communicated between ME 122 and UICC 125. For example, the RAT restriction informationDocket No. 14730881400PCTmodule 1280 can include the tables shown in FIG. 8A to FIG. 8D, message formats, heuristics or rules to implement the techniques of the disclosure, or other information supporting the techniques of the disclosure.

[0093] FIG. 13 shows a block diagram of an example wireless communication system 1300 showing hardware features and communication interfaces. The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like. The wireless communication system 1300 includes the same elements as described with reference to FIG. 1, including the UE 102, the BS 106, the satellite 104, and the CN 110. In some implementations, the UE 102 can support at least a 5G NR (or simply, “NR”) or E-UTRA air interface to communicate with the BS 106. The BS 106 connects to the CN 110 via an interface (e.g., SI or NG interface). The BS 106 can connect to other base stations (including the BS 106' or the BS 1314 operating a TN cell 1317) via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0094] The BS 106 is equipped with processing hardware 1304 that can include a receiver 1305B configured to receive data in the uplink direction. The processing hardware 1304 can also include a transmitter 1305 A configured to transmit data in the downlink direction. The processing hardware further can include one or more general-purpose processor(s) 1305C (e.g., CPUs) and a non-transitory computer-readable memory (CRM) 1305D storing instructions that the one or more general-purpose processors execute. Additionally, or alternatively, the processing hardware 1304 can include special-purpose processing units. The processor 1305C may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs), and the like. CRM 1305D may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory usable to store device data of the BS 106. The satellite 104 can include processing hardware 1306, such as a transmitter 1307A, a receiver 1307B, a processor 1307C, and CRM 1307D (similar to components 1304, 1305A, 1305B, 1305C and 1305D ofthe BS 106). In some implementations, the components 1307A, 1307B, 1307C and 1307D are shared or commonly implemented with the components 13O5A, 1305B, 1305C and 1305D. The BS 1314 can include similar components (not shown) as the processing hardware 1304.

[0095] The CN 110 can be an EPC and / or a 5GC. Among other components, the EPC can include a Serving Gateway (SGW), a Mobility Management Entity (MME), a Home SubscriberDocket No. 14730881400PCTServer (HSS), and a Packet Data Network Gateway (PGW). The SGW in general is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME is configured to manage authentication, registration, paging, and other related functions. The PGW provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC includes a User Plane Function (UPF), a Unified Data Management (UDM), an Access and Mobility Management Function (AMF), and / or Session Management Function (SMF). Generally speaking, the UPF is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF is configured to manage authentication, registration, paging, and other related functions, and the SMF is configured to manage PDU sessions. The HSS and the UDM store and maintain subscription information regarding the UE 102. The CN 110 can be implemented by one or more processing elements (shown as processing hardware 1310). The processing hardware 1310 can include a transmitter 1311 A, a receiver 131 IB, a processor 1311C, and a CRM 131 ID, similarly, to corresponding components described with reference to processing hardware 1302, 1306, and 1304.

[0096] The transmitters 1303 A, 1307A, 1305A, and 1311A and receivers 1303B, 1307B, 1305B, and 131 IB are examples of a communication unit. The processors 1303C, 1307C, 1305C, and 1311C are examples of a processing system. Other examples of a communication unit and a processing system are possible, including some examples that are commonly used in a wireless communication system. The BS 106, UE 102, satellite 104, and CN 110 can include other components not illustrated in FIG. 13.

[0097] FIG. 1 through FIG. 13 and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potential implementations or limit the scope of the claims. Some implementations may perform additional operations, fewer operations, operations in parallel or in a different order, and some operations differently. Alternatively, or in addition to the other examples described herein, examples include any combination of the following enumerated example implementation options (referred to as clauses for clarity).

[0098] Clause 1: A method of a mobile equipment (ME (122)) of a user equipment (UE (102)) for wireless communication, the method comprising: camping (332, 1032) on a cell of a radio access network (RAN) using a first radio access technology (RAT); and communicating (648,Docket No. 14730881400PCT1048), to a universal integrated circuit card (UICC (125)) of the UE, RAT restriction information (119) associated with at least the first RAT and the RAN.

[0099] Clause 2: The method of clause 1, wherein the communicating the RAT restriction information includes communicating the RAT restriction information when the UE is not allowed to use the first RAT or the first RAT is associated with the non-terrestrial network (NTN) RAT.

[0100] Clause 3: The method of clause 1 or 2, further comprising: receiving, from the UICC, a command associated with a proactive UICC session; and communicating the RAT restriction information in a terminal response (648).

[0101] Clause 4: The method of clause 3, wherein the command is an Open Channel command (342), and wherein the terminal response is an “Access technology unable to process command” message indicating the RAT restriction information for at least the first RAT.

[0102] Clause 5: The method of any one of clauses 1 to 4, wherein the RAT restriction information includes at least one of a first value ('00') indicating RAT restriction of a current RAT in use by the ME; a second value ('01') indicating RAT restriction for an NG-RAN; a third value ('02') indicating RAT restriction for a Satellite NG-RAN; a fourth value ('03') indicating RAT restriction for an E-UTRAN; a fifth value ('04') indicating RAT restriction for a Satellite E-UTRAN; a sixth value ('05') indicating RAT restriction for a UTRAN; or a seventh value ('06') indicating RAT restriction for a GPRS.

[0103] Clause 6: The method of any one of clauses 1 to 5, wherein the RAT restriction information includes additional RAT restriction information for at least a second RAT other than the first RAT.

[0104] Clause 7: The method of clause 6, wherein the additional RAT restriction information includes at least one of: a value associated with the second RAT from among a plurality of predefined RATs; a value associated with any NTN RAT; or a bitmap including bit indicators for each of a plurality of predefined RATs.

[0105] Clause 8: The method of any one of clauses 1 to 7, further comprising: transmitting, to the UICC, an indication (957) of an emergency scenario (935); and preventing the UICC from initiating a proactive UICC session based on the emergency scenario.

[0106] Clause 9: The method of any one of clauses 1 to 8, further comprising, during an emergency scenario (935): receiving, from the UICC, a command (342) associated with a proactive UICC session; blocking (943) the proactive UICC session based on the command beingDocket No. 14730881400PCTa non-emergency request; and communicating, to the UICC, a terminal response (948) including an indication of the emergency scenario.

[0107] Clause 10: A method of a universal integrated circuit card (UICC (125)) of a user equipment (UE (102)) for wireless communication, the method comprising: communicating (342, 1142), to a mobile equipment (ME (122)) of the UE, a command associated with a proactive UICC session while the ME is using a first radio access technology (RAT) of a radio access network (RAN); and receiving (648, 1148), from the ME, RAT restriction information (119) associated with at least the first RAT and the RAN.

[0108] Clause 11: The method of clause 10, wherein the receiving the RAT restriction information includes receiving the RAT restriction information when the UE is not allowed to use the first RAT or the first RAT is associated with a non-terrestrial network (NTN) RAT

[0109] Clause 12: The method of clause 10 or 11, further comprising: receiving the RAT restriction information in a terminal response (648), wherein the terminal response is an “Access technology unable to process command” message.

[0110] Clause 13: The method of any one of clauses 10 to 12, wherein the command is an Open Channel command (342).

[0111] Clause 14: The method of any one of clauses 10 to 13, wherein the RAT restriction information includes at least one of: a first value ('00') indicating RAT restriction of a current RAT in use by the ME; a second value ('01') indicating RAT restriction for an NG-RAN; a third value ('02') indicating RAT restriction for a Satellite NG-RAN; a fourth value ('03') indicating RAT restriction for an E-UTRAN; a fifth value ('04') indicating RAT restriction for a Satellite E-UTRAN; a sixth value ('05') indicating RAT restriction for a UTRAN; or a seventh value ('06') indicating RAT restriction for a GPRS.

[0112] Clause 15: The method of any one of clauses 10 to 14, wherein the RAT restriction information includes additional RAT restriction information for at least a second RAT other than the first RAT.

[0113] Clause 16: The method of clause 15, wherein the additional RAT restriction information includes at least one of: a value associated with the second RAT from among a plurality of predefined RATs; a value associated with any NTN RAT; or a bitmap including bit indicators for each of a plurality of predefined RATs.Docket No. 14730881400PCT

[0114] Clause 17: The method of any one of clauses 10 to 16, further comprising: receiving, from the UICC, an indication (957) of an emergency scenario (935); and refraining from initiating or retrying the proactive UICC session based on the emergency scenario.

[0115] Clause 18: An apparatus for use in a user equipment (UE), comprising: a communication interface; and a processing system configured to control the communication interface to implement any one of the methods of any one of clauses 1 to 17.

[0116] Aspects of the subject matter described in this disclosure can be implemented as a computer-readable medium having stored therein instructions which, when executed by a processor, causes the processor to perform any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as a system having means for implementing any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as an apparatus having one or more processors configured to perform one or more operations from any one of the above-mentioned functionalities.

[0117] The following additional considerations may apply to the foregoing and the following discussions. Generally speaking, description for one of the above figures can apply to another of the above figures. Any event or block described above can be optional. For example, an event orblock with dashed lines can be optional. In some implementations, “message” is used and can be replaced by “information element (IE),” and vice versa. In some implementations, “IE” is used and can be replaced by “field,” and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters,” and vice versa. In some implementations, “some” means “one or more.” In some implementations, “at least one” means “one or more.”

[0118] Unless defined otherwise, technical and scientific terms used herein have the same meaning as is commonly understood by one of ordinary skill in the art to which this specification belongs. The terms “first,” “second,” and the like, as used herein do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The use of terms “including,” “comprising” or “having” and variations thereof herein are meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms “connected” and “coupled” are not restricted to physical or mechanical connections or couplings and can include electrical connections or couplings, whether direct or indirect. Furthermore, terms “circuit” and “circuitry” and “control unit” may include either a singleDocket No. 14730881400PCTcomponent or a plurality of components, which are either active and / or passive and are connected or otherwise coupled together to provide the described function. In addition, the term operationally coupled as used herein includes wired coupling, wireless coupling, electrical coupling, magnetic coupling, radio communication, software based communication, or combinations thereof.

[0119] Some or all of the foregoing or the following implementations can be jointly combined or formed to be a new or another one implementation. The foregoing or the following techniques can be used to solve at least (but not limited to) the issue(s) or scenario(s) mentioned in this disclosure. Any two or more than two of the foregoing or the following paragraphs, (sub)-bullets, points, actions, or claims described in each method / technique / implementation may be combined logically, reasonably, and properly to form a specific method. Any sentence, paragraph, (sub)-bullet, point, action, or claim described in each of the foregoing or the following technique(s) / implementation(s) / concept(s) may be implemented independently and separately to form a specific method. Dependency, such as “based on,” “more specifically,” “where” or etc., in technique(s) / implementation(s) / concept(s) mentioned in this disclosure is just one possible implementation which would not restrict the specific method.

[0120] As used herein, the terms “user device”, “user equipment” (for example, UE 102), “wireless communication device”, “mobile communication device”, “communication device”, or “mobile device” refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, Internet-of-Things (loT) devices, palm-top computers, wireless electronic mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, display sub-systems, driver assistance systems, vehicle controllers, vehicle system controllers, vehicle communication system, infotainment systems, vehicle telematics systems or subsystems, vehicle display systems or subsystems, vehicle data controllers, point-of-sale (POS) terminals, health monitoring devices, drones, cameras, media-streaming dongles, other personal media devices, wearable devices such as smartwatches, wireless hotspots, femtocells, broadband routers or other types of routers, and similar electronic devices which include a programmable processor and memory and circuitry configured to perform operations as described herein. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, theDocket No. 14730881400PCTuser device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0121] Certain techniques are described in this disclosure as including logic or a number of components or modules. Modules can be software modules (e. ., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general -purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0122] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general -purpose processors or one or more specialpurpose processors.

[0123] As used herein, the terms “component” and “module” are intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly construed to mean “based at least in part on.”

[0124] As used herein, a phrase referring to a list of items separated by “or” refers to any combination of those items, including single members. For example, “a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

[0125] In this disclosure, an expression of “X / Y” may include the meaning of any of the following: “X or Y” or “X and Y” or “X and / or Y." An expression of “(A) B” or “B (A)” may include concept of “only B ” An expression of “(A) B” or “B (A)” may include the concept of “A+B” or “B+A.”Docket No. 14730881400PCT

[0126] In this disclosure, the term "can" indicates a capability, or alternatively indicates a possible implementation option. The term "may" indicates a permission or a possible implementation option.

[0127] Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0128] The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithm processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.

[0129] As described above, some aspects of the subject matter described in this specification can be implemented as software. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein can be implemented as one or more modules of one or more computer programs. Such computer programs can include non-transitory processor-executable or computer-executable instructions encoded on one or more tangible processor-readable or computer-readable storage media for execution by, or to control the operation of, a data processing apparatus including the components of the devices described herein. By way of example, and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media.

[0130] Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein but are to beDocket No. 14730881400PCTaccorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0131] Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0132] The drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

[0133] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. While the aspects of the disclosure have been described in terms of various examples, any combination of aspects from any of the examples is also within the scope of the disclosure. The examples in this disclosure are provided for pedagogical purposes.

Claims

1. Docket No. 14730881400PCTCLAIMSWhat is claimed is:

1. A method of a mobile equipment (ME (122)) of a user equipment (UE (102)) for wireless communication, the method comprising:camping (332, 1032) on a cell of a radio access network (RAN) using a first radio access technology (RAT);receiving, from a universal integrated circuit card (UICC (125)) of the UE, a command associated with a proactive UICC session; andcommunicating (648, 1048), to the UICC, a terminal response (648) in response to the command, the terminal response including RAT restriction information (119) associated with at least the first RAT and the RAN.

2. The method of claim 1, wherein the communicating the RAT restriction information includes communicating the RAT restriction information when the UE is not allowed to use the first RAT or the first RAT is associated with a non-terrestrial network (NTN) RAT.

3. The method of claim 1 or 2, wherein the command is an Open Channel command (342), and wherein the terminal response is an “Access technology unable to process command” message indicating the RAT restriction information for at least the first RAT.

4. The method of any one of claims 1 to 3, wherein the RAT restriction information includes at least one of:a first value ('00') indicating RAT restriction of a current RAT in use by the ME;a second value ('01') indicating RAT restriction for an NG-RAN;a third value ('02') indicating RAT restriction for a Satellite NG-RAN;a fourth value ('03') indicating RAT restriction for an E-UTRAN;a fifth value ('04') indicating RAT restriction for a Satellite E-UTRAN;a sixth value ('05') indicating RAT restriction for a UTRAN; ora seventh value ('06') indicating RAT restriction for a GPRS.Docket No. 14730881400PCT5. The method of any one of claims 1 to 4, wherein the RAT restriction information includes additional RAT restriction information for at least a second RAT other than the first RAT; and wherein the additional RAT restriction information includes at least one of:a value associated with the second RAT from among a plurality of predefined RATs; a value associated with any NTN RAT; ora bitmap including bit indicators for each of a plurality of predefined RATs.

6. The method of any one of claims 1 to 5, further comprising:transmitting, to the UICC, an indication (957) of an emergency scenario (935); and preventing the UICC from initiating the proactive UICC session based on the emergency scenario, wherein the preventing the UICC from initiating the proactive UICC session includes at least one of:blocking (943) the proactive UICC session based on the command being a nonemergency request, orcommunicating, to the UICC, a terminal response (948) including an indication of the emergency scenario.

7. A method of a universal integrated circuit card (UICC (125)) of a user equipment (UE (102)) for wireless communication, the method comprising:communicating (342, 1142), to a mobile equipment (ME (122)) of the UE, a command associated with a proactive UICC session while the ME is using a first radio access technology (RAT) of a radio access network (RAN); andreceiving (648, 1148), from the ME, RAT restriction information (119) associated with at least the first RAT and the RAN.

8. The method of claim 7, wherein the receiving the RAT restriction information includes receiving the RAT restriction information when the UE is not allowed to use the first RAT or the first RAT is associated with a non-terrestrial network (NTN) RAT9. The method of claim 7 or 8, further comprising:receiving the RAT restriction information in a terminal response (648), wherein the terminal response is an “Access technology unable to process command” message.

10. The method of any one of claims 7 to 9, wherein the command is an Open Channel command (342).Docket No. 14730881400PCT11. The method of any one of claims 7 to 10, wherein the RAT restriction information includes at least one of:a first value ('00') indicating RAT restriction of a current RAT in use by the ME;a second value ('01') indicating RAT restriction for an NG-RAN;a third value ('02') indicating RAT restriction for a Satellite NG-RAN;a fourth value ('03') indicating RAT restriction for an E-UTRAN;a fifth value ('04') indicating RAT restriction for a Satellite E-UTRAN;a sixth value ('05') indicating RAT restriction for a UTRAN; ora seventh value ('06') indicating RAT restriction for a GPRS.

12. The method of any one of claims 7 to 11, wherein the RAT restriction information includes additional RAT restriction information for at least a second RAT other than the first RAT.

13. The method of claim 12, wherein the additional RAT restriction information includes at least one of:a value associated with the second RAT from among a plurality of predefined RATs; a value associated with any NTN RAT; ora bitmap including bit indicators for each of a plurality of predefined RATs.

14. The method of any one of claims 7 to 13, further comprising:receiving, from the ME, an indication (957) of an emergency scenario (935); and refraining from initiating or retrying the proactive UICC session based on the emergency scenario.

15. An apparatus for use in a user equipment (UE), comprising:a communication interface; anda processing system configured to control the communication interface to implement any one of the methods of any one of claims 1 to 14.

Images