System and method for supporting tracking areas for satellite radio access

Abstract

A technique is described for supporting satellite radio access for user equipment (UE) using fixed tracking areas (TAs). A TA identifier (TAI) is broadcast in a satellite radio cell by a base station to indicate which TAs are covered by the radio cell. The UE can access the radio cell if at least one broadcast TAI is not barred for the UE. The base station provides the TAIs broadcast in the radio cell and the TAIs for the TAs in which the UE is located to a core network node to support access by the UE. The core network node uses the broadcast TAI to determine whether UE access is allowed and uses the broadcast TAI to assign a UE registration area. The UE may forward all broadcast TAIs to a barred TAI list if UE access is denied by the core network node.

Description

Technical Field

[0003] , ,

[0001] Cross - reference to Related Applications This application claims the benefit and priority of U.S. Non - Provisional Application No. 17 / 705,197, filed on March 25, 2022, entitled "Systems and Methods for Supporting Tracking Regions for Satellite Wireless Access"; U.S. Provisional Application No. 63 / 231,239, filed on August 9, 2021, entitled "Systems and Methods for Tracking Region Support with Hard and Soft Tracking Region Updates"; Greek Application No. 20210100552, filed on August 13, 2021, entitled "Systems and Methods for Tracking Region Support with Hard and Soft Tracking Region Updates"; U.S. Provisional Application No. 63 / 252,149, filed on October 4, 2021, entitled "Systems and Methods for Tracking Region Support with Hard and Soft Tracking Region Updates"; Greek Application No. 20210100709, filed on October 18, 2021, entitled "Systems and Methods for Tracking Region Support with Hard and Soft Tracking Region Updates", all of which are assigned to the assignee of this application and are hereby incorporated by reference in their entirety.

Background Art

[0002] Field of Disclosure The various aspects described herein generally relate to wireless communication systems, and more particularly, to accessing a wireless network using communication satellites.

[0003] <00\00014>Description of Related Technologies Wireless communication systems are widely deployed to provide various types of communication content, including voice, video, packet data, messaging, and broadcast. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes called New Radio (NR) systems. These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include a number of base stations or network access nodes, each of which simultaneously supports communication for multiple communication devices, and these may each be referred to as user equipment (UE).

[0004] Standardization is underway to combine satellite-based communication systems with terrestrial wireless communication systems such as 5G New Radio (NR) networks. In such systems, the UE (Underground User) accesses satellites, also known as spacecraft (SV), instead of base stations, while base stations connect to earth stations, also known as ground stations or non-terrestrial network (NTN) gateways, and then connect to the 5G network (e.g., directly or via base stations). The 5G network can treat satellite systems as a different but similar type of radio access technology (RAT) to terrestrial 5G NR.

[0005] Because satellites typically differ from ground base stations in terms of the size of their coverage area, the movement of their coverage area, longer propagation delays, and different carrier frequencies, satellite RATs may require different implementations than ground RATs to support common services to end users. One example of a different implementation is supporting tracking areas across the entire network coverage area. In such cases, it may be desirable to optimize these different implementations and minimize their impact. [Overview of the project]

[0006] This document describes a technique for supporting satellite radio access for user equipment (UEs) using fixed tracking areas (TAs). TA identifiers (TAIs) are broadcast by base stations in satellite radio cells, indicating which TAs are covered by the radio cell. An UE can access a radio cell if at least one broadcast TAI is not blocked for the UE. Base stations support UE access by providing core network nodes with the TAIs broadcast in the radio cell and the TAI for the TA where the UE is located. The core network nodes use the broadcast TAIs to determine whether UE access is permitted and allocate UE registration areas using the broadcast TAIs. If UE access is denied by the core network nodes, the UE may forward all broadcast TAIs to a blocked TAI list.

[0007] In one embodiment, the method is performed by a radio access network (RAN) node that supports satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN), the method comprising broadcasting one or more tracking area (TA) identifiers (TAI) in a satellite radio cell, receiving a non-access layer (NAS) message transmitted by the UE in the satellite radio cell from the user equipment (UE), determining the TA in which the UE is located, and transmitting the NAS message to a core network node, including, along with the NAS message, the TAI for the TA in which the UE is located and one or more TAIs broadcast in the satellite radio cell.

[0008] In one embodiment, a radio access network (RAN) node configured to support satellite radio access of a user device (UE) to a serving public land mobile network (PLMN) includes an external interface configured to communicate wirelessly with network entities, at least one memory, and at least one processor coupled to the external interface, wherein the at least one memory and the at least one processor are configured to broadcast one or more tracked area (TA) identifiers (TAIs) in a satellite radio cell via the external interface, receive non-access layer (NAS) messages from the UE transmitted into the satellite radio cell by the UE via the external interface, determine the TA where the UE is located, and transmit the NAS message to a core network node via the external interface, including the TAI for the TA where the UE is located and one or more TAIs broadcast in the satellite radio cell along with the NAS message.

[0009] In one embodiment, a radio access network (RAN) node configured to support satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN) includes a unit that broadcasts one or more tracking area (TA) identifiers (TAIs) in a satellite radio cell; a unit that receives non-access layer (NAS) messages transmitted by the UE in the satellite radio cell from the UE; a unit that determines the TA in which the UE is located; and a unit that transmits the NAS message to a core network node, including, along with the NAS message, the TAI for the TA in which the UE is located and one or more TAIs broadcast in the satellite radio cell.

[0010] In one embodiment, a non-temporary storage medium includes program code stored thereon, which is operable to constitute at least one processor in a radio access network (RAN) node for supporting satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN), and the program code includes instructions for broadcasting one or more tracked area (TA) identifiers (TAI) in a satellite radio cell, receiving a non-access layer (NAS) message transmitted by the UE in the satellite radio cell from the UE, determining the TA where the UE is located, transmitting the NAS message to a core network node, and including the TAI for the TA where the UE is located and one or more TAIs broadcast in the satellite radio cell together with the NAS message.

[0011] In one embodiment, the method is performed by a core network node to support satellite radio access to a Serving Public Land Mobile Network (PLMN) by a user device (UE), and the method includes receiving a non-access layer (NAS) request message and one or more tracking area (TAI) identifiers (TAI) from a radio access network (RAN) node, determining whether the UE is permitted to access the satellite radio cell based on the TAI broadcast in the satellite radio cell by the RAN node, and sending a NAS acceptance message to the UE in response to the decision that the UE is permitted to access the satellite radio cell, wherein the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include the TAI broadcast in the satellite radio cell by the RAN node and an instruction for the TAI for the TA where the UE is located.

[0012] In one embodiment, a core network node configured to support satellite radio access by user equipment (UE) to a Serving Public Land Mobile Network (PLMN) includes an external interface configured to communicate wirelessly with a network entity, at least one memory, and at least one processor coupled to the external interface, wherein the at least one memory and the at least one processor are configured to receive non-access layer (NAS) request messages and one or more tracked area (TAI) identifiers (TAI) from a radio access network (RAN) node via the external interface, determine whether a user equipment (UE) is permitted to access the satellite radio cell based on the TAI broadcast in the satellite radio cell by the RAN node, and transmit a NAS acceptance message to the UE via the external interface in response to the determination that the UE is permitted to access the satellite radio cell, wherein the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include a TAI broadcast in the satellite radio cell by the RAN node and an instruction for the TAI for the TA where the UE is located.

[0013] In one embodiment, a core network node configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN) by a user device (UE) includes a unit that receives non-access layer (NAS) request messages and one or more tracking area (TA) identifiers (TAIs) from a radio access network (RAN) node, a unit that determines whether the UE is permitted to access the satellite radio cell based on TAIs broadcast in the satellite radio cell by the RAN node, and a unit that, in response to the determination that the UE is permitted to access the satellite radio cell, transmits a NAS acceptance message to the UE, wherein the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include TAIs broadcast in the satellite radio cell by the RAN node and an instruction for a TAI for the TA where the UE is located.

[0014] In one embodiment, a non-temporary storage medium includes program code stored thereon, the program code is operable to constitute at least one processor in a core network node for supporting a user device (UE) satellite radio access to a serving public land mobile network (PLMN), the program code includes instructions to receive a non-access layer (NAS) request message and one or more tracked area (TAI) identifiers (TAI) from a radio access network (RAN) node, to determine whether the UE is permitted to access the satellite radio cell based on the TAI broadcast by the RAN node in the satellite radio cell, and to send a NAS acceptance message to the UE in response to the determination that the UE is permitted to access the satellite radio cell, the NAS request message being sent by the UE to the RAN node in the satellite radio cell, and the one or more TAIs including the TAI broadcast by the RAN node in the satellite radio cell and an instruction for the TAI for the TA where the UE is located.

[0015] In one embodiment, the method is performed by a user device (UE) to support satellite radio access to a Serving Public Land Mobile Network (PLMN), and the method includes receiving a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node, determining whether access to the satellite radio cell is permitted based on the plurality of TAIs, sending a non-access layer (NAS) request message to a core network node via the RAN node in the satellite radio cell in response to the decision that access to the satellite radio cell is permitted, and receiving a NAS response message from the core network node within the satellite radio cell via the RAN node in the satellite radio cell.

[0016] In one embodiment, a user device (UE) configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN) includes a radio transceiver configured to communicate wirelessly with a network entity, at least one memory, and at least one processor coupled to the radio transceiver, wherein the at least one memory and the at least one processor are configured to receive a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node via the radio transceiver, to determine via the radio transceiver whether access to the satellite radio cell is permitted based on the plurality of TAIs, to transmit a non-access layer (NAS) request message within the satellite radio cell to a core network node via the RAN node in response to the decision that access to the satellite radio cell is permitted, and to receive a NAS response message within the satellite radio cell from the core network node via the RAN node via the radio transceiver.

[0017] In one embodiment, a user device (UE) configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN) includes a unit that receives a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node; a unit that determines whether access to the satellite radio cell is permitted based on the plurality of TAIs; a unit that, in response to the decision that access to the satellite radio cell is permitted, transmits a non-access layer (NAS) request message for the satellite radio cell to a core network node via the RAN node; and a unit that receives a NAS response message for the satellite radio cell from the core network node via the RAN node.

[0018] In one embodiment, a non-temporary storage medium includes program code stored thereon, the program code is operable to constitute at least one processor in a user device (UE) for supporting satellite radio access to a Serving Public Land Mobile Network (PLMN), the program code includes instructions to receive a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node, to determine whether access to the satellite radio cell is permitted based on the plurality of TAIs, and in response to the decision that access to the satellite radio cell is permitted, to send a non-access layer (NAS) request message within the satellite radio cell to a core network node via the RAN node, and to receive a NAS response message in the satellite radio cell from the core network node via the RAN node. [Brief explanation of the drawing]

[0019] [Figure 1] Figure 1 shows a diagram of a communication system with a network architecture that includes a transparent spacecraft (SV) capable of supporting satellite access to a wireless network. [Figure 2]FIG. 2 shows a diagram of a communication system of a network architecture having a regenerative SV capable of supporting satellite access to a wireless network. [Figure 3] FIG. 3 shows a diagram of a communication system of a network architecture having a regenerative SV and a split satellite node B (gNB) architecture capable of supporting satellite access to a wireless network. [Figure 4] FIG. 4 shows an SV that generates multi-beams across a region including multiple countries. [Figure 5] FIG. 5 shows a wireless cell generated by an SV across a region including multiple fixed cells. [Figure 6] [[ID=1a2]]FIG. 6 shows the assignment of a wireless cell generated by an SV to a fixed tracking area (TA). [Figure 7] FIG. 7 shows an example of an environment including a wireless cell that includes a tracking area covered by the wireless cell. [Figure 8] FIG. 8 shows an example of an environment including a wireless cell that includes a tracking area covered by the wireless cell, and the wireless cell broadcasts a tracking area identifier (TAI) of some of the tracking areas. [Figure 9] FIG. 9 shows a signaling flow illustrating various messages transmitted between components of a communication network in a procedure for supporting TAI updates. [Figure 10] FIG. 10 is a diagram showing an example of a hardware implementation of a UE configured to support TAI updates as discussed in this specification. [Figure 11] FIG. 11 is a diagram showing an example of a hardware implementation of a core network node configured to support TAI updates as discussed in this specification. [Figure 12] FIG. 12 is a diagram showing an example of a hardware implementation of a network node configured to support TAI updates as discussed in this specification. [Figure 13]FIG. 13 is a flowchart showing an example of a procedure for assisting satellite wireless access by a user device to a PLMN (serving PLMN) performed by a radio access network (RAN) node. [Figure 14] FIG. 14 shows a flowchart of an example of a procedure for supporting satellite wireless access by a user equipment to a serving public land mobile network (PLMN) executed by a core network node. [Figure 15] FIG. 15 shows a flowchart of an example of a procedure for supporting satellite wireless access by a user equipment (UE) to a serving public land mobile network (PLMN) executed by the UE.

[0020] According to some exemplary implementations, like reference numerals in the various drawings indicate like elements. Additionally, multiple instances of an element may be indicated by following the first digit of the element with a letter or a hyphen and a second digit. For example, multiple instances of element 102 may be indicated as 102-1, 102-2, 102-3, etc. When referring to such an element using only the first digit, any instance of the element should be understood (e.g., element 102 in the previous example refers to elements 102-1, 102-2, 102-3).

Mode for Carrying Out the Invention

[0021] Satellites, also called spacecraft (SV) or communications satellites, can be used in communication systems, for example, to relay communication signals between a gateway and one or more UEs using a gateway and one or more satellites. UEs may have access to satellites (instead of ground base stations) that can be connected to earth stations (ES), also called ground stations or non-terrestrial network (NTN) gateways. The earth station then connects to elements within the network, such as modified base stations (without ground antennas) or network nodes of the core network (CN). These elements provide access to other elements within the network and ultimately to entities outside the network, such as internet web servers and other user devices.

[0022] The rationale for satellite access in UEs may include ubiquitous outdoor coverage for both users and mobile network operators (MNOs). For example, in many countries, including the United States, unavailable or insufficient cellular coverage is a common problem. Furthermore, even where cellular coverage is normally good, cellular access is not always possible. For example, cellular access can be hindered by traffic congestion, physical obstacles, local cellular outages caused by weather (e.g., disease or tornadoes), or local power outages. Satellite access to cellular networks could provide new, independent access available anywhere outdoors. Current satellite-enabled phones for low orbit (LEO) SVs may be about the same size as cellular smartphones, so mobile NR support via satellite-enabled phones would not require a significant increase in phone size. In addition, satellite-enabled smartphones could help boost mobile phone sales and increase operator revenue. For example, potential users include those with limited or no cellular access, those who need backup when cellular access is unavailable, those involved in public safety, or those who require (nearly) 100% reliable mobile communication. Additionally, some users may desire reliable emergency services (e.g., E911) for situations such as remote medical emergencies or vehicle breakdowns.

[0023] Satellite access offers several advantages. For example, it can reduce infrastructure costs for mobile network operators (MnOs). MNOs can use satellite access to reduce the number of ground base stations, such as GN NodeBs (also known as gNBs), and backhaul deployments in sparsely populated areas. Satellite access can also be used to overcome internet congestion in a given country. Furthermore, satellite access can provide diversification for spacecraft operators (SVOs). For instance, 5G NR satellite access could provide a new revenue stream for SVOs that previously offered fixed internet access.

[0024] A terrestrial network (TN) using ground cellular base stations can support relatively small fixed radio cells (e.g., 100 meters to 10 km from one side to the other) that have precisely known geographical coverage areas. This allows the TN operator to subdivide the entire service area into fixed tracking areas (TAS) consisting of multiple fixed radio cells. Using tracking areas, the operator can control user access (e.g., define specific geographical areas accessible only to certain users) and charge users based on their approximate location. Radio cells enable operators to have fine-grained access control and fine-grained charge identification and can be used for routing purposes and to support radio emergency alerts (WEAs). For example, a request to set up an emergency call sent to the TN by a UE may include the UE's current serving radio cell, which the TN can use to route the emergency call to a public safety response point (PSAP), providing service within the area of ​​the serving radio cell. In addition, if a WEA message needs to be broadcast to all UEs currently located in a predefined target area, the TN may instruct that the WEA message be broadcast only within radio cells whose coverage area is within or partially within the target area.

[0025] Satellite access to UEs is defined by the Third Generation Partnership Project (3GPP®). The primary objective of defining satellite access is to minimize or avoid new impacts on CNs. One way to avoid or minimize impacts on CNs is to maintain support for fixed tracking areas (TAs). Fixed TAs are geographically defined by operations and maintenance (O&M) as geographical definitions are provided to base stations (eNBs and / or gNBs, etc.) and CNs. The base station then determines the fixed TA where the UE is located based on the current geographical location of the UE and may provide the identifier (ID) of this TA to network nodes within the CN, such as Access and Mobility Management Functions (AMFs), when a signaling connection for the UE is established. The network nodes may later use the fixed TA information to send paging messages to the UE via one or more base stations. The use of fixed TAs has the advantage of mitigating or minimizing new impacts on CNs.

[0026] Figure 1 shows an example of a network architecture 100 capable of supporting satellite access using 5G New Radio (NR). Figure 1 shows a network architecture with a transparent spacecraft (SV). The transparent SV may implement frequency conversion and radio frequency (RF) amplifiers in both the uplink (UL) and downlink (DL) directions and may accommodate analog RF repeaters. The transparent SV may, for example, receive uplink (UL) signals from all serviced UEs and redirect the combined signal DL to the earth station without demodulating or decoding the signal. Similarly, the transparent SV may receive UL signals from the earth station and redirect the signal DL to the serviced UE without demodulating or decoding the signal. However, the SV may frequency convert the received signal and amplify and / or filter the received signal before transmitting the signal.

[0027] The network architecture 100 includes a number of UEs 105, a number of SVs 102-1 to 102-3 (collectively referred to herein as SV102), a number of non-terrestrial network (NTN) gateways 104-1 to 104-3 (collectively referred to herein as NTN gateways 104) (sometimes simply referred to herein as gateways 104, earth stations 104, or ground stations 104), and a number of NR node B (gNB) 106-1 to 106-3 (collectively referred to herein as gNB106) that can communicate with the UEs via the SVs and are part of the next-generation (NG) radio access network (RAN) (NG-RAN) 112. Note that the term gNB generally refers to an extended gNB that supports an SV, and may be called a gNB (e.g., in 3GPP), or may be called a satellite node B (sNB). The network architecture 100 is illustrated to further include numerous components of a fifth-generation (5G) network, including 5G core networks (5GCNs) 110-1 and 110-2 (collectively referred to herein as 5GCN110). 5GCN110 may also be public land mobile networks (PLMNs), which may be located in the same or different countries. Figure 1 shows various components within 5GCN1 110-1 that may operate with NG-RAN112. It should be understood that 5GCN2 110-2 and other 5GCNs may include identical, similar, or different components and associated NG-RANs, which are not illustrated in Figure 1 to avoid unnecessary obfuscation. 5G networks may also be called new radio (NR) networks. NG-RAN112 may be referred to as 5G RAN or NR RAN, and 5GCN110 may be referred to as the NG core network (NGC).

[0028] Network architecture 100 further utilizes information from spacecraft (SV) 190 for satellite positioning systems (SPS), including the Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Global Navigation Satellite System (GNSS) such as Galileo or Beidou, or several other local or regional SPS such as the Indian Regional Navigation Satellite System (IRNSS), European Geostationary Navigation Overlay Service (EGNOS), or Wide Area Augmentation System (WAAS), all of which may be referred to herein as GNSS. Note that SV 190 acts as a navigation SV and is separate from SV 102, which acts as a communications SV. However, it is not excluded that a part of SV 190 may act as part of SV 102, and / or a part of SV 102 may also act as part of SV 190. In some implementation examples, for example, SV 102 may be used for both communications and positioning. Additional components of network architecture 100 are described below. Network architecture 100 may include additional or alternative components.

