Managing non-terrestrial network access

Abstract

To access a non-terrestrial network (NTN), a user equipment (UE) receives (1402), in a terrestrial network (TN) cell, information related to non-terrestrial network (NTN) cell that operates using a low-power wide area network (LPWA) technology; searches for the NTN cell using the information (1410); and selects (814) the NTN cell for registration.

Description

PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00MANAGING NON-TERRESTRIAL NETWORK ACCESSCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 703,176 entitled “Managing Non-Terrestrial Network Access,” filed on October 3, 2024. The entire content of the provisional application is hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to wireless communication systems, and particularly to managing non-terrestrial network access.BACKGROUND

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

[0004] The 5G technology relies primarily on legacy terrestrial networks. However, the 3rd Generation Partnership Project (3GPP) organization has proposed to extend 5G communications to non-terrestrial networks (NTNs) with 5G new radio (NR) technologies, or with the Long- Term -Evolution (LTE) technologies tailored for the Narrowband Internet-of-Thing (NB-IoT) or the enhanced Machine Type Communication (eMTC) scenarios. In an NTN, an RF transceiver is mounted on a satellite, an unmanned aircraft systems (UAS) also referred to as drone, balloon, plane, or another suitable apparatus. For simplicity, the discussion below refers to all such apparatus as satellites. In addition to satellites, an NTN can include the sat-gateways that connect the Non-Terrestrial Network to a public data network, feeder links between sat-gateways and satellites, service links between satellites, and inter-satellite links (ISL) when satellites form constellations.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0005] A satellite can belong to one of several types based on altitude, orbit, and beam footprint size. The types include Low-Earth Orbit (LEO) satellite, Medium-Earth Orbit (MEO) satellite, Geostationary Earth Orbit (GEO) satellite, UAS platform (including High Altitude Platform Station (HAPS)), and High Elliptical Orbit (HEO) satellite. GEO satellites are also known as the Geosynchronous Orbit (GSO) satellites, and LEO / MEO satellites are also known as non-GSO (NGSO) satellites.

[0006] A GSO satellite can communicate with one or more sat-gateways deployed over a satellite targeted coverage area (e.g., a region, country, continent, etc.). A non-GSO satellite at different times can communicate with one or several serving sat-gateways. An NTN is designed to ensure service and feeder link continuity between successive serving sat-gateways, with sufficient time duration to proceed with mobility anchoring and hand-over procedures.

[0007] A satellite can support a transparent or a regenerative (with on board processing) payload, and typically generates several beams for a given service area bounded by the field of view. The footprints of the beams typically have an elliptic shape and depend on the on-board antenna configuration and the elevation angle. For a transparent payload implementation, a satellite can apply RF filtering and / or frequency conversion and amplification, and refrain from changing the waveform signal. For a regenerative payload implementation, a satellite can apply RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and / or coding / modulation. This approach is effectively equivalent to implementing most of the functions of a base station, e g., a gNB or an eNB.

[0008] NB-IoT and eMTC technologies are expected to be particularly suitable for loT devices operating in remote areas with limited or no terrestrial connectivity. Such loT devices can be used in a variety of industries including for example transportation (maritime, road, rail, air) and logistics; solar, oil, and gas harvesting; utilities; farming; environmental monitoring; and mining. However, to ensure the required loT connectivity, deployment of these technologies requires satellite connectivity to provide coverage beyond terrestrial deployments. Satellite NB- loT or eMTC is defined in a complementary manner to terrestrial deployments.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0009] Many non-IoT devices that fully support LTE and 5G networks have only the capability to connect to NB-IoT Non-Terrestrial Networks (NTNs) for messaging services. However, the existing technologies currently lack procedures that would allow a device to switch from a terrestrial LTE / 5G network to an NB-IoT NTNs. This is a significant gap, as a seamless switch from a TN network to an NB-IoT NTNs may be essential for a users in an emergency situation.SUMMARY

[0010] An example embodiment of the techniques of this disclosure is a method for accessing a non-terrestrial network (NTN). The method is implemented in a user equipment (UE) and comprises receiving, in a terrestrial network (TN) cell, information related to non-terrestrial network (NTN) cell that operates using a low-power wide area network (LPWA) technology; searching for the NTN cell using the information; and selecting the NTN cell for registration.

[0011] Another example embodiment of these techniques is a configuration method implemented in a radio access network (RAN). The method comprises transmitting, in a non- Internet-of-Things (non-IoT) cell, initial access information for accessing the non-IOT cell; and transmitting, in the non-IoT cell, information related to an loT non-terrestrial network (NTN) cell.

[0012] Still another example embodiment of these techniques is a communication device comprising a transceiver; and processing hardware configured to implement one of the methods above.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figs. 1A and IB are block diagrams of example wireless communication system in which a user device can communicate with a terrestrial network (TN) and an Internet-of-Things (loT) non-terrestrial network (NTN);

[0014] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1 communicates with base stations;PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0015] Fig. 3A is a block diagram of an example NTN node with transparent payload implementation, in which a base station is on the ground and connects to a satellite via a sat- gateway;

[0016] Fig. 3B is a block diagram of an example NTN node with regenerative payload implementation, in which a base station is located on a satellite;

[0017] Fig. 4 is a block diagram of an example scenario in which a UE moves from the area of coverage of TN cell to the area of coverage of an NTN cell;

[0018] Fig. 5A illustrates example PLMN access information which a UE can use to search for an NTN cell;

[0019] Fig. 5B illustrates example PLMN access information which a UE can use to determine the relationship between a TN PLMN and an NTN PLMN;

[0020] Fig. 6 is a messaging diagram of an example scenario in which the UE is initially in an TN cell coverage and later registers with an loT NTN cell associated with a different PLMN, based on the PLMN access configuration received in the TN cell;

[0021] Fig. 7 is a messaging diagram of an example scenario generally similar to that of Fig. 6, but in which the TN cell and the loT NTN cell belong to the same PLMN;

[0022] Fig. 8 is a flow diagram of an example method according to which a UE receives satellite information in a TN cell and uses the satellite information and / or PLMN access configuration to search for an NTN cell, which can be implemented in the UE of Fig. 1A;

[0023] Fig. 9 is a flow diagram of an example method generally similar to that of Fig. 8, except that the UE determines the RAT and / or carrier frequency using the satellite information and / or the PLMN access configuration;

[0024] Fig. 10A is a flow diagram of an example method generally similar to that of Fig. 8, except that the UE determines whether the NTN is associated with a certain PLMN, prior to the searching;PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0025] Fig. 1 OB is a flow diagram of an example method generally similar to that of Fig. 8, except that the UE determines whether the UE detects a USIM configured for NTN communication, prior to the searching;

[0026] Fig. 11 is a flow diagram of an example method generally similar to that of Fig. 8, except that the UE determines whether a broadcast message in the TN cell indicates a carrier frequency of a RAT used for NTN communication, prior to the searching;

[0027] Fig. 12 is a flow diagram of an example method generally similar to that of Fig. 8, except that the UE determines whether a broadcast message in the TN cell includes satellite information, prior to the searching;

[0028] Fig. 13 is a flow diagram of an example method for broadcasting access information for a TN cell and satellite information for an loT NTN cell, which can be implemented in the RAN of Fig. 1A;

