Managing non-terrestrial network (NTN) access

Abstract

This disclosure provides systems, methods, and apparatuses for managing a user equipment (UE) access to a non-terrestrial network (NTN) (such as a satellite (104) and an NTN BS 106) based on subscription, usage settings, or service type. The UE (102) may be a multi-Universal Subscriber Identity Module (USIM) device. Initially, the UE attempts to access a core network (110) via an NTN cell using a first USIM (122) and / or a first usage setting (124) (e.g., voice-centric). The UE receives a core network message indicating NTN access is not allowed. Rather than disabling an NTN access capability of its modem (108), the UE can attempt to access the NTN cell using a second USIM (162), a second usage setting (164) (e.g., non-voice-centric), or a second application (166) (e.g., emergency messaging) for which the UE is allowed (176) to use the NTN.

Description

Docket No. 14730879200PCTMANAGING NON-TERRESTRIAL NETWORK (NTN) ACCESS RELATED APPLICATION

[0001] This application claims the priority benefit of U.S. Provisional Patent Application Serial No. 63 / 755,029, filed February 6, 2025, entitled “MANAGING NON- TERRESTRIAL NETWORK (NTN) ACCESS,” 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 managing services over terrestrial network (TN) and non-terrestrial network (NTN).DESCRIPTION OF RELATED TECHNOLOGY

[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 a base station) enabling communication for a mobile communication device (referred to as a user equipment (UE)). Each base station operates one or more cells to provide coverage for the UE. Recent developments in wireless communication technology include the use of non-terrestrial networks (NTNs). An NTN refers to a network, or segment of networks, using radio frequency (RF) resources on board an NTN node, such as a satellite, uncrewed aircraft system (UAS), or high altitude platform (HAP). An NTN node can include a spaceborne vehicle (such as a satellite) or an airborne vehicle (such as a UAS). For simplicity, the discussion below refers to all such apparatus as satellites or NTN nodes. The altitude at which satellites operate can vastly increase the distances between a UE and the NTN base station compared to distances between the UE and terrestrial network (TN) base stations. Furthermore, link capacity for satellite-based networks can be relatively low, compared to terrestrial networks.

[0005] Some network operators are deploying NTN access for their subscribers. In some implementations, network operators make roaming agreements with other operators to provide NTN access for users with roaming subscriptions. For example, an NTN can provide limitedDocket No. 14730879200PCTaccess or roaming service for various UEs with subscriptions from other network operators. A network operator might desire to restrict NTN access to a particular UE or group of UEs based on a location, time, subscription, service, or usage, among other examples. Current techniques controlling NTN access fail to address many of the possible NTN access scenarios.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 for wireless communication by a user equipment (UE). The method includes the UE camping on a non-terrestrial network (NTN) cell of a satellite using a first universal subscriber information module (USIM) and a first UE usage setting. The method includes the UE transmitting an Attach Request message to a core network via the NTN cell. The method includes the UE receiving, from the core network, an Attach Response message that indicates NTN access is not allowed. The method includes the UE accessing the NTN cell using a second USIM, a second usage setting, or a second application for which NTN access is allowed.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method of a core network for wireless communication. The method includes the core network transmitting a message to a UE that uses a first USIM, the message indicating a first usage setting or a first service type for which the UE is not allowed to access the core network via an NTN. The method includes the core network communicating with the UE via the NTN cell using a second USIM, a second usage setting, or second service type for which the UE is allowed to access the core network via the NTN.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus or system. In some implementations, an apparatus includes a communication unit and a processing system. The processing system is configured to control the communication unit to implement any one of the methods described in this document. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0010] 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.Docket No. 14730879200PCTBRIEF DESCRIPTION OF THE DRAWINGS

[0011] 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.

[0012] FIG. 1 shows an example wireless communication system in which a user equipment (UE) can communicate with a non-terrestrial network (NTN) where NTN access is allowed depending on universal subscriber information module (USIM), usage setting, application, or service type.

[0013] FIG. 2A shows example USIM options.

[0014] FIG. 2B shows example usage settings.

[0015] FIG. 2C shows example services.

[0016] FIG. 3 shows example operations of a UE for managing NTN access and public land mobile network (PLMN) access.

[0017] FIG. 4 shows a block diagram 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.

[0018] FIG. 5A shows an example table of PLMN access information where PLMN access is associated with a UE usage setting.

[0019] FIG. 5B shows an example table of PLMN access information where PLMN access is associated with an application or service type.

[0020] FIG. 6 shows an example scenario in which a UE attempts to access an NTN cell using a first USIM and a second USIM.

[0021] FIG. 7A shows an example scenario in which a UE attempts to access an NTN cell using a first usage setting and a second usage setting.

[0022] FIG. 7B shows an example scenario in which a UE selects a usage setting for NTN access.

[0023] FIG. 7C shows an example scenario in which a UE accesses an NTN cell based on nonvoice services available at the NTN cell.

[0024] FIG. 8A shows an example scenario in which a UE accesses an NTN cell based on nonvoice services available at the NTN cell.Docket No. 14730879200PCT

[0025] FIG. 8B shows an example scenario in which a UE modifies its usage setting when accessing an NTN cell.

[0026] FIG. 9A shows an example scenario in which a UE modifies its service access based on services available as indicated in an Attach Accept message.

[0027] FIG. 9B shows an example scenario in which a UE modifies its service access based on services available as indicated in a system information message.

[0028] FIG. 10A shows example operations of a UE that refrains from disabling NTN capability when the UE has a second USIM that is allowed to access an NTN cell.

[0029] FIG. 10B shows example operations of a UE that re-enables NTN capability when the UE has a second USIM that is allowed to access an NTN cell.

[0030] FIG. 11A shows example operations of a UE that selects a usage setting based on whether it is accessing a TN or an NTN.

[0031] FIG. 11B shows example operations of a UE that selects a usage setting based on application or service.

[0032] FIG. 11C shows example operations of a UE that selects a usage setting based on which USIM the UE uses for accessing an NTN cell.

[0033] FIG. 11D shows example operations of a UE that selects a usage setting based on information from the NTN cell.

[0034] FIG. 12A shows example operations of a UE that selects a service based on whether it is accessing a TN or an NTN.

[0035] FIG. 12B shows example operations of a UE that selects a service based on application or service.

[0036] FIG. 12C shows example operations of a UE that selects a service based on which USIM the UE uses for accessing an NTN cell.

[0037] FIG. 12D shows example operations of a UE that selects a service based on information from the NTN cell.

[0038] FIG. 12E shows example operations of a UE that selectively performs a service registration based on whether it is accessing a TN or an NTN.

[0039] FIG. 12F shows example operations of a UE that selectively performs a service registration based on application or service.Docket No. 14730879200PCT

[0040] FIG. 12G shows example operations of a UE that selectively performs a service registration based on which USIM the UE uses for accessing an NTN cell.

[0041] FIG. 12H shows example operations of a UE that selectively performs a service registration based on information from the NTN cell.

[0042] FIG. 13A shows example operations of a UE that enables or disables a service based on whether it is accessing a TN or an NTN.

[0043] FIG. 13B shows example operations of a UE that enables or disables a service based on which USIM the UE uses for accessing an NTN cell.

[0044] FIG. 13C shows example operations of a UE that enables or disables a service based on information from the NTN cell.

[0045] FIG. 13D shows example operations of a UE that enables different services depending on whether it is accessing a TN or an NTN.

[0046] FIG. 13E shows example operations of a UE that enables different services depending on which USIM the UE uses for accessing an NTN cell.

[0047] FIG. 13F shows example operations of a UE that enables different services depending on information from the NTN cell.

[0048] FIG. 14A shows example operations of a UE that disables a service that is not available from the NTN cell.

[0049] FIG. 14B shows example operations of a UE that enables a service based on a message from the NTN cell indicating that the service is available from the NTN cell.

[0050] FIG. 15A shows example operations of a network entity in a radio access network (RAN) that manages service access for one or more UEs.

[0051] FIG. 15B shows example operations of a RAN network entity that controls disablement or enablement of services for one or more UEs.

[0052] FIG. 16A shows example operations of a core network that controls service access based on whether the UE is camped on an NTN cell.

[0053] FIG. 16B shows example operations of a core network that controls disablement or enablement of services for a UE based on whether the UE is camped on an NTN cell.

[0054] FIG. 17A shows a block diagram of an example wireless communication system implementing an NTN base station (BS) connecting to a satellite via an NTN gateway using a transparent payload implementation.Docket No. 14730879200PCT

[0055] FIG. 17B shows a block diagram of an example wireless communication system implementing an NTN BS with feeder links to multiple satellites.

[0056] FIG. 17C shows a block diagram of an example wireless communication system implementing an NTN BS onboard on a satellite using a regenerative payload implementation.

[0057] FIG. 18 shows an example control plane protocol stack in accordance with aspects of this disclosure.

[0058] FIG. 19 shows a block diagram illustrating an example UE.

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