[0029] In the network architecture 100 having a network architecture with transparent SVs as illustrated in Figure 1, permitted connections allow gNB 106 to access multiple earth stations 104 and / or multiple SVs 102. For example, gNB 106, illustrated by gNB 106-3, may also be shared by multiple PLMNs (5GCNs 110), which may all be in the same country or, in some cases, different countries, and earth station 104, illustrated by earth station 104-2, may also be shared by multiple gNB 106s.

[0030] Figure 1 provides only generalized examples of various components, and it should be noted that any or all of the components may be used as appropriate, and each of them may be duplicated or omitted as needed. Specifically, although only three UEs 105 are illustrated, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the network architecture 100. Similarly, the network architecture 100 may include a larger number (or fewer) of SVs 190, SVs 102, earth stations 104, gNBs 106, NG-RANs 112, 5GCNs 110, external clients 140, and / or other components. The illustrated connections connecting the various components within the network architecture 100 may include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or radio access, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0031] Figure 1 illustrates a 5G-based network, but similar network implementations and configurations can be used to support satellite radio access (e.g., using SV102) for other communication technologies such as 3G and 4G Long Term Evolution (LTE).

[0032] The UE105 is a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location (SUPL) enabled terminal (SET), and / or may be referred to as such, or by any other name. Furthermore, the UE105 may be compatible with mobile phones, smartphones, laptops, tablets, PDAs, tracking devices, navigation devices, Internet of Things (IoT) devices, or any other portable or mobile device. Typically, though not always, the UE105 may support wireless communication using one or more radio access technologies (RATs), such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA®), LTE, High-Speed ​​Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), Bluetooth® (BT), Global Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR) (e.g., using NG-RAN 112, 5GCN 140). The UE105 may also support wireless communication using wireless local area networks (WLANs), which can connect to other networks (e.g., the Internet) using digital subscriber lines (DSL) or packet cables. The UE105 further supports wireless communication using spacecraft such as the SV102. The use of one or more of these RATs may enable UE105 to communicate with an external client 140 (via an element of 5GCN110 not shown in Figure 1, or possibly via a Gateway Mobile Location Center (GMLC) 126).

[0033] UE105 may include a single entity or multiple entities in a personal area network where, for example, a user may have access to audio, video and / or data I / O devices and / or body sensors, as well as separate wireline or wireless modems.

[0034] UE105 may support positioning using signals and information from spacecraft 190 in SPS such as GPS, GLONASS, Galileo, or Beidou, or other local or regional SPS such as IRNSS, EGNOS, or WAAS, all of which are commonly referred to herein as GNSS. Positioning using SPS is based on measuring the propagation delay time of SPS signals broadcast from a number of orbiting satellites to an SPS receiver in UE105. Once the SPS receiver measures the signal propagation delay of each satellite, it can determine the range to each satellite and, using the measured range and the known positions of the satellites, determine precise navigation information such as the 3D position, velocity, and time of the SPS receiver. Positioning methods that may be supported using SV190 may include assisted GNSS (A-GNSS), real-time kinematic (RTK), precise point positioning (PPP), and differential GNSS (DGNSS). Positioning may also be assisted using information and signals from SV 102. Furthermore, the UE 105 may further support positioning using ground positioning methods such as observed time of arrival difference (ODOA), extended cell ID (ECID), round-trip signal propagation time (RTT), multi-cell RTT, angle of arrival (AOA), time of departure (AOD), time of arrival (TOA), receive-transmit time difference (RX-TX), and / or other positioning methods.

[0035] The location estimation of UE105 may be referred to as geodetic location, location, location estimate, location fixed, fixed, location, location estimate, or location fixed, and may be geographical, and therefore provides location coordinates (e.g., latitude and longitude) of UE105 that may or may not include elevation components (e.g., elevation above sea level, height or depth from the ground, floor level or basement level). Alternatively, the location of UE105 may be expressed as a city location (e.g., postal address, or designation of a destination or small area within a building, such as a specific room or floor). The location of UE105 may also be expressed as an area or volume (defined in either a geographical or civic form) where UE105 is expected to be located with some probability or confidence (e.g., 67%, 95%, etc.). The location of UE105 may also be a relative location, including distance and direction defined relative to some origin at a known location that can be defined, for example, geographically, in civil terms, or by referring to a point, area, or volume shown on a map, floor plan, or building plan, or relative X, Y (and Z) coordinates. In the descriptions contained herein, the use of the term location may include any of these variations unless otherwise indicated. When calculating the location of a UE, it is common to solve for local x, y, and possibly z coordinates, and then, if necessary, convert the local coordinates to absolute coordinates (for example, latitude, longitude, and altitude above or below mean sea level).

[0036] UE105 is configured to communicate with 5GCN110 via SV102, earth station 104, and gNB106. An NG-RAN corresponding to 5GCN110 may include one or more gNBs 106, as shown in NG-RAN 112. NG-RAN112 may further include a number of ground base stations, e.g., gNBs (not shown), that cannot communicate with the UE via SV102 (not shown). A pair of ground and / or satellite base stations, e.g., a gNB and gNB106-1 in NG-RAN112, may be connected using a ground link—e.g., directly or indirectly via another gNB or gNB106—and communicate using an Xn interface. Access to the 5G network is provided to UE105 via radio communication between each UE105 and a serving gNB106, via SV102 and earth station 104. gNBs106 may provide radio communication access to 5GCN110 on behalf of each UE105 using 5G NR. 5G NR radio access, also known as NR radio access or 5G radio access, is sometimes defined by the Third Generation Partnership Project (3GPP).

[0037] The base station (BS) in NG-RAN112 shown in Figure 1 may also include a next-generation evolved node B, also known as an ng-eNB, or alternatively, a next-generation evolved node B. The ng-eNB may be connected to one or more gNB106 and / or gNBs in NG-RAN112—for example, directly or indirectly via other gNB106, gNBs and / or other ng-eNBs. The ng-eNB may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE105.

[0038] gNB106 may be referred to as gNB or by other names such as “satellite node” or “satellite access node”. gNB106 may be based on a ground gNB that is not identical to a ground gNB but has additional capabilities. For example, gNB106 may terminate the radio interface and associated radio interface protocols to UE105, transmit DL signals to UE105, and receive UL signals from UE105 via SV102 and earth station (ES)104. gNB106 may support signaling connectivity and voice and data bearer for UE105 and support handover of UE105 between different radio cells, between different SV102 and / or between different gNB106 for the same SV102. In some systems, gNB106 may be referred to as gNB or augmented gNB. GNB106 may be configured to manage the moving radio beam (for LEO SV) and associated mobility of UE105. gNB106 can assist with the handover (or transfer) of SV102 between different earth stations 104, between different gNBs 106, and between different countries. gNB106 may conceal or obscure certain aspects of the connected SV102 from 5GCN110 by interface with 5GCN110 in the same or similar manner as a ground-based gNB, thereby avoiding the need for 5GCN110 to maintain configuration information of SV102 or perform mobility management associated with SV102. gNB106 can further assist with the sharing of SV102 across multiple countries. gNB106 may communicate with one or more earth stations 104, as exemplified by gNB106-3 communicating with earth stations 104-2 and 104-3, for example. gNB 106 may be separate from base station 104. gNB106 may alternatively include one or more earth stations 104, or be combined with one or more earth stations 104, for example, using a segmented architecture. For example, in a segmented architecture, gNB106 may include a central unit, and the earth stations may act as distributed units (DUs). gNB106 may typically be fixed to the ground in transparent SV operation.In one implementation, one gNB106 can be physically combined with or physically connected to one earth station 104 to reduce complexity and cost.

[0039] Earth station 104 may be shared by multiple gNBs 106 and may communicate with UE 105 via SV 102. Earth station 104 may be dedicated to only one SVO and one associated constellation of SV 102, and therefore may be owned and managed by the SVO. Earth station 104 may be contained within a gNB 106, for example, as a gNB-DU within gNB 106, which may occur if the same SVO or the same MNO owns both the gNB 106 and the contained earth station 104. Earth station 104 may communicate with SV 102 using control and user plane protocols that may be exclusive to the SVO. The control and user plane protocols between Earth Station 104 and SV102 (i) establish and release the communication link from Earth Station 104 to SV102, including authentication and cryptography; (ii) update the SV software and firmware; (iii) perform the operation and maintenance (O&M) of the SV; (iv) control the radio beam (direction, power, on / off state, etc.) and the mapping between the radio beam and the Earth Station's uplink (UL) and downlink (DL) payloads; and (v) assist in the handoff of SV102 or radio cells to another Earth Station 104.

[0040] As noted, Figure 1 depicts a node configured to communicate according to the 5G NR communication protocol for NG-RAN112, but nodes configured to communicate according to other communication protocols may be used, such as the LTE protocol for Evolutionary Universal Mobile Communications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), the Narrow Band Internet of Things (NB-IoT) protocol for E-UTRAN supporting low-bandwidth access using a variant of LTE, or the IEEE 802.11x protocol for WLAN. For example, in a 4G Evolved Packet System (EPS) providing LTE radio access to UE105, the RAN may comprise E-UTRAN, which may comprise base stations including evolved node B (eNB) supporting LTE radio access. The core network for the EPS may comprise an Evolved Packet Core (EPC). The EPS may then comprise E-UTRAN and EPC, where E-UTRAN corresponds to NG-RAN112 and EPC corresponds to 5GCN110 in Figure 1. The methods and techniques described herein for supporting fixed TAs may be applicable to other such networks.

[0041] gNB106 in NG-RAN112 may communicate with AMF122 in 5GCN110, which may communicate with Position Management Function (LMF)124 for positioning functions. For example, gNB 106 may provide an N2 interface to AMF 122. The N2 interface between gNB106 and 5GCN110 may be identical or similar to the N2 interface supported between the ground gNB and 5GCN110 for ground NR access by UE105, and may use the Next Generation Application Protocol (NGAP) as defined in 3GPP Technical Specification (TS) 38.413 between gNB106 and AMF122. AMF122 may support the mobility of UE105, including radio cell changes and handovers, and may participate in signaling connections to UE105, and optionally support data and voice bearers for UE105. The LMF124 may support the positioning of the UE105 when the UE accesses the NG-RAN112, and may support positioning procedures / methods such as A-GNSS, OTDOA, RTK, PPP, DGNSS, ECID, AOA, AOD, multi-cell RTT, and / or other positioning procedures, including positioning procedures based on communication signals from one or more SV102s. The LMF124 may also process location service requests for the UE105 received, for example, from the AMF122 or the Gateway Mobile Location Center (GMLC)126. The LMF124 may be connected to the AMF122 and / or the GMLC126. In some embodiments, a node / system implementing the LMF124 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobile Location Center (E-SMLC). In some embodiments, at least part of the positioning function (including the derivation of the position of UE105) may be performed in UE105 (for example, using signal measurements obtained by UE105 for signals transmitted by the support data provided to UE105 by SV102, SV190, gNB, and LMF124).

[0042] GMLC126 may support location requests for UE105 received from external client 140 and may forward such location requests to AMF122 for forwarding to LMF124 by AMF122. The location response from LMF124 (including, for example, the location estimation of UE105) may similarly be returned to GMLC126 via AMF122, and GMLC126 may then return the location response (including, for example, the location estimation) to external client 140. Although GMLC126 is shown connected only to AMF122 in Figure 1, in some embodiments it may be connected to both AMF122 and LMF124, and may support direct communication between GMLC126 and LMF124, or indirect communication, for example, via AMF122.

[0043] The Network Exposure Function (NEF) 128 may be included in the 5GCN 110, for example, connected to the GMLC 126 and AMF 122. In some embodiments, the NEF 128 may be connected to communicate directly with an external client 140. The NEF 128 may support the secure disclosure of capabilities and events regarding the 5GCN 110 and UE 105 to the external client 140, and enable the secure provision of information from the external client 140 to the 5GCN 110.

[0044] The User Plane Function (UPF) 130 may support voice and data bearers for the UE 105 and may enable voice and data access for the UE 105 to other networks such as the Internet. The UPF 130 may be connected to the gNB 106 and the gNB. The functions of the UPF 130 include an external protocol data unit (PDU) session point for interconnection to the data network, routing and forwarding of packets (such as Internet Protocol (IP)), the user plane portion of packet inspection and policy rule enforcement, user plane quality of service (QoS) processing, downlink packet buffering, and downlink data notification triggers. The UPF 130 may be connected to a SUPL positioning platform (SLP) 132 to enable support for positioning the UE 105 using Secure User Plane Positioning (SUPL). The SLP 132 may be further connected to or accessible from an external client 140.

[0045] As shown in the diagram, a session management function (SMF) 134 is connected to the AMF 122 and UPF 130. The SMF 134 may have the ability to control both local and central UPFs within a PDU session. The SMF 134 can manage the establishment, modification, and release of PDU sessions for the UE 105, perform IP address assignment and management for the UE 105, act as a Dynamic Host Configuration Protocol (DHCP) server for the UE 105, and select and control the UPF 130 on behalf of the UE 105.

[0046] The external client 140 may be connected to the core network 110 via GMLC 126 and / or SLP 132, and in some embodiments, via NEF 128. The external client 140 may optionally be connected to the core network 110 and / or a location server (e.g., SLP, i.e., outside 5GCN 110) via the internet. The external client 140 may be connected to UPF 130 directly (not shown) or via the internet. The external client 140 may be a user device such as a server, web server, personal computer, or UE.

[0047] The Location Search Function (LRF) 125 is connected to the GMLC 126 as shown in the diagram, and in some embodiments, it may be connected to the SLP 132 as defined in 3GPP Technical Specification (TS) 23.167. The LRF 125 may perform the same or similar functions as the GMLC 126 with respect to receiving and responding to location requests from an external client 140 corresponding to a Public Safety Answering Point (PSAP) that supports emergency calls from the UE 105. One or more of the GMLC 126, LRF 125, and SLP 132 may be connected to the external client 140 via another network, such as the Internet.

[0048] The AMF122 typically supports the mobility of the UE105, including network access and registration by the UE105, radio cell changes and handovers, and may participate in signaling connections to the UE105 and, optionally, support for the UE105's data and voice bearers. The role of the AMF122 may be to register the UE during the registration process, as discussed herein. The AMF122 may page the UE105, for example, by sending paging messages through one or more radio cells within the tracking area where the UE105 is located.

[0049] The network architecture 100 may be associated with or connected to a spacecraft (SV) 190 for a Global Navigation Satellite System (GNSS) such as GPS, GLONASS, Galileo, or Beidou, or other local or regional satellite positioning systems (SPS) such as IRNSS, EGNOS, or WAAS. UE 105 may obtain positional measurements from signals transmitted by SV 102, which enables UE 105 to determine its position estimate or obtain a position estimate for UE 105 from a location server in 5GCN 110, for example, LMF 124. For example, UE 105 may forward the positional measurements to a location server to calculate and return a position estimate. The UE105 (or LMF124) obtains its position estimate using positioning methods such as GPS, Assisted GPS (A-GPS), Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (ECID), Multi-cell RTT, Wireless Local Area Network (WLAN) positioning (e.g., using signals transmitted by an IEEE 802.11 WiFi access point), sensors on the UE105 (e.g., inertial sensors), or a (hybrid) combination of these. The UE 105 may use its position estimate during registration.

[0050] As noted, while the network architecture 100 is described in relation to 5G technology, the network architecture 100 may be implemented to support other communication technologies used to support and interact with mobile devices such as the UE105, e.g., GSM, WCDMA, LTE, etc. (e.g., implementing voice, data, positioning, and other functionalities). In some such embodiments, the 5GCN110 may be configured to control different air interfaces. For example, in some embodiments, the 5GCN110 may be connected to a WLAN directly or using a non-3GPP interworking function within the 5GCN110 (N3IWF, not shown in Figure 1). For example, the WLAN may support IEEE802.11 WiFi access for the UE105 and may have one or more WiFi APs. Here, the N3IWF may connect to the WLAN and other elements within the 5GCN110, such as the AMF122.

[0051] Figure 2 shows a diagram of a network architecture 200 capable of supporting satellite access using 5G New Radio (NR) as discussed herein. The network architecture shown in Figure 2 is similar to that shown in Figure 1, for example, having similar or identical specified elements. However, Figure 2 illustrates a network architecture having regenerated SV202-1, 202-2, and 202-3 (collectively referred to as SV202), in contrast to the transparent SV102 shown in Figure 1. Unlike the transparent SV102, the regenerated SV202 includes an onboard gNB202 (for example, including the functional capabilities of the gNB) and is sometimes referred to herein as SV / gNB202. NG-RAN112 is illustrated as including SV / gNB202. In this specification, reference to gNB202 is used when referring to the SV / gNB202 function related to communication with UE105 and 5GCN110, while reference to SV202 is used when referring to the SV / gNB202 function related to communication with earth station 104 and UE105 on physical radio frequencies. However, there is no precise distinction between SV202 and gNB202.

[0052] The onboard gNB202 may perform many of the same functions as the gNB106, as described above. For example, the gNB202 may terminate the radio interface and associated radio interface protocols to the UE105, transmit DL signals to the UE105, and receive UL signals from the UE105, which may include encoding and modulation of the transmitted signals, as well as demodulation and decoding of the received signals. The gNB202 may also support signaling connections and voice and data bearers to the UE105, and may support handover of the UE105 between different radio cells and between different gNB202s to the same gNB202. The gNBs202 may assist with handover (or transfer) of the SV202 between different earth stations 104, between different 5GCNs 110, and between different countries. gNBs202 may conceal or obscure certain aspects of SV202 from 5GCN110 by interface with 5GCN110, for example, in the same or similar manner as a ground-based gNB. This may further facilitate the sharing of SV202 across multiple countries. gNB202 may communicate with one or more earth stations 104 and one or more 5GCN110 via earth station 104. In some embodiments, gNB202 may communicate directly with other gNB202 using an interstellar link (ISL) (not shown in Figure 2), which may support Xn interfaces between any pair of gNB202.

[0053] In LEO SV, the SV / gNB202 needs to manage mobile radio cells that have coverage in different countries at different times. Earth station 104 may be directly connected to 5GCN110 as shown in the figure. For example, as shown in the figure, earth station 104-1 may be connected to AMF122 and UPF130 of 5GCN110-1, while earth station 104-2 may be similarly connected to 5GCN110-1 and 5GCN2110-2, and earth station 104-3 may be connected to 5GCN2110-2. Earth station 104 may be shared by multiple 5GCN110 if, for example, earth station 104 is limited. For example, in some embodiments (shown by dotted lines), earth station 104-2 may be connected to both 5GCN110-1 and 5GCN2110-2. 5GCN110 may need to be aware of the SV202's coverage area in order to page UE105 and manage handovers. Therefore, a network architecture with regenerative SVs may have greater impact and complexity with respect to both gNB202 and 5GCN110 than a network architecture with transparent SVs shown in Figure 1.

[0054] Figure 3 shows a diagram of a network architecture 300 capable of supporting satellite access using 5G New Radio (NR) as discussed herein. The network architecture shown in Figure 3 is similar to those shown in Figures 1 and 2, such that the specified elements are similar or identical. However, in contrast to the transparent SV102 shown in Figure 1, Figure 3 illustrates a network architecture having a partitioned architecture for regenerated SV302-1, 302-2, and 302-3 (collectively referred to as SV302) and gNBs. The gNB307 includes a central unit and is sometimes referred to as gNB-CU307, and the regenerated SV302, unlike the transparent SV102, includes an onboard gNB distributed unit (gNB-DU)302 and is sometimes referred to herein as SV / gNB-DU302. References to gNB-DU302 are used herein when referring to the SV / gNB302 function related to communication with UE105 and gNB-CU307, while references to SV302 are used when referring to the SV / gNB-DU302 function related to communication with earth station 104 and UE105 at the physical radio frequency level. However, there is no precise distinction between SV302 and gNB-DU302.