[0029] Fig. 14 is a flow diagram of an example method for accessing a TN cell and searching for an loT NTN cell using the satellite information the TN cell transmits, which can be implemented in the UE of Fig. 1A; and

[0030] Fig. 15 is a flow diagram of an example method according to which a UE determines whether the UE is allowed to access an NTN based on the PLMN access information and / or satellite information a TN cell transmits, which can be implemented in the UE of Fig. 1A.DETAILED DESCRIPTION OF THE DRAWINGS

[0031] The techniques discussed below provide mechanisms, for a user equipment (UE) and / or a network device operating in a radio access network (RAN), to allow the UE to perform a seamless switch from a TN network to an NB-IoT NTN or, more generally, to a cell that operates using a low-power wide area network (LPWA) technology.

[0032] Referring first to Fig. 1A, a wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, a radio access network (RAN) 105, a RAN 103, a core network (CN) 110, and a CN 109. The RAN 105 includes a base station 104 and may includePATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 one or more additional base station(s). The CN 110 may be an evolved packet core (EPC) 111, a fifth generation (5G) core (5GC) 160, or a sixth generation core (6GC) 170, for example. The CN 109 may be an EPC, 5GC, or 6GC, for example. The RAN 103 includes a base station 106 and may include one or more addition base station(s). The RAN 105 and the CN 110 belong to a Public Land Mobile Network (PLMN) 108, while the RAN 103 and the CN 109 belong to a PLMN 107. The base station 104 and / or the additional base station(s) in the RAN 105 communicates with UEs via one or more satellites (as suggested by the satellite icon), the PLMN 108 thus being a non-terrestrial network (NTN). The base station 106 and / or the additional base station(s) in the RAN 103 communicates with UEs using terrestrial equipment (as suggested by the tower icon) without employing satellites, the PLMN 107 being a terrestrial network (TN).

[0033] The base station 104 covers a cell 124, and the base station 106 covers a cell 126. If the base station 104 is a gNB, the cell 124 is an NR cell. If the base station 104 is an ng-eNB or eNB, the cell 124 is an Evolved Universal Terrestrial Radio access (E-UTRA) cell or a NB-IoT cell. If the base station 104 is a 6G base station, the cell 124 is a 6G cell or a 6G loT cell. Similarly, the cell 126 is an NR cell, a E-UTRA or NB-IoT cell, a 6G or 6G loT cell, depending on the base station is a gNB, an ng-eNB or eNB, or a 6G baes station. In general, each of the RANs 105 and 103 can include any number of base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. The UE 102 can support at least one of 6G, 5GNR (or simply, “NR”), E-UTRA, and / or NB-IoT air interface to communicate with the base stations 104 and 106. Each of the base station 104 and the additional base station(s) in the RAN 105 can connect to the CN 110 via an interface (e.g., SI, NG, or N6G interface). The base station 104 and the additional base station(s) in the RAN 105 also can be interconnected via an interface (e.g., X2, Xn, or X6G interface) for interconnecting RAN nodes. Each of the base station 106 and the additional base station(s) in the RAN 103 can connect to the CN 109 via an interface (e.g., SI, NG, or N6G interface). The base station 106 and the additional base station(s) in the RAN 103 also can be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting RAN nodes.

[0034] Among other components, the EPC 111 may include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00The SGW 112 in general is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The EPC 111 may include other MME, SGW and / or PGW not shown in Fig. 1 A. The 5GC 160 includes a User Plane Function (UPF) 162 and an Access and Mobility Management Function (AMF) 164, and / or Session Management Function (SMF) 166. The UPF 162 is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions. The 5GC 160 may include other AMF, SMF and / or UPF not shown in Fig. 1. The 6GC 170 includes a 6G UPF 172 and a 6G AMF 174, and / or 6G SMF 176, similar to the UPF 162, the AMF 164 and the SMF 176 with enhanced functions respectively. The CN 109 has similar components as the CN 110.

[0035] As illustrated in Fig. 1A, the base station 104 supports a cell 124, and the base station 106 supports a cell 126. Note that cell 124 has a shape corresponding to the footprint of the satellite beams, which unlike cell 126, may project on different areas at different times. The cells 124 and 126 partially overlap, so that the UE 102 can select, reselect, or hand over from one of the cells 124 and 126 to the other. The base station 104 and base station 106 may exchange messages via the CN 110, CN 109, the interface between the base station 104 and the CN 110, the interface between the base station 106 and the CN 109, and one or more interfaces between the CN 110 and the CN 109. Alternatively, the base station 104 and the base station 106 may support an X2, Xn, X6G interface to directly exchange messages. In general, the CN 110 is able to connect to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0036] The base station 104 is equipped with processing hardware 130 that includes one or more general -purpose processors (e.g., CPUs) and a non-transitory computer-readable memory (CRM) storing instructions that the one or more general -purpose processors execute.Additionally or alternatively, the processing hardware 130 may include special-purpose processing units. According to an embodiment illustrated in Figure 1, the processing hardwarePATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00130 includes a processor 134 to process data that the base station 104 transmits in the downlink direction, or data that the base station 104 receives in the uplink direction. The processing hardware 130 also includes a transceiver 132 configured to transmit data in the downlink direction and to receive data in the uplink direction. The CRM (not shown) stores executable codes for the processor 134 to perform methods according to embodiments described in this section. The base station 106 includes generally similar components. In particular, components 140, 142 and 144 of the base station 106 may be similar to the components 130, 132, and 134 respectively. The process hardware 140 further includes a NTN controller 148 configured to control UEs to search and access a NTN.

[0037] The UE 102 is equipped with processing hardware 150 that can include one or more general -purpose processors such as CPUs and non -transitory CRM storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. As schematically illustrated in Figure 1, the processing hardware 150 includes a processor 154 to prepare data that the UE 102 transmits in the uplink direction, or to process data that the UE 102 receives in the downlink direction. The processing hardware 150 also includes a transceiver 152 configured to transmit data in the uplink direction and to receive data in the downlink direction. The process hardware 150 further includes a protocol controller 156 configured to perform communication functions of protocol layers, e.g., described in Figs. 2A and 2B. For example, the communication functions includes mobility management functions, session management functions, and / or radio resource control functions. The process hardware 150 further includes a NTN controller 158 configured to determine whether to search and access a NTN.

[0038] Fig. IB is similar to Fig. 1A except that the base station 106 connects to the CN 110. The description for Fig. 1A can apply to Fig. IB. The base stations 104 and 106 may exchange messages via the interface between the base station 104 and the CN 110 and the interface between the base station 106 and the CN 110.

[0039] Fig. 2A illustrates, in a simplified manner, an example protocol stack 200A according to which the UE 102 can communicate with an eNB / ng-eNB or a gNB (e g., one or more of the base stations 104, 106).PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0040] In the example stack 200A, a physical (PHY) layer 202 provides transport channels to a MAC sublayer 204, which in turn provides logical channels to a RLC sublayer 206. The RLC sublayer 206 in turn provides RLC channels to a PDCP sublayer 208. The PDCP sublayer 208 in turn can provide data transfer services to a radio resource control (RRC) sublayer 210, an Internet Protocol (IP) layer and / or a Service Data Adaptation Protocol (SDAP) sublayer (not shown in Fig. 2). The PDCP sublayer 208 receives packets (e.g., from the RRC sublayer 210, the SDAP sublayer, or the IP layer, layered directly or indirectly over the PDCP sublayer 208) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC sublayer 206) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets”. In some implementations, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are EUTRA layers or sublayers. In other implementations, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are NR layers or sublayers.

