Managing satellite communication with multiple radio access technologies
The described methods for cell selection and reselection in UE and RAN nodes address latency and mobility challenges in 5G satellite communication by optimizing NTN RAT information transmission and reception, improving connectivity across terrestrial and non-terrestrial networks.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- GOOGLE LLC
- Filing Date
- 2025-11-01
- Publication Date
- 2026-05-07
AI Technical Summary
Existing 5G technologies face challenges in managing satellite communication with multiple radio access technologies (RATs) due to increased latency in acquiring system information blocks and unclear methods for seamless mobility and satellite assistance information transmission/reception, especially in non-terrestrial networks (NTNs).
Implementing methods in user equipment (UE) and radio access network (RAN) nodes for efficient cell selection and reselection, including receiving and transmitting NTN carrier frequency and satellite information in system information blocks, and providing initial access and satellite assistance information to support multiple RATs in TNs and NTNs.
Facilitates reduced latency and seamless mobility between different NTN RATs by optimizing the acquisition of system information and satellite assistance, enhancing connectivity in mixed terrestrial and non-terrestrial networks.
Smart Images

Figure US2025053671_07052026_PF_FP_ABST
Abstract
Description
PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00MANAGING SATELLITE COMMUNICATION WITH MULTIPLE RADIO ACCESS TECHNOLOGIESCROSS-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 / 715,500, entitled “Managing Satellite Communication with Multiple Radio Access Technologies,” filed on November 1, 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 satellite communication with multiple radio access technologies.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 third 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 / 308455-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 / 308455-00
[0009] 3GPP has specified NR NTN, NB-IoT NTN, and eMTC NTN. To access an NR NTN cell, the UE has to acquire a system information block (SIB) 19 (SIB 19) in addition to a master information block (MIB) and a SIB1 from the NT NTN cell, as specified in 3GPP specification38.331. The acquisition of SIB19 increases additional latency to accessing an NR NTN. To access an NB-IoT NTN cell, the UE has to acquire a MIB, a SystemlnformationBlockTypel-NB, a SystemInformationBlockType2-NB, and SystemInformationBlockType31-NB from the NB- loT NTN cell, as specified in 3GPP specification 36.331. To access an eMTC NTN cell, the UE has to acquire a MIB, a SystemlnformationBlockTypel, a SystemInformationBlockType2, and SystemhrformationBlockType31 from the eMTC NTN cell, as specified in 3GPP specification36.331. The acquisition of SystemInformationBlockType31-NB or SystemInformationBlockType31 increases additional latency to accessing a NB-IoT NTN or an eMTC NTN. Such additional latency should be eliminated in the 6G NTN design.
[0010] Additionally, a provider may operate terrestrial networks (TNs) and NTNs with different radio access technologies (RATs) to provide different services to different types of UEs. For example, a TN operator may operate an Evolved Universal Terrestrial Radio Access (E-UTRA) TN and operate an NR NTN. and a 6G NTN via the same satellite or different satellites owned by the TN operator and / or satellite operator(s). In another example, a TN operator may operate a 6G TN, and operate an NR NTN, an eMTC NTN, and / or an NB-IoT NTN via the same satellite or different satellites owned by the TN operator and / or satellite operator(s). To achieve ubiquitous connectivity, a UE can support multiple radio access technologies (RATs) for communication with TNs and NTNs. However, it is not clear how the RAN should transmit, and the UE should receive, satellite assistance information for different RATs of NTNs in a TN and an NTN. It is also not clear how UEs and / or RAN nodes should support seamless switches or mobility from an NTN of a first RAT to an NTN of a second RAT.SUMMARY
[0011] An example embodiment of the techniques of this disclosure is a method for cell selection or reselection implemented in a user equipment (UE). The method comprises receiving, in a serving cell and in a first system information block (SIB), non-terrestrial (NTN) carrier frequency information for an NTN radio access technology (RAT); receiving, in thePATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 serving cell and in a second SIB, satellite information for the NTN RAT; and selecting an NTN cell associated with the NTN RAT.
[0012] Another example embodiment of these techniques is a method implemented in a node of a radio access network (RAN). The method comprises transmitting, in a first system information block (SIB), NTN carrier frequency information for an NTN RAT; and transmitting, in a second SIB, satellite information for the NTN RAT.
[0013] Another example embodiment of these techniques is a method for cell selection or reselection. The method is implemented in a UE and comprises selecting or reselecting an NTN cell; and receiving, in the NTN cell, a system information message including (i) initial access information for the NTN cell and (ii) serving satellite information.
[0014] Another example embodiment of these techniques is a method for cell selection or reselection, implemented in a UE and comprising: receiving, in a serving cell, first neighboring satellite information related to a first NTN RAT; receiving, in the serving cell, second neighboring satellite information related to a second NTN RAT; and selecting an NTN cell using the first neighboring satellite information or the second neighboring satellite information.
[0015] Another example embodiment of these techniques is a method implemented in a node of a RAN, the method comprising: transmitting, in an NTN cell, a system information message including (i) initial access information for the NTN cell and (ii) serving satellite information; and receiving, from a UE, a request to access the NTN cell, the request based on the system information message.
[0016] Yet another example embodiment of these techniques is a method implemented in a node of a radio access network (RAN), the method comprising: transmitting, in a serving cell, first satellite information related to a first non-terrestrial network (NTN) radio access technology (RAT); and transmitting, in the serving cell, second satellite information related to a second NTN RAT.
[0017] Still another example embodiment of these techniques is a device comprising a transceiver and processing hardware. The device is configured to implement a method of any of the preceding claims.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figs. 1A and IB are block diagrams of example wireless communication systems in which a user device and a base station of this disclosure can implement the techniques of this disclosure;
[0019] Fig. 2A is a block diagram of an example protocol stack according to which the UE of Fig. 1A communicates with base stations;
[0020] Fig. 2B is a block diagram of an example protocol stack according to which the UE of Figs. 1A and IB communicates with base stations;
[0021] 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.
[0022] 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.
[0023] Fig. 4A illustrates example PLMN access information which a UE can use to search for an NTN cell;
[0024] Fig. 4B illustrates example PLMN access information which a UE can use to determine the relationship between a TN PLMN and an NTN PLMN;
[0025] Fig. 5 is a messaging diagram of an example scenario in which the UE initially selects a TN cell and then an NTN cell, and receives initial access information for the serving cell and satellite assistance information for two NTNs supporting different respective RATs;
[0026] Fig. 6 is a messaging diagram of an example scenario generally similar to that of Fig.5, but in which the UE initially selects an NTN cell and then a TN cell;
[0027] Fig. 7 is a messaging diagram of an example scenario generally similar to that of Fig.6, but in which the UE selects another NTN cell of a different RAT after initially selecting a first NTN cell;PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0028] Fig. 8 is a flow diagram of an example method according to which a RAN broadcasts serving satellite information and neighboring satellite information in an NTN cell and communicates with the UE via an NTN cell;
[0029] Fig. 9A is a flow diagram of an example method according to which a RAN broadcasts satellite assistance information for two NTNs supporting different respective RATs and initial access information for a TN in the TN cell and communicates with the UE via the TN cell;
[0030]
[0031] Fig. 9B is a flow diagram of an example method generally similar to that of Fig. 9A, except that the RAN broadcasts common satellite information, and broadcasts the satellite information for both NTNs in the same message;
[0032] Fig. 9C is a flow diagram of an example method generally similar to that of Fig. 9B, except that the RAN broadcasts the common satellite information and the satellite information for both NTNs in the same message;
[0033] Fig. 10A is a flow diagram of an example method generally similar to that of Fig. 9A, except that the RAN broadcasts the information in an NTN cell, and the initial access information is for accessing the NTN cell;
[0034] Fig. 10B is a flow diagram of an example method generally similar to that of Fig. 9B, except that the RAN broadcasts the information in an NTN cell, and the initial access information is for accessing the NTN cell;
[0035] Fig. 10C is a flow diagram of an example method generally similar to that of Fig. 10B, except that the RAN broadcasts the common satellite information and the satellite information for both NTNs in the same message;
[0036] Fig. 11 A is a flow diagram of an example method generally similar to that of Fig. 9A, except that the UE communicates with the RAN in a TN cell before selecting an NTN cell;
[0037] Fig. 1 IB is a flow diagram of an example generally similar to that of Fig. 9B. except that the UE communicates with the RAN in a TN cell before selecting an NTN cell;PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0038] Fig. 11C is a flow diagram of an example generally similar to that of Fig. 9B, except that the UE receives the messages from the RAN and communicates with the TN cell before selecting an NTN cell;
[0039] Fig. 12A is a flow diagram of an example method generally similar to that of Fig. IDA, except that the UE communicates with the RAN in an NTN cell before selecting a cell;
[0040] Fig. 12B is a flow diagram of an example generally similar to that of Fig. 10B, except that the UE communicates with the RAN in an NTN cell before selecting a cell;
[0041] Fig. 11C is a flow diagram of an example generally similar to that of Fig. 9B, except that the UE receives the messages from the RAN and communicates with the RAN in an NTN cell before selecting a cell; and
[0042] Fig. 13 is a flow diagram of an example method generally similar to that of Fig. 8, except that the UE communicates with the RAN in an NTN cell.DETAILED DESCRIPTION OF THE DRAWINGS
[0043] Referring first to Fig. 1A, a wireless communication system 100A includes a UE 102, a base station (BS) 104. a base station 106, a base station 103, a radio access network (RAN) 105A, a terrestrial network (TN) RAN 105B, a core network (CN) 110A, and a CN 110B. The RAN 105A includes a base station 104 and may include one or more additional base station(s). The CN 110A 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 110B may be an EPC, 5GC, or 6GC, for example. The RAN 105B includes a base station 106 and may include one or more additional base station(s). The RAN 105A and the CN 110A belong to a Public Land Mobile Network (PLMN) 108, while the TN RAN 105B and the CN 110B belong to a PLMN 107. The base station 104 and / or the additional base station(s) in the RAN 105 A communicates with UEs via one or more satellites (as suggested by the satellite icon), the PLMN 108 thus being a nonterrestrial network (NTN). The base station 106 and / or the additional base station(s) in the RAN 105B communicates with UEs using terrestrial equipment (as suggested by the tower icon) without employing satellites, the PLMN 107 being a terrestrial network (TN).PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0044] In some implementations, the base station 103 connects to the CN 110A (not shown in Fig. 1A). In such cases, the RAN 105A may include the base station 103. Alternatively, the base station 103 belongs to a first RAN different from the RAN 105 A and connecting to the CN 110 A. In some implementations, the first RAN and the RAN 105 A utilize different RATs. In other implementations, the first RAN and the RAN 105 A utilizes the same RAT. In other implementations, the base station 103 connects to the CN HOB (not shown in Fig. 1A). In such cases, the RAN 105B may include the base station 103. Alternatively, the base station 103 belongs to a second RAN different from the RAN 105B and connecting to the CN 110B. In such cases, the PLMN 107 includes a TN and an NTN. In yet other implementations, the base station 103 connects to another CN, not shown in Fig. 1A. In such cases, the base station 103 belongs to a third RAN connecting to the other CN. The third RAN and the other CN may belong to a PLMN that is neither the PLMN 107 nor the PLMN 108.
[0045] The base station 104 covers an NTN cell 124, the base station 106 covers a TN cell 126, and the base station 103 covers an NTN cell 123. If the base station 104 is a gNB, the NTN cell 124 is an NR NTN cell. If the base station 104 is an ng-eNB or eNB, the NTN cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) NTN cell or a NB-IoT NTN cell. If the base station 104 is a 6G base station, the NTN cell 124 is a 6G NTN cell or a 6G loT NTN cell. Similarly, the cell 123 is an NR NTN cell, an E-UTRA or NB-IoT NTN cell, a 6G NTN or 6G loT NTN cell, depending on the base station is a gNB, an ng-eNB or eNB, or a 6G base station, respectively. Similarly, the cell 126 is an NR TN cell, an E-UTRA or NB-IoT TN cell, a 6G TN or 6G loT TN cell, depending on the base station is a gNB, an ng-eNB or eNB, or a 6G base station, respectively. In general, each of the RANs described above 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. 5G NR (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 A can connect to the CN 110A via an interface (e.g., SI, NG, or N6G interface). The base station 104 and the additional base station(s) in the RAN 105A 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 additionalPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 base station(s) in the RAN 105B can connect to the CN HOB via an interface (e.g., SI, NG, or N6G interface). The base station 106 and the additional base station(s) in the RAN 105B also can be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting RAN nodes. Each of the base station 103 and additional base station(s) in the third RAN can connect to the corresponding CN via an interface (e.g., SI, NG, or N6G interface). The base station 103 and the additional base station(s) in the third RAN also can be interconnected via an interface (e.g., X2, Xn, or X6G interface) for interconnecting RAN nodes.
[0046] 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.The SGW 112 in general is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 1 14 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. 1A. 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. 1A. 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 110B has similar components as the CN 110 A.
[0047] As illustrated in Fig. 1A, the base station 104 supports a cell 124, the base station 106 supports a cell 126, the base station 103 supports a cell 123. Note that cell 124 or 123 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, 126 and / or 123 partially overlap, so that the UE 102 can select, reselect, or hand over from one of the cells 124, 126, and / or 123 to another of the cells 124, 126, and / or 123. The base stations 104, 106, 103 may exchange messages via the CNsPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00I IOA.110B, etc., the interfaces between the base stations 104, 106, 103 and the CNs 110A,I IOB, etc, and one or more interfaces among the CNs 110A, 110B, etc. Alternatively, the base stations 104, 106, 103 may support an X2, Xn, X6G interface to directly exchange messages. In general, the CNs 110A, 110B, etc. can connect to any suitable number of base stations supporting NR cells and / or EUTRA cells.
[0048] 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 hardware 130 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 processing hardware 140 further includes an NTN controller 148 configured to control UEs to search and access an NTN.
[0049] 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 processing 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,PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 session management functions, and / or radio resource control functions. The processing hardware 150 further includes an NTN controller 158 configured to determine whether to search and access an NTN.
[0050] Fig. IB is similar to Fig. 1A except that the base station 106 connects to the CN 110A. The description for Fig. 1A can apply to Fig. IB. The base stations 104, 106 may exchange messages via the SI, NG or N6G interfaces between the base stations 104, 106 and the CN 110A. Alternatively, the base stations 104, 106 may exchange messages directly via the X2, Xn, or X6G interfaces between the base stations 104 and 106. In the case where the base station 103 connects to the CN 110A, the base station 103 may exchange messages with the base stations 104, 106 via the SI, NG or N6G interfaces between the base stations 103, 106, 104 and the CN 110A. Alternatively, the base station 3 may exchange messages directly with the base stations 104, 106 via the X2, Xn, or X6G interfaces between the base station 103 and the base stations 104 and 106.
[0051] Fig. 2 A illustrates, in a simplified manner, an example protocol stack 200 A 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).
[0052] 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 otherPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 implementations, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are NR layers or sublayers.
[0053] 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.
[0054] 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.
[0055] Fig. 2B illustrates an example protocol stack 200B similar to the protocol stack 200A, except that the NAS layer 212 is not transparent to the base station (gNB / eNB 104 / 106). When the base station (gNB or eNB 104 / 106) receives a UL NAS PDU from the UE 102, the base station may process the UL NAS PDU and transmits a DL NAS PDU to the UE 102 in response. When the base station receives DL NAS PDUs from the CN 110, the base station may forward the DL NAS PDUs to the UE 102 without processing the DL NAS PDUs. In other words, the base station may be equipped with a portion of functions of the NAS layer 212 (e.g., a portion of NAS procedures initiated by the UE or processing UL PDUs).
[0056] Fig. 3A illustrates a certain type of NTN deployment 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 aPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 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.
[0057] 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) filtering, 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 location of the CN 110, or be connected to the CN 110 at a distance via a wired link or a wireless link.
[0058] Fig. 4A illustrates example PLMN access information 400A. 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 the frequency band for a TN, the UE determines the PLMN is associated with a TN. For example, the first row 492A shows that PLMN ID1 uses frequency band “455”, which is defined for satellite access in a 3GPPPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 specification. The seventh row 492G shows the PLMN ID4 is associated with an NTN because the frequency band “456” is defined for satellite access in a 3GPP specification.
[0059] Currently, 3GPP specifications indicate that frequency bands “253”, “254”, “255” and “256” are for satellite access, but in general 3GPP may define additional frequency bands for satellite access. However, 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 492B shows a PLMN ID2 using satellite E-UTRA access in frequency band 25. In situations where a UE relies on the frequency band number to determine whether a PLMN is associated with an NTN or a TN, the use of frequency bands may be limited, or the UE may be unable to distinguish NTN or TNs. For example, according to the second row 492B, PLMN ID2 operates a satellite E-UTRAN NTN in frequency band “25.” A UE may consider PLMN ID2 to be associated with a TN because frequency band “25” was not previously defined for satellite access.
[0060] In some implementations, the PLMN access information 400A explicitly indicates the RAT type. For example, the UE can determine that the PLMN ID1 is associated with an NTN because the first row 492 A 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 492D 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 492C indicates the “satellite” E-UTRA type. In yet another example, the UE determines a PLMN identified by the PLMN ID4 (seventh row 492G) 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 400A 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 of the row 492B and the row 492C.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0061] 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 UE can use the MCC 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 the PLMN access information 400A. However, a potential shortcoming is that the particular MCC ("901") can become overused, particularly as more NTNs are deployed. Moreover, 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 400A to distinguish NTN or TN so that the PLMN ID can use MCCs other than a general MCC for satellite access.
[0062] In some implementations, when the UE determines to search a PLMN identified by a PLMN ID, the UE determines which RAT and earner 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 492A, 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 492B, 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 492C, 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 400A 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.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00Further, 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 UE frequency range and a DE 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 UE 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.
[0063] Fig. 4B shows example TN and NTN association information 400B indicating association information between or among the TN PEMNs, NTN PEMNs, and / or satellites. In some implementations, a UE (e.g., the UE 102) can determine the association between TNs and NTNs based on the TN and NTN association information. For example, the first row 493 A shows that an 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 for an NTN cell of the NTN based on the first row 493A. In some implementations, based on the second row 492B in the PLMN access information 400A, 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 in 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. In some implementations, the TN and NTN information may include NTN and satellite information that indicates 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, the first row 493 A 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 the Satellite ID1. In some implementations, the UE receives satellitePATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 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) the 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 the 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 IDE In some implementations, if the TN is a home PLMN of the UE, the UE may determine to search, or searches, 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.
[0064] In another example, the first row 493A shows that a TN identified by the PLMN ID3 is associated with an NTN identified by the PLMN ID2. In some implementations, when or after the UE has registered with the NTN PLMN identified by the PLMN ID2, the UE may determine to search or search a TN cell of the TN identified by the PLMN ID3 based on the first row 493A. In some implementations, based on the fourth row 492D in the PLMN access information 400A, the UE may further determine to search or search 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 in 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 some implementations, if the NTN is a home PLMN of the UE, the UE may determine to search or search 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 implementations, if the UE detects a Universal Subscriber Identity Module (USIM) of the TN, the UE may determine to search or search the TN as described above. Otherwise, if the UE does not detect a USIM of the TN, the UE may refrain from searching the TN.
[0065] In some implementations, multiple NTNs are associated with a TN. For example, the second row 493B indicates that a first NTN identified by the PLMN ID1 is associated with a TN identified by the PLMN ID5, and the third row 493C indicates that a second NTN identified by the PLMN ID4 is associated with the TN. In some implementations, the first NTN is associatedPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 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 may determine to search or search an NTN cell of the first NTN and / or an NTN cell of the second NTN based on the second row 493B and / or the third row 493C as described above.
[0066] 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. 3 A or located with the satellite 304 as described for Fig. 3B. Generally speaking, events in Figs. 5-13 that are similar are labeled with similar reference numbers (e.g., event 516 of Fig. 5 is similar to event 816 of Fig 8, block 1016 of Figs. 10A-10C, blocks 1216 of Figs. 12A-12C, and block 1316 of Fig. 13), 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.
[0067] Fig. 5 illustrates an example scenario 500, where the scenario 500 includes a TN cell 126, an NTN cell 124 of a first RAT (i.e., first RAT NTN cell 124) and may additionally include an NTN cell 123 of a second RAT (i.e., second RAT NTN cell 123). In some implementations, a base station 106, a base station 104, and a base station 103 operate the TN cell 126, the first RAT NTN cell 124, and the second RAT NTN cell 123, respectively. In some implementations, the TN cell 126 is a non-IoT cell which is an E-UTRA, NR or 6G cell. In other implementations, the TN cell 126 is an loT cell such as an eMTC cell or an NB-IoT cell. In yet other implementations, the TN cell 126 is a third RAT cell. The third RAT is one of the E-UTRA, NR, or 6G and different from the first RAT and second RAT. In some implementations, one of the first RAT and the second RAT is NB-IoT and the other is E-UTRA, NR or 6G. In other implementations, one of the first RAT and the second RAT is eMTC and the other is E-UTRA, NR or 6G. In yet other implementations, one of the first RAT and the second RAT is NR and the other is 6G. In yet other implementations, one of the first RAT and the second RAT is E-UTRA and the other is NR or 6G. In some implementations, the TN cell 126 is a non-IoT cell. In otherPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 implementations, the TN cell 126 serves non-IoT UEs. In some implementations, the TN cell 126 does not serve NB-IoT UEs. In other implementations, the TN cell 126 does not serve eMTC UEs (i.e., bandwidth reduction UEs).
[0068] The UE 102 initially operates in coverage of the TN cell 126 and selects 501 or reselects 501 the TN cell 126. In some implementations, the UE 102 selects or reselects 501 the TN cell 126 similar to event 601 of Fig. 6. Examples and implementations described with respect to event 601 can apply to event 501. In other implementations, the UE 102 performs a TN cell search, discovers the TN cell 126 in the TN cell search, and then selects or reselects 501 the TN cell 126, when powered on, powered cycle, or a USIM inserted. In one implementation of the TN cell search, the UE 102 search a TN cell based on a pre-configured information (e.g.. 400A and / or 400B). In another implementation of the TN cell search, the UE 102 searches for a TN cell based on a TN carrier frequency IE. The TN carrier frequency IE indicates a TN carrier frequency and / or a TN frequency band of a TN cell (e.g., the TN cell 126 or another TN cell) that the UE 102 camps on, and the UE 102 stores the TN carrier frequency IE on a non-transitory computer- readable medium or the USIM.
[0069] When or after selecting ore reselecting the TN cell 126, the UE 102 receives 502 first system information including initial access information from the TN cell 126. 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 first system information block (SIB). For example, if the TN cell 126 is an NR cell, the at least one first 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 SystemlnformationBlockTypel and / or a SystemlnformationBlockType2 as defined in 3GPP specification 36.331. In yet another example, if the TN cell is a 6G cell, the at least one first SIB includes a SIB (e.g., SIB1) for 6G.
[0070] After event 501 or 502, the UE 102 may receive 504 second system information including a first NTN carrier frequency information element (IE) of the first RAT from the TNPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 cell 126. The first NTN carrier frequency IE indicates a first carrier frequency and / or a first frequency band for one or more NTN cells of the first RAT. The first carrier frequency belongs to the first frequency band. The second system information may include a second NTN carrier frequency IE of the first RAT that indicates a second carrier frequency and / or a second frequency band for one or more NTN cells of the first RAT. The second carrier frequency belongs to the first or second frequency band.
[0071] After event 501 or 502, the UE 102 may receive 506 third system information including a third NTN carrier frequency IE of the second RAT from the TN cell 126. The third NTN carrier frequency IE indicates a third carrier frequency and / or a third frequency band for one or more NTN cells of the second RAT. The third carrier frequency belongs to the third frequency band. The third system information may include a fourth NTN carrier frequency IE of the second RAT that indicates a fourth carrier frequency and / or a fourth frequency band for one or more NTN cells of the second RAT. The fourth carrier frequency belongs to the third or fourth frequency band.
[0072] In some implementations, the second system information is a second SIB, and the third system information is a third SIB. In some implementations, the base station 106 may transmit the second system information and third system information in a single transmission (e.g., a single system information message) on the TN cell 126 (i.e., events 504 and 506 can combined as a single event). In other implementations, the base station 106 may transmit the second system information and the third system information in separate transmissions (e.g., separate system information messages) on the TN cell 126 (i.e., events 504 and 506 can combined as a single event). In yet other implementations, the first RAT carrier frequency information and the second RAT carrier frequency information can be included in a single SIB transmitted by the base station 106 on the TN cell 126 (i.e., events 504 and 506 can combined as a single event).
[0073] After event 501 or 502, the UE 102 may receive 508 fourth system information including first satellite information for the first RAT from the TN cell 126. In some implementations, the first system information includes scheduling information for the third system information and the UE 102 receives 508 the fourth system information accordance with the scheduling information. In some alternative implementations, the UE 102 is preconfiguredPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 with the first satellite information before event 501. instead of event 508. The first satellite information may include parameters for one or more satellites or NTN cells. In some implementations, the first satellite information may include one or more satellite information elements (IES) each for a corresponding satellite. Each satellite IE may include a satellite ID identifying the corresponding satellite or satellite IE, ephemeris information, network-controlled common timing advance (TA) parameters, an 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 some implementations, the area is covered by or close to the TN cell 126. In other implementations, the area is not covered by the TN cell 126. In some implementations, the satellite IE includes an area conf iguration configuring the area to be covered by the corresponding satellite based on the service start time. In some implementations, each NTN carrier frequency IE of the first RAT in event 504 may include a satellite ID to associate the corresponding satellite IE with the corresponding NTN carrier frequency IE. For example, the first satellite information includes a first satellite IE for a first satellite (e.g., satellite 304) and the first satellite IE includes a first satellite ID, first ephemeris information, first network-controlled common TA parameters, a first epoch time, a first service start time, and / or a first scheduling offset. The second system information or the first NTN carrier frequency IE includes the first satellite ID to indicate that the first NTN carrier frequency IE is associated with the first satellite IE. Based on the first satellite ID indicating the association, the UE 102 identifies that the first satellite IE is associated with the first NTN carrier frequency IE. In some implementations, the UE 102 determines to search for an NTN cell on the first carrier frequency within the first frequency band using the first satellite IE. The first satellite information may additionally include a second satellite IE for a second satellite and the second satellite IE includes a second satellite ID, second ephemeris information, second network-controlled common TA parameters, a second epoch time, a second service start time, a second area configuration, and / or a second scheduling offset. In some implementations, the second system information or the first NTN carrier frequency IE may include the second satellite ID to indicate that the first NTN carrier frequency IE is associated with the second satellite IE. Based on the second satellite ID indicating the association, the UE 102 identifies that the secondPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 satellite IE is associated with the first NTN carrier frequency IE. In some implementations, the UE 102 determines to search (or searches) for an NTN cell on the first carrier frequency within the first frequency band using the second satellite IE. In some other implementations, the second system information or the second NTN carrier frequency IE may include the second satellite ID to indicate that the second NTN carrier frequency IE is associated with the second satellite IE. Based on the second satellite ID indicating the association, the UE 102 identifies that the second satellite IE is associated with the second NTN carrier frequency IE. In some implementations, the UE 102 determines to search for an NTN cell on the second carrier frequency within the second frequency band using the second satellite IE.
[0074] In other implementations, the first satellite information may include one or more NTN cell IES each for a corresponding NTN cell. In some implementations, each NTN cell IE includes parameters such as 1) a satellite ID identifying a corresponding satellite, 2) ephemeris information, 3) network-controlled common TA parameters, 4) an epoch time, a service start time, 5) an area configuration, 6) a scheduling offset, 7) a frequency band number indicating a frequency band, 8) frequency information indicating a carrier frequency, and / or 9) a physical cell identity (PCI), similar to the satellite IE described above. A frequency band, a carrier frequency and / or a PCI in an NTN cell IE indicates an NTN cell. In such cases, an NTN cell IE may or may not include a satellite ID. For example, the first satellite information includes a first NTN cell IE and the first NTN cell IE includes first ephemeris information, first network-controlled common TA parameters, a first epoch time, a first service start time, a first area configuration, a first scheduling offset, a first frequency band number indicating the first frequency band, first frequency information indicating the first carrier frequency, and / or a first PCI. In some implementations, the first PCI identifies the NTN cell 124. The UE 102 may determine to search or search an NTN cell (e.g.. the NTN cell 124) on the first carrier frequency within the first frequency band, using the one or more parameters in the first NTN cell IE. The first satellite information may additionally include a second NTN cell IE and the second NTN cell IE includes second ephemeris information, second network-controlled common TA parameters, a second epoch time, a second service start time, a second area configuration, a second scheduling offset, a second frequency band number indicating the second frequency band, second frequencyPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 information indicating the second carrier frequency, and / or a second PCI. In some implementations, the second PCI identifies another first RAT NTN cell. The UE 102 may determine to search or search an NTN cell (e.g., identified by the second PCI) on the second carrier frequency within the second frequency band, using the one or more parameters in the second NTN cell IE.
[0075] In some implementations, the first NTN carrier frequency IE is associated with a first measurement timing configuration configuring a first measurement window for searching one or more reference signals (RS(s)) of one or more NTN cells of the first RAT. In some implementations, the RS(s) can be one or more synchronization signal (SS) / physical broadcast channel (PBCH) blocks. The UE 102 may search an NTN cell on the first earner frequency within the first frequency band within the first measurement window. In some implementations, the UE 102 may adjust the first measurement window based on the ephemeris information in the first satellite IE or the first NTN cell IE. In other implementations, the first NTN carrier frequency IE is not associated with a measurement timing configuration. In some implementations, the second NTN carrier frequency IE is associated with the first measurement timing configuration. The UE 102 may search an NTN cell on the second carrier frequency within the second frequency band within the first measurement window. In other implementations, the second NTN earner frequency IE is associated with a second measurement timing configuration configuring a second measurement window for searching one or more reference signals (RS(s)) of one or more NTN cells of the first RAT. The UE 102 may search an NTN cell on the second carrier frequency within the second frequency band within the second measurement window. In some implementations, the UE 102 may adjust the second measurement window based on the ephemeris information in the first satellite IE or the first NTN cell IE. In other implementations, the second NTN carrier frequency IE is not associated with a measurement timing configuration.
[0076] In some implementations, the fourth system information includes at least one fourth SIB (SIB(s)). For example, if the TN cell 126 is an NR cell, the SIB is a SIB 19 (SIB 19) or a new, dedicated SIB defined in a relevant specification (such as 3GPP TS 38.331) specifically to support the scenarios of this disclosure. In another example, if the TN cell 126 is an E-UTRAPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 cell, the fourth SIB(s) includes a SystemInformationBlockType32 (rather than a System.lnformationBlockType33-NB) and / or a SystemInformationBlockType33 (rather than a SystemlnformationBlockType33-NB or a new, dedicated SIB, defined in a relevant specification (such as 3GPP TS 36.331) specifically to support the scenarios of this disclosure. Alternatively, the fourth SIB(s) includes a SystemBiformationBlockType32-NB and / or a SystemlnformationBlockType33-NB, or a new, dedicated SIB defined in relevant specification (such as 3GPP TS 36.331) specifically to support the scenarios of this disclosure. In yet another implementation, if the TN cell 126 is a 6G cell, the fourth SIB includes a SIB defined for 6G.
[0077] After event 501 or 502, the UE 102 may receive 510 fifth system information including second satellite information for the second RAT from the TN cell 126. In some implementations, the first system information includes scheduling information for the fifth system information and the UE 102 receives 510 the fifth system information accordance with the scheduling information. Alternatively, the UE 102 is preconfigured with the second satellite information before event 501. The second satellite information may include parameters for one or more satellites or NTN cells. In some implementations, the second satellite information may include one or more satellite information elements (IES) each for a corresponding satellite, as described for the first satellite information. For example, the second satellite information includes a third satellite IE for a third satellite (e.g., satellite 306) and the third satellite IE includes a third satellite ID, third ephemeris information, third network-controlled common TA parameters, a third epoch time, a third area configuration, a third service start time, and / or a third scheduling offset. The third system information or third NTN carrier frequency IE includes the third satellite ID to indicate that the third NTN carrier frequency IE is associated with the third satellite IE. Based on the third satellite ID indicating the association, the UE 102 identifies that the third satellite IE is associated with the third NTN carrier frequency IE. In some implementations, the UE 102 determines to search (or searches) for an NTN cell on the third carrier frequency within the third frequency band using the third satellite IE. In other implementations, the UE 102 determines not or refrains from searching an NTN cell on the third carrier frequency within the third frequency band. The second satellite information may additionally include a fourth satellite IE for a fourth satellite and the fourth satellite IE includes aPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 fourth satellite ID, fourth ephemeris information, fourth network-controlled common TA parameters, a fourth epoch time, a fourth service start time, a fourth area configuration, and / or a fourth scheduling offset. In some implementations, the third NTN carrier frequency IE may include the fourth satellite ID to indicate that the third NTN carrier frequency IE is associated with the fourth satellite IE. Based on the fourth satellite ID indicating the association, the UE 102 identifies that the fourth satellite IE is associated with the third NTN carrier frequency IE. In some implementations, the UE 102 determines to search (or searches) for an NTN cell on the third carrier frequency within the third frequency band using the fourth satellite IE. In other implementations, the UE 102 determines not or refrains from searching an NTN cell on the third carrier frequency within the third frequency band using the fourth satellite IE. In some other implementations, the fourth NTN carrier frequency information may include the second satellite ID to indicate that the fourth NTN carrier frequency information is associated with the fourth satellite IE. In some implementations, the UE 102 may determine to search or search an NTN cell on the fourth carrier frequency within the fourth frequency band using the fourth satellite IE. In other implementations, the UE 102 determines not or refrains from searching an NTN cell on the fourth carrier frequency within the fourth frequency band using the fourth satellite IE.
[0078] In other implementations, the second satellite information may include one or more NTN cell IES each for a corresponding NTN cell, as described for the first satellite information. For example, the second satellite information includes a third NTN cell IE and the third NTN cell IE includes third ephemeris information, third network-controlled common TA parameters, a third epoch time, a third service start time, a third area configuration, a third scheduling offset, a third frequency band number indicating the third frequency band, third frequency information indicating the third carrier frequency, and / or a third PCI. In some implementations, the third PCI identifies the NTN cell 123. In some implementations, the UE 102 searches for an NTN cell (e.g., the NTN cell 123) on the third carrier frequency within the third frequency band, using the one or more parameters in the third NTN cell IE. In other implementations, the UE determines not or refrains from searching an NTN cell on the third carrier frequency within the third frequency band, using the third NTN cell IE. The second satellite information may additionally include a fourth NTN cell IE and the fourth NTN cell IE includes fourth ephemeris information,PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 fourth network-controlled common TA parameters, a fourth epoch time, a fourth service start time, a fourth area configuration, a fourth scheduling offset, a fourth frequency band number indicating the fourth frequency band, fourth frequency information indicating the fourth carrier frequency, and / or a fourth PCI. In some implementations, the UE 102 searches for an NTN cell on the fourth carrier frequency within the fourth frequency band, using the one or more parameters in the fourth NTN cell IE. In other implementations, the UE 102 determines not or refrains from searching an NTN cell on the fourth carrier frequency within the fourth frequency band, using the fourth NTN cell IE. In other implementations, the UE 102 searches for an NTN cell (e.g., the NTN cell 123) on the third carrier frequency within the third frequency band, based on a pre-configured information (e.g., 400A and / or 400B).
[0079] In some implementations, the fifth system information includes at least one fifth SIB (SIB(s)). For example, if the TN cell 126 is an NR cell, the fifth SIB is a SIB 19 or a new, dedicated SIB defined as discussed above with reference to the fourth SIB. In another example, if the TN cell 126 is an E-UTRA cell, the fifth SIB(s) includes a SystemInformationBlockType32 (rather than a SystemInformationBlockType33-NB) and / or a SystemlnformationBlockType33 (rather than a SystemInformationBlockType33-NB), or a new, dedicated SIB, as discussed above with reference to the fourth SIB. Alternatively, the fifth SIB(s) includes a SyslemlnformalionBlockType32-NB and / or a SyslemlnformaUonBlockType33-NB, or a new, dedicated SIB. In yet another implementation, if the TN cell 126 is a 6G cell, the fifth SIB is a SIB defined for 6G.
[0080] In some implementations, the base station 106 may transmit the fourth system information and fifth system information in a single transmission (e.g., a single system information message) on the TN cell 126 (i.e., events 508 and 510 can combined as a single event). In other implementations, the base station 106 may transmit the fourth system information and the fifth system information in separate transmissions (e.g., separate system information messages) on the TN cell 126 (i.e., events 508 and 510 can combined as a single event). In yet other implementations, the first satellite information and the second satellite information can be included in a single SIB transmitted by the base station 106 on the TN cell 126 (i.e., events 508 and 510 can combined as a single event).PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0081] In some implementations, a satellite may operate cells of multiple RATs (e.g.. a first RAT NTN cell and a second RAT NTN cell). In such cases, one or more parameter(s) in satellite information for the satellite can be shared for the RATs. For example, the satellite 304 operates the second NTN cell 123 instead of the satellite 306. In this case, the second satellite information may share one or parameter(s) included in the first satellite information and thereby omit the parameter(s) to save signaling bits. In some implementations, the parameter(s) include ephemeris information, common TA parameters, an epoch time, a service start time, a scheduling offset, carrier frequency information, frequency band information, and / or a PCI. For example, the third satellite IE may share one or more parameter(s) included in the first satellite IE and therefore omit the parameter(s). In some implementations, the third satellite ID is set to the same value as the first satellite ID to indicate that the parameter(s) not signaled in the third satellite IE refer to the corresponding parameter(s) signaled in the first satellite IE. In some other implementations, the first satellite information (e.g., the first satellite IE) and the second satellite information (e.g., the third satellite IE) share a portion of the parameters described above and do not share the reset of the parameters. For example, the third satellite IE may share the first ephemeris information included in the first satellite IE and therefore omit the third ephemeris information. In this example, the third satellite IE may signal the other parameters described above. In another example, the third satellite IE may share the first ephemeris information and the first common TA parameters included in the first satellite IE and therefore omit the third ephemeris information and the third common TA parameters. In this example, the third satellite IE may signal the other parameters described above. Examples and implementations described above can apply to the first NTN cell IE and the third NTN cell IE, e.g., by replacing “first satellite IE” and “third satellite IE” with “first NTN cell IE” and “third NTN cell IE” respectively. In some implementations, the second satellite IE and the fourth satellite IE share at least a portion of the parameter(s) described above. In such cases, examples and implementations described above can apply to the second satellite IE and the fourth satellite IE, e.g., by replacing “first satellite IE” and “third satellite IE” with “second satellite IE” and “fourth satellite IE” respectively. In other implementations, the second satellite IE and the fourth satellite IE do not share any of the parameter(s) described above. In some implementations, thePATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 second NTN cell IE and the fourth NTN cell IE share at least a portion of the parameter(s) described above. In such cases, examples and implementations described above can apply to the second NTN cell IE and the fourth NTN cell IE, e.g., by replacing “first satellite IE” and “third satellite IE” with “second NTN cell IE” and “fourth NTN cell IE” respectively. In other implementations, the second NTN cell IE and the fourth NTN cell IE do not share any of the parameter(s) described above.
[0082] After events 502, 504, 506, 508, and / or 510, the UE 102 communicates 512 with the TN cell 126. In some implementations, the UE 102 accesses 512 the TN cell 126 based on the initial access information. In some implementations, the UE 102 performs the registration procedure with the TN cell 126 in event 512. 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 3GPP specification for 6G.
[0083] After event 512, the UE 102 selects or reselects 514 the NTN cell 124. In some implementations, the UE 102 stops receiving DL signals from the TN cell 126 in response to event 514. In other implementations, the UE 102 stops receiving DL signals from the TN cell 126 before event 514. Before event 514, the UE 102 performs a first RAT NTN cell search on the first carrier frequency within the first frequency band, using the first NTN carrier frequency IE, the first satellite information, and / or the first RAT, as described above. The UE 102 discovers the first RAT NTN cell 124 in the NTN cell search. The UE 102 measures DL signals from the NTN cell 124 and obtains measurement results from the measurement of the DL signals. The UE 102 determines whether the NTN cell 124 is a suitable cell based on the measurement results of the DL signals. In some implementations, the UE 102 determines the NTN cell 124 is a suitable cell and selects or reselects 514 the NTN cell 124. In some implementations, the UE 102 determines that the NTN cell 124 is suitable because the NTN cell 124 meets cell selection criteria, e.g., as specified in a 3GPP specification. In some implementations, the UE 102 reselects 514 the NTN cell 124 because the NTN cell 124 is suitable and meets cell reselection criteria, e.g., as specified in a 3GPP specification.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0084] Before event 514, the UE 102 performs a second RAT NTN cell search on the third carrier frequency within the third frequency band, using the third NTN carrier frequency IE, the third satellite information, and / or the second RAT, as described above. In some implementations, the UE 102 discovers the second RAT NTN cell 123 in the second NTN cell search. The UE 102 measures DL signals from the NTN cell 123 and obtains measurement results from the measurement of the DL signals. The UE 102 determines whether the NTN cell 123 is a suitable cell based on the measurement results of the DL signals. In some implementations, the UE 102 determines the NTN cell 123 is a not suitable cell and therefore the UE 102 does not select or reselect the NTN cell 123. In other implementations, the UE 102 determines that the NTN cell 123 is suitable because the NTN cell 123 meets cell selection criteria, e.g., as specified in a 3GPP specification. The UE 102 does not reselect the NTN cell 123 because the NTN cell 123 does not meet cell reselection criteria, e.g., as specified in a 3GPP specification. Alternatively, the UE 102 refrains from performing the second RAT NTN cell search.
[0085] In some implementations, after event 512 and before event 514, the UE 102 performs the first RAT NTN cell search and / or additionally the second RAT cell search. In other implementations, after event 512 and before event 514, the UE 102 may detect occurrence of at least one of the following events: 1) the TN cell 126 is not suitable, 2) detecting out of coverage of the TN cell 126, and / or 3) activating NTN communication. In some implementations, the UE 102 determines that the TN cell 126 is not suitable based on cell selection criteria. In some implementations, the UE 102 activates the NTN communication while in coverage of the TN cell 126. In other implementations, the UE 102 activates the NTN communication while in out of coverage of the TN cell 126. In some implementations, the activation of the NTN communication includes activating an NTN application, activating transmission of a message via an NTN, or dialing a voice call via an NTN. In response to the events 1), 2) and / or 3), the UE 102 performs the first RAT NTN cell search and / or second RAT NTN cell search, discovers the NTN cell 124, and selects or reselects the NTN cell 124, as described above.
[0086] After selecting or reselecting the NTN cell 124, the UE 102 receives 516 sixth system information (e.g., a sixth SIB) from the NTN cell 124, including initial access information.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00Examples and implementations described with respect to event 502 may apply to event 516. In some implementations, the sixth SIB includes serving satellite information (e.g., satellite assistance information for the NTN cell 124). In other implementations, the UE 102 receives additional system information (e.g., additional SIB) including the serving satellite information. The UE 102 communicates 526 with the TN cell 126 using the initial access information and the serving satellite information. By including the serving satellite information and the initial access information in the same SIB, the UE 102 can access the NTN cell 124 in event 526 more quickly, as it avoids waiting for an additional SIB transmission. In some implementations, the serving satellite information includes a satellite ID, ephemeris information, network-controlled common timing advance (TA) parameters, epoch time, and / or at least one scheduling offset. The satellite ID identifies the serving satellite information or a satellite operating the NTN cell 124. In some implementations, the UE 102 obtains a valid GNSS position before connecting to the NTN cell 124 (i.e., event 526). To achieve UL synchronization, before and / or during event 526, the UE 102 calculates a round- trip time (RTT) between the UE 102 and a reference point (RP) based on the GNSS position, the ephemeris information, and the common TA parameters. The UE 102 determines a timing advance (TTA) and the uses the timing advance to pre-compensate the RTT in UL transmissions. In some implementations, the UE 102 generates and transmits the UL transmissions using configuration parameters in the initial access information. In some implementations, the UE 102 calculates a frequency Doppler shift, and autonomously precompensates for the frequency Doppler shift in the UL transmissions, by considering the UE 102 position and the ephemeris information.
[0087] Before or after event 526, the UE 102 may receive 518 seventh system information (e.g., seventh SIB) including third satellite information (e.g., neighboring satellite information) for the first RAT. Examples and implementations described with respect to event 508 can apply to event 518. In some implementations, the third satellite information and the first satellite information are different. In other implementations, the third satellite information partially or completely overlaps with the first satellite information. In some implementations, the serving satellite information is included in the seventh SIB instead of the sixth SIB or the additional SIB. Before or after event 526, the UE 102 may receive 520 eighth system information (e.g., eighthPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00SIB) including fourth satellite information (e.g., neighboring satellite information) for the second RAT. Examples and implementations described with respect to event 510 can apply to event 520. In some implementations, the fourth satellite information and the second satellite information are different. In other implementations, the fourth satellite information partially or completely overlaps with the second satellite information.
[0088] Before or after event 526, the UE 102 may receive 522 ninth system information (e.g., ninth SIB) including TN carrier frequency IE indicating a TN carrier frequency and / or a TN frequency band for the TN cell 126 and / or one or more other TN cells. In some implementations, the TN carrier frequency and / or the TN frequency band belong to a third RAT, the first RAT or the second RAT. In some implementations, the third RAT is the RAT utilized by the TN cell 126. In some implementations, the UE 102 searches for a TN cell (e.g., the TN cell 126) on the TN carrier frequency within the TN frequency band after event 526. In other implementations, the UE 102 refrains from searching a TN cell on the TN earner frequency within the TN frequency band after event 526.
[0089] Before or after event 526, the UE 102 may receive 523 tenth system information (e.g., tenth SIB) including fifth NTN carrier frequency IE for the first RAT. Examples and implementations described with respect to event 504 can apply to event 523. Before or after event 526, the UE 102 may receive 524 eleventh system information (e.g., eleventh SIB) including sixth NTN carrier frequency IE for the second RAT. Examples and implementations described with respect to event 506 can apply to event 524.
[0090] In some implementations, the system information 516 is or includes at least one SIB. In some implementations, the UE 102 receives the system information 516, 518, 520, 522, 523, and / or 524 via a bandwidth reduction BCCH (BR-BCCH) for eMTC communication from the NTN cell 124 (e.g., eMTC NTN cell). In other implementations, the UE 102 receives the system information 516, 518, 520, 522, 523 and / or 524 via a BCCH for non-IoT communication from the NTN cell 124 (e.g., an E-UTRA (i.e., LTE), NR or 6G NTN cell). In yet other implementations, the NTN cell utilizes NB-IoT and the UE 102 receives the system information 516, 518, 520, 522, 523, and / or 524 via a BCCH for NB-IoT communication from the NTN cell 124 (e.g., NB-IoT NTN cell). In some implementations, the SIB 516 indicates whether the SIBsPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00518, 520, 522, 523, and / or 524 are scheduled and transmitted on the NTN cell. If SIB 516 indicates that the SIBs 520, 522, 523, and / or 524 are scheduled and transmitted on the NTN cell 124, the UE 102 attempts to receive or receives the SIBs 520, 522, 523, and / or 524. Otherwise if SIB 516 does not indicate that the SIBs 520, 522, 523, and / or 524 are scheduled and transmitted on the NTN cell 124, the UE 102 does not attempt to receive or receive the SIBs 520, 522, 523, and / or 524.
[0091] The events 502, 504, 506, 508, and 510 are collectively referred to a TN system information transmission procedure or a TN system information acquisition procedure 590. The events 516, 518, 520, 522, 523, and 524 are collectively referred to as an NTN system information transmission procedure or an NTN system information acquisition procedure 592.
[0092] Fig. 6 illustrates an example scenario 600 similar to the scenario 500. The difference between the scenarios 500 and 600 are described below. Initially the UE 102 selects or reselects 614 an NTN cell 124 of a first RAT. In some implementations, event 614 is similar to event 514, and examples and implementations described with respect to event 514 can apply to event 614. In other implementations, the UE 102 performs an NTN cell search, discovers the NTN cell 124 in the NTN cell search, and then selects or reselects 614 the NTN cell 124, when powered on, powered cycle, or a USIM inserted. In one implementation of the NTN cell search, the UE 102 searches an NTN cell based on a pre-configured information (e.g., 400A and / or 400B). In another implementation of the NTN cell search, the UE 102 searches an NTN cell based on an NTN carrier frequency IE. In some implementations, the UE 102 receives the NTN earner frequency IE from an NTN cell as described with respect to Fig. 5 and stores the NTN carrier frequency IE on a non-transitory computer-readable medium or the USIM. In other implementations, the NTN carrier frequency IE indicates an NTN carrier frequency and / or an NTN frequency band of an NTN cell (e.g., the NTN cell 124 or another NTN cell) that the UE 102 camps on, and the UE 102 stores the NTN earner frequency IE on a non-transitory computer-readable medium or the USIM.
[0093] After event 614, the UE 102 performs the NTN system information acquisition procedure 692 with the NTN cell 124, and then communicates 626 with the NTN cell 124, as described for Fig. 5. After event 626, the UE selects or reselects 601 the TN cell 126. In somePATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 implementations, after event 626, the UE 102 performs a TN cell search on a TN carrier frequency within a TN frequency band and discovers the TN cell 126 in the TN cell search. In some implementations, the UE 102 determines the TN cell 126 is a suitable cell and selects or reselects 601 the TN cell 126. In some implementations, the UE 102 determines that the TN cell 126 is suitable because the TN cell 126 meets cell selection criteria, e.g., as specified in a 3GPP specification. In some implementations, the UE 102 reselects 601 the TN cell 126 because the TN cell 126 is suitable and meets cell reselection criteria, e.g.. as specified in a 3GPP specification. In some implementations, the UE 102 obtains a TN carrier frequency IE as described for Fig. 5. The TN carrier frequency IE indicates the TN carrier frequency and / or the TN frequency band. In some implementations, the TN carrier frequency IE includes a PCI of the TN cell 126. In other implementations, the TN carrier frequency IE does not include the PCI.
[0094] In some implementations, after event 626 and before event 601, the UE 102 may detect occurrence of at least one of the following events: 1) the NTN cell 124 is not suitable, 2) detecting out of coverage of the NTN cell 124, and / or 3) deactivating NTN communication. In some implementations, the UE 102 determines that the NTN cell 124 is not suitable based on cell selection criteria. In some implementations, the UE 102 deactivates the NTN communication while in coverage of the NTN cell 124. In other implementations, the UE 102 deactivates the NTN communication while in out of coverage of the NTN cell 124. In some implementations, the deactivation of the NTN communication includes deactivating an NTN application, completing transmission of a message via the NTN cell 124, or completing a voice call via the NTN cell 124. In response to the events 1), 2) and / or 3), the UE 102 performs the TN cell search, discovers the TN cell 126, and selects or reselects the TN cell 126, as described above.
[0095] In some implementations, the UE 102 performs an NTN cell search on a carrier frequency within a frequency band of the second RAT and discovers the NTN cell 123 in the NTN cell search, as described for Fig. 5. The UE 102 refrains from selecting or reselecting the NTN cell 123 as described for Fig. 5. Alternatively, the UE 102 refrains from performing the NTN cell search.
[0096] After event 601, the UE 102 performs the TN system information acquisition procedure 690 with the TN cell 126 and then communicates 612 with the TN cell 126 asPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 described for Fig. 5. In some alternative implementations, the UE 102 may select or reselect a TN cell (i.e., a first TN cell) other than the TN cell 126, performs a TN system information acquisition procedure with the first TN cell, and communicates with the first TN cell, similar to events 601. 690 and 612 respectively.
[0097] Fig. 7 illustrates an example scenario 700 similar to the scenarios 500 and 600. The difference among the scenarios 500, 600, and 700 are described below.
[0098] Initially the UE 102 selects or reselects 714 an NTN cell 124 of a first RAT as described for Fig. 6. After event 714, the UE 102 performs the NTN system information acquisition procedure 792a with the NTN cell 124, and then communicates 726a with the NTN cell 124, as described for Fig. 5. After event 726a, the UE selects or reselects 715 the NTN cell 123. In some implementations, after event 726a, the UE 102 performs an NTN cell search on an NTN carrier frequency within an NTN frequency band of second RAT and discovers the NTN cell 123 in the NTN cell search, as described for Fig. 5. In some implementations, the UE 102 determines the NTN cell 123 is a suitable cell and selects or reselects 715 the NTN cell 123. In some implementations, the UE 102 determines that the NTN cell 123 is suitable because the NTN cell 123 meets cell selection criteria, e.g., as specified in a 3GPP specification. In some implementations, the UE 102 reselects 715 the NTN cell 123 because the NTN cell 123 is suitable and meets cell reselection criteria, e.g., as specified in a 3GPP specification.
[0099] In some implementations, after event 726a and before event 715, the UE 102 may detect occurrence of at least one of the events 1), 2) and / or 3) as described for Fig. 6. In response to the events 1), 2) and / or 3), the UE 102 performs the NTN cell search, discovers the NTN cell 123, and selects or reselects the NTN cell 123, as described above.
[0100] In some implementations, the UE 102 performs a TN cell search on a carrier frequency within a frequency band and discovers the TN cell 126 in the TN search, as described for Figs. 5 and 6. The UE 102 refrains from selecting or reselecting the TN cell 126. Alternatively, the UE 102 refrains from performing the TN cell search.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0101] After event 715, the UE 102 performs 792b an NTN system information acquisition procedure with the NTN cell 123 and then communicates 726b with the NTN cell 123, similar to event 592 and event 526 of Fig. 5 respectively.
[0102] Next, several example methods that can be implemented in a UE (e.g., the UE 102) or a RAN node (e.g., the base station 104, a distributed unit (DU) of the base station 104, or the central unit (CU) of the base station 104) are discussed with reference to Figs. 8-13. Descriptions for Figs. 5-7 can apply to Figs. 8-13. 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.
[0103] Fig. 8 illustrates an example method 800, which can be implemented by a RAN node. The method 800 begins at block 816, where the RAN node broadcasts a first SIB via a first NTN cell of a first RAT, where the first SIB includes initial access information for accessing the first NTN cell and serving satellite information. At block 818, the RAN node may broadcast a second SIB on the first NTN cell, where the second SIB includes first neighboring satellite information for the first RAT. At block 820, the RAN node may broadcast a third SIB on the first NTN cell, where the third SIB includes second neighboring satellite information for a second RAT. At block 822, the RAN node may broadcast a fourth SIB on the first NTN cell, where the fourth SIB includes TN carrier frequency information. At block 823, the RAN node may broadcast a fifth SIB on the first NTN cell, where the fifth SIB includes NTN carrier frequency information for the first RAT. At block 824, the RAN node may broadcast a sixth SIB on the first NTN cell, where the sixth SIB includes NTN carrier frequency information for the second RAT. At block 826, the RAN node communicates with the UE via the first NTN cell, based on the initial access information and one or more parameters in the serving satellite information.
[0104] In some implementations, the first neighboring satellite information includes one or more satellite IE each for a corresponding satellite supporting a neighboring NTN cell of the first RAT. In other implementations, the first neighboring satellite information includes one or more NTN cell IES each for a corresponding satellite supporting a neighboring NTN cell of the first RAT. In some implementations, the neighboring NTN cell(s) and the first NTN cell belong to the same PLMN. In other implementations, the neighboring NTN cell(s) and the first NTN cellPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 belong to different PLMNs. In yet other implementations, some the neighboring NTN cell(s) and the first NTN cell belong to the same PLMN and the other belong to different PLMNs. In some implementations, the neighboring NTN cell(s) and the first NTN cell shared by multiple PLMNs. In some implementations, the first neighboring satellite information indicates which PLMN(s) the neighboring NTN cell(s) belong to. For example, the first neighboring satellite information includes one or more PLMN ID(s) to indicate which PLMN(s) the neighboring NTN cell(s) belong to. In another example, each satellite IE or NTN cell IE including a PLMN ID indicating a PLMN where the corresponding NTN cell belongs. In other implementations, the NTN carrier frequency information of the first RAT indicates which PLMN(s) the neighboring NTN cell(s) belong to. For example, the NTN earner frequency information of the first RAT includes one or more PLMN ID(s) to indicate which PLMN(s) the neighboring NTN cell(s) belong to. In some alternative implementations, neither the first neighboring satellite information nor the NTN carrier frequency information of the first RAT indicate which PLMN(s) the neighboring cell(s) belong to. In such cases, the neighboring NTN cell(s) and the first NTN cell belong to the same PLMN. Alternatively, the neighboring NTN cell(s) and the first NTN cell belong to different PLMNs and a UE may use pre-configured information (e.g., 440A and / or 440B) to determine which PLMN(s) the neighboring cell(s) belong to.
[0105] In some implementations, the second neighboring satellite information includes one or more satellite IE each for a corresponding satellite supporting a neighboring NTN cell of the second RAT. In other implementations, the second neighboring satellite information includes one or more NTN cell IES each for a corresponding satellite supporting a neighboring NTN cell of the second RAT. In some implementations, the neighboring NTN cell(s) and the first NTN cell belong to the same PLMN. In other implementations, the neighboring NTN cell(s) and the first NTN cell belong to different PLMNs. In yet other implementations, some the neighboring NTN cell(s) and the first NTN cell belong to the same PLMN and the other belong to different PLMNs. In some implementations, the neighboring NTN cell(s) and the first NTN cell shared by multiple PLMNs. In some implementations, the second neighboring satellite information indicates which PLMN(s) the neighboring NTN cell(s) belong to. For example, the second neighboring satellite information includes one or more PLMN ID(s) to indicate which PLMN(s)PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 the neighboring NTN cell(s) belong to. In another example, each satellite IE or NTN cell IE including a PLMN ID indicating a PLMN where the corresponding NTN cell belongs. In other implementations, the NTN carrier frequency information of the second RAT indicates which PLMN(s) the neighboring NTN cell(s) belong to. For example, the NTN earner frequency information of the first RAT includes one or more PLMN ID(s) to indicate which PLMN(s) the neighboring NTN cell(s) belong to. In some alternative implementations, neither the second neighboring satellite information nor the NTN carrier frequency information of the second RAT indicate which PLMN(s) the neighboring cell(s) belong to. In such cases, the neighboring NTN cell(s) and the first NTN cell belong to the same PLMN. Alternatively, the neighboring NTN cell(s) and the first NTN cell belong to different PLMNs and a UE may use pre-configured information (e.g., 440A and / or 440B) to determine which PLMN(s) the neighboring cell(s) belong to.
[0106] Fig. 9A illustrates an example method 900A, which can be implemented by a RAN node. The method 900A begins at block 902, where the RAN node broadcasts a first SIB on a TN cell, where the first SIB includes initial access information for accessing the TN cell. At block 904, the RAN node may broadcast a second SIB on the TN cell, where the second SIB includes NTN carrier frequency information of a first RAT. At block 906, the RAN node may broadcast a third SIB on the TN cell, where the third SIB includes NTN carrier frequency information of a second RAT. At block 908, the RAN node broadcasts a fourth SIB on the TN cell, where the fourth SIB includes first satellite information for the first RAT. At block 910, the RAN node broadcasts a fifth SIB on the TN cell, where the fifth SIB includes second satellite information for the second RAT. At block 912, the RAN node communicates with the UE via the TN cell, based on the initial access information.
[0107] In some implementations, the first satellite information include neighboring satellite information. In some implementations, the first satellite information include neighboring satellite information. Examples and implementations described for Fig. 8 can apply to Fig. 9 by replacing “first NTN cell”, “first neighboring satellite information”, and “second neighboring satellite information” with “TN cell”, “first satellite information”, and “second satellite information”, respectively.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0108] Fig. 9B is a flow diagram of an example method 900B similar to the method 900A, except that the method 900B includes blocks 909 and 911 instead of blocks 908 and 910. At block 909, the RAN node broadcasts a fourth SIB on the TN cell, where the fourth SIB includes common satellite information for a first RAT and a second RAT (e.g., event 508 or 590). At block 911, the RAN node may broadcast a fifth SIB on the TN cell, where the fifth SIB includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 510 or 590).
[0109] In some implementations, the common satellite information includes one or more parameter(s) that are common for or shared between both the first RAT and second RAT. In some implementations, the parameter(s) include a first portion of s a set of parameters: ephemeris information, common TA parameters, an epoch time, a service start time, a scheduling offset, carrier frequency information, frequency band information, and / or a PCI. In some implementations, the first satellite information includes a second portion of the set of parameters with first values, and the second satellite information includes a third portion of the set of parameters with second values. The second portion and the third portion may include the same parameters with different values. In some implementations, the common satellite information includes ephemeris information common for the first RAT and the second RAT. In such implementations, the first satellite information includes first common TA parameters, a first epoch time and / or a first scheduling offset, and the second satellite information includes second common TA parameters, a second epoch time and / or a second scheduling offset.
[0110] In some implementations, the common satellite information includes the common TA parameters common for the first RAT and the second RAT, and the first and second satellite information do not include common TA parameters. In some implementations, the common satellite information includes an epoch time common for the first RAT and the second RAT, and the first and second satellite information do not include an epoch time. In some implementations, the common satellite information includes a scheduling offset for the first RAT and the second RAT, and the first and second satellite information do not include an a scheduling offset. In some implementations, the common satellite information includes a serving start time for the first RAT and the second RAT, and the first and second satellite information do notPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 include an a service start time. In some implementations, the common satellite information includes a polarization configuration for the first RAT and the second RAT, and the first and second satellite information do not include an a polarization configuration.
[0111] In some implementations, the first satellite information includes a first service start time. In such cases, neither the common satellite information nor the second satellite information include a serving start time. Alternatively, the second satellite information includes a second serving start time. In some implementations, the second satellite information includes a polarization configuration and neither the common satellite information nor the first satellite information include a polarization configuration. Alternatively, the second satellite information includes a polarization configuration.
[0112] Fig. 9C is a flow diagram of an example method 900C similar to the methods 900A and 900B, except that the method 900C includes block 907 instead of blocks 908, 910, 909, and 911. At block 907, the RAN node broadcasts a fourth SIB on the TN cell, where the fourth SIB includes common satellite information for the first RAT and second RAT and includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 508, 510, or 590).
[0113] Fig. 10A illustrates an example method 1000A, which can be implemented by a RAN node. The method 1000A begins at block 1016, where the RAN node broadcasts a first SIB on a first NTN cell of a first RAT, where the first SIB includes initial access information for accessing the first NTN cell. At block 1018, the RAN broadcasts a second SIB on the first NTN cell, where the second SIB includes first satellite information for the first RAT. At block 1020, the RAN node broadcasts a third SIB on the first NTN cell, where the third SIB includes second satellite information for a second RAT. At block 1022, the RAN node may broadcast a fourth SIB on the first NTN cell, where the fourth SIB includes TN carrier frequency information. At block 1023, the RAN node may broadcast a fifth SIB on the first NTN cell, where the fifth SIB includes NTN carrier frequency information for the first RAT. At block 1024, the RAN node may broadcast a sixth SIB on the first NTN cell, where the sixth SIB includes NTN carrier frequency information for the second RAT. At block 1026, the RAN node communicates with the UE via the first NTN cell, based on the initial access information.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0114] In some implementations, the first satellite information include neighboring satellite information. In some implementations, the first satellite information include neighboring satellite information. Examples and implementations described for Fig. 8 can apply to Fig. 10A by replacing “first neighboring satellite information”, and “second neighboring satellite information” with “first satellite information”, and “second satellite information”, respectively. In some implementations, the second SIB or the first satellite information includes serving satellite information for the first NTN cell. In other implementations, the second SIB does not include serving satellite information and the RAN node broadcasts an additional SIB on the first NTN cell, including serving satellite information for the first NTN cell.
[0115] Fig. 1 OB is a flow diagram of an example method 1000B similar to the method 1000A, except that the method 1000B includes blocks 1019 and 1021 instead of blocks 1018 and 1020. At block 1019, the RAN node broadcasts a second SIB on the NTN cell, where the second SIB includes common satellite information for a first RAT and a second RAT (e.g.. event 518 or 592). At block 1021, the RAN node may broadcast a third SIB on the NTN cell, where the third SIB includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 510 or 590).
[0116] Fig. 10C is a flow diagram of an example method 1000C similar to the methods 1000 A and 1000B, except that the method 1000C includes block 1017 instead of blocks 1018, 1020, 1019, and 1021. At block 1017, the RAN node broadcasts a fourth SIB on the TN cell, where the fourth SIB includes common satellite information for the first RAT and second RAT and includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 508, 510, or 590).
[0117] Examples and implementations described for Figs. 10A and 9B can apply to Figs. 10B and 10C.
[0118] Fig. 11 A illustrates an example method 1100A, which can be implemented by an UE. The method 1100A begins at block 1102, where the UE receives a first SIB on a TN cell, where the first SIB includes initial access information for accessing the TN cell. At block 1104, the UE receives a second SIB on the TN cell, where the second SIB includes NTN carrier frequencyPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 information for a first RAT. At block 1106, the UE may receive a third SIB on the TN cell, where the third SIB includes NTN carrier frequency information for a second RAT. At block1108, the UE receives a fourth SIB on the TN cell, where the fourth SIB includes first satellite information for the first RAT. At block 1110, the UE receives a fifth SIB on the TN cell, where the fifth SIB includes second satellite information for the second RAT. At block 1112, the UE communicates with the TN cell, based on the initial access information. At block 1114A, the UE selects or reselects a cell of an NTN cell of the first RAT based on the first satellite information and / or the NTN carrier frequency information for the first RAT. Examples and implementations described for Fig. 9A can apply to Fig. 11 A.
[0119] Fig. 1 IB is a flow diagram of an example method 100B similar to the method 1100A, except that the method 1100B includes blocks 1109, 111 1 , 1 114B instead of blocks 1108, 1 110, and 1114A. At block 1109, the UE receives a fourth SIB on the TN cell, where the fourth SIB includes common satellite information for a first RAT and a second RAT (e.g.. event 508 or 590). At block 1111, the UE may receive a fifth SIB on the TN cell, where the fifth SIB includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 510 or 590). At block 1114B, the UE selects or reselects a cell of an NTN cell of the first RAT based on the common satellite information, the first satellite information, and / or the NTN carrier frequency information for the first RAT.
[0120] Fig. 11C is a flow diagram of an example method 1100C similar to the methods 1100A and 1100B, except that the method 1100C includes block 1107 instead of blocks 1108, 1110,1109, and 1111. At block 1107, the UE receives a fourth SIB on the TN cell, where the fourth SIB includes common satellite information for the first RAT and second RAT and includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 508, 510, or 590). Examples and implementations described for Fig. 9B can apply to Figs. 1 IB and 11C.
[0121] Fig. 12A illustrates an example method 1200A, which can be implemented by a UE. The method 1200A begins at block 1216, where the UE receives a first SIB on a first NTN cell of a first RAT, where the first SIB includes initial access information for accessing the first NTN cell. At block 1218, the UE receives a second SIB on the first NTN cell, where the second SIBPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 includes first satellite information for the first RAT. At block 1220, the UE receives a third SIB on the first NTN cell, where the third SIB includes second satellite information for a second RAT. At block 1222, the UE may receive a fourth SIB on the first NTN cell, where the fourth SIB includes TN carrier frequency information. At block 1223, the UE may receive a fifth SIB on the first NTN cell, where the fifth SIB includes NTN carrier frequency information for the first RAT. At block 1224, the UE may receive a sixth SIB on the first NTN cell, where the sixth SIB includes NTN carrier frequency information for the second RAT. At block 1226. the UE communicates with the RAN via the first NTN cell, based on the initial access information. The flow may proceed to block 1201 or 1215A from block 1226. At block 1201, the UE may select or reselect a TN cell based on the TN earner frequency information. Alternatively, the UE may select or reselect a TN cell based on pre-configured information (e.g., 440A and / or 440B). At block 1215A, the UE may select or reselect an NTN cell of the second RAT NTN based on the second satellite information and / or the NTN carrier frequency information for the second RAT. Examples and implementations described for Fig. 10A can apply to Fig. 12A.
[0122] Fig. 12B is a flow diagram of an example method 1200B similar to the method 1200A, except that the method 1200B includes blocks 1219, 1221, and 1215B instead of blocks 1218, 1220, and 1215A. At block 1219, the UE receives a second SIB on the NTN cell, where the second SIB includes common satellite information for a first RAT and a second RAT (e.g., event 518 or 592). At block 1221, the UE may receive a third SIB on the NTN cell, where the third SIB includes first satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 510 or 590). The flow may proceed to block 1201 or 1215B from block 1226. At block 1215B, the UE may the UE may select or reselect an NTN cell of the second RAT NTN based on the common satellite information, the second satellite information, and / or the NTN carrier frequency information for the second RAT.
[0123] Fig. 12C is a flow diagram of an example method 1200C similar to the methods 1200 A and 1200B, except that the method 1200C includes block 1217 instead of blocks 1218, 1220, 1219, and 1221. At block 1217, the UE receives a fourth SIB on the TN cell, where the fourth SIB includes common satellite information for the first RAT and second RAT and includes firstPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 satellite information and second satellite information for the first RAT and the second RAT respectively (e.g., event 508, 510, or 590).
[0124] Examples and implementations described for Figs. 10A and 9B can apply to Figs. 12B and 12C.
[0125] Fig. 13 illustrates an example method 800, which can be implemented by a UE. The method 1300 begins at block 1316. where the UE receives a first SIB via a first NTN cell of a first RAT, where the first SIB includes initial access information for accessing the first NTN cell and serving satellite information. At block 1318, the UE may receive a second SIB on the first NTN cell, where the second SIB includes first neighboring satellite information for the first RAT. At block 1320, the UE may receive a third SIB on the first NTN cell, where the third SIB includes second neighboring satellite information for a second RAT. At block 1322, the UE may receive a fourth SIB on the first NTN cell, where the fourth SIB includes TN carrier frequency information. At block 1323, the UE may receive a fifth SIB on the first NTN cell, where the fifth SIB includes NTN carrier frequency information for the first RAT. At block 1324, the UE may receive a sixth SIB on the first NTN cell, where the sixth SIB includes NTN carrier frequency information for the second RAT. At block 1326, the UE communicates with the first NTN cell, based on the initial access information and one or more parameters in the serving satellite information. Examples and implementations described for Fig. 8 can apply to Fig. 13.
[0126] The following list of examples reflects a variety of the embodiments explicitly contemplated by the present disclosure.
[0127] Example 1. A method for cell selection or reselection, the method implemented in a user equipment (UE) and comprising: selecting or reselecting a non-terrestrial network (NTN) cell; and receiving, in the NTN cell, a system information message including (i) initial access information for the NTN cell and (ii) serving satellite information.
[0128] Example 2. The method of example 1, further comprising: receiving first neighboring satellite information for a first NTN radio access technology (RAT); and receiving second neighboring satellite information for a second NTN RAT.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0129] Example 3. The method of example 2, wherein: the first neighboring satellite information and the second neighboring satellite information are received in separate respective system information messages.
[0130] Example 4. The method of example 3, wherein: the first neighboring satellite information and the second neighboring satellite information are received in a same system information message.
[0131] Example 5. The method of any of examples 2-4, further comprising: receiving third neighboring satellite information common to the fist NTN RAT and the second NTN RAT.
[0132] Example 6. The method of any of examples 2-5, wherein: the first neighboring satellite information and the second neighboring satellite information are received in a prior cell, prior to the selecting or the reselecting of the NTN cell.
[0133] Example 7. The method of example 6, wherein: the NTN cell supports the first NTN RAT; and the selecting or the reselecting of the NTN cell includes using the first neighboring satellite information.
[0134] Example 8. The method of example 6 or 7, wherein: the prior cell is a terrestrial network (TN) cell.
[0135] Example 9. The method of example 8, wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in SIB 19 (SIB 19).
[0136] Example 10. The method of example 8, wherein: at least one of the first neighboring satellite information and the neighboring second satellite information is received in SIB type 32 (SIB32).
[0137] Example 11. The method of example 8, wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in SIB type 33 (SIB33).PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0138] Example 12. The method of example 8, wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in a SIB of a type dedicated exclusively to conveying satellite information associated with a certain RAT.
[0139] Example 13. The method of example of example 6 or 7, wherein: the prior cell is an NTN cell.
[0140] Example 14. The method of any of examples 6-13, further comprising: receiving, prior to the receiving of the first neighboring satellite information and the second neighboring satellite information, initial access information for the prior cell; wherein the first neighboring satellite information and the second neighboring satellite information are received according to a scheduling information included in the initial access information.
[0141] Example 15. The method of example 2 or 3, wherein: the second neighboring satellite information is received in the NTN cell, after the selecting or the reselecting of the NTN cell.
[0142] Example 16. The method of example 15, further comprising: selecting or reselecting a new NTN cell using the neighboring second satellite information.
[0143] Example 17. The method of example 15 or 16. wherein the second neighboring satellite information is received via a broadcast control channel (BCCH) for enhanced Machine Type Communication (eMTC).
[0144] Example 18. The method of example 15 or 16, wherein the second neighboring satellite information is received via a BCCH for narrowband (NB) Intemet-of-Things (loT) communication.
[0145] Example 19. The method of any of examples 2-16, further comprising: receiving first NTN carrier frequency information for the first NTN RAT; and receiving second NTN carrier frequency information for the second NTN RAT.
[0146] Example 20. The method of example 19, wherein: the first NTN carrier frequency information is received in a first system information block (SIB); and the second NTN carrier frequency information is received in a second SIB.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0147] Example 21. The method of example 19, wherein: the first NTN earner frequency information and the second NTN carrier frequency information are received in a same SIB.
[0148] Example 22. The method of any of examples 19-21, wherein: each of the first NTN carrier frequency information includes an NTN carrier frequency information element (IE) including a satellite identifier.
[0149] Example 23. The method of any of the preceding examples, further comprising, subsequent to the selecting or reselecting the NTN cell: receiving, in the NTN cell, carrier frequency information for a TN RAT; and selecting or reselecting a new TN cell using the frequency information for the TN RAT.
[0150] Example 24. The method of example 23, wherein the carrier frequency information for the TN RAT is received in a SIB that includes only TN information.
[0151] Example 25. The method of any of the preceding examples, wherein the initial access information includes one or more of: (i) one or more random access configuration parameters, (ii) one or more search space configuration parameters, (iii) a physical downlink control channel (PDCCH) configuration, (iv) a physical downlink shared channel (PDSCH) configuration, or (v) a physical uplink shared channel (PUSCH) configuration.
[0152] Example 26. The method of any of the preceding examples, wherein the serving 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.
[0153] Example 27. The method of any of the preceding examples, wherein the system information message is a SIB type 1 (SIB1) or SIB1 message.
[0154] Example 28. A method for cell selection or reselection, the method implemented in a user equipment (UE) and comprising: receiving, in a serving cell, first neighboring satellite information related to a first non-terrestrial network (NTN) radio access technology (RAT);PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 receiving, in the serving cell, second neighboring satellite information related to a second NTN RAT; and selecting an NTN cell using the first neighboring satellite information or the second neighboring satellite information.
[0155] Example 29. The method of example 28, wherein the first neighboring satellite information and the second neighboring satellite information are received in different respective system information blocks (SIBs).
[0156] Example 30. The method of example 28, wherein the first neighboring satellite information and the second neighboring satellite information are received in a same SIB.
[0157] Example 31. The method of example 29 or 30, wherein: the first neighboring satellite information and the second neighboring satellite information are received in at least one SIB 19.
[0158] Example 32. The method of example 29 or 30, wherein: the first neighboring satellite information and the second neighboring satellite information are received in at least one SIB32.
[0159] Example 33. The method of example 29 or 30, wherein: the first neighboring satellite information and the second neighboring satellite information are received in at least one SIB33.
[0160] Example 34. The method of any of examples 28-33, further comprising: receiving third neighboring satellite information common to the first NTN RAT and the second NTN RAT.
[0161] Example 35. The method of example 30, further comprising: receiving, in the SIB that includes the first neighboring satellite information and the second neighboring satellite information, an information element (IE) including third neighboring satellite information common to the fist NTN RAT and the second NTN RAT.
[0162] Example 36. The method of any of examples 28-35, further comprising: receiving first NTN carrier frequency information for the first NTN RAT; and receiving second NTN carrier frequency information for the second NTN RAT.
[0163] Example 37. The method of example 36, wherein: the first NTN carrier frequency information and the second NTN carrier frequency information are received in different respective SIBs.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0164] Example 38. The method of any of examples 28-37. further comprising, subsequently to the selecting of the NTN cell: receiving, in the NTN cell, a system information message including (i) initial access information for the NTN cell and (ii) serving satellite information.
[0165] Example 39. The method of example 38, wherein: the system information message is received in a SIB 1.
[0166] Example 40. The method of any of examples 28-39. wherein: the serving cell is a TN cell.
[0167] Example 41. The method of any of examples 28-39, wherein: the serving cell is an NTN cell.
[0168] Example 42. A method implemented in a node of a radio access network (RAN), the method comprising: transmitting, in a non-terrestrial network (NTN) cell, a system information message including (i) initial access information for the NTN cell and (ii) serving satellite information; and receiving, from a user equipment (UE), a request to access the NTN cell, the request based on the system information message.
[0169] Example 43. The method of example 42, further comprising: transmitting first neighboring satellite information for a first NTN radio access technology (RAT); and transmitting second neighboring satellite information for a second NTN RAT.
[0170] Example 44. The method of example 43, wherein: the first neighboring satellite information and the second neighboring satellite information are transmitted in separate respective system information messages.
[0171] Example 45. The method of example 44, wherein: the first neighboring satellite information and the second neighboring satellite information are transmitted in a same system information message.
[0172] Example 46. The method of any of examples 43-45. further comprising: transmitting third neighboring satellite information common to the first NTN RAT and the second NTN RAT.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0173] Example 47. The method of any of examples 43-46. wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in SIB 19 (SIB 19).
[0174] Example 48. The method of any of examples 43-46, wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in SIB type 32 (SIB32).
[0175] Example 49. The method of any of examples 43-46, wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in SIB type 33 (SIB33).
[0176] Example 50. The method of any of examples 43-46, wherein: at least one of the first neighboring satellite information and the second neighboring satellite information is received in a SIB of a type dedicated exclusively to conveying satellite information associated with a certain RAT.
[0177] Example 51. The method of any examples 42-50, wherein the initial access information includes one or more of: (i) one or more random access configuration parameters, (ii) one or more search space configuration parameters, (iii) a physical downlink control channel (PDCCH) configuration, (iv) a physical downlink shared channel (PDSCH) configuration, or (v) a physical uplink shared channel (PUSCH) configuration.
[0178] Example 52. The method of any examples 42-51, wherein the serving 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.
[0179] Example 53. The method of any of examples 42-52, wherein the system information message is a SIB type 1 (SIB1) message.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0180] Example 54. A method implemented in a node of a radio access network (RAN), the method comprising: transmitting, in a serving cell, first satellite information related to a first non-terrestrial network (NTN) radio access technology (RAT); and transmitting, in the serving cell, second satellite information related to a second NTN RAT.
[0181] Example 55. The method of example 54, wherein the first neighboring satellite information and the second neighboring satellite information are transmitted in different respective system information blocks (SIBs).
[0182] Example 56. The method of example 54, wherein the first neighboring satellite information and the second neighboring satellite information are transmitted in a same SIB.
[0183] Example 57. The method of example 55 or 56, wherein: the first neighboring satellite information and the second neighboring satellite information are transmitted in at least one SIB 19.
[0184] Example 58. The method of example 55 or 56. wherein: the first neighboring satellite information and the second neighboring satellite information are transmitted in at least one SIB32.
[0185] Example 59. The method of example 55 or 56. wherein: the first neighboring satellite information and the second neighboring satellite information are transmitted in at least one SIB33.
[0186] Example 60. The method of any of examples 54-59, further comprising: transmitting third neighboring satellite information common to the first NTN RAT and the second NTN RAT.
[0187] Example 61. The method of example 56. further comprising: transmitting, in the SIB that includes the first neighboring satellite information and the second neighboring satellite information, an information element (IE) that includes third neighboring satellite information common to the fist NTN RAT and the second NTN RAT.
[0188] Example 62. The method of any of examples 54-61, further comprising: transmitting first NTN carrier frequency information for the first NTN RAT; and transmitting second NTN carrier frequency information for the second NTN RAT.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00
[0189] Example 63. The method of example 62 wherein: the first NTN earner frequency information and the second NTN carrier frequency information are transmitted in different respective SIBs.
[0190] Example 64. The method of any of examples 54-63, wherein: the serving cell is a TN cell.
[0191] Example 65. The method of any of examples 54-63. wherein: the serving cell is an NTN cell.
[0192] Example 66. A device comprising: a transceiver; and processing hardware; the device configured to implement a method of any of the preceding examples.
[0193] The following description may be applied to the description above.
[0194] 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 another example, an event or block with solid lines in the figures can be omitted, if the omission does not cause technical or logical incorrectness. 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”.
[0195] 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 internet-of-things (loT) device or a mobile-internetPATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00 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.
[0196] 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 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.
[0197] 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 / 308455-00CLAIMS:
1. A method for cell selection or reselection, the method implemented in a user equipment (UE) and comprising: receiving, in a serving cell and in a first system information block (SIB), non-terrestrial (NTN) carrier frequency information for an NTN radio access technology (RAT); receiving, in the serving cell and in a second SIB, satellite information for the NTN RAT; and selecting an NTN cell associated with the NTN RAT.
2. The method of claim 1, wherein the first SIB includes an indication that the NTN carrier frequency information is associated with the satellite information for the NTN RAT.
3. The method of claim 2, wherein the indication is a satellite identifier (ID).
4. The method of any of the preceding claims, wherein: the serving cell is a terrestrial network (TN) cell.
5. The method any of the preceding claims, wherein the NTN cell is associated with narrowband (NB) Intemet-of-Things (loT) communication.
6. The method of any of the preceding claims, wherein the second SIB is a SIB type 33 (SIB33).
7. The method of claim 1, 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 thePATENT APPLICATIONAttorney Docket No.: 31730 / 308455-00(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.
8. The method of any of the preceding claims, wherein: the satellite information is a first neighboring satellite information, and the NTN RAT is a first NTN RAT; the method further comprising: receiving, in the serving cell, second neighboring satellite information related to a second NTN RAT.
9. The method of claim 8, wherein the first neighboring satellite information and the second neighboring satellite information are received in the second SIB.
10. A method implemented in a node of a radio access network (RAN), the method comprising: transmitting, in a first system information block (SIB), non-terrestrial (NTN) carrier frequency information for an NTN radio access technology (RAT); and transmitting, in a second SIB, satellite information for the NTN RAT.
11. The method of claim 10, wherein: the first SIB includes a satellite identifier (ID) to identify a satellite to which the satellite information pertains; and the second SIB includes the satellite ID.
12. The method of claim 10 or 11, wherein: the first SIB and the second SIB are transmitted in a terrestrial network (TN) cell.PATENT APPLICATIONAttorney Docket No.: 31730 / 308455-0013. The method of any of claims 10-12, wherein the second SIB is a SIB type 33 (SIB33).
14. The method of any of claims 10-12, wherein: the satellite information is a first neighboring satellite information; the NTN RAT is a first NTN RAT; and the second SIB further includes second neighboring satellite information related to a second NTN RAT.
15. A device comprising: a transceiver; and processing hardware; the device configured to implement a method of any of the preceding claims.
Citation Information
Patent Citations
Satellite assistance information provisioning from a terresterial network
WO2024171051A1