[0055] Each gNB-DU302 communicates with one ground-based gNB-CU307 via one or more earth stations 104. One gNB-CU307 performs functions together with one or more gNB-DU302 communicating with the gNB-CU307 and may use an internal communication protocol similar to or identical to a ground-based gNB having a segmented architecture as described in 3GPP TS 38.401. Here, the gNB-DU302 corresponds to, or performs similar or identical functions to, a ground-based gNB distributed unit (gNB-DU) as defined in TS38.401, while the gNB-CU307 corresponds to, or performs similar or identical functions to, a ground-based gNB central unit (gNB-CU) as defined in TS38.401. For example, gNB-DU302 and gNB-CU307 may communicate with each other using the F1 Application Protocol (F1AP) as defined in 3GPP TS 38.473, and together they may perform some or all of the same functions as gNB106 or gNB202 as described above. To simplify references to different types of gNBs, in the following description, gNB-DU302 may be referred to as gNB302 (without the "DU" label), and gNB-CU307 may be referred to as gNB307 (without the "CU" label).

[0056] The gNB-DU302 may terminate the radio interface and associated low-level radio interface protocols to the UE105, transmit DL signals to the UE105, and receive UL signals from the UE105, which may include coding and modulation of the transmitted signals, as well as demodulation and decoding of the received signals. The gNB-DU302 may support and terminate the radio link control (RLC), medium access control (MAC), and physical (PHY) protocol layers for the NR radio frequency (RF) interface to the UE105, as defined in 3GPP TS38.201, 38.202, 38.211, 38.212, 38.213, 38.214, 38.215, 38.321, and 38.322. The operation of the gNB-DU302 is partially controlled by the associated gNB-CU307. A single gNB-DU307 may support one or more NR radio cells for the UE105. The gNB-CU307 may support and terminate the Radio Resource Control (RRC), Packet Data Convergence (PDCP), and Service Data Protocol (SDAP) for the NR RF interface to the UE105, as defined in 3GPP TS38.331, 38.323, and 37.324, respectively. The gNB-CU307 may also be divided into separate control plane (gNB-CU-CP) and user plane (gNB-CU-UP) portions, where the gNB-CU-CP communicates with one or more AMF122s in one or more 5GCN110s using the NGAP protocol, and where the gNB-CU-UP communicates with one or more UPF130s in one or more 5GCN110s using the General Packet Radio System (GPRS) Tunneling Protocol (GTP) User Plane Protocol (GTP-U), as defined in 3GPP TS29.281.The gNB-DU302 and gNB-CU307 communicate via the F1 interface to support control plane signaling for the UE105 using the Internet Protocol (IP), Stream Control Transmission Protocol (SCTP), and F1 Application Protocol (F1AP) protocols, and to support user plane data transfer for the UE using the IP, User Datagram Protocol (UDP), PDCP, SDAP, GTP-U, and NR User Plane Protocol (NRUPP) protocols.

[0057] The gNB-CU307 may communicate with one or more other gNB-CU307s and / or one or more other ground gNBs using a ground link to support Xn interfaces between any pair of gNB-CU302s and / or between any gNB-CU307 and any ground gNB.

[0058] Together with the gNB-CU307, the gNB-DU302 (i) supports signaling connectivity and voice and data bearers to UE105, (ii) supports handover of UE105 between different radio cells and between different gNB-DU302s for the same gNB-DU302, and (iii) assists with handover (or transfer) of SV302 between different earth stations 104, different 5GCN110s, and different countries. The gNB-CU307 may, for example, conceal or obscure certain aspects of the SV302 from 5GCN110 by interfaceing to 5GCN110 in the same or similar manner as the gNB. The gNB-CU307 may further assist in the sharing of SV302 across multiple countries.

[0059] In network architecture 300, a gNB-DU302 that can communicate with any gNB-CU307 and connect from there, along with the LEO SV302, may be connected to a fixed gNB-CU307 that does not change over time and can reduce the difficulty of paging the UE105. For example, the 5GCN110 may not need to know which SV / gNB-DU302 is needed to page the UE105. A network architecture with a regenerative SV302 having a segmented gNB architecture can thereby reduce the impact of the 5GCN110 at the expense of additional impact on the gNB-CU307.

[0060] While supporting satellite access to wireless networks, SV 102 / 202 / 302 can transmit radio beams (also simply called "beams") across multiple countries. For example, a beam transmitted by SV102 / 202 / 302 can overlap with two or more countries. However, sharing a beam with two or more countries can introduce complex issues. For instance, if a beam is shared by two or more countries, earth station 104 and gNB106 / 202 / 302 / 307 in one country must support UE105 access from the other country. Sharing a beam across multiple countries can introduce security issues regarding the privacy of both data and voice. Furthermore, sharing an SV beam across multiple countries can lead to regulatory conflicts. For example, regulatory services in a first country, including WEA, lawful interception (LI), and emergency (EM) calls, may require support from gNB106 / 202 / 307 and earth station 104 in a second country that shares the same SV beam.

[0061] Figure 4 illustrates, as an example, SV102, 202, and 302, which generate multiple beams identified as beams B1, B2, B3, B4, B5, and B6 across a region 400 that includes portions of multiple countries, e.g., countries A, B, and C. If each beam is assigned to only one country, beams B1, B3, and B5 can be assigned to country A, beams B4 and B6 to country B, and beam B2 to country C.

[0062] In one implementation, individual beams may be assigned to a single country by controlling or maneuvering the beam. Non-geostationary Earth orbiting (NGEO) SVs have a moving coverage region, but the relative beam direction moves via a controllable antenna array, remaining in one country or staying almost there, which is sometimes called a “steerable beam.” For example, beam coverage may move slowly within one country after, for example, SV102, 202, 302 are transferred to a new earth station 104 or a new gNB106 or 307, and then jump into a new country.

[0063] Figure 5 shows radio cells generated by SV102, 202, and 302 on region 500 where fixed cells 502 and fixed tracking regions 506 are used. A radio cell may contain a single beam or multiple beams; for example, all beams within a radio cell may use the same frequency, or a radio cell may have one beam for each frequency in a different set of frequencies. For example, beams B1, B2, and B3 may support three separate radio cells (one beam per radio cell), or they may collectively support one radio cell (e.g., radio cell 504 shown by the dotted line). Preferably, the radio cells cover a contiguous region.

[0064] Radio beams and radio cells generated by SV102, 202, and 302 may not align with cells used by terrestrial radio networks, such as 5GCN110 terrestrial cells or LTE terrestrial cells. For example, in urban areas, radio beams or radio cells generated by SV102, 202, and 302 may overlap with many 5GCN terrestrial cells. When supporting satellite access to the radio network, radio beams and radio cells generated by SV102, 202, and 302 may be hidden from 5GCN110.

[0065] As illustrated in Figure 5, region 500 includes numerous Earth-fixed cells 502 and fixed tracking regions (TAs) such as TA 506. Fixed cells are sometimes referred to as "virtual cells," "mapping cells," or "geographic cells," rather than "real cells" used for, for example, terrestrial NR and LTE access. Fixed cells, such as fixed cell 502, have a fixed geographic coverage region, which may be defined by the PLMN operator. For example, the coverage region of a fixed cell or fixed TA may include the interior of a circle, ellipse, or polygon. The coverage region is fixed relative to the Earth's surface and does not change over time, unlike the coverage region of radio cells, which normally change over time in low Earth orbit (LEO) or medium Earth orbit (MEO) SVs. Fixed cell 502 may be handled by the same CN (e.g., 5GCN110) as real cells that support terrestrial access (e.g., using NR or LTE). A group of fixed cells 502 may define a fixed TA 506, which can be handled by the same CN (e.g., 5GCN110) as the TA defined for ground access (e.g., using NR or LTE). Fixed cells and fixed TAs used for satellite radio access can be handled by the CN (e.g., 5GCN110) and can support UE105's mobility management and regulatory services with minimal new impact.

[0066] In a regenerative SV202 having a non-divided architecture such as in network architecture 200, each radio cell may remain in the same SV202 and may have a mobile coverage area supporting different 5GCN110 at different times.

[0067] In transparent SV102 and regenerative SV302 for segmented architectures such as network architectures 100 and 300, each radio cell may be assigned to and controlled by one gNB106 or 307 on behalf of one or more PLMNs in a country. In the case of geostationary Earth orbit (GEO) SV102 / 302, the assignment to a gNB106 / 307 may be permanent or temporary. For example, the assignment may be changed daily to accommodate peak traffic occurring at different times in different parts of the SV 102 / 302 radio footprint, or it may be changed over a long period to accommodate changing regional traffic demands. In the case of non-geostationary (NGEO) SV 102 / 302, the assignment may last for a short time (e.g., just 5-15 minutes). The non-permanent radio cell may then be transferred to a new gNB106 / 307 as needed (e.g., when access to NGEO SV 102 / 302 is transferred to a new gNB106 / 307). Each gNB106 / 307 may have a fixed geographical coverage area, for example, including multiple fixed cells 502 and fixed TAs. A radio cell for the first NGEO SV102 / 302 may be transferred from the first gNB106 / 307 to the second gNB106 / 307 when it moves to (or thereafter) the fixed coverage area of ​​the second gNB106 / 307. Prior to this transfer, UE105s that access the radio cell in a connected state may move to the new radio cell for the first gNB106 / 307, or they may be handed off to the second gNB106 / 307 as part of the transfer of the radio cell. The SV102 / 302 can be accessed from only one gNB106 / 307, or from multiple gNB106 / 307, possibly from different countries. In one embodiment, the SV102 / 302 may be assigned to multiple gNB106 / 307s by dividing the radio cells generated by the SV102 / 302 among different gNB106 / 307s. The radio cells can then be forwarded to new gNB106 / 307s (and new countries) in response to the movement of the SV 102 / 302 or changes in traffic demand.Such embodiments may represent a form of soft handoff where the transfer of SV102 / 302 from one gNB106 / 307 to another occurs incrementally across the wireless cells, rather than all at once.

[0068] Figure 6 shows an example of the assignment of radio cells, e.g., cell 1 and cell 2, generated by one or more SV102, 202, 302 across region 600. As shown in the figure, region 600 includes a number of fixed TAs, e.g., TA1 to TA15, where TA4, TA5, TA8, and TA9 are assigned to gNB1 (which may be gNB106, gNB202, or gNB307, not shown), and TA12, TA13, TA14, and TA15 are assigned to gNB2 (which may be another gNB106, 202, or 307, not shown). In one embodiment, a wireless cell can be considered to support a fixed TA if the wireless cell is entirely within a TA (e.g., cell 2 within TA12), if the TA is entirely within a wireless cell (e.g., TA4 within cell 1), or if the overlap of the wireless cell and the TA area exceeds a predetermined threshold fraction of the total area of ​​the wireless cell or the total area of ​​the TA (e.g., cell 1 overlaps with TA1, TA3, TA5, TA8, or TA9). SV102, 202, and 302 broadcast, for example, in a System Information Block Type 1 (SIB1) or SIB Type 2 (SIB2), the identifier (ID) of a supported PLMN (if the PLMN ID includes the Mobile Country Code (MCC) and Mobile Network Code (MNC)) and, for each supported PLMN, the ID of a supported TA (if the TA ID includes the Tracking Area Code (TAC) or Tracking Area ID (TAI)). In the case of NGEO SV, if the coverage area of ​​a wireless cell changes, the supported PLMNs and TAs may change. The gNB 106 / 202 / 307 can determine PLMN and TA support (and therefore the PLMN ID and TAC broadcast in the SIB of each radio cell) from the known ephemeris data of each SV 102 / 202 / 302 and the known directivity and angular range of the constituent radio beams of each radio cell (e.g., cell 1 and cell 2). The gNB 106 / 202 / 307 may update the SIB broadcast.

[0069] Therefore, as illustrated in Figure 6, SV102 / 202 / 302 may broadcast an SIB to cell 1 that includes a TAI or TAC for TA4, and possibly TA1, TA3, TA5, TA8, and / or TA9. Similarly, SV 102 / 202 / 302 or another SV 102 / 202 / 302 may broadcast an SIB to cell 2 that includes a TAC or TAI for TA12 only. Cell 1 may be assigned to gNB1 (with coverage of TA4, TA5, TA8, and TA9), and cell 2 may be assigned to gNB2 (with coverage of TA12, TA13, TA14, and TA15). When cell coverage areas move from one gNB area to another, cells 1 and 2 may be transferred from gNB1 to gNB2, or from gNB2 to gNB1.

[0070] The coverage area of ​​a fixed TA can be defined in a simple, accurate, and flexible manner, requiring minimal signaling for delivery to entities within UE105, gNB106 / 202 / 307, or 5GCN110. A fixed TA area may be small enough to enable efficient paging by including an area supported by only a few radio cells (e.g., 5 or fewer), and may be large enough to avoid excessive UE registration (e.g., extending at least 100 kilometers in any direction). The shape of a fixed TA area may be arbitrary, for example, defined by the PLMN operator, or may have one or more constraints. For example, one constraint on the shape of a fixed TA area might be precise alignment with the border to avoid a fixed TA along the border of one country serving UE105 in another country. Furthermore, fixed TAs may be restricted to areas of interest, such as PSAP serving areas, cities, counties, states, or small countries. Furthermore, fixed TAs may be restricted to areas of interest, such as PSAP serving areas, cities, counties, states, or small countries.

[0071] The coverage area of ​​a fixed cell can similarly be defined in a way that is simple, accurate, flexible, and requires minimal signaling for delivery to UE105 or gNB106 / 202 / 307. The fixed cell coverage region allows for a simple and accurate association with fixed TAs, for example, one fixed cell can clearly belong to one TA.

[0072] Fixed cells may be used by radio core networks such as 5GCN110 to support regulatory services such as emergency (EM) call routing based on current fixed serving cells for UE105, the use of fixed cells to approximate the location of UE105, the use of fixed cell associations to direct radio emergency alert (WEA) alerts to recipient UE105s over small defined areas, or the use of fixed cells as approximate locations or trigger events for lawful interception (LI) for UE105s. Such use of fixed cells means that fixed cells should be able to be defined in size and shape similar to the size and shape of cells defined and used for terrestrial radio access, including allowing very small (e.g., pico) cells and large (e.g., rural) cells.

[0073] In satellite radio access, the UE105 may determine the TA based on broadcast information and from other sources. Furthermore, the network may broadcast one or more TACs or TAIs per PLMN within a radio cell. Broadcasting one TAC or one TAI per PLMN in a radio cell (such as a System Information Block Type 1 (SIB1)) may be referred to as a “hard TAC update” or “hard TAI update” (for example, because the broadcast TAC or TAI change is overall and therefore “hard”), and may coincide with support for TAC or TAI broadcasts within the terrestrial network (TN). Broadcasting one or more TACs or TAIs per PLMN within a radio cell may be referred to as a “soft TAC update” or “soft TAI update” (for example, because it is not necessary to change all broadcast TACs or TAIs simultaneously; instead, only one broadcast TAC or TAI, or a subset of broadcast TACs or TAIs, may be changed simultaneously, and therefore it may be considered “soft”). Depending on the network operator's configuration, both hard TAC (or hard TAI) updates and soft TAC (or soft TAI) updates may be supported.

[0074] It should be noted that the terms TAC and TAI may be used synonymously in this specification. In practice, a TAC is typically a single value (e.g., consisting of 24 bits) that indicates the TA of a known PLMN (e.g., if the MCC and MNC identifying the PLMN are known). A TAI typically consists of a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a TAC, indicating both the PLMN (via the MCC and MNC) and the TA within that PLMN (via the TAC). If a TAC is broadcast in a radio cell, one or more PLMNs are also indicated for these TACs via the broadcasted MCC and MNC values. A broadcast TAC also indicates a TAI by association with a PLMN (e.g., if a broadcast TAC is combined with a broadcast MCC and MNC, a TAI is obtained for each PLMN indicated in the broadcast TAC). Thus, a radio cell can effectively broadcast both a TAC and a TAI. The term “broadcast TAI” is commonly used herein because it may be more accurate since a TAC always refers to a TAI.

[0075] Figure 7 shows, as an example, an exemplary environment 700 including a wireless cell 704 and an SV702 (e.g., SV102, 202, or 302) containing a number of tracking areas 706, each having a fixed area at least partially covered by the wireless cell 704. In the environment 700 illustrated in Figure 7, TAIs for one or more of the tracking areas 706 may be broadcast by the SV702 in the wireless cell 704 (e.g., in SIB1). If hard TAI updates are used, the SV702 broadcasts only the TAI of one of the four TAs 706-1, 706-2, 706-3, or 706-4. For example, since TA 706-2 has the greatest coverage by the wireless cell 704, the TAI of TA 706-2 may be broadcast. This results in some distortion of the effective area of ​​broadcast TAIs (and other non-broadcast TAIs) because, for UE105 within the coverage of radio cell 704, one TA (e.g., TA706-2) appears to occupy the entire coverage area of ​​radio cell 704. If soft TAI updates are used, the TAIs of all four TA706-1, 706-2, 706-3, and 706-4 (or just TA706-1, 706-2, and 706-4) can be broadcast, thereby avoiding excluding any one TA706 of a UE105 that might be located within that TA706. However, another kind of distortion may exist in that a UE105 located in one of the TA706s (e.g., TA706-1) may be allowed to access radio cell 704 even if that TA is not in the UE105's current registration area (RA), as long as at least one of the broadcast TAIs is part of the UE105 RA.

[0076] If one TAI is broadcast for each PLMN within each physical radio cell (in the case of a hard TAI update), there may be no additional impact on the UE105 or AMF122 to access the physical radio cell and perform registration updates or paging, but the overhead of paging and / or registration updates may increase.

[0077] Multiple TAIs are broadcast for each PLMN within the physical radio cell (similar to soft TAI updates), and to minimize the new impact on the UE105, a simple solution might be to allow the UE105 to access the radio cell without mobility registration updates, as long as at least one of the broadcast TAIs belongs to the current UE105 RA. If none of the broadcast TAIs belong to the current UE105 RA, the UE105 may be required to perform a mobility registration update. This can reduce the overhead of paging and / or registration updates.

[0078] In the case of terrestrial network access, the serving terrestrial gNB for the UE typically indicates to the serving AMF for the UE the serving radio cell for the UE (using the cell ID) and the tracking area (using the TAI) where the UE is geographically located. The cell ID and TAI are usually contained in a parameter called User Location Information (ULI) IE (also known as Information Element (IE)). For example, the serving terrestrial gNB may provide the serving AMF in the ULI IE with instructions for the TA for the UE using the TAI, where the TAI may include the Mobile Country Code (MCC), Mobile Network Code (MNC), and TAC. For example, if a UE with TN access initiates a NAS procedure using 5GCN (e.g., for a Non-Access Layer (NAS) service request), the serving gNB may indicate the current TA where the UE is located in the ULI provided to 5GCN (e.g., AMF) in certain NGAP messages (e.g., NGAP Initial UE Message, NGAP Uplink NAS Transport, NGAP UE Context Release Complete, NGAP Handover Notify, NGAP Location Report), as discussed in 3GPP TS 38.413, for example. AMF may need to know the TAI to allocate a Registration Area (RA) to the UE, and the RA may include the TAI for TAs where the UE is permitted to access the network without performing a registration renewal procedure. Similarly, the cell ID shown in the ULI IE may be used by AMF or other network elements to route emergency calls for the UE or to assist with subsequent paging of the UE. Providing identical or similar information in the ULI IE for satellite radio access for UE105 may be desirable to mitigate new impacts on AMF122, enable efficient paging of UE105, and avoid excessive registration updates by UE105.

[0079] For NR satellite access, there are several possible alternatives for supporting TAI in the ULI IE passed to AMF122 by gNB 106 / 202 / 307 in NGAP messages as listed above. For example, when multiple TAIs are broadcast within a cell by gNB 106 / 202 / 307, as described below, several alternative options can exist to support TAI selection for NGAP ULI (e.g., in the NGAP Initial UE Message). These alternatives are referred to herein as Option A, Option B, Option C, Option D, and Option E.

[0080] Option A: Serving gNB106 / 202 / 307 selects a TAI from the TAI broadcast for the serving PLMN within the serving radio cell for UE105, prioritizing any TAI for the TA where UE105 is geographically located. This TAI is included in the ULI IE for UE105.