[0041] The RRC sublayer 210 provide data transfer services to a Non- Access-Stratum (NAS) layer 212. The NAS layer 212 includes a mobility management (MM) sublayer and / or a session management (SM) sublayer. In some implementations, the MM sublayer is an EPS MM (EMM) sublayer. In other implementations, the MM sublayer is a 5G MM (5GMM) sublayer. In some implementations, the SM sublayer is an EPS SM (ESM) sublayer. In other implementations, the SM sublayer is a 5G SM (5GSM) sublayer. When the base station (gNB or eNB 104 / 106) receives UL NAS PDUs from the UE 102, the base station forwards the UL NAS PDUs to the CN 110 without processing the UL NAS PDUs. When the base station receives DL NAS PDUs from the CN 110, the base station forwards the DL NAS PDUs to the UE 102 without processing the DL NAS PDUs. That is, the NAS layer 212 is transparent to the base station.

[0042] On a control plane, the PDCP sublayer 208 can provide signaling radio bearers (SRBs) to the RRC sublayer 210 to exchange RRC messages or NAS messages (e.g., MM messages and / or SM messages), for example. On a user plane, the PDCP sublayer 208 can provide Data Radio Bearers (DRBs) to support user plane data exchange. User plane data exchanged on the PDCP sublayer 208 can be SDAP PDUs, Internet Protocol (IP) packets or Ethernet packets.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0043] Fig. 3A illustrates a certain type of NTN deployment 300A referred to as transparent payload architecture, which involves a satellite gateway 302 and a “transparent” satellite 304 for extending the range of the Uu interface. In one implementation, the satellite 304 implements a frequency conversion and a Radio Frequency (RF) amplifier in both the uplink and downlink directions. With that being said, the satellite function is similar to that of an analogue RF repeater. As a result, the satellite 304 repeats the Uu radio interface from the feeder link (between the NTN gateway and the satellite) to the service link (between the satellite and the UE) in the downlink direction and vice versa in the uplink direction. The Satellite Radio Interface (SRI) on the feeder link is the Uu, and the NTN gateway 302 supports all necessary functions to forward the signal of the Uu interface. The NTN gateway 302 can be placed at the same site as the base station (e.g., eNB, gNB) 104 location, or be connected to the base station 104 at a distance via a wired link. It is also possible to connect more than one NTN gateway to a base station. Different transparent satellites may be connected to the same base station on the ground, via the same NTN gateway, or via different NTN gateways.

[0044] Fig. 3B illustrates a certain type of NTN deployment 300B referred to as regenerative payload architecture, which involves the UE 102, the satellite gateway 302, a satellite 304, and the base station 104 on the satellite 304. The satellite 304 implements a Radio Frequency (RF) fdtering, a RF amplifier, and a frequency conversion in both the uplink and / or downlink directions. As a result, the base station 104 communicates with the UE 102 via the satellite 304 and the Uu radio interface in the downlink direction and vice versa in the uplink direction. The base station 104 communicates with the CN 110 via a feeder link (between the NTN gateway 302 and the satellite 304) and a link between the NTN gateway 302 and the CN 110. The NTN gateway 302 can be placed at the same site as the CN 110, or be connected to the CN 110 at a distance via a wired link or a wireless link.

[0045] Fig. 4 illustrates an example scenario 400 in which the UE 102 initially is in the coverage of the NTN cell 124 at time ti. The UE 102 registers with the PLMN 108 via the NTN cell 124 at time tl. The PLMN 108 may be a home, equivalent home, or visited PLMN for the UE 102. At time t2, the UE 102 moves out of TN coverage (i.e., the TN cell 126) and into an NTN coverage (i.e., the NTN cell 124). The UE 102 may perform an NTN search (i.e.,PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 searching for an NTN cell) in response to detecting an out-of-TN coverage event. Alternatively, the UE 102 may refrain from performing an NTN search in response to detecting the out-of-TN coverage event and perform an NTN search in response to activating NTN communication (e.g., activating an NTN application of the UE 102 or initiating the process of sending a message).

[0046] Fig. 5A illustrates a table 500A listing example PLMN access information. In some implementations, a UE (e.g., the UE 102) 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 a frequency band for a TN, the UE determines the PLMN is associated with a TN. For example, row 592A indicates 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). Row 592G specifies that the PLMN ID4 is associated with an NTN because the frequency band 256 is defined for satellite access in a 3GPP specification (e.g., 3GPP TS 36.102 or 38.101-5).

[0047] Rows 592E and 592F specify frequency bands 25 and 41, respectively, for NR. Rows 592H and 5921 specify frequency bands 17 and 13, respectively, for EUTRA. Row 592J specifies frequency band 150 for 6G, and row 592K specifies frequency band 252 for satellite 6G.

[0048] In some configurations, frequency bands 253, 254, 255, and 256 are allocated for satellite access. In other configurations, however, it possible to allocate additional frequency bands for satellite access (and specify these allocations in a 3GPP specification similar to the table of Fig. 5A). However, as more NTNs are deployed and newer types of spacebome or airborne vehicles are created, it is possible for an NTN to use frequency bands that were previously considered reserved for TN access. For example, row 592B specifies that PLMN ID2 uses satellite E-UTRA access in frequency band 25. In implementations where a UE relies on the frequency band number to determine whether a PLMN is associated with a NTN or a TN, the use of frequency bands might be limited or the UE might be unable to distinguish NTN or TNs. For example, consider second row 592B, where PLMN ID2 operates a satellite E-UTRA NTN inPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 frequency band “25.” A UE might consider PLMN ID2 to be associated with a TN because frequency band “25” is not previously defined for satellite access.

[0049] In some implementations, the PLMN access information in table 500A explicitly indicates the RAT type. For example, the UE can determine that the PLMN ID1 is associated with an NTN because the first row 592A 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 592D indicates the E-UTRA type (i.e., no “satellite” in the RAT type). In another example, the UE determines that PLMN LD3 is associated with a NTN because the third row 592C indicates the “satellite” E-UTRA type. In yet another example, the UE determines a PLMN identified by the PLMN ID4 (seventh row 592G) is associated with an NTN because the RAT type is the satellite NR. A potential technical advantage of indicating the RAT type in table 500A 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 is not specific to NTN or TN (such as frequency band “25” being used for an NTN in the PLMN ID2 and the PLMN ID3 and also used for an NR RAN in the PLMN ID3). In some implementations, the PLMN access information may include either one of rows 592B or 592C.

[0050] 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, 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 table 500A. 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 typePATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 indicated in table 500A to distinguish NTN or TN so that the PLMN ID can use MCCs other than a general MCC for satellite access.