[0060] 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 the art 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 3rd Generation Partnership Project (3GPP) wireless standards, such as the 4th generation (4G) Long Term Evolution (LTE) and 5th generation (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, 6th generation (6G), WiFi, or future radio technology.

[0061] This disclosure provides systems, methods, and apparatuses for managing radio access network (RAN) access and access to core network services by a user equipment (UE). In some implementations, the UE's access to core network services can depend on whether the UE is communicating via a terrestrial network (TN) or a non -terrestrial network (NTN). An NTN-capable UE has software and hardware that the UE can use to access an NTN RAN. NTN access refers to the UE using an NTN RAN to access a core network (CN). In some aspects, a UE can obtain NTN access based on a particular subscription, usage setting, application, or service type. In legacy technologies, a technical specification assumed a UE would have a single USIM for accessing either a TN RAN or an NTN RAN. The legacy UE would disable its NTN capabilityDocket No. 14730879200PCT(i.e., refrain from further attempts for NTN access) after receiving a non-access stratum (NAS) message indicating NTN access is not allowed. A core network might indicate NTN access is not allowed for a variety of reasons, including subscription, service availability, or congestion, among other reasons. Furthermore, a UE has a usage setting that relates to the type of UE and associated services that the UE is expected to use from a core network. Examples of usage settings include voice-centric and non-voice-centric (to refer to data, messaging, or other nonvoice services).

[0062] UE capabilities continue to evolve such that a UE can have multiple usage settings that are used for different core networks or services. Furthermore, a UE might have more than one Universal Subscriber Identity Module (USIM) (sometimes referred to as a dual-USIM, multi-USIM, multiple USIM, or MUSIM device). Absent the techniques of this disclosure, a UE might disable the UE's NTN capability based on a NAS message that indicates NTN access is not allowed, even though the UE might have a different USIM, different usage setting, or some applications for which NTN access would be allowed. For example, the UE might have a first USIM for which NTN access is not allowed based on a subscription (or roaming agreement). However, the UE might have a second USIM for a different subscription for which NTN access is allowed. If the UE were to disable its NTN capability, the UE might not attempt to access the NTN RAN and core network using the second USIM. In some aspects of this disclosure, the UE refrains from disabling the NTN capability when the UE has another USIM. In some aspects, the UE disables NTN capability when using the first USIM and re-enables the NTN capability when using the second USIM. In this disclosure, “USIM” may refer to a physical USIM card, a Universal Integrated Circuit Card (UICC), a USIM profile stored in an USIM chip embedded in the UE, and / or an Embedded SIM (eSIM) with multiple profiles.

[0063] Another aspect of this disclosure enables the UE to manage its usage settings based on NTN access. For example, the UE can change its usage setting depending on the available NTN access. In some implementations, the UE uses a voice-centric usage setting when accessing a TN cell, since the TN RAN generally has more capacity and less latency than an NTN RAN. When accessing an NTN cell, the UE can change to a non-voice-centric usage setting to limit power consumption or network overhead. In some implementations, an operator might provide a subscription that allows the UE to access an NTN cell using a non-voice-centric usage setting and disallows NTN access for the voice-centric usage setting. In some implementations, the operator provides the subscription in a USIM of the UE. In accordance with this disclosure, theDocket No. 14730879200PCTUE can adjust its usage setting based on which RAN type is available, user subscription, or application requirements.

[0064] In some aspects, the UE can determine whether to perform an IP multimedia subsystem (IMS) registration (or registration for a particular service) based on NTN access for a particular USIM, usage setting, information from the NTN RAN, or a message from the core network. For example, an NTN cell or the core network can indicate which services are allowed for the UE using NTN access. For example, a core network can transmit an Attach Accept message that indicates allowed services (or allowed usage setting, application type, or other indicia of permissible core network access) for which the UE can use NTN access. In some implementations, the UE can disable some services and enable other services when using NTN access. Alternatively, or additionally, the UE can enable or disable particular services based on an indication in a system information message. In some implementations, the UE can select which USIM or UE usage setting to use for NTN access depending on which services the CN makes available to the UE.

[0065] In some aspects, the UE can obtain or store public land mobile network (PLMN) access information. Each TN or NTN typically has a different PLMN identity (ID), although this is not necessarily required. An operator may operate one or more PLMNs. An operator will typically configure a UE to register to a home PLMN (HPLMN) or equivalent HPLMN (EHPLMN) of the operator when the UE is in a coverage area of the HPLMN / EHPLMN. For the sake of simplicity in this disclosure, an HPLMN can refer to either an HPLMN or an EHPLMN. Meanwhile, when the UE is out of a coverage area of the HPLMN, the UE might register with another operator's PLMN (referred to as a Visited PLMN, or VPLMN) under a roaming agreement between the operators. A satellite operator (with an NTN PLMN) might support roaming agreements from one or multiple TN operators. The NTN access to the NTN PLMN might depend on the UE's subscription, usage setting, and / or services. In some aspects of this disclosure, the UE can modify its USIM, usage setting, or IMS registration based on the PLMN. The UE stores or obtains PLMN access information for use by a particular USIM. In some implementations, the PLMN access information can indicate the allowed usage settings or supported services on a per-PLMN basis. The PLMN access information can also include radio access technology (RAT) information and frequency information to aid the UE in scanning frequencies supporting the PLMN using a particular RAT.Docket No. 14730879200PCT

[0066] In some implementations, the UE's application requirements might impact which USIM, usage setting, or service to use. For example, the UE having a particular messaging application might enable NTN access with a particular usage setting and / or IMS registration that is allowed for that application. The particular messaging application may be an emergency messaging application. Meanwhile, other applications or services might not be allowed to access a PLMN via an NTN cell. The UE or the NTN cell might control NTN access based on any combination of application, service type, usage setting, USIM (i.e., subscription), RAT, or other consideration. This disclosure includes several example scenarios and implementation options to provide an understanding of how the UE and NTN cell can manage NTN access using these various considerations.

[0067] Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. A UE can access an NTN cell when allowed for a particular use. NTN operators can support NTN access (either for directly subscribed users or roaming users) with more control over which UEs and / or conditions are allowed. The techniques of this disclosure provide more granular management of NTN access than historically available to network operators. A potential technical advantage for the UE is that the UE can enjoy NTN access, albeit restricted, where they might not otherwise be able to access the NTN absent the techniques of this disclosure.

[0068] FIG. 1 shows an example wireless communication system 100 in which a UE 102 can communicate with an NTN where NTN access is allowed depending on USIM, usage setting, application, or service type. The example wireless communication system 100 shows the UE 102 attempting to communicate with a CN 110 via 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, as further described with reference to FIG. 17A and FIG. 17C. For a transparent payload implementation (as shown in FIG. 17A), a satellite 104 can apply RF filtering and frequency conversion and amplification, and not change the waveform signal. For a regenerative payload implementation (such as shown in FIG. 17C), a satellite 104 can apply RFDocket No. 14730879200PCTfiltering, frequency conversion and amplification, demodulation and decoding, routing, and coding / modulation.

[0069] An NTN gateway 109 (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 resources). 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 NTN BS 106' on the ground (when present) or the BS 106 (when onboard the satellite 104). The satellite 104, the NTN gateway 109, and the BS 106 / 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. Alternatively, 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-Thing (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 (6GC).

[0070] In this disclosure, the NTN node 101 can refer to the satellite 104, the BS 106 / 106', or collectively to the satellite 104 and the BS 106 / 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), orDocket No. 14730879200PCT• 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).

[0071] 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.

[0072] The radio connection between the UE 102 and the satellite 104 can be referred to as a 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 109. An NTN can also include inter-satellite links (ISLs), such as when multiple NTN nodes form constellations and communicate directly between the NTN nodes. The UE 102 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 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, where the NTN RAN provides AS connections. In order to access core network services, the UE 102 and the CN 110 communicate non-access stratum (NAS) messages. For example, the UE 102 can communicate a network registration request (e.g., Attach Request message) 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 (e.g., an Attach Accept message or Attach Reject message, collectively referred to as an Attach Response message) or other downlink NAS messages to the UE 102 via the NTN RAN.

[0073] The CN 110 includes various network functions for subscription, mobility management, and service management. The CN 110 may restrict access to an NTN for a variety of reasons, such as based on a subscription, to conserve limited bandwidth / power, or to maintain a quality of service for a UE or group of UEs. In some implementations, a network operator may not allow NTN access based on a usage setting or particular service type. As an example, the network operator may not allow voice traffic over an NTN but allow data traffic (such as for loT devices).

[0074] Considering a first scenario, a UE 102 might use a first USIM 122 (associated with particular subscription or other parameters) to perform an attach procedure with an NTN. For example, the UE 102 can transmit an Attach Request message to the CN 110 via the satellite 104 / BS 106. In the attach procedure, the UE 102 receives an Attach Reject message including aDocket No. 14730879200PCTreject cause (such as a reject cause code associated with NTN access not allowed). According to 3GPP technical specification (TS) 24.301 (version 19.0.0), the UE would disable its NTN access capability. For example, if the UE 102 receives an ATTACH REJECT or TRACKING AREA UPDATE REJECT message including both EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "NB-IoT not allowed" after the UE 102 requests access to the satellite 104, the UE 102 may disable the NB-IoT capability and memorize the identity of the PLMN where the NB-IoT capability was disabled. The UE 102 uses that stored information in subsequent PLMN selections to prevent selecting an NTN cell of the NTN. If the UE 102 disables its NTN access capability, the UE 102 does not search for an NTN cell of the NTN. However, in some cases, the UE 102 may be able to access the NTN with a second USIM 162. In accordance with aspects of this disclosure, the UE 102 can change from the first USIM 122 to the second USIM 162 and reattempt the attach procedure with the NTN (or with another NTN).

[0075] Similar to the first USIM 122 and the second USIM 162, the UE 102 might have multiple usage settings available. A UE 102 (e.g., a smartphone) that fully supports LTE and 5G networks might be classified and use a “voice centric” usage setting (such as a first usage setting 124). The CN 110 might not allow NTN access for voice-centric devices. Absent the techniques of this disclosure, the UE 102 might disable its NTN capability if the NTN does not support the voicecentric usage setting. For example, according to 3GPP TS 24.501 (version 19.0.0), the UE would disable its NTN access capability (i.e., N1 mode capability for 3GPP access) if the UE's usage setting is "voice centric" and the UE receives an indication that "IMS voice not available" from the core network (such as in a REGISTRATION ACCEPT message). However, the UE 102 might be able to use a second usage setting 164 (e.g., “non-voice-centric”) for which the CN 110 does allow NTN access. In accordance with aspects of this disclosure, the UE 102 can change its current usage setting based on NTN access permissions. In some implementations, the UE 102 performs an attach procedure with an NTN of a first radio access technology (RAT). In the attach procedure, the UE receives an Attach Accept message that indicates voice is not supported. The UE 102 might disable its NTN access of the first RAT and search for a TN or an NTN of a second RAT that supports voice services. However, in some cases, the UE 102 cannot find a TN or an NTN of the second RAT. Additionally, or alternatively, the UE 102 can change its usage setting to the second usage setting 164 and use the NTN access for non-voice services. In suchDocket No. 14730879200PCTcases, the UE operates in a limited service even though the UE is able to perform non-voice services (e.g., message services or data services) via the NTN of the first RAT.

[0076] Generally, a CN 110 can connect to a TN RAN (not shown) and an NTN RAN (represented by the NTN node 101 in FIG. 1). In some cases, the CN 110 may want to provide different services in the TN RAN and the NTN RAN. This is because the NTN RAN and TN RAN may have different capacities. For example, a 5G core (5GC) network connects to a TN NR-RAN and an NTN NR-RAN. The 5GC provides a voice service (i.e., VoNR) over the TN NR-RAN and does not provide the voice service over the NTN NR-RAN. Absent the techniques of this disclosure, the CN 110 might not indicate different services provided in the TN RAN and the NTN RAN to the UE 102. As a result, the UE 102 might stay in the current serving cell of the TN RAN or NTN RAN and not take advantage of different applications or service types that are allowed for NTN access.

[0077] This disclosure provides several examples in which an NTN access is not allowed (shown at block 172 for an example satellite 104') based on a first USIM 122, a first usage setting 124, or a first application or service type 126. Thus, when a UE 102 uses its modem 108 with the first USIM 122, the first usage setting 124, or the first application or service type 126, the NTN access is not allowed (shown collectively as block 120). However, the UE 102 might have a second USIM 162, a second usage setting 164, or a second application or service type 166 for which NTN access is allowed (block 176). When the UE 102 either requires NTN access or has obtained limited NTN access, the UE 102 can use its modem 108 with the second USIM 162, the second usage setting 164, or the second application or service type 166 (shown collectively as block 160).

[0078] FIG. 2A shows example USIM options 250A. The example USIM options 250A include first USIM 222 associated with a subscription that is limited to TN access (or TN roaming), and a second USIM 262 associated with a subscription that supports NTN access (or NTN roaming). When the UE needs NTN access, the UE can use the second USIM 262. Otherwise, the UE might use the first USIM 222. The USIMs 222 and 262 can be from the same network operator or from different network operators.

[0079] FIG. 2B shows example UE usage settings 250B. The example UE usage settings 250B include a voice-centric usage setting 224 and a non-voice-centric usage setting 264. The nonvoice-centric usage setting can be referred to by other terms, such as data-centric, messagingcentric, loT-centric or any other non-voice descriptor. As further described in the followingDocket No. 14730879200PCTexamples, the UE can change its usage setting according to the available NTN access. For example, if the UE receives an Attach Reject message while using the voice-centric usage setting 224, the UE can reattempt an attach procedure using a non-voice-centric usage setting 264. Alternatively, or additionally, if the UE receives an Attach Accept message while using the voicecentric usage setting 224 and the Attach Accept message indicates that voice services are not allowed, the UE can change to the non-voice-centric usage setting 264 and communicate data for non-voice applications.

[0080] FIG. 2C shows example services 250C. The example services 250C include voice services 226 and messaging services 266. Messaging services can refer to short message service (SMS), IP multimedia subsystem (IMS) SMS, SMS over NAS, or emergency messaging, among other examples. Other types of services are possible. As further described with reference to FIG.5B, various RAN and RAT combinations can support different services. When performing a PLMN search or preparing to perform an attach procedure, the UE can enable a particular service 250C based on which service(s) are supported by a particular NTN.

[0081] FIG. 3 shows example operations 300 of a UE for managing NTN access and PLMN access. At block 315, the UE performs a PLMN search based on PLMN access rule(s). For example, the UE can use PLMN access information to search for an available PLMN. In some implementations, the PLMN access information includes an indication of allowed usage settings (such as shown in FIG. 5 A) or application types (such as shown in FIG. 5B). At block 316, the UE selects an NTN for NTN access based on an application or service. At block 350, the UE obtains the NTN access using a particular USIM, usage setting, and / or service type. In some implementations, the UE changes its current USIM and usage setting based on the allowed NTN access associated with the selected NTN (from block 316). At block 380, the UE registers with a PLMN providing the NTN access. At block 390, the UE communicates data for the application or service based on the NTN access. For example, if (at block 350) the UE changed its usage setting or service type, then (at block 390) UE can limit which application(s) or service(s) communicate via the NTN access.

[0082] FIG. 4 shows a block diagram 400 of an example scenario in which a UE moves from a coverage area of a TN cell 416 to a coverage area of an NTN cell 414. In the scenario shown in diagram 400, the UE 102 initially is in the coverage of the TN cell 416 provided by a TN BS 406 at time ti. The UE 102 registers with a PLMN associated with the TN BS 406 at time ti. The PLMN may be a home, equivalent home, or visited PLMN for the UE 102. At time t2, the UEDocket No. 14730879200PCT102 moves out of TN coverage (i.e., the TN cell 416) and into an NTN coverage (i.e., the NTN cell 414). The UE 102 may perform an NTN search (i.e., searching an NTN cell) in response to detecting out of TN coverage. Alternatively, the UE 102 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).

[0083] In accordance with aspects of this disclosure, the UE 102 might change its USIM, usage setting, or enabled applications at time t2 based on detecting the NTN cell 414. Alternatively, or additionally, the UE 102 might change its USIM, usage setting, or enabled applications when accessing a core network via the NTN cell 414. For example, the UE 102 can perform a network registration or send a service request to a core network message via the satellite 104 and change its USIM, usage setting, or enabled applications based on the response from the core network.

[0084] FIG. 5A shows an example table of PLMN access information 510A where PLMN access is associated with a UE usage setting information 514. In some implementations, the UE can determine whether a PLMN is associated with an NTN or TN based on the frequency band. If the frequency band number is associated with a frequency band for satellite access, the UE can determine the PLMN is associated with an NTN. Otherwise, if the frequency band number indicates the frequency band for a TN, the UE determines the PLMN is associated with a TN. For example, the first row 524A shows that PLMN ID1 uses frequency band “255”, which is defined for satellite access in a 3GPP specification (e.g., 3GPP TS 36.102 or 38.101-5). The sixth row 524F shows the PLMN ID4 is associated with an NTN because the frequency band “256” is defined for satellite access.

[0085] At the time of this disclosure, the 3GPP specifications define frequency bands “255” and “256” for satellite access. As more NTNs are deployed and newer types of spaceborne or airborne vehicles are created, it is possible for an NTN to use frequency bands that were previously considered to be for TN access. For example, the second row 524B shows a PLMN ID2 using satellite E-UTRA in frequency band 25. In implementations where a UE relies on the frequency band number to determine whether a PLMN is associated with an NTN or a TN, the UE might be unable to distinguish NTNs from TNs. For example, consider second row 524B, where PLMN ID2 operates a satellite E-UTRA NTN in frequency band “25.” A UE might mistakenly consider PLMN ID2 to be associated with a TN because frequency band “25” is not previously defined for satellite access.Docket No. 14730879200PCT

[0086] In some implementations, the PLMN access information explicitly indicates the RAT type. For example, the UE can determine that the PLMN ID1 is associated with an NTN because the first row 524A indicates the satellite NB-IoT RAT type. In another example, the UE determines that the PLMN ID3 is associated with a TN (i.e., E-UTRA TN or LTE TN) because the fourth row 524D indicates the E-UTRA type (i.e., no “satellite” in the RAT type). In another example, the UE determines that PLMN ID3 is associated with an NTN because the third row 524C indicates the “satellite” E-UTRA type. In yet another example, the UE determines a PLMN identified by the PLMN ID4 (sixth row 524F) is associated with an NTN because the RAT type is the satellite NR. A potential technical advantage of indicating the RAT type in the PLMN access information is that a UE can easily distinguish whether a PLMN is associated with an NTN or TN based on the indicated RAT type. Another potential technical advantage is that the frequency band number no longer needs to be specific to NTN or TN (thus frequency band “25” can be used for an NTN in the PLMN ID2 of row 524B and also used for an NR TN RAN in the PLMN ID3 of row 524E).

[0087] In some implementations, a UE can determine whether a PLMN is an NTN or TN based on a portion of the PLMN ID. Because a PLMN ID includes an MCC, the MCC can be used to determine whether the PLMN includes NTN access. A particular MCC (e.g., “901”) is commonly used to indicate a PLMN that provides services via a satellite. If a PLMN ID includes the particular MCC, the UE can determine that the PLMN identified by that PLMN ID is associated with an NTN. For example, when the PLMN ID2 includes the particular MCC ("901"), the UE can determine that the PLMN ID2 is associated with an NTN. A potential technical advantage is that the RAT type information can be removed from the PLMN access information. However, a potential shortcoming is that the particular MCC ("901") can become overused, particularly as more NTNs are deployed. Furthermore, an NTN can remain over the same country (such as a GEO satellite coverage over a large country) where the generic MCC ("901") is less meaningful. More general MCCs could be defined. Alternatively, or additionally, a UE can use the RAT type indicated in the PLMN access information to distinguish NTN or TN so that the PLMN ID can use MCCs other than a general MCC for satellite access.

[0088] In some implementations, when the UE determines to search a PLMN identified by a PLMN ID, the UE determines which RAT and carrier frequencies to search based on the RAT type and the PLMN frequency information (such as the frequency band and / or the frequency range). The frequency range can indicate an uplink (UL) frequency range and a downlink (DL)Docket No. 14730879200PCTfrequency range. For example, when the UE determines to search PLMN ID1, based on PLMN access information in the first row 524A, the UE may search one or more carrier frequencies in frequency band 255 and / or the frequency range (i.e., DL: 1525-1559 MHz) using the satellite NB-IoT RAT. In another example, based on the second row 524B, when the UE determines to search PLMN ID2, the UE searches one or more carrier frequencies in the frequency range (i.e., DL: 1990-1995 MHz) using the satellite E-UTRA RAT. In yet another example, when the UE determines to search PLMN ID3, based on the third row 524C, the UE searches one or more carrier frequencies in the frequency range (i.e., DL: 869-894 MHz) using the E-UTRA RAT. The use of explicit frequency ranges in the PLMN access information can provide a variety of potential technical advantages, such as the ability for operators to segment a frequency band to different RAT types or the ability so mix NTN and TN within the same frequency band. Furthermore, a UE can limit the number of frequencies based on the indicated frequency range, which provides a potential technical advantage of power saving and faster PLMN search times. In some implementations, the frequency range can be represented in one or more absolute radio frequency channel numbers (ARFCNs). The frequency range in a row may indicate a duplex mode (e.g., frequency division duplex (FDD) or time division duplex (TDD)) for a frequency band or a carrier frequency within the frequency band in the row. For example, if a UL frequency range and a DL frequency range for a frequency band or a carrier frequency within the frequency band in a row completely overlap, the carrier frequency or the band is a TDD carrier frequency or a TDD band. Otherwise, if the frequency range for UL and the frequency range for DL for a frequency band or a carrier frequency within the frequency band in a row don’t overlap, the carrier frequency or the band is a FDD carrier frequency or a FDD band.

[0089] In some implementations, the PLMN access information 510A includes UE usage setting information 514 to indicate the usage setting that is supported for each PLMN. A usage setting indicates whether the UE has preference for voice services over data services or vice-versa. In the example of FIG. 5A, the first row 524A shows that the usage setting is "non-voice centric" for PLMN ID1 and / or the satellite NB-IoT RAT type. When accessing a cell in the frequency range for PLMN ID1, the UE can change its usage setting to non-voice-centric. Alternatively, or additionally, if the UE requires voice services, the UE can use the UE usage setting information 514 to identify which PLMNs to search for available cells.

[0090] FIG. 5B shows an example table of PLMN access information 510B where PLMN access is associated with an application or service type. The PLMN access information 510A isDocket No. 14730879200PCTsimilar to the PLMN access information 51 OB (of FIG. 5B), except that instead of the UE usage setting information 514, the PLMN access information 51 OB includes supported application or service type information 516. The supported application or service type information 516 indicates which applications or service types are supported for various PLMNs. The UE can enable various applications or service types when it accesses a particular PLMN. Alternatively, or additionally, the when the UE requires a particular application or service type, UE can use the supported application or service type information 516 to filter the list of PLMNs and perform a PLMN search for only those PLMNs that support the required application / service type.

[0091] This disclosure now includes several examples in FIG. 6 through FIG. 16B to illustrate some options of various aspects of the disclosure. For brevity, the following description will focus on the differences in each figure compared to the concepts described in preceding figures. Where possible, to reduce redundancy, the figures include like reference numbers to represent an event or message already described in a previous figure and the description of that event or message is omitted or summarized in the description of the latter figure. Generally speaking, similar elements in the figures that are labeled with reference numbers have the same lower-order digits to represent similar features. For example, block 724 is similar to block 824, and block 764 is similar to block 824. For brevity, similar elements are not discussed in detail in each instance, but the discussion of a certain element with reference to one of the figures also applies to similar elements in other figures.

[0092] FIG. 6 shows an example scenario 600 in which a UE attempts to access an NTN cell using a first USIM and a second USIM. The NTN cell is provided by a satellite 104 and a BS 106. All or part of the functions of the BS 106 can be onboard the satellite 104 or on the ground (e.g., the NTN BS 106' shown in FIG. 1). To simplify the description and illustration, the satellite 104 and the BS 106 are shown together, representing an access stratum of the NTN. The UE 102 and the CN 110 communicate non-access stratum messages via the NTN.

[0093] As part of a first access attempt 620, at block 622, the UE 102 initially selects the first USIM to access the NTN (e.g., BS 106 and satellite 104). The UE 102 is initially in coverage of the satellite 104. At block 618, the UE camps on an NTN cell of the BS 106. The UE 102 receives system information 619 via the NTN cell from the BS 106. The UE 102 can receive the system information from a system information block (SIB). In some implementations, the UE 102 receives a master information block (MIB) from the NTN cell. The system information may include information to access the NTN cell. In some implementations, the information to accessDocket No. 14730879200PCTthe NTN cell includes random access configuration parameters, search space configuration parameters, a physical downlink control channel (PDCCH) configuration, a physical downlink shared channel (PDSCH) configuration, and / or a physical uplink shared channel (PUSCH) configuration.

[0094] In some implementations, the UE 102 obtains the system information 619 from at least one SIB. For example, if the NTN cell is a NR cell, the at least one SIB includes a SIB 1 (SIB1) and / or a SIB 19 (SIB19), e.g., defined in 3GPP specification 38.331. In another example, if the NTN cell is an E-UTRA cell, the at least one SIB includes a SystemlnformationBlockType 1 , a SystemInformationBlockType2 and / or a SystemlnformationBlockType 31 as defined in 3 GPP specification 36.331. In yet another example, if the NTN cell is a NB-IoT cell, the at least one SIB includes a SystemlnformationBlockType 1 -NB , a SystemInformationBlockType2-NB, and / or a SystemlnformationBlockType 31-NB as defined in 3GPP specification 36.331. In yet another example, if the NTN cell is a 6G cell, the at least one SIB includes one or more 6G SIB(s).

[0095] After receiving the system information 619, the UE 102 initiates a first attach procedure with the CN 110. The UE 102 transmits an Attach Request message 630 to the CN 110 (e.g., a first network node such as a Mobility Management Entity (MME) or Access and Mobility Function (AMF)). In the example of FIG. 6, the CN 110 transmits an Attach Reject message 632 to the UE 102. For example, the CN 110 transmits the Attach Reject message 632 when the CN 110 determines that the UE 102 with the first USIM is not authorized to access the NTN. That is, the UE 102 with the first USIM does not have a subscription that includes NTN access. In some implementations, after receiving the Attach Request message 630, the first network node (i.e., the MME or AMF) may transmit a first interface message to a second network node (e.g., a Home Subscriber Server (HSS), an Authentication Server Function (AUSF), and / or Unified Data Management Function (UDM)) to determine whether the UE 102 with the first USIM is authorized to access the NTN. In response, the second network node transmits a second interface message to the first network node, indicating that the UE 102 is not authorized to use the NTN. Based on receiving the second interface message, the first network node transmits the Attach Reject message to the UE 102. In some implementations, the reject cause is a cause code such as #11, #12, #13, or #14 as specified in 3GPP TS 24.301 or TS 24.501. In some implementations, the reject cause is a cause code such as #15, #25, #31, #35, 42 or #78 as specified in 3GPP TS 24.301 or TS 24.501. In some implementations, the reject cause is an extended cause (e.g., extended EMM cause, an extended 5GMM cause, or an extended 6GMMDocket No. 14730879200PCTcause). In some implementations, the reject cause causes the UE 102 to disable an NTN access capability for accessing an NTN (e.g., the NTN including the base station 104 and the satellite 304). In some implementations, the UE 102 disables NTN access capability for accessing an NTN in response to receiving the reject cause. If the UE 102 disables the NTN access capability based on the first access attempt 620, the UE 102 re-enables the NTN access capability for the second access attempt 660. In other implementations, the UE 102 refrains from disabling the NTN access capability in response to receiving the reject cause if the UE 102 has another USIM available.

[0096] In some implementations, in response to receiving the reject cause, the UE 102 determines whether to disable the NTN access capability, depending on whether the UE 102 is equipped with a second USIM. If the UE 102 is equipped with the second USIM, the UE 102 might refrain from disabling the NTN access capability. Otherwise, if the UE 102 is not equipped with the second USIM, the UE 102 disables the NTN access capability. In some implementations, the second USIM is a particular USIM including a specific Mobile Country Mode (MCC) or a specific PLMN ID. In such cases, if the second USIM is not the particular USIM, the UE 102 may disable the NTN access capability.

[0097] FIG. 6 shows the UE 102 performing a second access attempt 660 using the second USIM after a rejection in the first access attempt 620. At block 662, the UE 102 selects the second USIM to access the NTN. For the second access attempt 660, the UE 102 transmits an Attach Request message 670 to the CN 110. In response to the Attach Request message 670, the CN 110 transmits an Attach Accept message 672 to the UE 102. The CN 110 does so because the CN 110 determines that the UE 102 with the second USIM is authorized to access the NTN. That is, the UE 102 with the second USIM subscribes the NTN. The UE 102 transmits an Attach Complete message 678 to the CN 110 in response to receiving the Attach Accept message 672. In some implementations, after receiving the Attach Request message 670, the first network node (e.g., MME or AMF) may transmit (not shown) a third interface message to the second network node (e.g., HSS, AUSF, and / or UDM) to determine whether the UE 102 with the second USIM is authorized to access the NTN. The second network node transmits (not shown) a fourth interface message to the first network node, indicating that the UE 102 is authorized to use the NTN. After (e.g., in response to) receiving (not shown) the fourth interface message, the first network node transmits the Attach Accept message 672 to the UE 102. After transmitting the Attach Complete message 678, the UE 102 communicates (shown at block 695) with the CN 110Docket No. 14730879200PCTvia the NTN. At block 695, the UE 102 can communicate control plane messages and / or user plane data packets with the CN 110. In some implementations, in response to receiving (not shown) the fourth interface message, the first network node performs (not shown) an authentication and / or key agreement (AKA) procedure and / or a security mode control procedure with the UE 102. After successfully completing the AKA procedure and / or the security mode control procedure, the first network node transmits 672 the Attach Accept message to the UE 102. In some implementations, the BS 106 receives an indication from the CN 110 that a voice service is not available and includes the indication in the system information 619.

[0098] FIG. 7A shows an example scenario 700A in which a UE attempts to access an NTN cell using a first usage setting and a second usage setting. FIG. 7A is similar to FIG. 6, except that it refers to a usage setting that is enabled for NTN access rather than a particular USIM for NTN access. At block 724, the UE 102 has a voice-centric usage setting. In some implementations, the voice-centric usage is a default or preconfigured usage setting for the UE 102. Events 618, 619, and 630 are the same as described with reference to FIG. 6. In this scenario 700A, instead of transmitting an Attach Reject message, the CN 110 transmits an Attach Accept message 735 that indicates that voice service is not available. In other words, the CN 110 accepts the attach procedure while providing an indication of a voice service not available for the UE 102 to use via the NTN access. The voice service may be a voice over packet-switch (VoPS) service or an IMS voice service. In this example, the UE 102 will not use the voice service and instead will change the UE's usage setting to non-voice-centric. The UE 102 transmits an Attach Complete message 738 to the CN 110. At block 764, the UE changes the UE's usage setting to non-voice centric in response to receiving the indication. At block 768, the UE continues camping on the NTN cell. In some alternative implementations, the indication of the voice service not available is included in the system information 619 instead of the Attach Accept message. In such cases, the UE 102 changes its usage setting to non-voice-centric based on the indication included in the system information.

[0099] In some implementations, shown at block 788, the UE 102 performs an IMS registration for non-voice services (e.g., SMS or other messaging) with an IMS network via the CN 110 and the NTN cell. At block 795, the UE communicates data of non-voice services with the CN 110 via the NTN cell. In some implementations, the IMS network is part of the CN 110. In other implementations, the IMS network is outside the CN 110. The IMS network may include at least one Call Session Control Function (CSCF). The at least one CSCF may include a Proxy CSCFDocket No. 14730879200PCTP-CSCF), an Interrogating CSCF (I-CSCF), a Serving CSCF (S-CSCF), and / or an emergency CSCF.

[0100] FIG. 7B shows an example scenario 700B in which a UE 102 selects a usage setting for NTN access. At block 750, the UE 102 is configured to support multiple UE usage settings. At block 618, the UE camps on an NTN cell of the NTN. At block 725, the UE selects one of the multiple UE usage settings for the NTN. In this example scenario, the UE 102 selects the voicecentric usage setting in block 725. Events 619, 630, 735, and 738 are as described with reference to FIG. 6 and FIG. 7A. In short, the UE 102 completes an attach procedure in which the Attach Accept message 735 indicates that a voice service is not available for the UE to use in the NTN. Based on the Attach Accept message 735, at block 765, the UE 102 adjusts the UE usage setting. For example, where the Attach Accept message 735 indicates that the voice service is not available, the UE 102 changes its usage setting to non-voice-centric. Blocks 788 and 795 are described with reference to FIG. 7A. In some alternative implementations, the indication that the voice service is not available is included in the system information 619 instead of the Attach Accept message. In such cases, the UE 102 adjusts the UE usage setting based on the system information. For example, the UE 102 changes its usage setting to non-voice-centric in response to the indication.

[0101] FIG. 7C shows an example scenario 700C in which a UE accesses an NTN cell based on non-voice services available at the NTN cell. FIG. 7C is similar to FIG. 7A except that FIG.7C shows that the UE 102 refrains from disabling one or more NTN capabilities for accessing the NTN cell (at block 745). Thus, the UE 102 can continue to camp on the NTN cell (shown at block 768) after receiving the indication of the voice service is not available in the Attach Accept message 735 or the system information 619 and having the UE usage setting set to voice-centric. For example, the UE 102 might have only a voice-centric usage setting or might avoid making a change. Blocks 788 and block 795 are the same as described above in FIG. 7A. As shown in block 795, the UE 102 still only communicates data of non-voice services (e.g., SMS) when using the NTN cell because the Attach Accept message 735 indicated that the voice service is not available.

[0102] FIG. 8 A shows an example scenario 800A in which a UE accesses an NTN cell based on non-voice services available at the NTN cell. Initially, the UE 102 may be camping on a TN cell and communicating data of IMS voice services. For example, at block 824, the UE 102 is configured for the voice-centric usage setting. At block 817, the UE 102 camps on a TN cell ofDocket No. 14730879200PCTa TN BS 806. The UE 102 can receive system information 819A from the TN BS 806. The UE 102 transmits an Attach Request message 832 to the CN 110 via the TN BS 806. The CN 110 transmits an Attach Accept message 834 to the UE 102. The UE 102 transmits an Attach Complete message 838 to the CN 110. After this attach procedure, the UE 102 can perform an IMS registration with the CN 110 via the TN BS 806. At block 888A, the UE 102 performs the IMS registration for voice services with an IMS network via the TN BS 806. At block 895A, the UE communicates data of IMS voice services with the IMS network via the TN cell. In some implementations, the Attach Accept message 834 or the system information 819A indicates that the IMS voice service is available.

[0103] At some point, the UE 102 may perform a cell reselection, a cell selection, or a PLMN search. For example, the UE 102 may move to a different location or lose signal from the TN BS 806. In the example scenario 800A, the selects an NTN cell provided by the satellite 104 and the BS 106. At block 818, the UE 102 camps on the NTN cell. At block 864, the UE 102 changes the UE's usage settings to non-voice centric. For example, the UE 102 may determine, based on the system information 819B, the Attach Accept message 874, or PLMN access information (e.g., as described in FIG. 5 A), that the voice service is not available via the NTN cell. Alternatively, or additionally, the UE 102 may change the usage setting to non-voice-centric whenever accessing an NTN cell.

[0104] The UE 102 receives system information 819B from the BS 106. The UE 102 transmits an Attach Request message 870 to the CN 110. The CN 110 transmits an Attach Accept message 874 to the UE 102, and the UE 102 transmits an Attach Complete message 878 to the CN 110. At block 888B, based on the non-voice-centric usage setting, the UE performs IMS registration for non-voice services (e.g., SMS) with an IMS network via the BS 106 and the NTN cell. At block 895B, UE communicates data of non-voice services (e.g., SMS) via the NTN cell. In some implementations, the Attach Accept message 874 or the system information 819B indicates that the IMS voice service is not available.

[0105] FIG. 8B shows an example scenario 800B in which a UE modifies its usage setting when accessing an NTN cell. FIG. 8B is similar to FIG. 8A, except that FIG. 8B shows the UE 102 has multiple UE usage settings and dynamically selects the usage setting and IMS registration based on whether it is using a TN cell or an NTN cell for core network access. At block 850, the UE 102 supports, or is pre-configured, with multiple UE usage settings. At block 825, the UE 102 selects a first one (e.g., voice-centric) of the multiple UE usage settings before accessing the TNDocket No. 14730879200PCTcell provided by TN BS 806. Events 817, 819A, 832, 834, 838, 888A, and 895 A are as described with reference to FIG. 8 A. Before accessing an NTN cell provided by the satellite 104 and BS 106, the UE 102 selects a second one (e.g., non-voice-centric) of the multiple usage settings. Thus, the UE 102 uses the second usage setting for the attach procedure and IMS registration via the NTN cell, as described in FIG. 8A.

[0106] FIG. 9A shows an example scenario 900A in which a UE modifies its service access based on services indicated as being available in an Attach Accept message. At block 950, the UE 102 supports multiple services, e.g., user plane (UP) data (e.g., IP data, Ethernet data, nonIP data), control plane (CP) data (e.g., IP data, Ethernet data, non-IP data), voice, video, SMS over NAS, and / or SMS over IMS. At block 918, the UE 102 camps on an NTN cell of the satellite 104 / BS 106. The UE 102 receives system information 619 from the BS 106. The UE 102 transmits an Attach Request message 630 to the CN 110 via the NTN cell. The CN 110 transmits an Attach Accept message 936A to the UE 102 with an indication 981 of supported services (i.e., available for use over NTN access). The indication 981 indicates at least one of the multiple services supported by the UE 102. The UE 102 transmits an Attach Complete message 738 to the CN 110 to complete the attach procedure.

[0107] At block 987A, the UE 102 disables one or more services not indicated as being supported in the Attach Accept message 936A. At block 988, the UE performs an IMS registration for at least a first service that is supported by the UE 102 and included in the indication 981 of the Attach Accept message 936A. At block 995, the UE 102 communicates data of the first service with the CN 110 via the RAN.

[0108] FIG. 9B shows an example scenario 900B in which a UE modifies its service access based on services available as indicated in a system information message. FIG. 9B is similar to FIG. 9A, except that, in FIG. 9B, the indication 981 of supported services is provided in system information 919 rather than in the Attach Accept message. In this scenario 900B, the BS 106 transmits system information 919 that includes the indication 981 of supported services (i.e., available for use over NTN access). The indication 981 indicates at least one of the multiple services (block 950) that the UE 102 supports. The system information 919 can be any type of system information message, such as a SIB1, SIB2, SIB 19, SIB31, or a new SIB type, among other examples. The UE 102 performs an attach procedure similar to the attach procedures described in other figures. In this scenario 900B, the Attach Accept message 936B does not need to provide an indication of supported services for NTN access because that indication 981 hasDocket No. 14730879200PCTbeen provided in the system information 919. At block 987B, the UE disables one or more services not indicated by the indication 981 in the system information 949. Blocks 988 and 995 are the same as described in FIG. 9A.

[0109] FIG. 10A shows a flow diagram 1000A of example operations of a UE that refrains from disabling NTN capability when the UE has a second USIM that is allowed to access an NTN cell. In this example, the UE accesses an NTN with a first USIM and an NTN capability. At block 1030, the UE transmits a first Attach Request message to the CN using the first USIM. At block 1032, the UE receives an Attach Reject message from the CN. At block 1045, the UE refrains from disabling the NTN capability in response to receiving the reject message. At block 1062, the UE selects a second USIM to access the NTN. At block 1070, the UT transmits a second Attach Request message to the CN using the second USIM. At block 1072, the UE receives an Attach Accept message from the CN in response to the second Attach Accept message. At block 1078, the UE transmits an Attach Complete message to the CN.

[0110] In some implementations, the UE 102 prioritizes selecting the first USIM over the second USIM to access the NTN. In some implementations, the UE is roaming to the NTN with the second USIM active. In some implementations, the TN is a home network of the UE with the first USIM active.

[0111] FIG. 10B shows a flow diagram 1000B of example operations of a UE that re-enables NTN capability when the UE has a second USIM that is allowed to access an NTN cell. FIG.10B is similar to the flow diagram of FIG. 10A, except that diagram 1000B includes blocks 1037 and 1063 instead of block 1045. At block 1037, the UE disables the NTN capability in response to receiving the reject message. At block 1062, the UE selects a second USIM to access the NTN. At block 1063, the UE (re-)enables the NTN capability in response to selecting the second USIM to access the NTN. The rest of the blocks in FIG. 10A are as described with reference to FIG.10A.

[0112] FIG. 11A shows a flow diagram 1100A of example operations of a UE that selects a usage setting based on whether it is accessing a TN or an NTN. At block 1116, the UE accesses or determines to access a RAN. Accessing the RAN can include an attach procedure, including the various example attach procedures in this disclosure (e.g., the Attach Request messages 630, 670, 832, 870, the Attach Accept messages 672, 735, 834, 874, 936A, 936B, and the Attach Complete messages 678, 738, 838, 878).Docket No. 14730879200PCT

[0113] At block 1151, the UE determines whether the RAN is an NTN. If the RAN is an NTN (i.e., “Yes” branch of block 1151), the flow proceeds to block 1164. At block 1164, the UE accesses the RAN (or CN via the RAN) with a second usage setting (e.g., non-voice-centric). In some implementations, the UE transmits 1164 a UL message to the RAN (or the CN via the RAN), indicating the UE's second usage setting. For example, the UL message can be an Attach Request message, an attach complete message, an IMS registration message, or another NAS message. Otherwise, if the RAN is not an NTN (i.e., “No” branch of block 1151), the RAN is a TN and the flow proceeds to block 1124. At block 1124, the UE accesses the RAN with a first usage setting (e.g., voice-centric). In some implementations, the UE transmits 1124 an UL message to the RAN, indicating the UE’s first usage setting. For example, the UL message can be an attach request message, an attach complete message, an IMS registration message, or another NAS message. In some implementations, the UE’s second usage setting is as described for row 524A or row 524B in FIG. 5 A and the UE’s first usage setting is as described for row 524D, 524E, 524F, 524H, 5241, or 5241.

[0114] FIG. 11B shows a flow diagram 1100B of example operations of a UE that selects a usage setting based on application or service. FIG. 11B is similar to FIG. 11 A, except that in FIG. 1 IB the diagram 1100B includes block 1156 instead of block 1151. At block 1156, the UE determines whether the RAN access (from block 1116) was triggered by a particular application (e.g., an emergency-type application or emergency data messaging application). In some implementations, the particular application is an emergency SOS messaging application. If the UE has accessed the RAN with a particular application (i.e., “Yes” branch of block 1156), the flow proceeds to block 1164 where the UE uses a second usage setting (e.g., non-voice-centric) that is appropriate for the particular application. Otherwise, if the UE accesses the RAN without using the particular application (i.e., No" branch of block 1156), the flow proceeds to block 1124. That is, if the UE does not use the particular application when accessing the network, the UE accesses the network using the UE’s first usage setting (e.g., voice-centric) which may be a default usage setting of the UE.

[0115] FIG. 11C shows a flow diagram 1100C of example operations of a UE that selects a usage setting based on which USIM the UE uses for accessing an NTN cell. The difference between FIG. UC and FIG. 11A is that FIG. 11C includes block 1152 instead of block 1151. At block 1152, the UE determines whether the UE accesses the RAN with a particular USIM (e.g., a second USIM for NTN access). If the UE accesses the RAN with a particular USIM (i.e., “Yes”Docket No. 14730879200PCTbranch of block 1152), the flow proceeds to block 1164. Otherwise, if the UE accesses the RAN without using the particular USIM (i.e., “No" branch of block 1152), the flow proceeds to block 1124. In some implementations, if the UE accesses the RAN with a USIM (e.g., the first USIM) other than the particular USIM, the UE accesses the RAN using the UE’s first usage setting (e.g., voice-centric) as a default usage setting of the UE.

[0116] FIG. HD shows a flow diagram HOOD of example operations of a UE that selects a usage setting based on information from the NTN cell. At block 1148, the UE receives a message from a RAN or CN (e.g., an Attach Accept message or a system information message). At block 1158, the UE determines whether the message includes particular information (e.g., an indication that a voice service is not available or an indication of allowed services for NTN access). If the message includes the particular information (i.e., “Yes” branch of block 1158), the flow proceeds to block 1164. In some implementations, the UE applies the UE’s second usage setting in response to or in accordance with the particular information. For example, the message can be the Attach Accept message 735, the Attach Accept message 936A, or the system information 919, or any type of message that indicates that the voice service is not available or permitted for the UE when the UE is using NTN access. The UE applies the second usage setting (non-voice-centric) in block 1164. Otherwise, if the message does not include the particular information (i.e., “No" branch of block 1158), the flow proceeds to block 1124, where the UE uses the first usage setting (e.g., voice-centric).

[0117] FIG. 12A through FIG. 13F include several alternative outcomes from the decision blocks of FIG. 11A through FIG. 11D. In particular, FIG. 12A through FIG. 12H describe how the UE might handle IMS registration based on various conditions (such as whether the RAN is an NTN, whether a particular USIM, usage setting, or application triggered the NTN access, or whether the NTN or CN has provided an indication of permissible services for which the UE is allowed to access the CN via the NTN). FIG. 13A through FIG. 13F describe how the UE enables or disables a service based on the various conditions. For brevity, the descriptions of these figures focus on the changes to IMS registration based on the conditions without repeating the descriptions of similar blocks from FIG. 11 A through FIG. 1 ID.

[0118] FIG. 12A shows a flow diagram 1200A of example operations of a UE that selects a service based on whether it is accessing a TN or an NTN. Blocks 1116 and 1151 are described from FIG. 11A. If the RAN is an NTN (i.e., “Yes” branch of block 1151), the flow proceeds to block 1266. At block 1266, the UE performs an IMS registration (procedure) with a CN via theDocket No. 14730879200PCTRAN for at least one second service such as a non-voice-centric service (e.g., as in blocks 788, 888B, 988). In some implementations, the UE performs 1266 the IMS registration (procedure) with an IMS network via the CN and the RAN. Otherwise, if the RAN is a TN (i.e., “No” branch of block 1151), the flow proceeds to block 1226. At block 1226, the UE performs an IMS registration (procedure) with the CN for at least one first service (e.g., as in block 888A). In some implementations, the UE performs 1226 the IMS registration (procedure) with the IMS network via the CN and the RAN. In some implementations, the at least one first service includes a voice service, and the at least one second service does not include the voice service. In some implementations, the at least one second service includes a short message service (SMS). In some implementations, the at least one first service includes a video service, and the at least one second service does not include the video service.

[0119] FIG. 12B shows a flow diagram 1200B of example operations of a UE that selects a service based on application or service. If the UE accesses the RAN (e.g., an NTN) with a particular application (i.e., “Yes” branch of block 1156), the flow proceeds to block 1266. Otherwise, if the UE accesses the RAN (e.g., a TN RAN) without using the particular application (i.e., No" branch of block 1156), the flow proceeds to block 1226. Block 1226 (IMS registration for a first service, such as voice) and block 1226 (IMS registration for a second service, such as messaging) are as described with reference to FIG. 12 A.

[0120] FIG. 12C shows a flow diagram 1200C of example operations of a UE that selects a service based on which USIM the UE uses for accessing an NTN cell. If the UE accesses the RAN (e.g., NTN) with a particular USIM (e.g., a second USIM), then the flow proceeds via the “Yes” branch of block 1152 to block 1266 (i.e., IMS registration for a second service, such as a messaging service). Otherwise, if the UE accesses the RAN without using the particular USIM (e.g., the UE is using a first USIM), then the flow proceeds via the "No" branch of block 1152 to block 1226 (i.e., IMS registration for a first service, such as a voice service).

[0121] FIG. 12D shows a flow diagram 1200D of example operations of a UE that selects a service based on information from the NTN cell. If the UE receives a message that includes particular information (such as an indication that a voice service is not available), the flow proceeds via the “Yes” branch of block 1158 to block 1266 (i.e., IMS registration for a second service, such as a messaging service). Otherwise, if the message does not include the particular information, the flow proceeds via the "No" branch of block 1158 to block 1226 (i.e., IMS registration for a first service, such as a voice service).Docket No. 14730879200PCT

[0122] FIG. 12E shows a flow diagram 1200E of example operations of a UE that selectively performs a service registration based on whether it is accessing a TN or an NTN. FIG. 12E is similar to FIG. 12A, except that the UE either refrains from performing an IMS registration or performs an IMS registration based on whether the RAN is an NTN or a TN, respectively. If the RAN is an NTN (i.e., “Yes” branch of block 1151), the flow proceeds to block 1289. At block 1289, the UE refrains from performing an IMS registration (procedure) with the CN. Otherwise, if the RAN is a TN (i.e., “No” branch of block 1151), the flow proceeds to block 1288, where the UE performs the IMS registration (procedure) with the CN.

[0123] FIG. 12F shows a flow diagram 1200F of example operations of a UE that selectively performs a service registration based on application or service. If the RAN access was triggered by a particular application (e.g., a messaging or emergency-type application), the flow proceeds via the “Yes” branch of block 1156 to block 1289 (i.e., refrain from IMS registration). Otherwise, if the RAN access was not triggered by a particular application, the flow proceeds via the “No” branch of block 1156 to block 1288 (i.e., perform the IMS registration).

[0124] FIG. 12G shows a flow diagram 1200G of example operations of a UE that selectively performs a service registration based on which USIM the UE uses for accessing an NTN cell. If the UE is using a particular USIM (e.g., the second USIM for NTN access), the flow proceeds via the “Yes” branch of block 1152 to block 1289 (i.e., refrain from IMS registration). Otherwise, the flow proceeds via the “No” branch of block 1152 to block 1288 (i.e., perform the IMS registration).

[0125] FIG. 12H shows a flow diagram 1200H of example operations of a UE that selectively performs a service registration based on information from the NTN cell. If the UE receives a message (block 1148) that includes particular information (e.g., an indication that a voice service is not available or an indication of allowed services for NTN access), the flow proceeds via the “Yes” branch of block 1158 to block 1289 (i.e., refrain from IMS registration). Otherwise, the flow proceeds via the “No” branch of block 1152 to block 1288 (i.e., perform the IMS registration).

[0126] FIG. 13A shows a flow diagram 1300A of example operations of a UE that enables or disables a service based on whether it is accessing a TN or an NTN. If the RAN is an NTN (i.e., “Yes” branch of block 1151), the flow proceeds to block 1387. At block 1387, the UE disables at least one service (e.g., a voice service or a video service). In some implementations, disabling at least one service means that the UE refrains from initiating a connection for the at least oneDocket No. 14730879200PCTservice. Otherwise, if the RAN is a TN (i.e., “No” branch of block 1151), the flow proceeds to block 1389. At block 1389, the UE enables the at least one service.

[0127] FIG. 13B shows a flow diagram 1300B of example operations of a UE that enables or disables a service based on which USIM the UE uses for accessing an NTN cell. If the UE accesses the RAN (e.g., NTN) with a particular USIM (e.g., a second USIM), then the flow proceeds via the “Yes” branch of block 1152 to block 1387 (i.e., disable at least one service, such as voice and / or video). Otherwise, if the UE accesses the RAN without using the particular USIM (e.g., the UE is using a first USIM), then the flow proceeds via the "No" branch of block 1152 to block 1389 (i.e., enable the at least one service).

[0128] FIG. 13C shows a flow diagram 1300C of example operations of a UE that enables or disables a service based on information from the NTN cell. If the UE receives a message (block 1148) that includes particular information (e.g., an indication that a voice service is not available or an indication of allowed services for NTN access), the flow proceeds via the “Yes” branch of block 1158 to block 1387 (i.e., disable at least one service, such as voice and / or video). Otherwise, the flow proceeds via the “No” branch of block 1158 to block 1389 (i.e., enable the at least one service).

[0129] FIG. 13D shows a flow diagram 1300D of example operations of a UE that enables different services depending on whether it is accessing a TN or an NTN. If the RAN is an NTN (i.e., “Yes” branch of block 1151), the flow proceeds to block 1386B. At block 1386B, the UE enables at least one second service (e.g., a non-voice service). The non-voice service may be a SMS or another messaging service. Otherwise, if the RAN is a TN (i.e., “No” branch of block 1151), the flow proceeds to block 1386A. At block 1386A, the UE enables at least one first service (e.g., a voice service and / or video service). The voice service and video service may be a IMS voice service and a IMS video service, respectively.

[0130] FIG. 13E shows a flow diagram 1300E of example operations of a UE that enables different services depending on which USIM the UE uses for accessing an NTN cell. If the UE accesses the RAN (e.g., NTN) with a particular USIM (e.g., a second USIM), then the flow proceeds via the “Yes” branch of block 1152 to block 1386B. Otherwise, if the UE accesses the RAN without using the particular USIM (e.g., the UE is using a first USIM), then the flow proceeds via the "No" branch of block 1152 to block 1386A.

[0131] FIG. 13F shows a flow diagram 1300F of example operations of a UE that enables different services depending on information from the NTN cell. If the UE receives a messageDocket No. 14730879200PCT(block 1148) that includes particular information (e.g., an indication that a voice service is not available or an indication of allowed services for NTN access), the flow proceeds via the “Yes” branch of block 1158 to block 1386B. Otherwise, the flow proceeds via the “No” branch of block 1152 to block 1386A.

[0132] FIG. 14A shows a flow diagram 1400A of example operations of a UE that disables a service not available from the NTN cell. At block 1481, the UE receives a message from RAN indicating at least one service. In this example, the message indicates a service that is allowed for NTN access. In some implementations, the message enables the at least one service. In other implementations, the message indicates the at least one service supported. At block 1487A, the UE disables services (e.g., at least one other service) not indicated in the message. At block 1488A, the UE performs an IMS registration for the at least one service via or with a CN. At block 1495A, the UE communicates data of the at least one service via or with the RAN and / or the CN.

[0133] FIG. 14B shows a flow diagram 1400B of example operations of a UE that enables a service based on a message from the NTN cell indicating that the service is available from the NTN cell. At block 1481, the UE receives a message from a RAN indicating at least one service. In this example, the message indicates a service that is not allowed for NTN access. In some implementations, the message disables the at least one service. In other implementations, the message indicates the at least one service not supported. At block 1489B, the UE enables one or more services not indicated in the message. At block 1488B, the UE performs an IMS registration for the enabled service(s) with a CN and the RAN. At block 1495B, the UE communicates data for the services with the RAN and / or the core network.

[0134] FIG. 15A shows a flow diagram 1500A of example operations of a network that manages service access for one or more UEs. In some implementations, the network (e.g., RAN) is or includes a base station. In some implementations, the network (e.g., CN) is or includes at least one function of the CN (such as an MME or AMF, UPF, and / or S-CSCF). At block 1581A, the network transmits a first DL message to a first UE, indicating at least one service not supported for the first UE to use over NTN access. For example, a first function of the network (e.g., MME, AMF, or S-CSCF) transmits the first DL message to the first UE via a base station. At block 1595 A, the network communicates data of a service other than the at least one service with the first UE. For example, a second function of the network (e.g., UPF or S-CSCF) communicates data of the service other than the at least one service with the first UE via the base station. AtDocket No. 14730879200PCTblock 1581B, the network can transmit a second DL message to a second UE, indicating the at least one service supported for the second UE to use via NTN access. For example, the first function of the network transmits the second DL message to the second UE. For example, the first UE might not have a subscription that permits NTN access for the service, while the second UE might have a subscription that permits the NTN access for the service. At block 1595B, the network can communicate data of the at least one service with the second UE. For example, the second function of the network communicates data of the at least one service with the second UE.

[0135] In some implementations, the at least one service are unicast service(s). For example, the unicast service(s) include a voice service (e.g., an IMS voice service) and / or a video service (e.g., an IMS video service).

[0136] FIG. 15B shows a flow diagram 1500B of example operations where a network controls the disablement or enablement of services for one or more UEs. In some implementations, the network (e.g., RAN) is or includes a base station. In some implementations, the network (e.g., CN) is or includes at least one function of the CN (such as an MME or AMF, UPF, and / or S-CSCF). FIG. 15B is similar to FIG. 15A except that FIG. 15B includes blocks 1587 and 1589. At block 1587, the network transmits a first DL message to a first UE, instructing the first UE to disable at least one service. For example, a first function of the network (e.g., MME, AMF, or S-CSCF) transmits the first DL message to the first UE via a base station. At block 1589, the network transmits a second DL message to a second UE, instructing the second UE to enable the at least one service. For example, the first function of the network transmits the second DL message to the second UE via a base station. For example, the first UE might not have a subscription that permits NTN access for the service, while the second UE might have a subscription that permits the NTN access for the service. In some implementations, the at least one service are unicast service(s). For example, the unicast service(s) include a voice service (e.g., an IMS voice service) and / or a video service (e.g., an IMS video service).

[0137] FIG. 16A shows a flow diagram 1600A of example operations of a network node that controls service access based on whether the UE is camped on an NTN cell. In some implementations, the network node is a base station. In some implementations, the network node is a function of a core network (such as an MME or AMF). At block 1618, the network node communicates with a UE. At block 1651, the network node determines whether the network node communicates with the UE via a satellite. If the network node communicates with the UEDocket No. 14730879200PCTvia a satellite (i.e., “Yes” branch of block 1651), the flow proceeds to block 1687A. At block 1687A, the network node transmits a DL message to the UE, indicating at least one service not supported. Otherwise, if the network node communicates with the UE via a TN (i.e., “No” branch of block 1651), the flow proceeds to block 1681 A. At block 1681 A, the network node transmits a DL message to the UE, indicating the at least one service supported.

[0138] FIG. 16B shows a flow diagram 1600B of example operations of a network entity controls disablement or enablement of services for a UE based on whether the UE is camped on an NTN cell. In some implementations, the network node is a base station. In some implementations, the network node is a function of a core network (such as an MME or AMF). FIG. 16B is similar to FIG. 16A, except that FIG. 16B includes blocks 1687B and 1681B instead of blocks 1687A and 1681 A. If the network node communicates with the UE via a satellite (i.e., “Yes” branch of block 1651), the flow proceeds to block 1687B. At block 1687B, the network node transmits a DL message to the UE, indicating the UE to disable at least one service (e.g., a voice service). Otherwise, if the network node communicates with the UE via a TN (i.e., “No” branch of block 1651), the flow proceeds to block 168 IB. At block 168 IB, the network node transmits a DL message to the UE, indicating the UE to enable at least one service (e.g., a voice service).

[0139] FIG. 17A shows a block diagram of an example wireless communication system implementing an NTN BS connecting to a satellite via an NTN gateway using a transparent payload implementation. The example wireless communication system uses one type of NTN deployment 1700A referred to as transparent payload architecture, which involves an NTN gateway 109 and a “transparent” satellite 104 for extending the range of a Uu interface. The Uu interface refers to the link between the UE 102 and a base station 106'. In some implementations, the satellite 104 implements a frequency conversion and an RF amplifier in both the uplink and downlink directions. With that being said, the satellite 104 function is similar to that of an analogue RF repeater. As a result, the satellite 104 repeats the Uu radio interface from a feeder link (between the NTN gateway 109 and the satellite 104) to the service link (between the satellite 104 and the UE 102) in the downlink direction and vice versa in the uplink direction. The Satellite Radio Interface (SRI) on the feeder link is the Uu interface, and the NTN gateway 109 supports all necessary functions to forward the signal of the Uu interface. The NTN gateway 109 can be placed at the same site as the NTN BS 106' location, or can be connected to the NTN BS 106' at a distance via a wired link. It is also possible to connect more than one NTN gateway 109 to anDocket No. 14730879200PCTNTN BS 106'. Different transparent satellites may be connected to the same base station on the ground, via the same NTN gateway, or via different NTN gateways.

[0140] FIG. 17B shows a block diagram of an example wireless communication system implementing an NTN BS with feeder links to multiple satellites. In the example NTN deployment 1700B, an NTN BS 106' has feeder links to multiple satellites. Two different satellites 104 and 1704 are connected to the same NTN BS 106' via the same NTN gateway 109. The two satellites 104 and 1704 can each provide different NTN cells on the Earth surface and the different NTN cells can use different Physical Cell IDs (PCIs).

[0141] Although the transparent payload architecture illustrated in FIG. 17A and FIG. 17B is the current focus of the 3GPP development, the regenerative payload architecture that installs the BS functions on the satellite 104 is also a possible NTN deployment in the future. In such an architecture, a Uu interface exists between the satellite 104 and the UE 102, and some or all of the functions of the NTN BS 106' are on-board the satellite 104 (such as shown in FIG. 17C).

[0142] FIG. 17C shows a block diagram of an example wireless communication system implementing an NTN BS onboard on a satellite using a regenerative payload implementation. The example wireless communication system uses a type of NTN deployment 1700C referred to as regenerative payload architecture. FIG. 17C shows an NTN BS 106 onboard on a satellite 104. The BS 106 can perform some or all of the functions of a base station, including those described with reference to NTN BS 106' or NTN BS 106' in this disclosure. The Uu interface is shown between the UE 102 and the BS 106. The feeder link from the BS 106 to the NTN gateway 109 can be referred to as a Satellite Radio Interface (SRI). The SRI is a transport link between the NTN gateway 109 and the satellite 104. The Ng interface from the BS 106 includes a portion over the SRI (shown as Ng over SRI) and a portion on the ground. In some implementations, a first portion of the base station functionality (such as NTN BS 106') can be implemented on the satellite 104 while a second portion of the base station functionality (shown as BS 106) can be implemented at a ground entity. For example, in a disaggregated network, NTN BS 106' can be divided into two components: the Distributed Unit (DU) and Centralized Unit (CU). In an example, the BS 106 can operate as a DU that handles baseband processing, including RF signal processing and modulation / demodulation. The NTN BS 106' can be an example CU that manages higher-layer tasks such as resource management, scheduling, and network optimization.Docket No. 14730879200PCT

[0143] FIG. 18 shows an example control plane protocol stack 1800 in accordance with aspects of this disclosure. The control plane protocol stack 1800 illustrated in FIG. 18 shows various protocol layers of the UE 102, satellite 104, NTN gateway 109, NTN BS 1806, and CN 110 (such as the AMF in a 5G core network). The “NR-Uu” interface refers to the interface between the UE 102 and the NTN BS 1806 (via the satellite 104 and NTN gateway 109). In some implementations, aspects of the NTN BS 1806 can be implemented on board the satellite 104. The "NG-C" interface refers to the interface between the NTN BS 1806 and the CN 110.

[0144] In the control plane, the UE 102 includes a NAS layer, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a MAC layer, and a PHY layer. The RRC layer implements the RRC protocol and can transmit or receive RRC messages such as those described in this disclosure. The NTN BS 1806 (and the satellite 104) also have an RRC layer. The NR-Uu interface (between RRC layers of the UE 102 and the NTN BS 1806 or satellite 104) are part of the access stratum (AS) of the control plane. The NAS protocol is implemented between the NAS layer of the UE 102 and a NAS layer of an entity in the CN 110.

[0145] FIG. 19 shows a block diagram illustrating an example UE. Note that the depicted hardware configurations represent the processing components and communication components of a UE 1902 (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.

[0146] The UE 1902 includes antennas 1911A, a radio frequency front end (RF front end) 191 IB, and radio-frequency transceivers (e.g., an LTE transceiver 1903A and a 5G NR transceiver 1903B) for communicating with a network entity (such as an NTN node). The RF front end 191 IB includes one or more modems configured for the corresponding RAT(s) employed (for example, Third Generation Partnership Project (3GPP) Fifth Generation New Radio (5GNR)), 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. 19, the RF front end 191 IB of the UE 1902 may couple or connect the LTE transceiver 1903 A, and the 5G NR transceiver 1903B to the antennas 1911A to facilitate various types of wireless communication. The RF front end 191 IB operates, in effect, as a physical (PHY) transceiver interface to conduct and process signaling between the one or more processor(s) 1903C and antennas 1911 A so as to facilitate various types of wireless communication.Docket No. 14730879200PCT

[0147] The antennas 1911 A of the UE 1902 may include an array of multiple antennas that may be tuned to one or more frequency bands associated with a corresponding RAT. The antennas 1911 A and the RF front end 191 IB may be tuned to, and / or be tunable to, one or more frequency bands defined by the 3 GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 1903A, and / or the 5G NR transceiver 1903B. Additionally, the antennas 1911A, the RF front end 191 IB, the LTE transceiver 1903 A, and / or the 5G NR transceiver 1903B 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 1911A and the RF front end 191 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.

[0148] The UE 1902 also includes processor(s) 1903C and computer-readable storage media (CRM) 1903D. The processor(s) 1903C 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) 1903C may include an application processor (AP) utilized by the UE 1902 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 191 IB.

[0149] CRM 1903D 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) 1903C and other components of the UE 1902 to perform the various functions described herein and attributed to the UE 1902. 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) 1903C to enable user-plane communication, control-plane signaling, and user interaction with the UE 1902.

[0150] In some aspects, the UE 1902 has a modem 1908 that includes or controls the LTE transceiver 1903 A and / or the 5G NR transceiver 1903B. The modem 1908 has an NTN capability 1909, meaning the UE 1902 is an NTN-capable UE. The UE 1902 also has PLMN information 1910 which can include, for example priority, RAT, frequency info, NTN access allowed / not-Docket No. 14730879200PCTallowed information, or other settings. In some implementations, the PLMN information 1910 can include the PLMN access information 510A of FIG. 5 A and / or the PLMN access information 51 OB of FIG. 5B. The UE 1902 can operate one or more applications (collectively illustrated as application / service 1901). In accordance with aspects of this disclosure, the UE 1902 can adjust its usage setting, USIM (not shown), and or operation of the application / service 1901 based on whether the modem 1908 is using the NTN capability 1909 to access an NTN. For example, the UE 1902 can implement any of the features of the UE 102 described with reference to FIG. 1 through FIG. 14B.

[0151] FIG. 20 shows a block diagram of an example wireless communication system 2000 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 2000 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 2006) via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes. In FIG. 20, the BS 2006 operates a terrestrial network (TN) cell 2009.

[0152] The BS 106 is equipped with processing hardware 2007 that can include a receiver 2016B configured to receive data in the uplink direction. The processing hardware 2007 can also include a transmitter 2016A configured to transmit data in the downlink direction. The processing hardware further can include one or more general-purpose processor(s) 2016C (e.g., CPUs) and a non-transitory computer-readable memory (CRM) 2016D storing instructions that the one or more general-purpose processors execute. Additionally, or alternatively, the processing hardware 2007 can include special -purpose processing units. The processor 2016C 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 2016D 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 2004, such as a transmitter 2014A, a receiver 2014B, a processor 2014C, and CRMDocket No. 14730879200PCT2014D (similar to components 2007, 2016A, 2016B, 2016C and 2016D of the BS 106). In some implementations, the components 2014A, 2014B, 2014C and 2014D are shared or commonly implemented with the components 2016A, 2016B, 2016C and 2016D. The BS 2006 can include generally similar components (not shown) as the processing hardware 2007.

[0153] The UE 102 is equipped with processing hardware 2002 that can include one or more general -purpose processors such as CPUs and non-transitory computer-readable memory 2012D storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The processing hardware 2002 can also include a transmitter 2012A configured to transmit data in the downlink direction. The processing hardware further can include a receiver 2012B configured to receive data in the uplink direction. The processing hardware 2002, in an example implementation, includes a processor 2012C to process data that the UE 102 will transmit in the uplink direction or process data received by UE 102 in the downlink direction. The processor(s) 2012C may include, for example, one or more central processing units, GPUs, or other ASICs, and the like. To illustrate, the processor(s) 2012C may include an application processor (AP) utilized by the UE 102 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. The CRM 2012D may include any suitable memory or storage device such as RAM, SRAM, DRAM, NVRAM, ROM, Flash memory, SSD or other massstorage 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) 2012C and other components of the processing hardware 2002 to perform the various functions described herein and attributed to the UE 102. 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) 2012C to enable user-plane communication, control-plane signaling, and user interaction with the UE 102.

[0154] The CN 110 can be an Evolved Packet Core (EPC) and / or a 5G core (5GC). Among other components, the EPC can include a Serving Gateway (SGW), a Mobility Management Entity (MME), a Home Subscriber Server (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)Docket No. 14730879200PCTMultimedia 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 2010). The processing hardware 2010 can include a transmitter 2011A, a receiver 201 IB, a processor 2011C, and a CRM 201 ID, similar to corresponding components described with reference to processing hardware 2002, 2004, and 2007.