[0081] Option B: UE105 may select a TAI from the TAIs broadcast on the serving radio cell for the serving PLMN, and may prioritize TAIs within UE105's registration area (RA). UE105 may then indicate this TAI in the serving gNB106 / 202 / 307 (e.g., in an RRC message), and then include this TAI in the ULI IE.

[0082] Option C: Serving gNB106 / 202 / 307 selects TAI as the TAI of the TA belonging to the Serving PLMN where UE105 is geographically located.

[0083] Option D: Serving gNB106 / 202 / 307 provides all TAI broadcast in the serving radio cell for serving PLMN as part of the ULI IE for UE105.

[0084] Option E: Serving gNB106 / 202 / 307 selects the TAI as the TAI for the TA of the serving PLMN where UE105 is geographically located if this TAI is broadcast in the serving radio cell. Otherwise, serving gNB106 / 202 / 307 selects the TAI broadcast within the serving cell for the TA of the serving PLMN geographically closest to UE105's location.

[0085] Figure 8 shows an example of environment 800, which includes an SV802 (e.g., SV102, 202, 302, or 702) broadcasting multiple TACs (or TAIs) within a radio cell 804. The radio cell 804 has a coverage area at time t (shown by a solid line) and a coverage area at time t+δ (shown by a dotted line), where δ may be small (e.g., several minutes). TACs or TAIs broadcast in radio cell 804 by satellite 802 at time T are shown in shaded areas, while tracking areas not broadcast in radio cell 804 by satellite 802 at time T are shown unshaded (white). Therefore, environment 800 illustrates a number of TAs 806, including TAs in radio cell 804 at time T labeled TA1, TA2, TA3, TA4, TA5, and TA6, where the TAC or TAI for TA1, TA2, TA3, TA4, and TA5 are broadcast within the radio cell by satellite 802 at time T, while the TAC or TAI for tracking area TA6 is not broadcast by satellite 802 at time T. Environment 800 further illustrates UE805a located at TA1 and another UE805b located at TA6 (for example, UE805a and 805b could be examples of UE105).

[0086] Examples of options A through E are shown in Table 1 below for UE805a located at TA1 (where the TAC or TAI is broadcast) and UE805b located at TA6 (where the TAC or TAI is not broadcast in this example), where (for option E) UE805b is assumed to be closer to TA5 than the other TAs where the TAC or TAI is broadcast. Table 1 shows (in the rightmost column) the TAs shown in the ULI IE (by including the TAC or TAI) for each UE and option A through E shown in Figure 8.

[0087] [Table 1]

[0088] Options A through E above can be evaluated against several criteria, as described below.

[0089] One criterion is how well each option helps the AMF decide whether to select a new registration area (RA) for the UE or retain an existing RA when the UE performs initial registration or registration renewal. For example, in the case of TN access, the AMF needs to ensure that the TAI from the ULI is included in the RA (so that the UE can access its current serving cell), and can also assign one or more other TAIs to nearby TAs to enable some UE mobility without additional registration renewal. In the case of satellite access, some options may perform worse with respect to this criterion, as shown below.

[0090] Option C may provide a TAI to UE105 in a ULI that is not broadcast in the serving radio cell (as illustrated by the example above for UE805b in TA6, for example), which may lead AMF122 to select an RA for UE105 that includes any TAI that is being broadcast. In that case, UE105 would not be able to access the serving cell without performing another registration update that may lead to a series of registration updates or cause UE105 to look for another radio cell.

[0091] Option B allows providing a TAI to UE105 in the ULI for a TA that is far from the actual location of UE105 (because UE105 typically does not know which TA it is located in or which TA is near its location). For example, suppose UE805a, located at TA1 in Figure 8, selects a TAI for TA5, which is delivered to AMF122 in the ULI, and together with AMF122, then includes the TAI for TA5, but does not include any other TAIs in the RA for UE805a. If radio cell 804 moves to the region indicated by the dashed circle in Figure 8 at time T+δ, UE805a is still within the radio cell's coverage, but since the TAC or TAI for TA5 is (presumably) no longer broadcast, a registration update from UE805a occurs, which could be avoided if a TAC or TAI for TA1, or another TA closer to UE805a's location, had been provided to AMF122 in the ULI. Similar instances of unnecessary registration updates may occur for other TAIs provided by ULI, excluding the TAI of TA1 (for UEs located in TA1).

[0092] Option A, like Option B, can suffer from performance degradation in some cases (e.g., in the case of UE805b in TA6 of Figure 8 where the TAI is not broadcast), because gNB106 / 202 / 307 may include the TAI in the ULI of a TA that is also far from the actual location of the UE (e.g., in the case of UE805b). While it is argued that such a case should not occur if the broadcast TAI selection includes all covered TAs, this cannot be guaranteed.

[0093] Option D may be less advantageous than Option B because AMF122 does not know which of the TAs indicated by the TAI provided in the ULI the UE105 could be located at, or which TA(s) is closest to the UE105.

[0094] Option E provides a broadcasted TAI that is closest to the location of UE105, which can reduce the occurrence of additional registration updates for UE105 as the cell coverage area moves. gNB106 / 202 / 302 may determine the TA closest to the location of UE105 based, for example, on the shortest distance between the location of UE105 and the periphery of the TA, or on the shortest distance between the location of UE105 and the center (or centroid) of the TA. As an example, for UE805a in TA1 in Figure 8, Option E provides an AMF122 with a TAI for TA1 in the ULI, allowing AMF122 to include the TAI for TA1 in the RA for UE805a. For UE805b in TA6, where the TAI is not broadcast, AMF122 will receive the TAI for TA5, which is a broadcasted TAI and is for the TA closest to the location of UE805b. This would lead to further registration by UE805b if cell 804 moves away from TA5 to cover TA6, in which case AMF122 could receive the TAI for TA6 in the ULI and then include the TAI for TA6 in the new RA for UE805b.

[0095] Another criterion may relate to whether the TAI provided in the ULI matches the RA currently assigned to the UE. For TNs, the TAI provided in the UE's ULI for an unregistered NAS message must always be part of the current UE RA. Otherwise, the UE performs a registration update. For TNs, the UE provides the AMF (e.g., within "Last Visited Registered TAI" as defined in 3GPP TS 24.501) with the last registered TAI placed in the NAS registration request, and this should also be part of the current RA. For satellite access, there is a small risk that providing a TAI to UE105 for any of these purposes that is not part of the current UE105 RA may cause some abnormal behavior (e.g., an error condition) in AMF122. This is avoidable for satellite RATs, as AMF122 can be programmed to ignore any differences between the TAI in the ULI or the TAI in the NAS registration request and the current RA of UE105. Furthermore, the AMF122 can perform a NAS configuration update to update the RA in the UE105 with a TAI included in the ULI when this TAI is not part of the current RA. However, option B may have the advantage of avoiding any new AMF122 implementation by ensuring that the TAI provided in the UE105 ULI for the AMF122 is part of the UE105 RA. All other options may be insufficient in this respect.

[0096] The options also differ in terms of new impacts. Option B may have a new RRC signaling impact, allowing UE105 to forward selected TAUs to serving gNB106 / 202 / 307 for other instances of RRC connection setup and NAS message forwarding. Option D may have a new NGAP impact, forwarding all TAIs broadcast in the wireless cell to AMF 122. Options A, C, and E may not have any new signaling impacts.

[0097] Regarding the complexity of the gNB, options B and D may be particularly simple because they do not require gNB106 / 202 / 307 to map the current location of UE105 to the TA where UE105 is located, or to the TA closest to the location of UE105. Options A and C may require the capability of gNB106 / 202 / 307 to map the location of UE105 to the TA where UE105 is located, and option E may further require gNB106 / 202 / 307 to map the location of UE105 to the TA closest to the location of UE105, and to broadcast the TAI of the TA where UE105 is located when the TAI of that TA is not broadcast. However, the mapping capability does not add much new complexity, as similar functionality may already be required (for all options) when gNB106 / 202 / 307 determines which TAI to broadcast within a given radio cell at a given time, and when gNB106 / 202 / 307 maps the location of UE105 to a specific cell global identity (CGI), which may also include the ULI IE. For example, an operator (or offline tool) can configure a fixed mapping from the CGI to the relevant TAI (in the case of the TA where the cell of the CGI is located), thereby simplifying the mapping from the UE location to the TAI for options A and C via a mapping from the UE location to the CGI and then from the CGI to the TAI. A similar mapping can be configured from the CGI to a sequence of TAIs of TAs at progressively increasing distances from the cell area defined by the CGI, thereby also supporting the mapping for option E.