[0051] 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 uplink (UL) frequency range and downlink (DL) frequency range. For example, when the UE determines to search PLMN ID1, based on PLMN access information in the first row 592A, 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 592B, 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 592D, 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 table 500A 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 a 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.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0052] Fig. 5B illustrates a table 500B listing example TN and NTN information, which indicates the relationship between TN PLMNs, NTN PLMNs, and / or satellites. In some implementations, a UE (e.g., the UE 102) can determine association between TNs and NTNs based on the TN and NTN association information. For example, the first row 593A shows that a NTN of a PLMN identified by the PLMN ID2 is associated with a TN identified by the PLMN ID3. In some implementations, when or after the UE has registered with the TN, the UE may determine to search or search a NTN cell of the NTN based on row 593 A. In some implementations, based on row 592B in table 500A, the UE may further determine to search for an NTN cell of the NTN on band 25 and / or one or more carrier frequencies within the frequency range. If the UE finds a suitable NTN cell of the NTN as a result of the NTN search, the UE performs an attach procedure, a tracking area update procedure, or a registration procedure with the NTN via the NTN cell.

[0053] In some implementations, the TN and NTN information may include NTN and satellite information that indicates an association between NTNs and satellites. The UE (e.g., the UE 102) can determine association between NTNs and satellites based on the NTN and satellite association information. For example, row 593A further indicates that a satellite identified by Satellite ID1 is associated with the PLMN ID2. In this example, the UE may determine to search for an NTN cell of the NTN on a satellite identified by Satellite ID1. In some implementations, the UE receives satellite information from a TN cell of the TN (e.g., event 604 of Fig. 6 or event 704 of Fig. 7). If the satellite information indicates (e.g., includes) Satellite ID1, the UE may determine to search for an NTN cell of the NTN as described above. Otherwise, if the satellite information does not indicate Satellite ID1, the UE may refrain from searching the NTN. In some implementations, the satellite information may or may not include one or more other Satellite IDs different from the Satellite ID1. In some implementations, if the TN is a home PLMN of the UE, the UE may determine to search or search the NTN as described above. Otherwise, if the TN is a visited PLMN for the UE, the UE may refrain from searching the NTN. In some implementations, if the UE detects a Universal Subscriber Identity Module (USIM) of the NTN, the UE may determine to search or search the NTN as described above. Otherwise, if the UE does not detect a USIM of the NTN, the UE may refrain from searching the NTN.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0054] In another example, the first row 593A shows that a TN identified by the PLMN ID3 is associated with a NTN identified by the PLMN ID2. In some scenarios, when or after the UE has registered with the NTN PLMN identified by the PLMN ID2, the UE determines to search for an TN cell of the TN identified by the PLMN ID3 based on row 593 A. In some scenarios, based on row 592D in table 500A, the UE further determines to search for a TN cell of the TN on band 5 and / or a carrier frequency within the frequency range. If the UE finds a TN cell of the TN as a result of the TN search, the UE performs an attach procedure, a tracking area update procedure, or a registration procedure with the TN via the TN cell. In If the NTN is a home PLMN of the UE, the UE may determine to search for the TN as described above. Otherwise, if the NTN is a visited PLMN for the UE, the UE may refrain from searching the TN. In some scenarios, if the UE detects a Universal Subscriber Identity Module (USIM) of the TN, the UE determines to search for the TN as described above. Otherwise, if the UE does not detect a USIM of the TN, the UE refrains from searching the TN.

[0055] In some implementations, multiple NTNs are associated with a TN. For example, row 593B indicates that a first NTN identified by PLMN ID1 is associated with a TN identified by PLMN ID5, and row 593 C indicates that a second NTN identified by the PLMN ID4 is associated with the TN. In some implementations, the first NTN is associated with Satellite ID2, and the second NTN is associated with Satellite ID3. In some implementations, when or after the UE has registered with the TN, the UE determines to search for an NTN cell of the first NTN and / or a NTN cell of the second NTN based on row 593B and / or row 593C as described above.

[0056] Row 593D indicates that an NTN of a PLMN identified by PLMN ID1 is associated with a TN identified by PLMN ID6, and row 593E indicates that an NTN of a PLMN identified by PLMN ID1 is also associated with a TN identified by PLMN ID7. Thus, in some cases, the same NTN can correspond to multiple TNs. Next, several example scenarios in which the base station 104 operating in the system of Fig. 1A or Fig. IB communicates with the UE 102 and the CN 110 via the satellite 304. The base station 104 can be either on the ground as described for Fig. 3A or located with the satellite 304 as described in connection with Fig. 3B.

[0057] Generally speaking, events in Figs. 6-15 that are similar are labeled with similar reference numbers (e.g., event 604 of Fig. 6 is similar to event 704 of Fig 7, block 802 of Figs. 8,PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-009, 10A and 1OB is similar to block 1102 of Fig. 11, block 1302 of Fig. 13 and block 1402 of Fig. 14), with differences discussed below where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures. Note, the descriptions below may apply to communication between a UE and a base station in a terrestrial network.

[0058] Fig. 6 illustrates an example scenario 600, in which PLMN 107 is a TN and PLMN 108 is a NTN. The UE 102 is initially in coverage of the PLMN 107. The UE 102 receives 601 first system information including initial access information from a TN cell (e.g., cell 126 in Fig. 1A) of the PLMN 107. In some implementations, the initial access information 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. In some implementations, first system information includes at least one system information block (SIB). For example, if the TN cell is a NR. cell, the at least one SIB includes a SIB 1 (SIB1), e.g., defined in 3GPP specification 38.331. In another example, if the TN cell is an E-UTRA cell, the at least one SIB includes a SystemlnformationBlockType 1 and / or aSystemInformationBlockType2 as defined in 3GPP specification 36.331. In yet another example, if the TN cell is a 6G cell, the at least one SIB are 6G SIB(s).

[0059] After receiving 601 the first system information, the UE 102 may receive 602 second system information including satellite information from the TN cell. In some implementations, the first system information includes scheduling information for the second system information and the UE 102 receives 602 the second system information accordance with the scheduling information. Alternatively, the UE 102 is preconfigured with the satellite information before event 601. Yet alternatively, the UE 102 receives the satellite information in one or more Internet Protocol (IP) packets from a server via the PLMN 107 or Internet. The satellite information may include parameters for one or more satellites or NTN cells. In some implementations, the satellite information may include one or more satellite information elements (IES) each for a corresponding satellite. Each satellite IE may include a satellite IDPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 identifying the corresponding satellite or satellite IE, ephemeris information, network-controlled common timing advance parameters, epoch time, a service start time, and / or a scheduling offset. The service start time indicates the earliest time when an area is going to be covered by a satellite indicated by the corresponding satellite IE. In other implementations, the satellite information may include one or more NTN cell information elements (IES) each for a corresponding NTN cell. Each NTN cell IE may include a satellite ID identifying a corresponding satellite, ephemeris information, network-controlled common TA parameters, epoch time, a service start time, a scheduling offset, a frequency band number indicating a frequency band, carrier frequency information indicating a carrier frequency, and / or a physical cell identity. A frequency band, a carrier frequency and / or a physical cell identity in a NTN cell IE indicates a NTN cell. In such cases, a NTN cell IE may or may not include a satellite ID.