[0155] The transmitters 2012A, 2014A, 2016A, and 2011A and receivers 2012B, 2014B, 2016B, and 201 IB are examples of a communication unit. Any of the processors 2012C, 2014C, 2016C, and 2011C can also be referred to as 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. 20.

[0156] The following description may be applied to the description above.

[0157] Generally speaking, description for one of the above figures can apply to another of the above figures. Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures 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.”

[0158] A user device in which the techniques of this disclosure can be implemented (e.g, the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadbandDocket No. 14730879200PCTrouter. 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, the user 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.

[0159] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules can be software modules (e.g., 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 include 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 include 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.

[0160] 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.

[0161] Upon reading this disclosure, those of skill in the art will appreciate still additional and alternative structural and functional designs for handling mobility between base stations through the principles disclosed herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those of ordinary skill in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein.

[0162] FIG. 1 through FIG. 20 and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potentialDocket No. 14730879200PCTimplementations 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.

[0163] 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. Alternatively, or in addition to the other examples described herein, examples include any combination of the following implementation options (enumerated as clauses for clarity).

[0164] CLAUSES

[0165] Clause 1 : A method for wireless communication by a user equipment (UE), comprising: camping on a non-terrestrial network (NTN) cell of a satellite using a first universal subscriber information module (USIM) and a first usage setting; transmitting an Attach Request message to a core network via the NTN cell; receiving, from the core network, an Attach Response message that indicates NTN access is not allowed; and accessing the NTN cell using a second USIM or a second usage setting, or a second application for which NTN access is allowed.

[0166] Clause 2: The method of clause 1, further comprising, prior to accessing the NTN cell: determining that the UE is not allowed to access the NTN cell using the first USIM, the first usage setting, or for a first application type: disabling an NTN capability of the UE; changing a configuration of the UE to use the second USIM or the second usage setting; and re-enabling the NTN capability of the UE.

[0167] Clause 3: The method of clause 1, further comprising: determining that the UE is not allowed to access the NTN cell using the first USIM, the first usage setting, or for a first application type: refraining from disabling an NTN capability of the UE based on the UE having the second USIM or the second usage setting.

[0168] Clause 4: The method of clause 1, wherein the receiving the Attach Response message includes at least one of: receiving an Attach Reject message that indicates NTN access is not allowed; or receiving an Attach Accept message that indicates the NTN access is not allowed for an application type associated with the first UE usage setting.Docket No. 14730879200PCT

[0169] Clause 5: The method of any one of clauses 1 to 4, further comprising: receiving an indication from the NTN cell that a voice service is not allowed via the NTN access; disabling the voice service based on the voice service being not allowed for the NTN access; and enabling a non-voice service for the NTN access.

[0170] Clause 6: The method of clause 5, wherein the receiving the indication includes at least one of: receiving the indication in an Attach Accept message from a core network via the NTN cell; or receiving the indication in a system information message from the NTN cell.

[0171] Clause 7: The method of any one of clauses 1 to 6, wherein the accessing the NTN cell using the second USIM, the second usage setting, or for the second application, includes at least one of: disabling the first USIM; selecting the second USIM; changing a usage setting of the UE from the first usage setting to the second usage setting; selecting the second usage setting from among multiple usage setting options of the UE; selecting the second usage setting as non-voice-centric based on an indication that a voice service is not available via the NTN cell; or disabling, at the UE, access to a first service and enabling access to a second service.

[0172] Clause 8: The method of any one of clauses 1 to 7, wherein the accessing the NTN cell using the second USIM, the second usage setting, or for the second application, includes at least one of: performing an IP multimedia system (IMS) registration for a second service when the UE accesses the NTN cell using the second USIM or the second usage setting; performing an IMS registration for the second application when the NTN cell indicates the second service is available for NTN access; performing an IMS registration for the second service based on an application at the UE attempting to access the second service via the NTN cell; or performing an IMS registration for the second service based on the UE using the second USIM to access the NTN cell.

[0173] Clause 9: The method of any one of clauses 1 to 8, further comprising: determining that the second usage setting or the second application is allowed for NTN access based on public land mobile network (PLMN) access information, wherein the PLMN access information includes an indication of allowed usage settings or application types associated with PLMNs.

[0174] Clause 10: The method of any one of clauses 1 to 9, further comprising: using the first USIM or the first usage setting when accessing a terrestrial network (TN) cell; and using the second USIM or the second usage setting when accessing the NTN cell.

[0175] Clause 11: The method of any one of clauses 1 to 10, further comprising: enabling an NTN capability of the UE based on at least a first application or service type, where the firstDocket No. 14730879200PCTapplication or service type is an emergency-type application; and restricting data communication for a second application or service type for which NTN access is not allowed.

[0176] Clause 12: The method of any one of clauses 1 to 11, wherein the first usage setting is voice-centric and the second usage setting is non-voice-centric.

[0177] Clause 13: A method of a core network for wireless communication, the method comprising: transmitting a message to a user equipment (UE) that uses a first universal subscriber information module (USIM), the message indicating a first usage setting or a first service type for which the UE is not allowed to access the core network via a non-terrestrial network (NTN); and communicating with the UE via the NTN cell using a second USIM, a second usage setting, or second service type for which the UE is allowed to access the core network via the NTN.

[0178] Clause 14: The method of clause 13, further comprising: receiving a request for the first service type; determining that the UE is accessing the core network via the NTN; and transmitting the message to indicate that the UE is not allowed to access the NTN for the first service type.

[0179] Clause 15: The method of clause 13 or 14, further comprising: transmitting, to the UE, at least one of: a message indicating the UE to disable the first service type; a message indicating the UE to disable the first usage setting; a message indicating the UE to enable the second service type; or a message indicating the UE to enable the second usage setting.

[0180] Clause 16: An apparatus, comprising: a communication unit; and a processing system configured to control the communication unit to implement any one of the methods of any one of clauses 1 to 15.

[0181] Another innovative aspect 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.

[0182] Another innovative aspect 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.

[0183] Another innovative aspect 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 methods.Docket No. 14730879200PCT

[0184] 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.”

[0185] 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.

[0186] In this disclosure, an expression of “X / Y” may include 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.”

[0187] 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.

[0188] 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.

[0189] 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.

[0190] The hardware and data processing apparatus used to implement the various illustrative components, logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chipDocket No. 14730879200PCTprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, particular processes, operations and methods may be performed by circuitry that is specific to a given function.

[0191] 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.

[0192] As used herein, the terms “user device”, “user equipment” (for example, UE 110), “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 or another personal mediaDocket No. 14730879200PCTdevices, 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, a mobile-internet device (MID). Depending on the type, the user 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.

[0193] 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 be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0194] Additionally, various features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also 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.

[0195] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, 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,Docket No. 14730879200PCTand 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.

Claims

Docket No. 14730879200PCTCLAIMSWhat is claimed is:

1. A method for wireless communication by a user equipment (UE) (102), comprising:camping (618, 818) on a non-terrestrial network (NTN) cell of a satellite (104) using a first universal subscriber information module (USIM) (122) and a first usage setting (124); transmitting (1030) an Attach Request message (630) to a core network (110) via the NTN cell;receiving (1032), from the core network, an Attach Response message (632, 735, 874) that indicates NTN access is not allowed (120) or a voice service is not available; and accessing (660) the NTN cell using a second usage setting (164) or a second application (166) for which NTN access is allowed (160).

2. The method of claim 1, further comprising, prior to the accessing the NTN cell:determining that the UE is not allowed to access the NTN cell using the first USIM, the first usage setting, or for a first application type;disabling an NTN capability of the UE;changing (764, 765) a configuration of the UE to use a second USIM (162) or the second usage setting; andre-enabling the NTN capability of the UE.

3. The method of claim 1, further comprising, prior to the accessing the NTN cell:determining that a second USIM (162), the second usage setting, or the second application is allowed for NTN access; andrefraining (745) from disabling an NTN capability of the UE based on the UE having the second USIM, the second usage setting, or the second application.

4. The method of claim 3, wherein the determining that the second usage setting or the second application is allowed for NTN access is based on public land mobile network (PLMN) access information, and wherein the PLMN access information includes an indication of allowed usage settings or application types associated with PLMNs.Docket No. 14730879200PCT5. The method of any one of claims 1 to 4, wherein the receiving the Attach Response message includes at least one of:receiving an Attach Reject message (632) that indicates NTN access is not allowed; or receiving an Attach Accept message (735, 874) that indicates the NTN access is not allowed for an application type associated with the first usage setting.

6. The method of any one of claims 1 to 5, further comprising:receiving an indication from the NTN cell that the voice service is not allowed via the NTN access;disabling the voice service based on the voice service being not allowed for the NTN access; andenabling a non-voice service for the NTN access.

7. The method of claim 6, wherein the receiving the indication includes at least one of:receiving the indication in an Attach Accept message from a core network via the NTN cell; orreceiving the indication in a system information message from the NTN cell.

8. The method of any one of claims 1 to 7, wherein the accessing the NTN cell using the second usage setting or for the second application, includes at least one of:disabling the first USIM;selecting a second USIM;changing a usage setting of the UE from the first usage setting to the second usage setting; selecting the second usage setting from among multiple usage setting options of the UE; selecting the second usage setting as non-voice-centric based on an indication that a voice service is not available via the NTN cell; ordisabling, at the UE, access to a first service and enabling access to a second service.

9. The method of any one of claims 1 to 8, wherein the accessing the NTN cell using the second usage setting or for the second application, includes at least one of:performing an IP multimedia system (IMS) registration for a second service when the UE accesses the NTN cell using a second USIM or the second usage setting;performing an IMS registration for the second application when the NTN cell indicates the second service is available for NTN access;Docket No. 14730879200PCTperforming an IMS registration for the second service based on an application at the UE attempting to access the second service via the NTN cell; orperforming an IMS registration for the second service based on the UE using the second USIM to access the NTN cell.

10. The method of any one of claims 1 to 9, further comprising:using the first USIM or the first usage setting when accessing a terrestrial network (TN) cell; andusing a second USIM or the second usage setting when accessing the NTN cell.

11. The method of any one of claims 1 to 10, further comprising:enabling an NTN capability of the UE based on at least a first application or service type, where the first application or service type is an emergency-type application; andrestricting data communication for a second application or service type for which NTN access is not allowed.

12. The method of any one of claims 1 to 11, wherein the first usage setting is voice-centric and the second usage setting is non-voice-centric.

13. A method of a core network for wireless communication, the method comprising:transmitting a message to a user equipment (UE) that uses a first universal subscriber information module (USIM), the message indicating a first usage setting or a first service type for which the UE is not allowed to access the core network via a non-terrestrial network (NTN); andcommunicating with the UE via the NTN using a second USIM, a second usage setting, or second service type for which the UE is allowed to access the core network via the NTN.

14. The method of claim 13, further comprising:receiving a request for the first service type;determining that the UE is accessing the core network via the NTN; andtransmitting the message to indicate that the UE is not allowed to access the NTN for the first service type.Docket No. 14730879200PCT15. The method of claim 13 or 14, further comprising:transmitting, to the UE, at least one of:a message indicating the UE to disable the first service type;a message indicating the UE to disable the first usage setting;a message indicating the UE to enable the second service type; or a message indicating the UE to enable the second usage setting.

16. An apparatus, comprising:a communication unit; anda processing system configured to control the communication unit to implement any one of the methods of any one of claims 1 to 15.

Images