[0098] Another aspect of TAI selection may relate to what happens when the gNB106 / 202 / 307 does not have enough accurate UE105 location information to determine location-related TAUs for options A, C, and E. This can occur when the UE105 transitions from an idle state to a connected state (e.g., during the UE105's initial PLMN access) and the RRC message sent to the serving gNB106 / 202 / 307 does not include an approximate location (e.g., because such a location may not be encrypted and therefore may be insecure or unreliable). When this scenario occurs, the serving gNB106 / 202 / 307 for the UE105 can provide one of the TAIs broadcast in the ULI for the serving radio cell for the UE105, but thereafter any location importance is lost. Options A, C, and E are no worse, as they behave similarly to option B in that they support RA assignment by AMF 122 for NAS registration. Another alternative is for serving gNB106 / 202 / 307 to indicate in the ULI sent to serving AMF122 that it cannot determine the TAI of the ULI due to insufficient positional information from UE105. For example, the indication can be encoded as a flag in the ULI or as a special reserved value for the TAI of the ULI (e.g., all zeros in binary or all ones in binary). Since the special reserved value for TAI does not encode an actual TAC or actual TAI value, it may be called a "null value," "null TAC value," or "null TAI value."

[0099] A further aspect of TAI selection may relate to paging efficiency. This may relate to how well the current RA for UE105 includes the TAI of the TA where UE105 actually is located, as well as nearby TAs. If the RA includes TAI for TAs far from UE105 (for example, because serving AMF122 is misled by receiving a ULI with TAI for TAs far from UE105's location), then paging across the entire RA may include cells that do not cover the actual location of UE105. Such paging is wasted because UE105 cannot access these cells. As an example, consider the case of UE805a located at TA1 in Figure 8, where the ULI for IE805a includes TAI for TA5 (for example, as possible in option B or option D as shown in Table 1). Then the RA for UE805a may include TAI for TA5. There may be one or more cells with coverage for TA5 that does not cover TA1, and paging for these cells is wasted. As already implied, this issue is more likely to occur in options B and D, where the reported TAA is not based on the actual UE location, and in option A, where the TAI of the TA where the UE is located is not currently broadcast. The issue can be further complicated if AMF 122 assigns RAs containing multiple TAIs to reduce unnecessary registration updates.

[0100] Another criterion concerns whether various options can be used to select a TAI for a ULI in NGAP messages of UE105 that are not associated with NAS message forwarding. These NGAP messages include PDU session management messages, UE context management messages, UE mobility management messages, and location reporting messages used to track UE locations. Options C and E, and to a lesser extent option A, can be reused to select a TAI for a ULI IE in these non-NAS-related NGAP messages, since the TAI can always or generally be UE location-related (e.g., it can be determined by serving gNB 106 / 202 / 307 from a known or approximate UE location). In this case, using options B or D to select a TAI may cause problems due to the lack of location importance for these options. For example, the NGAP location reporting procedure can be used to track the location of UE105 in a region of interest, which may be defined as a single TA or a set of TAs. Option C, and to a lesser extent Option E, can effectively support the NGAP location reporting procedure because the ULI included in the NGAP location reporting message includes either the TAI of the TA where UE105 is located (for Option C and sometimes Option E) or the TAI of a TA close to UE105's location (otherwise, Option E). Using the TAI selected by UE105 to determine whether UE105 is located in the region of interest is not useful, as in Option B, because the TAI selected by UE105 may not be location-related. Furthermore, the reuse of Option B can have significant additional implications because gNB106 / 202 / 307 must either obtain the TAI from UE105 (e.g., using RRC) or store and utilize the last TAI provided by UE105 (although it may not always be available when a handover occurs). Therefore, Options B and D require some different solution (such as another option) to determine the TAI for location reporting and, in some cases, the TAI for NGAP messages that are not related to other NAS.

[0101] While there is clearly no ideal option, option E appears to be at least slightly better than the other options.

[0102] Regarding option E, as mentioned above, the inability to always provide TAI, which is part of the RA for UE105, is not a serious issue, and the extra complexity of gNB106 / 202 / 307 can be mitigated by additional configuration. Therefore, option E seems in principle suitable for supporting TAI selection for NGAP ULI IE.

[0103] In some embodiments, the TAIs provided by the AMF122 in the registration area (RA) for UE105 may be presented to UE105 in order of priority based on the proximity of the corresponding TAs to UE105. For example, the AMF122 may determine the proximity of each TA represented by the TAI to the location of UE105 and generate an RA for UE105 that provides a list of TAIs in order from the TAI of the TA closest to UE105's current location to the TAI of the TA furthest from UE105's location. In option B, for example, UE105 may select TAIs from the RA with the highest priority (e.g., the TAI listed first for the TA closest to UE105) in the RA broadcast in the serving radio cell. In the example of Figure 8 with respect to UE805b at TA6, for example, the RA may provide a list of TAIs with higher priority in order based on proximity, including TAIs for TA6, TA5, TA2, TA4, TA1, and TA3. The UE805b selects the highest priority TAI in the RA (e.g., the first TAC listed) and which is broadcast on the serving radio cell. In this example, this is the TAI for TA5 (in the example in Figure 8, the TAI for TA6 is not broadcast).

[0104] Similarly, for example in option D, gNB106 / 202 / 307 may include all TAIs broadcast in the serving radio cell of UE105 in the ULI sent to AMF122, but may also provide a prioritized list of these TAIs based on the proximity of the corresponding TAs to the location of UE105. Thus, gNB106 / 202 / 307 may determine the location of UE105 and generate a list of broadcast TAIs to be provided to AMF122, where the TAI for the TA closest to the current location of UE105 is given a higher priority (e.g., appears earlier in the prioritized list) than the TAI for the TA furthest from UE105. In the example of Figure 8 for UE805b at TA6, the provided list of TAIs then includes the TAIs for TA5, TA2, TA4, TA1, and TA3 in that order. AMF122 can determine, or assist in determining, the prioritized list of TAIs for UE105 RA as described above, using the prioritized list of TAIs provided by gNB106 / 202 / 307 for option D.

[0105] In some embodiments, two or more of the above options A through E may be merged or combined to mitigate or eliminate some of the previous disadvantages. A merge is referred to using the options they contain (for example, option B+C means combining option B and option C).

[0106] In one option, B+E, for forwarding NAS messages other than NAS registration, UE105 selects the TAI from the RA, similar to option B, and sends this TAI to gNB106 / 202 / 307 using RRC. gNB 106 / 202 / 307 includes this TAI in the ULI. For forwarding NAS registration requests, UE105 does not include the TAI. Based on the absence of the TAI, gNB 106 / 202 / 307 selects the TAI in the ULI, similar to option E. In other instances of the ULI, gNB 106 / 202 / 307 may also select the TAI, similar to option E.

[0107] In another option B+C+D, for the forwarding of NAS messages other than NAS registration, UE105 selects a TAI from the RA, similar to option B, and sends this TAI to gNB106 / 202 / 307 using RRC. gNB 106 / 202 / 307 then includes this TAI in the ULI sent to AMF 122. For the forwarding of NAS registration requests, UE105 does not include a TAI. Based on the absence of a TAI, gNB 106 / 202 / 307 then selects a TAI, similar to option C, and includes this TAI in the ULI, and further includes all TAIs broadcast in the serving cell in the ULI, similar to option D. In other instances of the ULI, gNB 106 / 202 / 307 selects a TAI, similar to option C.

[0108] In the further option C+D, gNB 106 / 202 / 307 selects a TAI, similar to option C, and includes this TAI in the ULI, and further includes all TAIs broadcast in the serving cell in the ULI, similar to option D.

[0109] In options B+E, B+C+D, and C+D respectively, gNB106 / 202 / 307 may include an instruction (e.g., a Null TAC value or a Null TAI value) in the ULI for UE105 if it does not have or has insufficient location information to determine the TA where UE105 is located (in the case of option C or option E) or the TA closest to UE105's location (in the case of option E). In options C+D or B+C+D, gNB106 / 202 / 307 may then include this instruction in the ULI sent to AMF122, and further, may indicate in the ULI all TAIs broadcast by SV802 in the radio cell for UE105. AMF122 may not know which TA UE105 is located in, but still knows which TAs may be near UE105, thereby helping AMF122 determine UE105's RA. The provision of instructions by gNB106 / 202 / 307 (e.g., Null TAC value or Null TAI value) can also be used when the location information of UE105 is available, but gNB106 / 202 / 307 is not implemented or configured to support mapping the location information of UE105 to the TA where UE105 is located (e.g., UE105 location estimation). Such provision of instructions (e.g., Null TAC value or Null TAI value) can assist implementation by not requiring all gNB106 / 202 / 307 to necessarily support mapping the location information of UE105 to the TA closest to UE105 or to the TA where UE105 may be located. In such cases, and for options B+C+D and C+D, gNB106 / 202 / 307 can provide instructions for all TAI broadcast on the serving radio cell for UE105, which can still assist AMF122 in RA determination for UE105.

[0110] Option B+E may have the impact of RRC and higher gNB 106 / 202 / 307 complexity, but otherwise may perform at or above the level of Option E.

[0111] Option B+C+D may potentially perform better than Option E and Option B+E in terms of effective RA assignment to UE105 and support for paging efficiency for UE105 by AMF122, because it provides AMF122 with the TA where UE105 is located, and (ii) all broadcast TAIs, even if the TAI corresponding to this TA is not broadcast. Then, for each TA where UE105 may be located, AMF122 can configure a list of other TAs in order of distance from this TA. Next, AMF122 can select a TAI or set of TAIs for an RA that is broadcast and whose corresponding TA is close to the TA where UE105 is located, or includes the TA, which enables better RA assignment to UE105 by AMF122. However, Option B+C+D may have the greatest signaling impact, with a high influence of gNB 106 / 202 / 307 due to the influence of both RRC and NGAP.

[0112] Option C+D may function similarly to Option B+C+D, but with reduced impact (due to the absence of RRC impact to support Option B), and the TAI included in ULI is not necessarily part of UE105 RA.

[0113] Support for service and restricted areas may be omitted for satellite access. However, this means that operators who allocate permitted and restricted areas for UEs for terrestrial network (TN) access cannot do the same for satellite access. This could lead to abnormal behavior. For example, a UE could move into a restricted TN area and then periodically (e.g., outdoors at any time) obtain satellite access and service, thereby circumventing TN service restrictions. This could change user behavior, for example, a user could circumvent TN restrictions by going outdoors (or near a window if indoors) for services supported by satellite access—and thus reduce the value of TN restrictions by limiting themselves to services only available using TN (e.g., high-speed data).

[0114] This suggests that even a rough form of service area control may be useful for satellite access. While the level of control may not be precise, it can be helpful in estimating TN limits. The following rules, called Rules 1, 2, 3, and 4, can be used to support service and restricted areas.

[0115] Rule 1 allows UE105 to access satellite radio cells if at least one broadcast TAI is not on UE105's unauthorized or prohibited TAI list. For example, at least one broadcast TAI may be part of the current RA to UE105 and / or part of the authorized TAI list to UE105. Otherwise, UE105 will follow existing TN rules regarding prohibited TAIs if all broadcast TAIs in the radio cell are prohibited TAIs, or otherwise follow rules regarding unauthorized TAIs that may allow UE105 to send at least a NAS registration request.

[0116] As a complement to Rule 1, and in Rule 2, AMF122 may allow UE105 to access a wireless cell if at least one broadcast TAI for the wireless cell is not on UE105's disallowed or prohibited list. AMF122 may then accept a NAS procedure request by UE105 (e.g., a NAS registration request or a NAS service request). However, if all TAIs broadcast within the wireless cell are part of the prohibited TAI list for UE105, AMF122 may reject a NAS procedure request by UE105 (e.g., a NAS registration denial or NAS service denial) by sending a NAS denial message (e.g., a NAS registration denial or NAS service denial), which may include a cause indicating that the broadcast TAI is prohibited for UE105. Otherwise, if one or more of the broadcast TAIs are not permitted but not prohibited for UE105, AMF122 may permit and accept a NAS registration request but reject other NAS messages such as a NAS service request. As mentioned above, the AMF122 can determine which TAI is broadcast within the wireless cell if option D, option C+D, or option B+C+D is supported. Rules 1 and 2 can also be applied to hard TAI updates if only one TAI is broadcast in the wireless cell, and the reference to "all TAIs broadcast in the wireless cell" above is replaced with "one TAI broadcast in the wireless cell".

[0117] Rule 3 stipulates that for UE105 receiving a NAS denial message, if the denial indicates that the current TAI is prohibited (for example, as described above for Rule 2), UE 105 will treat all broadcast TAIs for the current serving radio cell that are not in the current RA and are not in the permitted TAI list as prohibited TAIs.

[0118] Rule 4 dictates that UE105 updates its prohibited TAI list by removing the TAI from the prohibited TAI list if the TAI is received as part of a new RA to UE105 (for example, in a registration request received from AMF122) or if the TAI is received as an authorized TAI (from AMF122).

[0119] These rules may (A) allow UE105 access to unauthorized areas, or (B) deny UE105 access to authorized areas. However, if the service area is carefully managed to always show authorized TAs near UE105, (A) is likely to occur, but (B) is unlikely to occur. This avoids a reduction in UE 105 PLMN access compared to TN, and provides additional access that is not possible with TN, but does not provide unlimited additional access.

[0120] Figure 9 shows a signaling flow 900 illustrating various messages transmitted between PLMN components with satellite access in a procedure supporting TAI updates, as discussed herein. The signaling flow 900 may be executed by entities within the network architectures 100, 200, or 300 in Figures 1, 2, or 3, respectively, where UE902 corresponds to UE105, SV904 corresponds to SV102, 202, or 302, gNB906 corresponds to gNB106 / 202 / 307, and AMF908 corresponds to AMF122. It should be understood that gNB906 or elements of gNB906 may be contained within SV904. For example, in SV202, gNB202 is entirely contained within SV202, as described in Figure 2. Alternatively, in SV302, gNB307 (also called gNB-CU) is ground-based and physically separate from SV302, while SV302 includes gNB-DU302, as described in Figure 3. In some embodiments, eNB may be used instead of gNB906, and MME may be used instead of AMF908. Additional or fewer stages / messages may be included in the signaling flow 900.

[0121] In Stage 1 of Figure 9, UE902 may be started in the 5G System (5GS) Mobility Management (5GMM)-REGISTERED and RRC IDLE states. During registration (e.g., prior to the occurrence of Stage 11), AMF908 may provide a list of TAIs in the UE RA, or a prioritized list of TAIs in the UE RA, based on the proximity of the corresponding TAs to the location of UE902, as described in Figure 8.

[0122] In Stage 2, the UE902 receives broadcast TAI information from the SV904 (and possibly from other SVs not shown in Figure 9) for one or more radio cells that indicate one or more TAIs supported by each radio cell, and selects radio cells (and associated SV904) based on the radio cells permitted to the UE902. Based on Rule 1 described above, the UE902 may decide whether or not to allow access to the radio cells. Access may be unconditionally permitted if at least one broadcast TAI is part of the current UE902 RA, or if at least one broadcast TAI is not part of the disallowed TAI list and is not part of the UE902's prohibited TAI list (for example, if it is part of the UE902's permitted TAI list). When unconditional access is not permitted, conditional access may be permitted for the UE105 to send NAS registration request messages (not necessarily other NAS messages) if at least one broadcast TAI is not part of the UE902's prohibited TAI list, for example, if some or all of the broadcast TAIs are part of the UE902's disallowed TAI list. Additionally, the UE902 may obtain location information, such as its own location estimate, by, for example, obtaining measurements from the SPS SV190 and using those measurements to determine a location estimate. If access to the radio cell is not permitted in Stage 2, Stages 3 through 12 will not be executed. If access to the radio cell (conditionally or unconditionally) is permitted in Stage 2, Stages 3 through 12 can be executed.

[0123] In Stage 3, the UE902 performs a random access procedure to obtain permission from the gNB906 for uplink (UL) transmission (not shown in Figure 9), and then sends an RRC configuration request to the gNB906 supporting the radio cell selected in Stage 2 to request an RRC signaling connection.

[0124] In Stage 4, the gNB906 returns an RRC configuration message to the UE902.

[0125] In Stage 5, the UE902 sends an RRC setup complete message that includes a NAS request message. The NAS request may be a request for a NAS procedure or a request to provide information to the AMF908. The NAS request may be, for example, a registration request, a connection request, a service request, or a PDU session establishment request, or an uplink (UL) NAS transport. The NAS request may require a NAS response, and in some embodiments, a NAS response may not be required. In some embodiments, the UE902 may include multiple TACs or TAIs from broadcast TAI information received in the radio cell selected in Stage 2. In some embodiments (for example, Option B), if the NAS request is not a registration request, the UE902 may select and include TACs or TAIs in the RRC setup complete message. For example, in the case of Option B, Option B+E, or Option B+C+D, as described above for Option B, the UE902 may select and include one TAI from the TAI broadcasts within the selected radio cell, and may further prioritize a TAI within the UE902 RA or a higher-priority TAI within the UE902 RA. The UE902 may also include any UE location information acquired in Stage 2 (e.g., the estimated location of the UE902) in the RRC setup completion message.

[0126] In Stage 6, the gNB906 determines a UE902 user location information (ULI) containing one or more TAIs for one of options A, B, C, D, or E, or several combinations thereof (e.g., option B+E, option B+C+D, or option C+D), as described above. The gNB906 may utilize UE902 location information received in Stage 5 or already known to the gNB906 (e.g., from the radio cell coverage area) to determine one or more TAIs. For example, as described above for Option C (or Option C+D), gNB906 may select a TAI as the TAI for the TA where UE902 is located if this TA can be determined, or it may include an instruction (e.g., a Null TAC or Null TAI value) in the ULI if it is unable to determine the TA due to insufficient UE902 location information received in Stage 5 or because gNB906 is unable to map the UE902 location information to the TA where UE902 is located. For example, as described above for Option E, gNB906 may select a TAI as the TAI for the TA where UE902 is located if a TAI for this TA is broadcast in the serving radio cell. Otherwise, gNB906 may select a TAI that is broadcast in the serving cell for the TA closest to UE902 (e.g., as indicated by the UE location information received in Stage 5). In some embodiments (e.g., option B), as described above, the gNB906 may determine the TAI based on the TAI provided by the UE902 in the RRC message at stage 5. In some embodiments, for example, option D or option C+D, the gNB906 may include instructions for all TAIs broadcast within the radio cell, or generate and include a prioritized list of these TAIs based on the proximity of each corresponding TA to the UE902 (e.g., as indicated by the UE location information received at stage 5). In the case of combined options, the gNB906 may include several types of TAIs in the ULI.For example, in option C+D, gNB906 may include a TAI for the TA where UE902 is located if this TA can be determined, or an instruction (e.g., a Null TAI value) if this TA cannot be determined, and may also include instructions for all TAIs broadcast within the radio cell.

[0127] In Stage 7, the gNB or gNB-CU906 forwards the NAS request to the AMF908 in the serving PLMN for UE902 in an NGAP transport message, such as the NGAP initial UE message. The NGAP transport message includes the NAS request and the ULI determined in Stage 6, which includes the determined TAI and / or a list of TAIs.

[0128] In Stage 8, the AMF908 may determine whether the TAI for UE902 included in the ULI received in Stage 7 is an acceptable TAI for UE902. Based on whether the TAI is permitted, the AMF908 may use Rule 2, as previously described, to determine whether UE902 is permitted to access the radio cell selected in Stage 2. For example, when Option D, Option C+D, or Option B+C+D is used, the AMF908 may determine that access to the radio cell is unconditionally permitted if at least one of the TAIs is permitted for UE902 (e.g., not included in the prohibited TAI list and not included in the disallowed TAI list for UE902). However, if all TAIs broadcast within the radio cell are not permitted for UE902 (e.g., each is on the prohibited TAI list or disallowed TAI list for UE902), the AMF908 may determine that access by UE902 is unconditionally disallowed. If all TAIs broadcast within a wireless cell are part of the prohibited TAI list for UE902, AMF908 may determine that UE902 is not permitted to access the wireless cell selected in Stage 2. However, if all TAIs broadcast within a wireless cell are not permitted for UE902, but at least one TAI broadcast within the wireless cell is not part of the prohibited TAI list for UE902 (for example, it is on the unapproved TAI list for UE902), AMF908 may determine that UE902 is conditionally permitted to access the wireless cell selected in Stage 2, and may accept registration requests from UE902, but may not accept other NAS messages from UE902, such as service requests.

[0129] In Stage 9, if a TAI(s) are not permitted in Stage 8, such that UE902 is not allowed (even conditionally) to access the wireless cell selected in Stage 2, the AMF908 sends a NAS denial message to UE902 indicating that the current TAI(s) are denied. The NAS denial message may include, for example, the denied TAI and / or the reason for the denial, and a cause value indicating that UE902 will add the TAI to UE902's list of denied TAIs. The NAS denial message may respond to a NAS request and may deny the NAS procedure associated with the NAS request. For example, a NAS denial may be a denial of registration, a denial of service, a denial of connectivity, or a denial of PDU session establishment.

[0130] In Stage 10, if UE902 receives a TAI or a list of TAIs and an instruction that the TAIs are prohibited, UE902 adds the received TAIs to UE902's list of prohibited TAIs. If UE902 receives an instruction that the TAIs are prohibited but does not receive a TAI or a list of TAIs, UE902 may, as previously stated, forward all TAIs broadcast in the serving radio cell to the list of prohibited TAIs, in accordance with Rule 3. However, UE902 does not forward broadcast TAIs to the list of prohibited TAIs that are part of the current UE902 RA or are included in UE902's list of permitted TAIs. Subsequently, Stages 11 and 12 are not performed.

[0131] In Stage 11, if access to the wireless cell is permitted or conditionally permitted in Stage 8, the AMF908 sends a NAS Acceptance message to the UE902, which may be a Registration Acceptance, Connection Acceptance, or (e.g., if access is unconditionally permitted) a Service Acceptance message. If the NAS Acceptance message is a Registration Acceptance message, the AMF908 may include a new Registration Area (RA) for the UE902, which is a list of TAIs that the UE902 is permitted to use. The AMF908 may include in the RA the TAI received in Stage 7 if typically only one TAI is received, and may further include additional TAIs for TAs close to the TAI received in Stage 7. In Option D or Option C+D, if the TAI received in Stage 7 is prioritized by TAIs of TAs closer to the UE902 that are earlier in the priority list, the AMF908 may include one or more higher-priority TAIs in the RA (e.g., the highest-priority TAI and one or more of the next highest-priority TAIs). For option D or option C+D, if no TAI is prioritized, the AMF908 may include at least one of the TAIs broadcast in the radio cell within the RA. For option C+D, the AMF908 may instead include in the RA only the TAI of the TA where the UE902 is located (received in stage 7 as part of the ULI) if (i) this TA is determined by the gNB906 in stage 6 and this TAI is one of the TAIs broadcast in the radio cell, and otherwise, (ii) at least one of the TAIs broadcast in the radio cell within the RA. The registration acceptance message may further include service area instructions which may include the permitted area (TAI) and non-permitted area (TAI) of the UE902.

[0132] In Stage 12, if UE902 receives a new RA in Stage 11, UE902 may, as previously stated, follow Rule 4 and remove any TAI from the list of prohibited TAIs included in the new RA from UE902's list of prohibited TAIs. Similarly, if UE902 receives a service area instruction in Stage 11, UE902 may further remove any TAI from the list of prohibited TAIs included in the list of permitted TAIs received for the service area in Stage 11 from UE902's list of prohibited TAIs.

[0133] As mentioned above, it should be noted that each of options A-E, option C+D, option B+C+D, rules 1-4, and signaling flow 900 can be applied to satellite radio access using other types of satellite RATs such as LTE, NB-IoT, or future 6G, as long as fixed TAs continue to be used to support mobility management of UEs. In such cases, the above references to gNBs will be replaced with other types of base stations (e.g., eNB or ng-eNB for LTE satellite access, or eNB for NB-IoT satellite access), the above references to AMFs will be replaced with other types of core network nodes (e.g., MME for LTE or NB-IoT satellite access), and the references to types of NAS messages (e.g., NAS request, NAS accept, NAS reject) will be replaced with other types of NAS messages applicable to other satellite RATs (e.g., for LTE or NB-IoT satellite access, NAS connection request will be replaced with NAS registration request, NAS connection accept will be replaced with NAS registration accept, and NAS connection reject will be replaced with NAS registration reject).

[0134] Figure 10 shows an example of a hardware implementation of UE1000, such as UE105 shown in Figures 1, 2, and 3, or UE902 shown in Figure 9. UE1000 may be configured to execute the signal flow in Figure 9, the process flow 1500 in Figure 15, and the algorithms disclosed herein. UE1000 may include hardware components such as a satellite transceiver 1003 for wirelessly communicating with SV102 / 202 / 302 via a radio antenna (not shown in Figure 10), as shown, for example, in Figures 1, 2, and 3. UE1000 may further include a radio transceiver 1002 for wirelessly communicating with a ground base station in NG-RAN112, such as a gNB or ng-eNB, via a radio antenna (not shown in Figure 10). The UE1000 may also include additional transceivers, such as a wireless local area network (WLAN) transceiver 1006, and an SPS receiver 1008 for receiving and measuring signals from the SPS SV190 (shown in Figures 1, 2, and 3) via a wireless antenna (not shown in Figure 10). In some embodiments, the UE1000 may receive data from satellites, for example via a satellite transceiver 1003, and may also respond to ground base stations, for example via a wireless transceiver 1002 or via a WLAN transceiver 1006. Thus, the UE1000 may include one or more transmitters, one or more receivers, or both, which may be integrated, discrete, or a combination of both. The UE1000 may further include one or more sensors 1010, such as a camera, accelerometer, gyroscope, electronic compass, magnetometer, and barometer. The UE1000 may further include a user interface 1012, which may include other input devices such as a display, a keypad, or a virtual keypad on a display, through which a user can interface with the UE1000. The UE1000 may further include one or more processors 1004, memory 1016, and non-temporary computer-readable media 1018, which may be coupled together with a bus 1014.One or more processors 1004 and other components of the UE1000 may also be coupled together with a separate bus, which is a bus 1014, or they may be directly connected or coupled to one another using the aforementioned combinations.

[0135] One or more processors 1004 may be implemented using a combination of hardware, firmware, and software. For example, one or more processors 1004 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 1020 on a non-temporary computer-readable medium such as medium 1018 and / or memory 1016. In some embodiments, one or more processors 1004 may represent one or more circuits that can be configured to perform at least a portion of a data signal calculation procedure or process related to the operation of UE 1000.

[0136] The medium 1018 and / or memory 1016 may store instructions or program code 1020, which, when executed by one or more processors 1004, causes one or more processors 1004 to operate as a special-purpose computer programmed to perform the techniques disclosed herein (e.g., the signal flow in Figure 9 and the process flow 1500 in Figure 15, and the supporting techniques described herein). As illustrated in UE 1000, the medium 1018 and / or memory 1016 may include one or more components or modules that can be implemented by one or more processors 1004 to perform the methods described herein. The components or modules are illustrated as software in the medium 1018 that can be executed by one or more processors 1004, but it should be understood that the components or modules may be stored in memory 1016, or may be dedicated hardware either in or outside of the processors 1004.

[0137] Numerous software modules and data tables reside within medium 1018 and / or memory 1016 and may be utilized by one or more processors 1004 to manage both communications and the functionalities described herein. The configuration of the contents of medium 1018 and / or memory 1016 as shown in UE 1000 is merely illustrative, and it should be understood that the functionality of modules and / or data structures may be combined, separated, and / or structured in different ways depending on the implementation of UE 1000. While components or modules are illustrated as software within medium 1018 and / or memory 1016 executable by one or more processors 1004, it should be understood that components or modules may be firmware or dedicated hardware either within or outside of the processors 1004.

[0138] As illustrated, the program code 1020 stored in the medium 1018 and / or memory 1016 may include a TAI module 1021 that, when implemented by one or more processors 1004, configures one or more processors 1004 to receive multiple TAIs broadcast in a satellite radio cell by a RAN node via a radio transceiver 1002 or a satellite transceiver 1003. The one or more processors 1004 may be further configured to determine whether access to the satellite radio cell is permitted based on the multiple TAIs. For example, the one or more processors 1004 may be configured to determine that access is unconditionally permitted when at least one of the multiple TAIs is part of the current UE RA or part of the UE's permitted TAI list, to determine that access is conditionally permitted when access is not unconditionally permitted and at least one of the multiple TAIs is not part of a prohibited TAI list, and to determine that access is not permitted when all of the multiple TAIs are part of a prohibited TAI list for the UE.

[0139] As illustrated, the program code 1020 stored in the medium 1018 and / or memory 1016 may include a NAS request module 1022 that, when implemented by one or more processors 1004, configures one or more processors 1004 to send a non-access layer (NAS) request to a core network node such as an AMF 122 in the satellite radio cell via a RAN node when it is determined that access to the satellite radio cell is permitted via a radio transceiver 1002 or satellite transceiver 1003. The NAS request message may be, for example, an arbitrary uplink NAS message when it is determined that access is unconditionally permitted, and the NAS message may include a NAS registration request or a NAS connection request when it is determined that access is conditionally permitted.

[0140] As shown in the figure, the program code 1020 stored in the medium 1018 and / or memory 1016 may include a NAS response module 1024 that, when implemented by one or more processors 1004, configures one or more processors 1004 to receive NAS response messages from core network nodes in satellite radio cells via RAN nodes through a radio transceiver 1002 or satellite transceiver 1003.

[0141] As illustrated, the program code 1020 stored in the medium 1018 and / or memory 1016 may include a list update module 1026 that, when implemented by one or more processors 1004, causes one or more processors 1004 to store, for example, in memory 1016 or the medium 1018, all of which are not included in the current registration area or authorized area list in a list of prohibited TAs, and remove TAs included in a new list of a new registration area or authorized area from the list of prohibited TAs. For example, a NAS request message may include a NAS registration request, and a NAS response message may include a NAS registration acceptance message; or a NAS request message may include a NAS connection request, and a NAS response message may include a NAS connection acceptance message; a NAS acceptance message may be at least one of a registration area (RA) containing a first list of TAIs and an authorized TAI list containing a second list of TAIs; and one or more processors 1004 may be configured to remove each TAI in the first list of TAIs or the second list of TAIs, or TAIs in the first and second lists of TAIs, from the UE's list of prohibited TAIs if each TAI is part of a prohibited TAI list. In another example, the NAS request message may include a NAS registration request, and the NAS response message may include a NAS registration rejection message; or the NAS request message may include a NAS connection request, and the NAS response message may include a NAS connection rejection message, and the NAS response message may indicate a prohibited tracking area, include a list of TAIs, and one or more processors 1004 may be configured to add each TAI in the list of TAIs to a list of prohibited TAIs for the UE.In another example, the NAS request message may include a NAS registration request and the NAS response message may include a NAS registration rejection message, or the NAS request message may include a NAS connection request and the NAS response message may include a NAS connection rejection message, the NAS response message may indicate a prohibited tracking area and not include a list of TAIs, and one or more processors 1004 may be configured to add each of the multiple TAIs to a list of prohibited TAIs for the UE.

[0142] As shown in the figure, the program code 1020 stored in the medium 1018 and / or memory 1016 may include a registration module 1028 that, when implemented by one or more processors 1004, configures one or more processors 1004 to receive, for example, a new list of new registration or authorization areas via a radio transceiver 1002 or a satellite transceiver 1003.

[0143] As shown in the figure, the program code 1020 stored in the medium 1018 and / or memory 1016 may include a selection module 1030 that, when implemented by one or more processors 1004, causes one or more processors 1004 to treat the satellite radio cell as associated with a prohibited TA if any of several TAs for a PLMN in a radio cell broadcast from the satellite are on the list of prohibited TAs.

[0144] The methods described herein can be implemented by various means depending on the application. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In the case of hardware implementation, one or more processors 1004 can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.

[0145] In the case of an implementation of UE1000 including firmware and / or software, the methodology may be implemented in modules (e.g., procedures, functions, etc.) that perform separate functions described herein. Any machine-readable medium that tangibly embodies instructions may be used when performing the methods described herein. For example, software code may be stored in medium 1018 or memory 1016 and executed by one or more processors 1004, causing one or more processors 1004 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. Memory may be implemented inside one or more processors 1004 or outside one or more processors 1004. As used herein, the term “memory” means any type of long-term memory, short-term memory, volatile memory, non-volatile memory, or other memory, and is not limited to a particular type of memory or a particular number of memories, nor is it limited to a particular type of medium in which the memory is stored.

[0146] When implemented in firmware and / or software, the functions performed by UE1000 may be stored as one or more instructions or codes on a non-temporary computer-readable storage medium such as medium 1018 or memory 1016. Examples of storage media include computer-readable media encoded in data structures and computer-readable media encoded in computer programs. Computer-readable media include physical computer storage media. Storage media can be any available medium that can be accessed by a computer. Examples, but not limited to, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor storage, or any other medium that can be accessed by a computer and used to store desired program code in the form of instructions or data structures. As used herein, “disk” and “disc” include Compact Disc (CD), Laser Disc, Optical Disc, Digital Versatile Disc (DVD), Floppy Disc, and Blu-ray® Disc, where “disk” typically reproduces data magnetically, and “disc” reproduces data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0147] In addition to storage on a computer-readable storage medium, instructions and / or data for the UE 1000 may be provided as signals on a transmission medium included in a communication device. For example, a communication device including part or all of the UE 1000 may include a transceiver having signals indicating instructions and data. The instructions and data are stored in a non-temporary computer-readable medium 1018 or memory 1016 and configured to cause one or more processors 1004 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. That is, the communication device includes a transmission medium having signals indicating information for performing the disclosed functions. Initially, the transmission medium included in the communication device may include a first part of the information for performing the disclosed functions, and a second part may include a second part of the information for performing the disclosed functions.