[0060] In some implementations, the second system information includes at least one SIB (SIB(s)). For example, if the TN cell is a NR cell, the SIB is a SIB 19 (SIB 19) defined in 3GPP specification 38.331. In another example, if the TN cell is an E-UTRA cell, the SIB(s) include a SystemInformationBlockType32 (not a SystemInformationBlockType33-NB) and / or a SystemInformationBlockType33 (not a System Infor mationBlockType 33-NB) as defined in 3 GPP specification 36.331. Alternatively, the SIB(s) include a SystemInformationBlockType32-NB and / or a SystemInformationBlockType33-NB as defined in 3GPP specification 36.331. In yet another implementation, if the TN cell is a 6G cell, the SIB is a SIB defined for 6G. In some implementations, the TN cell is a non-IoT cell. In other implementations, the TN cell serves non-IoT UEs. In some implementations, the TN cell does not serve NB-IoT UEs. In other implementations, the TN cell does not serve enhanced machine type communication (eMTC) UEs (i.e., bandwidth reduction UEs).

[0061] In some implementations, the UE 102 may receive 604 PLMN access configuration from the PLMN 107 (e.g., the TN cell, another TN cell or WiFi) before or after event 601. In one implementation, the UE 102 may receive 604 third system information including the PLMN access configuration from the PLMN 107. For example, the third system information is or includes a SIB and different from the second system information. In another implementation, event 602 and event 604 can be combined as a single event. In such cases, the second systemPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 information includes the PLMN access configuration. In yet another implementations, the UE 102 receives one or more IP packets including the PLMN access configuration from the PLMN 107 (e.g., via the TN cell, another TN cell or WiFi) or from a server via the PLMN 107 or Internet. In other implementations, the UE 102 is preconfigured with the PLMN access configuration before event 601. For example, the UE 102 has the PLMN access configuration pre-stored in a non-transitory computer-readable medium. In another example, the UE 102 retrieves the PLMN access configuration from a USIM. In some implementations, the PLMN access configuration includes PLMN access information similar to Fig. 5A. In other implementations, the PLMN access configuration includes TN and NTN association information similar to Fig. 5B.

[0062] In some implementations, the UE 102 is a non-IoT UE and the TN cell serves non-IoT UEs. The UE 102 receives the first system information, second system information and / or the third system information via a broadcast control channel (BCCH) defined for non-IoT UEs.

[0063] After receiving the first system information, the second system information, and / or the PLMN access configuration, the UE 102 then performs 606 a registration procedure with the PLMN 107, e.g., based on the initial access information. When the UE 102 successfully performs the registration procedure with the PLMN 107, the UE 102 operates in a registered state with the PLMN 107. In some implementations, the UE 102 uses a first USIM to register with the PLMN 107. In some implementations, the registration procedure is an Attach procedure or a Tracking Area Update procedure defined in 3GPP specification 24.301. In other implementations, the registration procedure is a Registration procedure defined in 3GPP specification 24.501. In yet other implementations, the registration procedure is a Registration procedure defined in a 3 GPP specification for 6G.

[0064] After registering with the PLMN 107 or while operating in the registered state with the PLMN 107, the UE 102 detects 608 the TN cell is not suitable, detects 608 out of coverage of the PLMN 107, or activates 608 NTN communication. In some implementations, the UE 102 determines that the TN cell is not suitable based on cell selection criteria. In some implementations, if signal strength is below or equal to a first threshold (e.g., default or preconfigured value), the UE 102 determines that the TN cell is not suitable. For example, thePATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 first threshold may be zero. In some implementations, if signal strength and signal quality is below or equal to a first threshold and a second threshold respectively, the UE 102 determines that the TN cell is not suitable. In some implementations, the first threshold and the second threshold are different values (e.g., default values or preconfigured values). In other implementations, the first threshold and the second threshold are the same value (e.g., default or preconfigured value). For example, the first threshold and second threshold may be zero. In some implementations, the UE 102 activates 608 the NTN communication while in coverage of the PLMN 107. In other implementations, the UE 102 activates 608 the NTN communication while in out of coverage of the PLMN 107. In some implementations, the activation of the NTN communication includes activating an NTN application or activating transmission of a message via a NTN. In response to event 608, the UE 102 searches a NTN cell of the PLMN 108 based on the PLMN access configuration and / or the satellite information. The UE 102 discovers 612, as a result of the NTN search 610, a suitable NTN cell (e.g., cell 124 of Fig. 1 A) of the PLMN 108 and selects 614 the NTN cell. In some implementations, the UE 102 determines that the NTN cell is suitable based on a cell selection criteria. After selecting the NTN cell, the UE 102 receives 615 (fourth) system information including initial access information and may receive 616 (fifth) system information including satellite information from the NTN cell.

[0065] In some implementations, the UE 102 receives the fourth system information and the fifth system information via a bandwidth reduction BCCH (BR-BCCH) for eMTC communication from the NTN cell. In other implementations, the UE 102 receives the fourth system information and the fifth system information via a BCCH for non-IoT communication from the NTN cell. In yet other implementations, the NTN cell utilizes NB-IoT and the UE 102 receives the fourth system information and the fifth system information via a BCCH for NB-IoT communication from the NTN cell. In some implementations, the UE 102 determines that the NTN cell is suitable based on a cell selection criteria for NB-IoT. In some implementations, the fourth system information is or includes at least one SIB. For example, the at least one SIB includes a SystemlnformationBlockType 1 and / or a SystemInformationBlockType2 as defined in 3GPP specification 36.331. In another example, the at least one SIB includes aPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00SystemlnformationBlockTypel-NB and / or a SystemInformationBlockType2-NB as defined in 3GPP specification 36.331.

[0066] In some implementations, the fourth system information may indicate whether the fifth system information is scheduled and transmitted on the NTN cell. If the fourth system information indicates, the fifth system information is scheduled and transmitted on the NTN cell, the UE 102 attempts to receive or receives 616 the fifth system information. Otherwise, the UE 102 does not attempt to receive or receive the fifth system information. The satellite information may include a satellite ID identifying a corresponding satellite, ephemeris information, network- controlled common timing advance parameters, epoch time, and / or a scheduling offset for the NTN cell. The UE 102 them performs 618 a registration procedure with the PLMN 108 via the NTN cell, e.g., based on the initial access information and / or the satellite information. Examples and implementations for the registration procedure 606 can apply to the registration procedure 618. In some implementations, the UE 102 uses the first USIM to register with the PLMN 108. In other implementations, the UE 102 uses a second USIM to register with the PLMN 108.

[0067] In some implementations, the first USIM and the second USIM include a first home PLMN ID and a second home PLMN ID. The first home PLMN ID and the second home PLMN ID have different MCCs. Alternatively, the first home PLMN ID and the second home PLMN ID have the same MCC. The first home PLMN ID and the second home PLMN ID have different Mobile Network Codes (MNCs). Alternatively, the first home PLMN ID and the second home PLMN ID have the same MNC. In some implementations, the first PLMN ID is a PLMN ID of the PLMN 107. In other implementations, the first PLMN ID is a PLMN ID of the PLMN 108. In some implementations, the second PLMN ID is a PLMN ID of the PLMN 108. In other implementations, the second PLMN ID is a PLMN ID of the PLMN 107.

[0068] Fig. 7 illustrates an example scenario 700 similar to the scenario 600, except that the PLMN 108 in the scenario 700 includes TN coverage and an NTN coverage provided by the base station 104 and the base station 106, respectively. The description of events 601, 602, 604, 606, 608, 610, 612, 614, 615, 616, and 618 above can apply to events 701, 702, 704, 706, 708, 710, 712, 714, 715, and 718, respectively.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0069] Next, several example methods that can be implemented in a UE (e.g., the UE 102) or a base station are discussed with reference to Figs. 8-15. Descriptions for Figs. 6-7 can apply to Figs. 8-15. Each of these methods can be implemented using processing hardware such as one or more processors to execute instructions stored on a non-transitory computer-readable medium such as computer memory.

[0070] Fig. 8 illustrates an example method 800, which can be implemented by a UE, such as the UE 102 of Fig. 1A. The method 800 begins at block 802, where the UE receives satellite information from a TN cell. At block 804, the UE may obtain a PLMN access configuration. In some implementations, the UE obtains the PLMN access configuration as described above. At block 806, the UE registers with a first PLMN via a TN cell. At block 808, the UE may detect the TN cell is not suitable, detect out of coverage of the first PLMN or activates NTN communication. At block 810, the UE searches for an NTN cell, based on the PLMN access configuration and / or the satellite information. At block 812, the UE discovers a NTN cell in the NTN cell search. At block 814, the UE selects the NTN cell. At block 815, the UE receives initial access information for accessing the NTN cell. In some implementations, the UE receives the initial access information from the NTN cell. In other implementations, the UE receives the initial access information from the TN cell or another TN cell. At block 818, the UE performs a registration procedure via the NTN cell. In some implementations, the TN cell belongs to a second PLMN and the UE performs the registration procedure 818 with the second PLMN via the NTN cell. In other implementations, the TN cell belongs to the first PLMN and the UE performs the registration procedure 818 with the first PLMN.

[0071] In some implementations, the TN cell serves non-IoT UEs and the UE is a non-IoT UE (e.g., a smartphone). For example, the TN cell is an E-UTRA cell, a NR cell or a 6G cell. In some implementations, the UE at block 802 receives the satellite information in a SIB via a BCCH for non-IoT communication. That is, the BCCH is neither a BR-BCCH nor a BCCH for NB-IoT.

[0072] Fig. 9 is a flow diagram of an example method 900 similar to the method 800, and the description of blocks 802-806 and 814-818 above can apply to blocks 902-906 and 914-918, respectively, but the method 900 includes blocks 909 and 911 instead of blocks 808 and 810. AtPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 block 909, the UE determines a RAT and / or a carrier frequency based on the PLMN access configuration and / or satellite information. At block 911, the UE searches a NTN cell on the carrier frequency using the RAT and the satellite information.

[0073] Fig. 10A illustrates an example method 1000A generally similar to the method 800, except that the method 1000A includes block 1020, 1010 and 1022. At block 1020, the UE determines whether an NTN is associated with the first PLMN. In some implementations, the UE determines whether an NTN is associated with the first PLMN based on the PLMN access configuration. If an NTN is associated with the first PLMN (i.e., “Yes” branch of block 1020), the flow proceeds to block 1010 (similar to block 810 discussed above) and optionally blocks 812, 814, 815 and 818. Otherwise, if an NTN is not associated with the first PLMN (i.e., “No” branch of block 1020), the flow proceeds to block 1022. At block 1022, the UE refrains from searching a NTN cell.

[0074] Fig. 10B is a flow diagram of an example method 1000B similar to the methods 800 and 1000A, except that the method 1000B includes block 1021. At block 1021, the UE determines whether the UE detects a USIM for communication with a NTN. If the UE detects a USIM for communication with a NTN (i.e., “Yes” branch of block 1021), the flow proceeds to block 810. Otherwise, if the UE does not detect a USIM for communication with a NTN (i.e., “No” branch of block 1021), the flow proceeds to block 1022.

[0075] Fig. 11 illustrates an example method 1100, which can be implemented by a UE. The method 1100 may begin at block 1104 (similar to block 804) and / or block 1102. At block 1102, the UE receives a first SIB including satellite information from a RAN. At block 1124, the UE determines whether the UE receives a second SIB indicating a carrier frequency of a RAT associated with the satellite information. If the UE receives a SIB indicating a carrier frequency of a RAT associated with the satellite information (i.e., “Yes” branch of block 1124), the flow proceeds to block 1110. The SIB may be the first SIB or a second SIB. At block 1110, the UE searches for an NTN cell on the carrier frequency using the RAT and the satellite information. Otherwise, if the UE does not receive a SIB indicating a carrier frequency of a RAT associated with the satellite information (i .e., “No” branch of block 1124), the flow proceeds to blocks 909 and 910. The flow may proceed to blocks 1112 (similar to block 812) from block 1110 as well asPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 from block 910. The flow proceeds to blocks 1114, 1115, and 1118 (similar blocks 814, 815, and 818), from block 1112. In some implementations, if the UE at block 1110 does not discover an NTN cell, the flow may proceed to blocks 909 and 910. In some implementations, if the UE at block 910 does not discover a NTN cell, the flow proceeds to the end. In some implementations, if the UE at block 1110 does not discover a NTN cell, the flow proceeds to the end.

[0076] Fig. 12 illustrates an example method 1200, which can be implemented by an UE. The method 1200 begins at block 1204 and proceeds to block 1226. At block 1226, the UE determines whether the UE receives a SIB including satellite information. If the UE receives a SIB including satellite information (i.e., “Yes” branch of block 1226), the flow proceeds to block 1210. At block 1210, the UE searches for an NTN cell based on the satellite information in the SIB. Otherwise, if the UE does not receive a SIB including satellite information, the flow proceeds to block 1211. At block 1211, the UE searches for an NTN cell based on stored satellite information. The flow may proceed to block 1212 from block 1211 as well as from block 1210. The flow may proceeds to blocks 1214, 1215, and 1218 from block 1212.

[0077] Fig. 13 illustrates an example method 1300, which can be implemented by a first RAN node (e.g., base station 106). The method 1300 begins at block 1301, where the first RAN node broadcasts first system information on a non-IoT cell, where the first system information includes initial access information for accessing the non-IoT cell. At block 1302, the first RAN node broadcasts second system information on the non-IoT cell, where the second system information includes satellite information for an loT NTN. Descriptions above can apply to Fig. 13. In some implementations, the first system information includes first SIB(s), and the second system information includes second SIB(s).

[0078] The first RAN node receives the satellite information from a second RAN node (e.g., base station 104). In other implementations, the first RAN node receives the satellite information from an Operation, Administration and Maintenance (0AM) node. In some implementations, a third RAN node broadcasts third system information including the satellite information on an loT NTN cell of the loT NTN (e.g., event 616). In one implementation, the loT NTN cell is an NB-IoT NTN cell. In another implementation, the loT NTN cell is an eMTC loT NTN cell. In some implementations, the first RAN node broadcasts the first systemPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 information and the second system information via a BCCH neither for eMTC nor for NB-IoT. In some implementations, the third RAN node broadcasts the third system information via a BR- BCCH for eMTC. In other implementations, the third RAN node broadcasts the third system information via a BCCH for NB-IoT. In some implementations, the third system information includes third SIB(s).

[0079] In some implementations, the second SIB(s) include a SystemInformationBlockType32 and / or a SystemInformationBlockType33 as defined in 3GPP specification 36.331. In other implementations, the second SIB(s) include a SystemInformationBlockType32-NB and / or a SystemInformationBlockType33-NB as defined in 3GPP specification 36.331. In some implementations, the third SIB(s) include a SystemInformationBlockType32 and / or a SystemInformationBlockType33 as defined in 3GPP specification 36.331 . In other implementations, the third SIB(s) include a SystemInformationBlockType32-NB and / or a SystemInformationBlockType33-NB as defined in 3GPP specification 36.331. In some implementations, the second SIB(s) include a SIB19 as defined in 3GPP specification 38.331. In other implementations, the second SIB(s) includes a 6G SIB as defined in a 3 GPP 6G specification.