[0148] Figure 11 shows an example of a hardware implementation of a core network node 1100 in a PLMN. The core network node 1100 may be, for example, an AMF122 as shown in Figures 1, 2, and 3, or an AMF908 as shown in Figure 9, or an MME that supports LTE or NB-IoT satellite access by the UE. The core network node 1100 may execute the signal flow in Figure 9 and the process flow 1400 in Figure 14 and the algorithms disclosed herein. The network node 1100 includes hardware components such as an external interface 1102 configured to communicate with other network components in the PLMN. The network node 1100 includes one or more processors 1104, memory 1116, and non-temporary computer-readable media 1118, which may be coupled with a bus 1107.

[0149] One or more processors 1104 may be implemented using a combination of hardware, firmware, and software. For example, one or more processors 1104 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 1120 on a non-temporary computer-readable medium such as a medium 1118 and / or memory 1116. In some embodiments, one or more processors 1104 may represent one or more circuits that can be configured to perform at least a portion of a data signal calculation procedure or process related to the operation of a network node 1100.

[0150] The medium 1118 and / or memory 1116 may store instructions or program code 1120, which, when executed by one or more processors 1104, causes one or more processors 1104 to operate as a special-purpose computer programmed to execute the techniques disclosed herein (e.g., the signal flow in Figure 9 and the process flow 1400 in Figure 14, and the supporting algorithms described herein). As exemplified by the network node 1100, the medium 1118 and / or memory 1116 may include one or more components or modules that can be implemented by one or more processors 1104 to execute the methods described herein. While the components or modules are illustrated as software in the medium 1118 executable by one or more processors 1104, it should be understood that the components or modules may be stored in memory 1116 or may be dedicated hardware either within or outside of the processors 1104.

[0151] Numerous software modules and data tables reside within the medium 1118 and / or memory 1116 and may be utilized by one or more processors 1104 to manage both communications and the functionalities described herein. The configuration of the contents of the medium 1118 and / or memory 1116, as shown in network node 1100, is merely illustrative, and it should be understood that the functionality of modules and / or data structures may be combined, separated, and / or structured in different ways depending on the implementation of network node 1100. While components or modules are illustrated as software within the medium 1118 and / or memory 1116 executable by one or more processors 1104, it should be understood that components or modules may be firmware or dedicated hardware either within or outside of the processors 1104.

[0152] As illustrated, the program code 1120 stored in the medium 1118 and / or memory 1116 includes a NAS request module 1122 which, when implemented by one or more processors 1104, configures one or more processors 1104 to receive non-access layer (NAS) request messages and one or more TAIs from radio access network (RAN) nodes via an external interface 1102, the NAS request messages being sent by the UE to the RAN node in the satellite radio cell, and the one or more TAIs being broadcast by the RAN node in the satellite radio cell, the TAIs indicating a TA where the UE is located.

[0153] As shown in the figure, the program code 1120 stored in the medium 1118 and / or memory 1116 may include a verification module 1124 that, when implemented by one or more processors 1104, causes one or more processors 1104 to determine whether the UE is allowed to access the satellite radio cell based on the TAI broadcast to the satellite radio cell by the RAN node.

[0154] As illustrated, the program code 1120 stored in the medium 1118 and / or memory 1116 may include a NAS response module 1126, when implemented by one or more processors 1104, which is configured to send a NAS acceptance message to the UE when the UE is permitted to access a satellite radio cell, for example, via an external interface. For example, the NAS request message may be a NAS registration request, the NAS acceptance message may be a NAS registration acceptance, the NAS request message may be a NAS connection request, and the NAS acceptance message may be a NAS connection acceptance. One or more processors 1104 may be configured to include a registration area (RA) in the NAS acceptance message. One or more processors 1104 may include the TAI of the TA where the UE is located in the RA when the TAI of the TA where the UE is located is one of the TAIs broadcast to the satellite radio cell by a RAN node. One or more processors 1104 may be configured to include in the RA at least one of the TAIs broadcast to the satellite radio cell by the RAN node if the TAI of the TA where the UE is located is not one of the TAIs broadcast to the satellite radio cell by the RAN node. One or more processors 1104 may be configured to include in the RA at least one of the TAIs broadcast to the satellite radio cell by the RAN node if the TAI instruction for the TA where the UE is located indicates that the TA where the UE is located is not determined by the RAN node.

[0155] The methods described herein can be implemented by various means depending on the application. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In hardware implementation form, one or more processors 1104 can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.

[0156] In the case of an implementation of a network node 1100 including firmware and / or software, the methodology may be implemented in modules (e.g., procedures, functions, etc.) that perform separate functions described herein. Any machine-readable medium that tangibly embodies instructions may be used when performing the methods described herein. For example, software code may be stored in a medium 1118 or memory 1116 and executed by one or more processors 1104, causing one or more processors 1104 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. Memory may be implemented inside one or more processors 1104 or outside one or more processors 1104. As used herein, the term “memory” means any type of long-term memory, short-term memory, volatile memory, non-volatile memory, or other memory, and is not limited to a particular type of memory or a particular number of memories, nor is it limited to a particular type of medium in which the memory is stored.

[0157] When implemented in firmware and / or software, the functions performed by the network node 1100 may be stored as one or more instructions or codes on a non-temporary computer-readable storage medium such as medium 1118 or memory 1116. Examples of storage media include computer-readable media encoded in data structures and computer-readable media encoded in computer programs. Computer-readable media include physical computer storage media. Storage media can be any available medium that can be accessed by a computer. Examples, but not limited to, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor storage, or any other medium that can be accessed by a computer and used to store desired program code in the form of instructions or data structures. As used herein, “disk” and “disc” include Compact Disc (CD), Laser Disc, Optical Disc, Digital Versatile Disc (DVD), Floppy Disc, and Blu-ray Disc, where “disk” typically reproduces data magnetically, and “disc” reproduces data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0158] In addition to storage on computer-readable storage media, instructions and / or data to the network node 1100 may be provided as signals on a transmission medium included in the communication device. For example, a communication device including some or all of the network node 1100 may include transceivers having signals indicating instructions and data. The instructions and data are stored on a non-temporary computer-readable medium, for example, medium 1118 or memory 1116, and are configured to cause one or more processors 1104 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. That is, the communication device includes a transmission medium having signals indicating information for performing the disclosed functions. Initially, the transmission medium included in the communication device may include a first portion of the information for performing the disclosed functions, and a second portion of the information for performing the disclosed functions may include a second portion.

[0159] Figure 12 shows an example of a hardware implementation of RAN node 1200, such as NR node B (gNB) or eNB. RAN node 1200 may correspond to (i) gNB106 as illustrated in Figure 1, (ii) gNB202 in SV202 as illustrated in Figure 2, or (iii) gNB-DU302 in SV302 or gNB-CU307 as illustrated in Figure 3. RAN node 1200 may execute the signal flow 900 in Figure 9 and the process flow 1300 in Figure 13, as well as the algorithms disclosed herein. The RAN node 1200 may include hardware components such as an external interface 1202, which may have one or more entities in the core network within the PLMN, such as the AMF122 or UPF130 of 5GCN110 shown in Figure 2, and earth station 104, as well as other gNBs, UE105 (for example, if the RAN node 1200 is part of SV202 or SV302), and one or more wired and / or wireless interfaces that can connect to and communicate with other elements in the wireless network, either directly or via one or more intermediate networks and / or one or more network entities, as shown in Figures 1, 2, and 3. The external interface 1202 may include one or more antennas to support wireless backhaul to the wireless interface and / or elements in the wireless network. The RAN node 1200 further includes one or more processors 1204, memory 1216, and non-temporary computer-readable media 1218, which may be coupled with bus 1207. RAN node 1200 is illustrated as including gNB-DU1212 and / or gNB-CU1214 (for example, if RAN node 1200 corresponds to gNB202 in Figure 2, which has gNB202 containing gNB-CU and one or more gNB-DUs), which may be hardware components or may be implemented by one or more specially configured processors 1204. If RAN node 1200 itself corresponds to gNB-DU (e.g., gNB-DU 302) or gNB-CU (e.g., gNB-CU 307), then gNB-DU1212 and gNB-CU1214 may not be present.

[0160] One or more processors 1204 may be implemented using a combination of hardware, firmware, and software. For example, one or more processors 1204 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 1220 on a non-temporary computer-readable medium such as a medium 1218 and / or memory 1216. In some embodiments, one or more processors 1204 may represent one or more circuits that can be configured to perform at least a portion of a data signal calculation procedure or process related to the operation of the RAN node 1200.

[0161] The medium 1218 and / or memory 1216 may store instructions or program code 1220, which, when executed by one or more processors 1204, causes one or more processors 1204 to operate as a special-purpose computer programmed to execute the techniques disclosed herein (e.g., the signal flow in Figure 9 and the process flow 1300 in Figure 13, and the supporting algorithms described herein). As exemplified by the RAN node 1200, the medium 1218 and / or memory 1216 may include one or more components or modules that can be implemented by one or more processors 1204 to execute the methods described herein. While the components or modules are illustrated as software in the medium 1218 executable by one or more processors 1204, it should be understood that the components or modules may be stored in memory 1216 or may be dedicated hardware either within or outside of one or more processors 1204.

[0162] Several software modules and data tables reside in medium 1218 and / or memory 1216 and may be utilized by one or more processors 1204 to manage both the communications and functionalities described herein. The configuration of the contents of medium 1218 and / or memory 1216, as shown in RAN node 1200, is merely illustrative, and it should be understood that the functionality of modules and / or data structures may be combined, separated, and / or structured in different ways depending on the implementation of RAN node 1200. While components or modules are illustrated as software in medium 1218 and / or memory 1216 executable by one or more processors 1204, it should be understood that components or modules may be firmware or dedicated hardware either within or outside of the one or more processors 1204.

[0163] As shown in the figure, the program code 1220 stored in the medium 1218 and / or memory 1216 may include a TAI module 1221 that, when implemented by one or more processors 1204, configures one or more processors 1204 to broadcast one or more tracking area (TA) identifiers (TAIs) in a satellite radio cell via an external interface 1202.

[0164] As illustrated, the program code 1220 stored in the medium 1218 and / or memory 1216 may include a NAS request module 1222 that, when implemented by one or more processors 1204, configures one or more processors 1204 to receive non-access layer (NAS) messages from UEs transmitted by UEs in a satellite radio cell via an external interface 1202. One or more processors 1204 may be configured to send the NAS message to a core network node via the external interface 1202, including a TAI for the TA where the UE is located and one or more TAIs broadcast in the satellite radio cell along with the NAS message. One or more processors 1204 may be configured to send the NAS message to a core network node via the external interface 1202, including multiple TAIs broadcast in the satellite radio cell and an instruction indicating that the TA where the UE is located cannot be determined along with the NAS message.

[0165] As shown in the figure, the program code 1220 stored in the medium 1218 and / or memory 1216 may include a TAC selection module 1224 which, when implemented by one or more processors 1204, is configured so that one or more processors 1204 determine the TA where the UE is located.

[0166] The methods described herein can be implemented by various means depending on the application. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. In the case of hardware implementation, one or more processors 1204 can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.

[0167] In the case of an implementation of the RAN node 1200 including firmware and / or software, the methodology may be implemented in modules (e.g., procedures, functions, etc.) that perform separate functions described herein. Any machine-readable medium that tangibly embodies instructions may be used when performing the methods described herein. For example, software code may be stored in medium 1218 or memory 1216 and executed by one or more processors 1204, causing one or more processors 1204 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. Memory may be implemented inside one or more processors 1204 or outside one or more processors 1204. As used herein, the term “memory” means any type of long-term memory, short-term memory, volatile memory, non-volatile memory, or other memory, and is not limited to a particular type of memory or a particular number of memories, nor is it limited to a particular type of medium in which the memory is stored.

[0168] When implemented in firmware and / or software, the functions performed by the RAN node 1200 may be stored as one or more instructions or codes on a non-temporary computer-readable storage medium such as medium 1218 or memory 1216. Examples of storage media include computer-readable media encoded in data structures and computer-readable media encoded in computer programs. Computer-readable media include physical computer storage media. Storage media can be any available medium that can be accessed by a computer. Examples, but not limited to, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, semiconductor storage, or any other medium that can be accessed by a computer and used to store desired program code in the form of instructions or data structures. As used herein, “disk” and “disc” include Compact Disc (CD), Laser Disc, Optical Disc, Digital Versatile Disc (DVD), Floppy Disc, and Blu-ray Disc, where “disk” typically reproduces data magnetically, and “disc” reproduces data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0169] In addition to storage on computer-readable storage media, instructions and / or data to the RAN node 1200 may be provided as signals on a transmission medium included in a communication device. For example, a communication device including part or all of the RAN node 1200 may include transceivers having signals indicating instructions and data. The instructions and data are stored on a non-temporary computer-readable medium, for example, medium 1218 or memory 1216, and are configured to cause one or more processors 1204 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. That is, the communication device includes a transmission medium having signals indicating information for performing the disclosed functions. Initially, the transmission medium included in the communication device may include a first portion of the information for performing the disclosed functions, and a second portion of the information for performing the disclosed functions may include a second portion.

[0170] Figure 13 illustrates Procedure 1300 for supporting satellite radio access to a public land mobile network (PLMN) served by user equipment (e.g., UE105, UE902, UE1000) as performed by a Radio Access Network (RAN) node. The RAN node may correspond to gNB106, gNB202, gNB307, gNB906, RAN node 1200, or an eNB or ng-eNB supporting LTE for the UE, or an eNB supporting NB-IOT access for the UE. Generally, Procedure Example 1300 is applicable to Options C+D and Rules 1-4 described above.

[0171] As shown in the figure, in block 1302, the RAN node broadcasts one or more Tracking Area (TA) identifiers (TAIs) within the satellite radio cell, for example, as discussed in Stage 2 of Figure 9. The unit broadcasting one or more Tracking Area (TA) identifiers (TAIs) within the satellite radio cell may, for example, have an external interface 1202 and, in the RAN node 1200 of Figure 12, have dedicated hardware or one or more processors 1204 that implement executable code or software instructions in a medium 1218 such as memory 1216 and / or TAI module 1221.

[0172] In block 1304, the RAN node receives a Non-Access Layer (NAS) message from the UE, which is transmitted by the UE in the satellite radio cell, for example, as discussed in stage 5 of Figure 9. The unit that receives the Non-Access Layer (NAS) message from the UE, transmitted by the UE in the satellite radio cell, may have, for example, an external interface 1202 and, in the RAN node 1200 of Figure 12, dedicated hardware, or one or more processors 1204 that implement executable code or software instructions in a medium 1218 such as memory 1216 and / or NAS request module 1222.

[0173] In block 1306, the RAN node determines the TA where the UE is located, as discussed, for example, in stage 6 of Figure 9, and with reference to options C and C+D. The unit that determines the TA where the UE is located may be, for example, in the RAN node 1200 of Figure 12, one or more processors 1204 that have dedicated hardware or implement executable code or software instructions in a medium 1218 such as memory 1216 and / or TAC selection module 1224.

[0174] In block 1308, the RAN node sends a NAS message to the core network node, including with the NAS message the TAI for the TA where the UE is located and one or more TAIs broadcast within the satellite radio cell, as discussed, for example, in stage 7 of Figure 9 and in relation to option C+D. The unit for sending the NAS message to the core network node and including with the NAS message the TAI for the TA where the UE is located and one or more TAIs broadcast within the satellite radio cell may, for example, have an external interface 1202 and, in the RAN node 1200 of Figure 12, have dedicated hardware or one or more processors 1204 that implement executable code or software instructions in a medium 1218 such as memory 1216 and / or NAS request module 1222.

[0175] In one embodiment, as discussed with reference to Figure 9, the RAN node may be an NR node B (gNB), the core network node may be an access and mobility management function (e.g., AMF122), or the RAN node may be an evolved node B (eNB), and the core network node may be a mobility management entity (MME).

[0176] In one embodiment, the one or more TAIs broadcast within a satellite radio cell may be a single TAI, for example, as discussed in relation to hard TAI updates in connection with Figure 7.

[0177] In one embodiment, the RAN node may fail to determine the TA where the UE is located, for example, as discussed in stage 6 of Figure 9. The RAN node then sends a NAS message to the core network node, which may include, along with the NAS message, one or more TAIs broadcast within the satellite radio cell and an instruction indicating that the TA where the UE is located cannot be determined, for example, as discussed in stages 6 and 7 of Figure 9 and discussed in relation to option C+D. The unit for failing to determine the TA where the UE is located may, for example, in the RAN node 1200 of Figure 12, have dedicated hardware or one or more processors 1204 that implement executable code or software instructions in a medium 1218 such as memory 1216 and / or TAC selection module 1224. A unit for sending a NAS message to the core network and including, along with the NAS message, multiple TAIs broadcast in satellite radio cells and an instruction indicating that the TA on which the UE is located cannot be determined, may, for example, have an external interface 1202 and, in the RAN node 1200 in Figure 12, have dedicated hardware or one or more processors 1204 that implement executable code or software instructions in a medium 1218 such as memory 1216 and / or NAS request module 1222.

[0178] Figure 14 shows a flowchart of Procedure Example 1400 for supporting satellite radio access to the Serving Public Land Mobile Network (PLMN) by user equipment (e.g., UE105, UE902, UE1000) as performed by a core network node. The core network node may correspond to AMF122, AMF908, core network node 1100, or an MME supporting LTE or NB-IoT satellite access for the UE. Generally, Procedure Example 1400 is applicable to Options C+D and Rules 1-4 described above.