[0080] In some implementations, the non-loT cell is a TN cell. In some implementations, the non-IoT cell serves non-loT UEs. The first RAN node may be a 6G base station, a gNB, or an eNB, and the non-loT cell may be a 6G cell, a NR cell or an E-UTRA cell. The third RAN node is an eNB. In some implementations, the first RAN node and the third RAN node are the same RAN node. In other implementations, the first RAN node and the third RAN node are different RAN nodes.

[0081] In some implementations, the first RAN node broadcasts neighboring cell information and / or neighboring carrier frequency information for the loT NTN on the non-loT cell. For example, the first RAN node broadcasts a fourth SIB on the non-loT cell, including the neighboring cell information and / or the neighboring carrier frequency information. In other implementations, the first RAN node refrains from broadcasting the fourth SIB or the neighboring cell information and / or the neighboring carrier frequency information on the loT cell.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0082] Fig. 14 illustrates an example method 1400 similar to the method 800. The method 1400 begins at block 1041. At block 1401, the UE receives first system information on a non- loT cell, where the first system information includes initial access information for accessing the non-IoT cell. At block 1402, where the UE receives second system information on the non-IoT cell, where the second system information includes satellite information for an loT NTN. The flow may proceed to block 804 and proceeds to block 810. The flow may further proceed to blocks 812, 814, 815, and 818 from block 810. The discussion of blocks 810, 812, 814, 815, and 818 above is also applicable to Fig. 14.

[0083] Fig. 15 illustrates an example method 1500 similar to the methods 800 and 1000A. The method 1500 begins at block 1503. At block 1531, the UE determines whether the UE is allowed to access a NTN based on the PLMN access configuration and / or satellite information. If the UE is not allowed to access a NTN based on the PLMN access configuration and / or satellite information (i.e., “No” branch of block 1531), the flow proceeds to block 1522. Otherwise, if the UE is allowed to access a NTN based on the PLMN access configuration and / or satellite information (i.e., “Yes” branch of block 1531), the flow proceeds to block 1510.

[0084] The following list of examples reflects a variety of the embodiments explicitly contemplated by the present disclosure.

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

[0086] Example 1 . A method for accessing a non-terrestrial network (NTN), the method implemented in a user equipment (UE) and comprising: receiving, in a terrestrial network (TN) cell, information related to a non-terrestrial network (NTN) loT cell that operates using a low- power wide area network (LPWA) technology; searching for the NTN cell using the information; and selecting the NTN cell for registration.

[0087] Example 2. The method of example 1, wherein: the TN cell is associated with a first Public Land Mobile Network (PLMN), and the NTN cell is associated with a second PLMN.

[0088] Example 3. The method of example 1, wherein: the TN cell and the NTN cell are associated with a same PLMN.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0089] Example 4. The method of any of the preceding examples, wherein: the LPWA technology is Narrowband Intemet-of-Things (NB-IoT).

[0090] Example 5. The method of any of examples 1-3, wherein: the LPWA technology is enhanced Machine Type Communication (eMTC).

[0091] Example 6. The method of any of the preceding examples, wherein the TN cell is a non-IoT cell.

[0092] Example 7. The method of any of the preceding examples, wherein the TN cell is a non-NB cell.

[0093] Example 8. The method of any of the preceding examples, wherein the TN cell operates using an Evolved Universal Terrestrial Radio Access (EUTRA) protocol stack.

[0094] Example 9. The method of example 8, wherein: the receiving of the information related to the NTN cell includes receiving one of: a system information block (SIB) of type 32 (SIB32), a SIB of type 32 for narrowband (SIB32-NB), a SIB of type 33 (SIB33), or a SIB of type 33 for narrowband (SIB33-NB).

[0095] Example 10. The method of any of examples 1-9, wherein the TN cell operates using a fifth-generation (5G) New Radio (NR) protocol stack.

[0096] Example 11. The method of example 10, wherein: the receiving of the information related to the NTN cell includes receiving a SIB of type 19 (SIB 19).

[0097] Example 12. The method of any of the preceding examples, wherein: the information related to the NTN cell includes satellite information for the NTN cell.

[0098] Example 13. The method of example 12, wherein the satellite information includes one or more of: (i) a satellite identifier (ID) identifying a satellite with which the NTN cell is associated, (ii) ephemeris information for the satellite, (iii) one or more timing advance parameters, (iv) an epoch time, (v) a service start time for the NTN cell, (vi) a scheduling offset, (vii) an indication of a frequency band of the NTN cell, or (viii) a physical cell identifier (PCI) of the NTN cell.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0099] Example 14. The method of example 12 or 13, wherein: the satellite information for the NTN cell identifies multiple candidate satellites.

[0100] Example 15. The method of any examples 1-8 or 10, wherein: the receiving of the information related to the NTN cell includes receiving an Internet Protocol (IP) packet via the TN cell.

[0101] Example 16. The method of any of the preceding examples, further comprising: receiving a PLMN access configuration related to the NTN cell, and using the PLMN access configuration to search for the NTN cell.

[0102] Example 17. The method of example 16, wherein: the access configuration is received in the NT cell.

[0103] Example 18. The method of example 17, wherein: the access configuration is received in a radio resource configuration (RRC) message.

[0104] Example 19. The method of example 17, wherein: the information related to the NTN cell and the PLMN access configuration are received in a same broadcast message.

[0105] Example 20. The method of example 17, wherein: the information related to the NTN cell and the PLMN access configuration are received in separate broadcast messages.

[0106] Example 21. The method of example 16, wherein: the PLMN access configuration is received from a Universal Subscriber Identity Module (USIM) of the UE.

[0107] Example 22. The method of example 16, wherein: the access configuration is received via a local area network.

[0108] Example 23. The method of any of examples 16-22, wherein: the PLMN access configuration specifies, for a TN PLMN, one or more NTN PLMNs in which the UE is allowed to register.

[0109] Example 24. The method of example 23, wherein: the PLMN access configuration further specifies, for the TN PLMN, one or more satellite identifiers.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0110] Example 25. The method of any of examples 16-24, wherein: the PLMN access configuration specifies, for each of one or more PLMNs, at least one of: (i) a radio access technology type (RAT), (ii) a frequency band, or (iii) a frequency range.

[0111] Example 26. The method of any of the preceding examples, further comprising: initiating the searching for the NTN cell in response to determining that the UE is out of coverage of the TN cell.

[0112] Example 27. The method of any of examples 1-25, further comprising: initiating the searching for the NTN cell in response to initiation of NTN communication at the UE.

[0113] Example 28. The method of any of examples 1-25, further comprising: initiating the searching for the NTN cell in response to determining that at least one of a signal strength or signal quality of the TN cell is below a respective threshold.

[0114] Example 29. The method of any of examples 26-28, further comprising: performing a network registration via the NT cell prior to the initiating the searching for the NTN cell.

[0115] Example 30. The method of any of examples 26-29, further comprising: initiating the searching for the NTN cell further in response to determining that an NTN to which the NTN cell belongs is associated with a certain PLMN.

[0116] Example 31. The method of any of examples 26-29, further comprising: initiating the searching for the NTN cell further in response to detecting a USIM configured for NTN communication.

[0117] Example 32. The method of example 12, further comprising: initiating the searching for the NTN cell in response to receiving an indication of a carrier frequency associated with the satellite information.

[0118] Example 33. The method of example 32, wherein: the indication of the carrier frequency is received in a SIB transmitted separately from the information related the NTN cell.

[0119] Example 34. The method of example 12, further comprising: initiating the searching for the NTN cell in response to determining that the information related to the NTN cell includes the satellite information.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0120] Example 35. The method of any of examples 1-25, further comprising: initiating the searching for the NTN cell in response to determining that the UE is allowed to access an NTN to which the NTN cell belongs.

[0121] Example 36. The method of any of the preceding examples, wherein: the UE is a Bandwidth reduced Low complexity (BL) UE.

[0122] Example 37. The method of any of examples 1-35, wherein: the UE is a Coverage Enhancement (CE) UE.

[0123] Example 38. The method of any of examples 1-35, wherein: the UE is an NB-IoT UE.

[0124] Example 39. A configuration method implemented in a radio access network (RAN), the method comprising: transmitting, in a non-Internet-of-Things (non-IoT) cell, initial access information for accessing the non-IOT cell; and transmitting, in the non-IoT cell, information related to an loT non-terrestrial network (NTN) cell.

[0125] Example 40. The method of example 39, wherein the loT NTN cell operates using a low-power wide area network (LPWA) technology.

[0126] Example 41. The method of example 39 or 40, wherein: the non-IOT cell is a terrestrial network (TN) cell.

[0127] Example 42. The method of example 39 or 40, wherein: the non-IOT cell is a non-NB cell.

[0128] Example 43. The method of any of examples 39-42, wherein: the non-IOT cell is associated with a first Public Land Mobile Network (PLMN), and the loT NTN cell is associated with a second PLMN.

[0129] Example 44. The method of any of examples 39-42, wherein: the non-IOT cell and the loT cell are associated with a same PLMN.

[0130] Example 45. The method of any of examples 39-44, wherein: the transmitting of the initial access information includes transmitting the initial access information using an Evolved Universal Terrestrial Radio Access (EUTRA) protocol stack.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00

[0131] Example 46. The method of any of examples 39-45, wherein: the transmitting of the information related to the loT non-terrestrial network includes transmitting one of: a system information block (SIB) of type 32 (SIB32), a SIB of type 32 for narrowband (SIB32-NB), a SIB of type 33 (SIB33), or a SIB of type 33 for narrowband (SIB33-NB).

[0132] Example 47. The method of any examples 39-46, wherein: the information related to the loT NTN cell includes satellite information for the loT NTN cell.

[0133] Example 48. The method of example 47, wherein the satellite information includes one or more of: (i) a satellite identifier (ID) identifying a satellite with which the NTN cell is associated, (ii) ephemeris information for the satellite, (iii) one or more timing advance parameters, (iv) an epoch time, (v) a service start time for the NTN cell, (vi) a scheduling offset, (vii) an indication of a frequency band of the NTN cell, or (viii) a physical cell identifier (PCI) of the NTN cell.

[0134] Example 49. The method of example 47 or 48, wherein: the satellite information for the NTN cell identifies multiple candidate satellites.

[0135] Example 50. The method of any examples 39-46, further comprising: transmitting, in the non-loT cell, PLMN access configuration related to the loT NTN cell.

[0136] Example 51. The method of example 50, wherein: the PLMN access configuration specifies, for a TN PLMN, one or more NTN PLMNs in which the UE is allowed to register.

[0137] Example 52. The method of example 51, wherein: the PLMN access configuration further specifies, for the TN PLMN, one or more satellite identifiers.

[0138] Example 53. The method of any of example 49, wherein: the PLMN access configuration specifies, for each of one or more PLMNs, at least one of: (i) a radio access technology type (RAT), (ii) a frequency band, or (iii) a frequency range.

[0139] Example 54. A communication device comprising: a transceiver; and processing hardware configured to implement a method of any of the preceding examples.

[0140] 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, ifPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 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, “satellite information” can be replaced by “satellite assistance information”. In some implementations, “satellite” can be replaced by “NTN” or “NTN cell” or vice versa.

[0141] 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 broadband router. 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 intemet-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.

[0142] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may 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 comprise dedicated circuitry or logic that is permanently configured e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software toPATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00 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.

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

Claims

PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-00CLAIMS:

1. A method for accessing a non-terrestrial network (NTN), the method implemented in a user equipment (UE) and comprising: receiving, in a terrestrial network (TN) cell, information related to non-terrestrial network (NTN) cell that operates using a low-power wide area network (LPWA) technology; searching for the NTN cell using the information; and selecting the NTN cell for registration.

2. The method of claim 1, wherein: the TN cell is associated with a first Public Land Mobile Network (PLMN), and the NTN cell is associated with a second PLMN.

3. The method of claim 1, wherein: the TN cell and the NTN cell are associated with a same PLMN.

4. The method of any of the preceding claims, wherein: the LPWA technology is Narrowband Internet-of-Things (NB-IoT).

5. The method of any of the preceding claims, wherein the TN cell operates using an Evolved Universal Terrestrial Radio Access (EUTRA) protocol stack.

6. The method of claim 5, wherein: the receiving of the information related to the NTN cell includes receiving a SIB of type 33 (SIB33).

7. The method of any of the preceding claims, wherein: the information related to the NTN cell includes satellite assistance information for the NTN cell.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-008. The method of claim 8, wherein the satellite assistance information includes one or more of:(i) a satellite identifier (ID) identifying a satellite with which the NTN cell is associated,(ii) ephemeris information for the satellite,(iii) one or more timing advance parameters,(iv) an epoch time,(v) a service start time for the NTN cell,(vi) a scheduling offset,(vii) an indication of a frequency band of the NTN cell, or(viii) a physical cell identifier (PCI) of the NTN cell.

9. The method of claim 7 or 8, wherein: the satellite information for the NTN cell identifies multiple candidate satellites.

10. The method of any of the preceding claims, further comprising: receiving a PLMN access configuration related to the NTN cell, wherein the PLMN access configuration specifies, for each of one or more PLMNs, at least one of:(i) a radio access technology type (RAT),(ii) a frequency band, or(iii) a frequency range.

11. The method of any of the preceding claims, further comprising: initiating the searching for the NTN cell in response to determining that the UE is out of coverage of the TN cell.

12. The method of claim 11, further comprising: initiating the searching for the NTN cell further in response to determining that an NTN to which the NTN cell belongs is associated with a certain PLMN.PATENT APPLICATIONAttorney Docket No.: 31730 / 308421-0013. A configuration method implemented in a radio access network (RAN), the method comprising: transmitting, in a non-Intemet-of-Things (non-IoT) cell, initial access information for accessing the non-IOT cell; and transmitting, in the non-IoT cell, information related to an loT non-terrestrial network (NTN) cell.

14. The method of claim 13, further comprising: transmitting, in the non-IoT cell, PLMN access configuration related to the loT NTN cell15. An apparatus comprising: a transceiver; and processing hardware configured to implement a method of any of the preceding claims.

Images