[0179] As shown in the figure, in block 1402, the core network node receives a non-access layer (NAS) request message and one or more tracking area (TA) identifiers (TAIs) from a radio access network (RAN) node, the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include a TAI broadcast by the RAN node in the satellite radio cell, as discussed in stages 2, 5, 6, and 7 of Figure 9 and in relation to option C+D, and an instruction for the TAI for the TA where the UE is located. A unit that receives Non-Access Layer (NAS) request messages and one or more Tracking Area (TAI) identifiers (TAIs) from a Radio Access Network (RAN) node may, for example, have an external interface 1102 and, within the core network node 1100 in Figure 11, have dedicated hardware or be one or more processors 1104 that implement executable code or software instructions in a medium 1118 such as memory 1116 and / or NAS request module 1122, the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and one or more TAIs include a TAI broadcast by the RAN node within the satellite radio cell and an indication of the TAI for the TA where the UE is located.

[0180] In block 1404, the core network node may determine whether the UE is permitted to access the satellite radio cell based on the TAI broadcast within the satellite radio cell by the RAN node, as discussed in stage 8 of Figure 9, with reference to option C+D, and with reference to rule 2. The unit that determines whether the UE is permitted to access the satellite radio cell based on the TAI broadcast within the satellite radio cell by the RAN node may, for example, have dedicated hardware in the external interface 1102 and, in the core network node 1100 of Figure 11, one or more processors 1104 that implement executable code or software instructions in a medium 1118 such as memory 1116 and / or verification module 1124.

[0181] In block 1406, the core network node may send a NAS Acceptance message to the UE in response to a decision that the UE is permitted to access the satellite radio cell, as discussed in stages 8 and 11 of Figure 9, discussed with reference to option C+D, and discussed with reference to rule 2. The unit that sends the NAS Acceptance message to the UE in response to a decision that the UE is permitted to access the satellite radio cell may, for example, have dedicated hardware in the external interface 1102 and, in the core network node 1100 of Figure 11, or one or more processors 1104 that implement executable code or software instructions in a medium 1118 such as memory 1116 and / or NAS response module 1126. [What about NAS rejection (stage 9 of Figure 9)?]

[0182] In one embodiment, for example, as discussed with reference to Figure 9, the RAN node may be an NR node B (e.g., gNB106, 202, or 307), the core network node may be an access and mobility management function (e.g., AMF122), or the RAN node may be an evolved NodeB (eNB), and the core network node may be a mobility management entity (MME).

[0183] In one embodiment, one or more TAIs broadcast within a satellite radio cell may include a single TAI, for example, as discussed in relation to hard TAI updates in connection with Figure 7.

[0184] In one embodiment, for example, as discussed in stages 5 and 11 of Figure 9, a NAS request message may be a NAS registration request, a NAS acceptance message may be a NAS registration acceptance, a NAS request message may be a NAS connection request, and a NAS acceptance message may be a NAS connection acceptance. A core network node may include in its RA the TAI for the TA where the UE is located if the TAI for the TA where the UE is located is one of the TAIs broadcast within the satellite radio cell by the RAN node, for example, as discussed in stage 11 of Figure 9 and in reference to option C+D. A core network node may include in its RA at least one of the TAIs broadcast within the satellite radio cell by the RAN node if the TAI for the TA where the UE is located is not one of the TAIs broadcast within the satellite radio cell by the RAN node, for example, as discussed in stage 11 of Figure 9 and in reference to option C+D. The core network node may include in its RA at least one of the TAIs broadcast within the satellite radio cell by the RAN node, for example, if the display of the TAI for the TA where the UE is located indicates that the TA where the UE is located is not determined by the RAN node, as discussed in Stage 11 of Figure 9 and in relation to Option C+D.A unit that includes a registration area (RA) in the NAS acceptance, and includes in the RA the TAI for the TA where the UE is located if the TAI for the TA where the UE is located is one of the TAIs broadcast in the satellite radio cell by the RAN node, and includes in the RA at least one of the TAIs broadcast in the satellite radio cell by the RAN node if the TAI for the TA where the UE is located is not one of the TAIs broadcast in the satellite radio cell by the RAN node, and includes in the RA at least one of the TAIs broadcast in the satellite radio cell by the RAN node if the indication of the TAI for the TA where the UE is located indicates that the TA where the UE is located is not determined by the RAN node, may, for example, have an external interface 1102 and, in the core network node 1100 of Figure 11, one or more processors 1104 that have dedicated hardware or implement executable code or software instructions in a medium 1118 such as memory 1116 and / or NAS response module 1126.

[0185] Figure 15 shows a flowchart of an exemplary procedure 1500 performed by a UE to support satellite radio access to the Serving Public Land Mobile Network (PLMN) by user equipment (e.g., UE105, UE902, UE1000). Generally, example procedure 1500 can be applied to options C+D and rules 1-4 described above.

[0186] As illustrated, in block 1502, the UE may receive multiple tracking area (TA) identifiers (TAIs) broadcast within the satellite radio cell by a radio access network (RAN) node, for example, as discussed in stage 2 of Figure 9. A unit that receives multiple tracking area (TA) identifiers (TAIs) broadcast within the satellite radio cell by a radio access network (RAN) node may, for example, a radio transceiver 1002 and, in UE 1000 of Figure 10, one or more processors 1004 that have dedicated hardware or implement executable code or software instructions in a medium 1018 such as memory 1016 and / or TAI module 1021.

[0187] In block 1504, the UE may determine whether access to the satellite radio cell is permitted based on a plurality of TAIs, for example, as discussed in Stage 2 and Rule 1 of Figure 9. The unit that determines whether access to the satellite radio cell is permitted based on a plurality of TAIs may, for example, in UE 1000 of Figure 10, have dedicated hardware or one or more processors 1004 that implement executable code or software instructions in a medium 1018 such as memory 1016 and / or TAI module 1021.

[0188] In block 1506, the UE may, for example, as discussed in stage 5 of Figure 9, send a Non-Access Layer (NAS) request message to the core network node via the RAN node in response to a decision that access to the satellite radio cell is permitted. The unit that sends a Non-Access Layer (NAS) request message to the core network node via the RAN node in response to a decision that access to the satellite radio cell is permitted may, for example, a radio transceiver 1002 and one or more processors 1004 in UE 1000 of Figure 10 that have dedicated hardware or implement executable code or software instructions in a medium 1018 such as memory 1016 and / or NAS request module 1022.

[0189] In block 1508, the UE receives NAS response messages in the satellite radio cell from the core network node via the RAN node, as discussed, for example, in stage 9 or 11 of Figure 9 and discussed with reference to rule 2. The unit that receives NAS response messages in the satellite radio cell from the core network node via the RAN node may, for example, a radio transceiver 1002 and one or more processors 1004 that have dedicated hardware or implement executable code or software instructions in a medium 1018 such as memory 1016 and / or NAS response module 1024, in UE 1000 of Figure 10.

[0190] In one embodiment, the RAN node may be an NR node B (e.g., gNB106, 202, or 307), as discussed in Figure 9, the core network node may be an access and mobility management function (e.g., AMF122), or the RAN node may be an evolved NodeB (eNB), and the core network node may be a mobility management entity (MME).

[0191] In one embodiment, for example, as discussed in Stage 2 of Figure 9 and discussed with reference to Rules 1 and 2, the UE may determine whether access to a satellite radio cell is permitted based on a set of TAIs by determining that access is unconditionally permitted if at least one of the set of TAIs is part of the current UE registration area (RA) or part of the UE's permitted TAI list; that access is conditionally permitted if access is not unconditionally permitted and at least one of the set of TAIs is not part of the UE's prohibited TAI list; and that access is not permitted if all of the set of TAIs are part of the UE's prohibited TAI list. A unit that determines whether access to a satellite radio cell is permitted based on multiple TAIs includes a unit that determines access is unconditionally permitted if at least one of the multiple TAIs is part of the current UE registration area (RA) or part of the UE's permitted TAI list; a unit that determines access is conditionally permitted if access is not unconditionally permitted and at least one of the multiple TAIs is not part of the UE's prohibited TAI list; and a unit that determines access is not permitted if all of the multiple TAIs are part of the UE's prohibited TAI list, which may, for example, in UE 1000 in Figure 10, have dedicated hardware or one or more processors 1004 that implement executable code or software instructions in a medium 1018 such as memory 1016 and / or TAI module 1021.

[0192] In one embodiment, if it is determined that access is to be granted unconditionally, the NAS request message may include an optional uplink NAS message, where if it is determined that access is to be granted conditionally, the NAS request message may include a NAS registration request or a NAS connection request, for example, as discussed in stage 11 of Figure 9.

[0193] In one embodiment, a NAS request message may include a NAS registration request, and a NAS response message may include a NAS registration acceptance message, or a NAS request message may include a NAS connection request, and a NAS response message may include a NAS connection acceptance message, where the NAS acceptance message includes at least one of a registration area (RA) containing a first list of TAIs and an authorized TAI list containing a second list of TAIs, as discussed, for example, in stages 5 and 11 of Figure 9 and in relation to rules 1 and 2. The UE may then remove each TAI from the first list of TAIs or the second list of TAIs, or from the first and second lists of TAIs, from the UE's list of prohibited TAIs, as discussed, for example, in stage 12 of Figure 9 and in relation to rule 4, if each TAI is part of a prohibited list of TAIs. If each TAI is part of a TAI ban list, the unit that removes each TAI in the first list of TAIs, the second list of TAIs, or both of the first and second lists of TAIs from the UE's ban list of TAIs may, for example, in the UE 1000 of Figure 10, have dedicated hardware or one or more processors 1004 that implement executable code or software instructions in a medium 1018 such as memory 1016 and / or list update module 1026.

[0194] In one embodiment, a NAS request message may include a NAS registration request, and a NAS response message may include a NAS registration rejection message, or a NAS request message may include a NAS connection request, and a NAS response message may include a NAS connection rejection message, where the NAS response message includes, for example, a prohibited tracking area and a list of TAIs, as discussed in stages 5 and 9 of Figure 9. The UE may then add each TAI in the list of TAIs to the UE's prohibited TAI list, for example, as discussed in stage 10 of Figure 9. The unit that adds each TAI in the list of TAIs to the UE's prohibited TAI list may, for example, in UE 1000 of Figure 10, have dedicated hardware or one or more processors 1004 that implement executable code or software instructions in a medium 1018 such as memory 1016 and / or a list update module 1026.

[0195] The unit that adds each TAI in the TAI list to the UE's list of prohibited TAIs may, for example, in UE1000 in Figure 10, have dedicated hardware or one or more processors 1004 that implement executable code or software instructions in a medium 1018 such as memory 1016 and / or list update module 1026. The UE may then add each TAI of the multiple TAIs to the UE's list of prohibited TAIs, for example, as discussed in stage 10 of Figure 9 and discussed with reference to rule 3. The unit that adds each TAI of the multiple TAIs to the UE's list of prohibited TAIs may, for example, in UE1000 in Figure 10, have dedicated hardware or one or more processors 1004 that implement executable code or software instructions in a medium 1018 such as memory 1016 and / or list update module 1026.

[0196] The abbreviations used are as shown in Table 1 below.

[0197] [Table 2]

[0198] Substantial modifications may be made to meet specific requirements. For example, customized hardware may be used, and / or certain elements may be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, may be employed.

[0199] The configuration may be described as a process shown as a flowchart or block diagram. While flowcharts or block diagrams may describe the operation as a sequential process, many operations can be performed in parallel or simultaneously. In addition, the order of operations may be rearranged. The process may have additional steps not included in the diagram. Furthermore, examples of methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments for performing the required tasks may be stored in a non-temporary computer-readable medium such as a storage medium. The processor can then perform the described tasks.

[0200] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as they are commonly understood or conventionally understood. The articles “a” and “an” used herein refer to one or more (i.e., at least one) grammatical objects of the article. For example, “an element” means one or more elements. When referring to measurable values ​​such as quantity or duration, “about” and / or “approximately” used herein include variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, where such variations are appropriate in the context of the systems, devices, circuits, methods, and other forms of implementation described herein. As used herein, “substantially” also includes variations of ±20%, ±10%, ±5%, or +0.1% from a specified value, where such variations are appropriate in the context of the systems, devices, circuits, methods, and other implementations described herein.

[0201] As used herein, including in the claims, "or" in a list of items ending in "at least one of" or "one or more of" indicates a disjunctive list, such as when the list "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or a combination of two or more features (e.g., AA, AAB, ABBC, etc.). Also, as used herein, unless otherwise specified, the statement that a function or operation is "based on" an item or condition means that the function or operation is based on the item or condition stated, and may be based on one or more items and / or conditions in addition to the item or condition stated.

[0202] As used herein, mobile device, user equipment (UE), or mobile station (MS) means a device such as a cellular or other wireless communication device, a smartphone, a tablet, a personal communication system (PCS) device, a personal navigation device (PND), a personal information manager (PIM), a personal digital assistant (PDA), a laptop, or any other suitable mobile device capable of receiving wireless communications and / or navigation signals, such as navigation positioning signals. The terms “mobile station” (or “mobile device,” “wireless device,” or “user equipment”) are also intended to include devices that communicate with a PND, such as via short-range wireless connection, infrared connection, wireline connection, or other connection, whether the satellite signal reception, assisted data reception, and / or location-related processing are performed in the device or in the personal navigation device (PND). Furthermore, “Mobile Station” or “User Equipment” includes all devices, including wireless communication devices, computers, laptops, tablet devices, etc., that are capable of communicating with a server via the Internet, Wi-Fi, or other networks, regardless of whether satellite signal reception, support data reception, and / or location-related processing are performed on the device, on the server, or on another device or node associated with the network. Any operational combination of the above shall be considered a “Mobile Station” or “User Equipment.” A mobile device or user equipment (UE) may also be referred to as a mobile terminal, terminal, device, Secure User Plane Location Enabled Terminal (SET), target device, target, or any other name.

[0203] Some of the techniques, processes, and / or implementations presented herein may conform in whole or in part to one or more standards, but in some embodiments, such techniques, processes, and / or implementations may not conform in whole or in part to one or more such standards.

[0204] In light of this description, embodiments may include various combinations of features. Examples of implementations are described in the following numbered clauses. Close 1. A method performed by a Radio Access Network (RAN) node supporting satellite radio access of a user device (UE) to a Serving Public Land Mobile Network (PLMN), comprising: broadcasting one or more tracking area (TA) identifiers (TAIs) in a satellite radio cell; receiving a non-access layer (NAS) message transmitted by the UE in the satellite radio cell from a user device (UE); determining the TA in which the UE is located; and transmitting the NAS message to a core network node, including, together with the NAS message, the TAI for the TA in which the UE is located and one or more TAIs broadcast in the satellite radio cell.

[0205] Close 2. The method according to Close 1, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0206] Close 3. The method according to any one of Close 1 to 2, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0207] Close 4. The method according to any one of Close 1 to 3, further comprising failing to determine the TA on which the UE is located, transmitting the NAS message to the core network node, and including together with the NAS message one or more TAIs to be broadcast in the satellite radio cell, and an instruction indicating that the TA on which the UE is located could not be determined.

[0208] Close 5. A radio access network (RAN) node configured to support satellite radio access of a user device (UE) to a serving public land mobile network (PLMN), comprising an external interface configured to communicate wirelessly with a network entity, at least one memory, and at least one processor coupled to the external interface, wherein the at least one memory and the at least one processor broadcast one or more tracking area (TA) identifiers (TAIs) in a satellite radio cell via the external interface, receive a non-access layer (NAS) message transmitted by the UE into the satellite radio cell from the UE via the external interface, determine the TA where the UE is located, transmit the NAS message to a core network node via the external interface, and include, along with the NAS message, the TAI for the TA where the UE is located and one or more TAIs broadcast in the satellite radio cell.

[0209] Close 6. The RAN node according to Close 5, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an evolved Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0210] Close 7. The RAN node according to any one of Close 5 to 6, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0211] Close 8. The RAN node according to any one of Close 5 to 7, wherein at least the processor is further configured to fail to determine the TA on which the UE is located, and to transmit the NAS message to the core network node via the external interface, and together with the NAS message include one or more TAIs to be broadcast in the satellite radio cell and an instruction indicating that the TA on which the UE is located could not be determined.

[0212] Close 9. A radio access network (RAN) node configured to support satellite radio access of a user device (UE) to a serving public land mobile network (PLMN), comprising: a unit that broadcasts one or more tracking area (TA) identifiers (TAIs) in a satellite radio cell; a unit that receives non-access layer (NAS) messages transmitted by the UE in the satellite radio cell from a user device (UE); a unit that determines the TA in which the UE is located; and a unit that transmits the NAS message to a core network node, including, together with the NAS message, the TAI for the TA in which the UE is located and one or more TAIs broadcast in the satellite radio cell.

[0213] Close 10. The RAN node according to Close 9, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0214] Close 11. The RAN node according to any one of Close 9 to 10, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0215] Close 12. The RAN node according to any one of Close 9 to 11, further comprising a unit that fails to determine the TA on which the UE is located, and a unit that transmits the NAS message to the core network node and, together with the NAS message, includes one or more TAIs broadcast in the satellite radio cell and an instruction indicating that the TA on which the UE is located could not be determined.

[0216] Closed 13. A non-temporary storage medium containing program code stored thereon, wherein the program code is operable to constitute at least one processor in a radio access network (RAN) node for supporting satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN), the program code comprising instructions for broadcasting one or more tracked area (TA) identifiers (TAI) in a satellite radio cell, receiving the non-access layer (NAS) message transmitted by the UE in the satellite radio cell, determining the TA where the UE is located, transmitting the NAS message to a core network node, and including together with the NAS message the TAI for the TA where the UE is located and one or more TAIs broadcast in the satellite radio cell.

[0217] Close 14. The non-temporary storage medium according to Close 13, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0218] Close 15. The non-temporary storage medium according to any one of Close 13 to 14, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0219] Close 16. The non-temporary storage medium according to any one of Close 13 to 15, wherein the program code further includes instructions that fail to determine the TA on which the UE is located, transmit the NAS message to the core network node, and together with the NAS message, include one or more TAIs to be broadcast in the satellite radio cell, and instructions indicating that the TA on which the UE is located could not be determined.

[0220] Close 17. A method performed by a core network node to support satellite radio access to a Serving Public Land Mobile Network (PLMN) by a user device (UE), comprising: receiving a Non-Access Layer (NAS) request message and one or more Tracking Area (TA) identifiers (TAIs) from a Radio Access Network (RAN) node; determining whether the UE is permitted to access the satellite radio cell based on TAIs broadcast in the satellite radio cell by the RAN node; and sending a NAS Acceptance message to the UE in response to the determination that the UE is permitted to access the satellite radio cell, wherein the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell; and the one or more TAIs include TAIs broadcast in the satellite radio cell by the RAN node and instructions for TAIs for the TA where the UE is located.

[0221] Close 18. The method according to Close 17, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0222] Close 19. The method according to any one of Close 1 to 18, characterized in that 17 or more TAIs broadcast in the satellite radio cell include a single TAI.

[0223] Close 20. The method according to any one of paragraphs 17 to 19, characterized in that the NAS request message includes a NAS registration request and the NAS acceptance message includes a NAS registration acceptance, or the NAS request message includes a NAS connection request and the NAS acceptance message includes a NAS connection acceptance, wherein the NAS request message includes a registration area (RA), and if the TAI for the TA where the UE is located is one of the TAIs broadcast in the satellite radio cell by the RAN node, the RA includes the TAI for the TA where the UE is located; if the TAI for the TA where the UE is located is not one of the TAIs broadcast in the satellite radio cell by the RAN node, the RA includes at least one of the TAIs broadcast in the satellite radio cell by the RAN node; and if the indication of the TAI for the TA where the UE is located indicates that the TA where the UE is located was not determined by the RAN node, the RA includes at least one of the TAIs broadcast in the satellite radio cell by the RAN node.

[0224] Close 21. A core network node configured to support satellite radio access by a user device (UE) to a Serving Public Land Mobile Network (PLMN), comprising an external interface configured to communicate wirelessly with a network entity, at least one memory, and at least one processor coupled to the external interface, wherein the at least one memory and the at least one processor are configured to receive non-access layer (NAS) request messages and one or more tracked area (TAI) identifiers (TAI) from a radio access network (RAN) node via the external interface, determine whether a user device (UE) is permitted to access the satellite radio cell based on the TAI broadcast by the RAN node in the satellite radio cell, and transmit a NAS acceptance message to the UE via the external interface in response to the determination that the UE is permitted to access the satellite radio cell, wherein the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include a TAI broadcast by the RAN node in the satellite radio cell and an instruction for a TAI for the TA where the UE is located.

[0225] Close 22. The core network node according to Close 21, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an evolved Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0226] Close 23. The core network node according to any one of Close 21 to 22, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0227] Close 24. The NAS request message includes a NAS registration request and the NAS acceptance message includes a NAS registration acceptance, or the NAS request message includes a NAS connection request and the NAS acceptance message includes a NAS connection acceptance, and the at least one processor includes a registration area (RA) in the NAS acceptance message, and if the TAI for the TA where the UE is located is one of the TAIs broadcast in the satellite radio cell by the RAN node, the RA includes the TAI for the TA where the UE is located, and if the TAI for the TA where the UE is located is not one of the TAIs broadcast in the satellite radio cell by the RAN node, the RA includes at least one of the TAIs broadcast in the satellite radio cell by the RAN node, and if the indication of the TAI for the TA where the UE is located indicates that the TA where the UE is located was not determined by the RAN node, the RA The core network node according to any one of clauses 21 to 23, further configured to include in the RA at least one of the TAIs broadcast in the satellite radio cell by the N node.

[0228] Close 25. A core network node configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN) by a user device (UE), comprising: a unit that receives a Non-Access Layer (NAS) request message and one or more Tracking Area (TA) identifiers (TAIs) from a Radio Access Network (RAN) node; a unit that determines whether the UE is permitted to access the satellite radio cell based on TAIs broadcast in the satellite radio cell by the RAN node; and a unit that, in response to the determination that the UE is permitted to access the satellite radio cell, transmits a NAS acceptance message to the UE, wherein the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include TAIs broadcast in the satellite radio cell by the RAN node and instructions for TAIs for the TA where the UE is located.

[0229] Close 26. The core network node according to Close 25, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0230] Close 27. The core network node according to any one of Close 25 to 26, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0231] Close 28. A unit including a registration area (RA) in the NAS acceptance message, and a unit including the TAI for the TA where the UE is located in the RA if the TAI for the TA where the UE is located is one of the TAIs broadcast in the satellite radio cell by the RAN node, and a unit including at least one of the TAIs broadcast in the satellite radio cell by the RAN node in the RA if the TAI for the TA where the UE is located is not one of the TAIs broadcast in the satellite radio cell by the RAN node, and an instruction for the TAI for the TA where the UE is located indicates that the TA where the UE is located was not determined by the RAN node, the RA The core network node according to any one of Clauses 25 to 27, characterized by including a unit in which the RA includes at least one of the TAIs broadcast in the satellite radio cell by the N node, wherein the NAS request message includes a NAS registration request and the NAS acceptance message includes a NAS registration acceptance, or the NAS request message includes a NAS connection request and the NAS acceptance message includes a NAS connection acceptance.

[0232] Closed 29. A non-temporary storage medium containing program code stored thereon, wherein the program code is operable to constitute at least one processor in a core network node for supporting satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN), the program code includes instructions for receiving a non-access layer (NAS) request message and one or more tracked area (TAI) identifiers (TAI) from a radio access network (RAN) node, determining whether the UE is permitted to access the satellite radio cell based on TAIs broadcast by the RAN node in the satellite radio cell, and in response to the determination that the UE is permitted to access the satellite radio cell, the NAS request message is transmitted by the UE to the RAN node in the satellite radio cell, and the one or more TAIs include TAIs broadcast by the RAN node in the satellite radio cell and instructions for TAIs for the TA where the UE is located.

[0233] Close 30. The non-temporary storage medium according to Close 29, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0234] Close 31. The non-temporary storage medium according to any one of Close 29 to 30, characterized in that one or more TAIs broadcast in the satellite radio cell include a single TAI.

[0235] Close 32. The NAS request message includes a NAS registration request and the NAS acceptance message includes a NAS registration acceptance, or the NAS request message includes a NAS connection request and the NAS acceptance message includes a NAS connection acceptance, and the program code includes a registration area (RA) in the NAS acceptance message, and if the TAI for the TA where the UE is located is one of the TAIs broadcast in the satellite radio cell by the RAN node, the RA includes the TAI for the TA where the UE is located, and if the TAI for the TA where the UE is located is not one of the TAIs broadcast in the satellite radio cell by the RAN node, the RA includes at least one of the TAIs broadcast in the satellite radio cell by the RAN node, and if the indication of the TAI for the TA where the UE is located indicates that the TA where the UE is located was not determined by the RAN node, the RA The non-temporary storage medium according to any one of clauses 29 to 31, characterized in that it includes an instruction in which the RA contains at least one of the TAIs broadcast in the satellite radio cell by the N node.

[0236] Close 33. A method performed by user equipment (UE) to support satellite radio access to a Serving Public Land Mobile Network (PLMN), comprising: receiving a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node; determining whether access to the satellite radio cell is permitted based on the plurality of TAIs; in the satellite radio cell, sending a non-access layer (NAS) request message to a core network node via the RAN node in response to the decision that access to the satellite radio cell is permitted; and receiving a NAS response message from the core network node via the RAN node in the satellite radio cell.

[0237] Close 34. The method according to Close 33, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0238] Close 35. The method according to any one of paragraphs 33 to 34, wherein determining whether access to the satellite radio cell is permitted based on the plurality of TAIs includes determining that access is unconditionally permitted if at least one of the plurality of TAIs is part of the current UE registration area (RA) or is part of the UE's permitted TAI list; determining that access is conditionally permitted if access is not unconditionally permitted and at least one of the plurality of TAIs is not part of the UE's prohibited TAI list; and determining that access is not permitted if all of the plurality of TAIs are part of the UE's prohibited TAI list.

[0239] Close 36. The method according to any one of paragraphs 33 to 35, characterized in that if it is determined that access is permitted unconditionally, the NAS request message may include an arbitrary uplink NAS message, and if it is determined that access is permitted conditionally, the NAS request message may include a NAS registration request or a NAS connection request.

[0240] Close 37. The method according to any one of paragraphs 33 to 36, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration acceptance message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection acceptance message, and the NAS acceptance message includes at least one of a registration area (RA) including a first list of TAIs and an authorized TAI list including a second list of TAIs, and each TAI is part of the prohibited list of TAIs, further comprising removing each TAI in the first list of TAIs or the second list of TAIs, or both of the first and second lists of TAIs, from the prohibited TAI list of the UE.

[0241] Close 38. The method according to any one of paragraphs 33 to 37, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and includes a list of TAIs, and the method further includes adding each TAI in the list of TAIs to the list of prohibited TAIs of the UE.

[0242] Close 39. The method according to any one of paragraphs 33 to 38, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and does not include a TAI or a list of TAIs, and the method further includes adding each TAI in the plurality of TAIs to the list of prohibited TAIs of the UE.

[0243] Close 40. User equipment (UE) configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN), comprising a radio transceiver configured to communicate wirelessly with a network entity, at least one memory, and at least one processor coupled to the radio transceiver, wherein the at least one memory and the at least one processor are configured to receive a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node via the radio transceiver, determine via the radio transceiver whether access to the satellite radio cell is permitted based on the plurality of TAIs, transmit a non-access layer (NAS) request message within the satellite radio cell to a core network node via the RAN node in response to a decision that access to the satellite radio cell is permitted, and receive a NAS response message within the satellite radio cell from the core network node via the RAN node via the radio transceiver.

[0244] Close 41. The UE according to Close 40, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0245] Close 42. The UE described in any one of paragraphs 40 and 41, wherein determining whether access to the satellite radio cell is permitted based on the plurality of TAIs includes determining that access is unconditionally permitted if at least one of the plurality of TAIs is part of the current UE registration area (RA) or is part of the UE's permitted TAI list; determining that access is conditionally permitted if access is not unconditionally permitted and at least one of the plurality of TAIs is not part of the UE's prohibited TAI list; and determining that access is not permitted if all of the plurality of TAIs are part of the UE's prohibited TAI list.

[0246] Close 43. The UE described in any one of paragraphs 40 to 42, characterized in that if it is determined that access is permitted unconditionally, the NAS request message may include any uplink NAS message, and if it is determined that access is permitted conditionally, the NAS request message may include a NAS registration request or a NAS connection request.

[0247] Close 44. The UE according to any one of paragraphs 40 to 43, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration acceptance message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection acceptance message and the NAS acceptance message includes at least one of a registration area (RA) including a first list of TAIs and an authorized TAI list including a second list of TAIs, and the at least one processor is further configured to remove each TAI in the first list of TAIs or the second list of TAIs, or both of the first and second lists of TAIs, from the UE's list of prohibited TAIs, if each TAI is part of a prohibited list of TAIs.

[0248] Close 45. The UE according to any one of Close 40 to 44, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and includes a list of TAIs, and the at least one processor is further configured to add each TAI in the list of TAIs to the UE's list of prohibited TAIs.

[0249] Close 46. The UE according to any one of Close 40 to 45, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and does not include a TAI or a list of TAIs, and the at least one processor is further configured to add each of the TAIs of a plurality of TAIs to the list of prohibited TAIs of the UE.

[0250] Close 47. User equipment (UE) configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN), comprising: a unit that receives a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node; a unit that determines whether access to the satellite radio cell is permitted based on the plurality of TAIs; a unit that, in response to the decision that access to the satellite radio cell is permitted, transmits a non-access layer (NAS) request message for the satellite radio cell to a core network node via the RAN node; and a unit that receives a NAS response message for the satellite radio cell from the core network node via the RAN node.

[0251] Close 48. The UE according to Close 47, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an evolved Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0252] Close 49. The UE according to any one of paragraphs 47 and 48, wherein the unit that determines whether access to the satellite radio cell is permitted based on the plurality of TAIs includes a unit that determines that access is unconditionally permitted if at least one of the plurality of TAIs is part of the current UE registration area (RA) or is part of the UE's permitted TAI list; a unit that determines that access is conditionally permitted if access is not unconditionally permitted and at least one of the plurality of TAIs is not part of the UE's prohibited TAI list; and a unit that determines that access is not permitted if all of the plurality of TAIs are part of the UE's prohibited TAI list.

[0253] Close 50. The UE described in any one of paragraphs 47 to 49, characterized in that if it is determined that access is permitted unconditionally, the NAS request message may include any uplink NAS message, and if it is determined that access is permitted conditionally, the NAS request message may include a NAS registration request or a NAS connection request.

[0254] Close 51. The UE according to any one of paragraphs 47 to 50, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration acceptance message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection acceptance message and the NAS acceptance message includes at least one of a registration area (RA) including a first list of TAIs and an authorized TAI list including a second list of TAIs, wherein each TAI is part of a prohibited TAI list, the UE further includes a unit for removing each TAI in the first list of TAIs or the second list of TAIs, or both of the first and second lists of TAIs, from the prohibited TAI list of the UE.

[0255] Close 52. The UE according to any one of Close 47 to 51, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and includes a list of TAIs, and further includes a unit that adds each TAI in the list of TAIs to the UE's list of prohibited TAIs.

[0256] Close 53. The UE according to any one of Close 47 to 52, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and does not include a TAI or a list of TAIs, and further includes a unit that adds each TAI in the plurality of TAIs to the UE's list of prohibited TAIs.

[0257] Close 54. A non-temporary storage medium containing program code stored thereon, wherein the program code is operable to constitute at least one processor in a user device (UE) for supporting satellite radio access to a Serving Public Land Mobile Network (PLMN), and the program includes instructions to receive a plurality of tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node, determine whether access to the satellite radio cell is permitted based on the plurality of TAIs, and in response to the decision that access to the satellite radio cell is permitted, send a non-access layer (NAS) request message within the satellite radio cell to a core network node via the RAN node, and receive a NAS response message in the satellite radio cell from the core network node via the RAN node.

[0258] Close 55. The non-temporary storage medium according to Close 54, characterized in that the RAN node includes an NR node B (gNB) and the core network node includes an Access and Mobility Management Function (AMF), or the RAN node includes an Evolutionary Node B (eNB) and the core network node includes a Mobility Management Entity (MME).

[0259] Close 56. The non-temporary storage medium according to any one of paragraphs 54 and 55, wherein the instruction for determining whether access to the satellite radio cell is permitted based on the plurality of TAIs includes an instruction for determining that access is unconditionally permitted if at least one of the plurality of TAIs is part of the current UE registration area (RA) or is part of the UE's permitted TAI list, for determining that access is conditionally permitted if access is not unconditionally permitted and at least one of the plurality of TAIs is not part of the UE's prohibited TAI list, and for determining that access is not permitted if all of the plurality of TAIs are part of the UE's prohibited TAI list.

[0260] Close 57. The non-temporary storage medium according to any one of paragraphs 54 to 56, characterized in that if it is determined that access is permitted unconditionally, the NAS request message may include any uplink NAS message, and if it is determined that access is permitted conditionally, the NAS request message may include a NAS registration request or a NAS connection request.

[0261] Close 58. The non-temporary storage medium according to any one of paragraphs 54 to 57, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration acceptance message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection acceptance message and the NAS acceptance message includes at least one of a registration area (RA) including a first list of TAIs and an authorized TAI list including a second list of TAIs, and the program code further includes an instruction to remove each TAI in the first list of TAIs or the second list of TAIs, or both of the first and second lists of TAIs, from the prohibited TAI list of the UE, if each TAI is part of a prohibited TAI list.

[0262] Close 59. The non-temporary storage medium according to any one of paragraphs 54 to 58, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and includes a list of TAIs, and the program code further includes an instruction to add each TAI in the list of TAIs to the list of prohibited TAIs of the UE.

[0263] Close 60. The non-temporary storage medium according to any one of Close 54 to 59, characterized in that the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and does not include a TAI or a list of TAIs, and the program code further includes an instruction to add each TAI in the plurality of TAIs to the list of prohibited TAIs of the UE.

[0264] While this specification discloses specific embodiments in detail, these are for illustrative purposes only and are not intended to limit the scope of the appended claims. In particular, various substitutions, changes, and modifications are intended to be made without departing from the spirit and scope of the disclosure as defined by the claims. Other embodiments, advantages, and modifications are considered to be within the scope of the following claims. The presented claims are representative of the embodiments and features disclosed herein. Other unclaimed embodiments and features are also intended. Accordingly, other embodiments are within the scope of the following claims.

Claims

1. A method performed by a radio access network (RAN) node that supports satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN), The RAN node broadcasts multiple tracking area (TA) identifiers (TAI) within the satellite radio cell, The satellite radio cell receives non-access layer (NAS) messages transmitted by the UE, To determine the TA on which the UE is located, Transmitting the NAS message to a core network node, wherein the NAS message includes a TAI for the TA where the UE is located, and the plurality of TAIs broadcast in the satellite radio cell. Methods that include...

2. The method according to claim 1, wherein the RAN node includes an NR node B (gNB) and the core network node includes an access and mobility management function (AMF), or the RAN node includes an evolved Node B (eNB) and the core network node includes a mobility management entity (MME).

3. A radio access network (RAN) node configured to support satellite radio access of user equipment (UE) to a serving public land mobile network (PLMN), An external interface configured to communicate wirelessly with a network entity, At least one memory, The system comprises the external interface and at least one memory, and the at least one processor is coupled to the external interface and at least one memory, Broadcasting multiple Tracking Area (TA) Identifiers (TAIs) within a satellite radio cell, The satellite radio cell receives non-access layer (NAS) messages transmitted by the UE, To determine the TA on which the UE is located, Transmitting the NAS message to a core network node, wherein the NAS message includes a TAI for the TA where the UE is located, and the plurality of TAIs broadcast in the satellite radio cell. A wireless access network (RAN) node configured to perform the following actions.

4. The RAN node according to claim 3, wherein the RAN node includes an NR node B (gNB) and the core network node includes an access and mobility management function (AMF), or the RAN node includes an evolutionary node B (eNB) and the core network node includes a mobility management entity (MME).

5. User equipment (UE) configured to support satellite radio access to a Serving Public Land Mobile Network (PLMN), A wireless transceiver configured to communicate wirelessly with a network entity, At least one memory, The system comprises the wireless transceiver and the at least one memory, and the at least one processor is coupled to the at least one memory, The wireless transceiver receives multiple tracking area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a radio access network (RAN) node, Whether or not access to the aforementioned satellite radio cell is permitted depends on the multiple TAIs, (v) A list of authorized TAIs relating to the UE, or (vi) Current UE registration area The decision is based on a comparison with, In response to the decision that access to the satellite radio cell is permitted, the satellite radio cell sends a non-access layer (NAS) request message to the core network node via the RAN node, The satellite radio cell receives a NAS response message from the core network node via the RAN node through the wireless transceiver. User equipment (UE) configured to perform the following actions.

6. The UE according to claim 5, wherein the RAN node includes an NR node B (gNB) and the core network node includes an access and mobility management function (AMF), or the RAN node includes an evolutionary node B (eNB) and the core network node includes a mobility management entity (MME).

7. Determining whether or not access to the satellite radio cell is permitted based on the aforementioned multiple TAIs is, If at least one of the aforementioned TAIs is part of the current UE registration area (RA) or part of the UE's permitted TAI list, it is determined that access is unconditionally permitted; if access is not unconditionally permitted, and at least one of the aforementioned TAIs is not part of the UE's prohibited TAI list, it is determined that access is conditionally permitted. If all of the aforementioned TAIs are part of the aforementioned prohibited TAI list of the aforementioned UE, access will be denied. The UE according to claim 5, including the following:

8. The UE according to claim 5, wherein if it is determined that access is permitted unconditionally, the NAS request message includes an arbitrary uplink NAS message, and if it is determined that access is permitted conditionally, the NAS request message includes a NAS registration request or a NAS connection request.

9. The UE according to claim 5, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration acceptance message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection acceptance message, and the NAS registration acceptance message or the NAS connection acceptance message includes at least one of a registration area (RA) including a first list of TAIs and an authorized TAI list including a second list of TAIs, and the at least one processor is further configured to remove each TAI in the first list of TAIs or the second list of TAIs, or both of the first and second lists of TAIs, from the prohibited TAI list of the UE if the TAI is part of a prohibited TAI list.

10. The UE according to claim 5, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and includes a list of TAIs, and the at least one processor is further configured to add each TAI in the list of TAIs to the UE's list of prohibited TAIs.

11. The UE according to claim 5, wherein the NAS request message includes a NAS registration request and the NAS response message includes a NAS registration rejection message, or the NAS request message includes a NAS connection request and the NAS response message includes a NAS connection rejection message, the NAS response message indicates a prohibited tracking area and does not include a TAI or a list of TAIs, and the at least one processor is further configured to add each TAI of a plurality of TAIs broadcast within the satellite radio cell to the UE's list of prohibited TAIs.

12. A computer-readable storage medium storing program code, wherein the program code is operable to configure at least one processor to carry out any method according to claim 1 or 2.

13. A method performed by user equipment (UE) to support satellite radio access to a serving public land mobile network (PLMN), Receiving multiple Tracking Area (TA) identifiers (TAIs) broadcast within a satellite radio cell by a Radio Access Network (RAN) node, To determine whether access to the satellite radio cell is permitted based on the multiple TAIs, In the satellite radio cell, in response to a decision that access to the satellite radio cell is permitted, a non-access layer (NAS) request message is sent to the core network node via the RAN node. A method comprising receiving a NAS response message from the core network node via the RAN node within the satellite radio cell.

14. A computer-readable storage medium storing program code, wherein the program code is operable to configure at least one processor to carry out the method described in Claim 13.

Images