Systems and methods for reporting generalized unavailable periods of access to wireless networks

Reporting unavailable periods to the wireless network through the UE solves the problem of unavailable period management in the wireless communication system, improves the reliability and efficiency of the system, and reduces the impact of service interruptions.

CN119032520APending Publication Date: 2024-11-26QUALCOMM INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202380036973.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-04
Filing Date
2023-05-05
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In wireless communication systems, user equipment (UE) cannot effectively predict and manage unavailable periods when it cannot access the wireless network, resulting in service interruption and waste of resources.

Method used

By reporting unavailable periods to the wireless network, the network entity can prepare and buffer data in advance, reduce the impact of service interruptions, and restore services after the unavailable period ends.

Benefits of technology

By reporting unavailable periods in advance, UEs and networks can be prepared to reduce the impact of service interruptions and improve the reliability and efficiency of communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032520A_ABST
    Figure CN119032520A_ABST
Patent Text Reader

Abstract

A user equipment (UE) may transmit a reporting capability to a network entity of a wireless network to indicate that the UE may report a generalized unavailable period to the wireless network for a plurality of different events, wherein the generalized unavailable period includes a period during which the UE does not have wireless communication access to the wireless network. The UE may later determine an upcoming unavailable period due to one or more of the plurality of events. The UE may then transmit an unavailable period report to the network entity prior to the unavailable period and the unavailable period report indicates the unavailable period. The UE may include a start time, an end time, a duration, and / or an event of the unavailable period in the report. The UE may later indicate to the network entity when the unavailable report has ended or has been cancelled or modified.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims the benefit of U.S. Application No. 18 / 312,461, filed on May 4, 2023, entitled “SYSTEMS AND METHODS FOR REPORTING A GENERALIZED UNAVAILABLE PERIOD FOR ACCESS TO A WIRELESS NETWORK,” which claims the benefit of U.S. Provisional Application Nos. 63 / 338,884, filed on May 5, 2022, entitled “PROVISIONING OF NON-TERRESTRIAL NETWORK COVERAGE INFORMATION,” and U.S. Provisional Application Nos. 63 / 338,884, filed on August 9, 2022, entitled “PROVISIONING OF NON-TERRESTRIAL NETWORK COVERAGE INFORMATION.” The present application relates to U.S. Provisional Application No. 63 / 370,925, entitled “PROVISIONING OF NON-TERRESTRIAL NETWORK COVERAGE INFORMATION”, U.S. Provisional Application No. 63 / 484,187, filed on February 9, 2023, and U.S. Provisional Application No. 63 / 494,764, filed on April 6, 2023, and entitled “PROVISIONING OF NON-TERRESTRIAL NETWORK COVERAGE INFORMATION”, all of which are assigned to the assignee of the present application and are incorporated herein by reference in their entirety. Technical Field

[0003] The following relates to wireless communications, including support for coverage gaps for satellite access to wireless networks. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to 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, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as 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 FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, which may be further referred to as user equipment (UE).

[0005] Access to a wireless network may be provided using a communication satellite that may support 5G NR, 4G LTE, future 6G access, or other types of radio access technology (RAT) radio interfaces to the UE. In such cases, the communication satellite may not always be visible to the UE, resulting in coverage gaps (also referred to as "discontinuous satellite coverage" or "unavailable periods") whenever no communication satellite is visible or whenever a visible communication satellite is unable or not allowed to provide wireless coverage to the UE. In addition to coverage gaps, other types of events may also result in unavailable periods during which the UE cannot access the serving wireless network. These events may include UE-based events, such as a reboot or software upgrade of the UE. The unavailable period resulting from one of these types of events may not be known in advance by the serving wireless network. Summary of the invention

[0006] According to the present disclosure, an example method performed by a user equipment (UE) for indicating a generalized unavailable period to a wireless network may include transmitting a reporting capability to a network entity of the wireless network, wherein the reporting capability indicates that the UE is able to report a generalized unavailable period to the wireless network for multiple different events, wherein the generalized unavailable period includes a time period when the UE does not have wireless communication access to the wireless network. The method may also include, after transmitting the reporting capability, determining an upcoming unavailable period for the UE due to one or more of the multiple events. The method may also include, in response to determining the upcoming unavailable period, transmitting an unavailable period report to the network entity of the wireless network, wherein the unavailable period report is transmitted before the unavailable period and indicates the unavailable period.

[0007] According to the present disclosure, an example method performed by a network entity of a wireless network for enabling indication of a generalized unavailable period of a user equipment (UE) to the wireless network may include receiving a reporting capability from the UE, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailable period to the wireless network for a plurality of different events, wherein the generalized unavailable period includes a period of time during which the UE does not have wireless communication access to the wireless network. The method may also include, after receiving the reporting capability, receiving an unavailable period report from the UE, wherein the unavailable period report is received prior to an upcoming unavailable period of the UE and indicates the unavailable period. The method may also include, in response to receiving the unavailable period report, transmitting at least one message to the UE, wherein the at least one message indicates a periodic registration timer or a periodic tracking area update (TAU) timer having a value equal to or greater than the duration of the unavailable period.

[0008] According to the present disclosure, an example user equipment (UE) capable of indicating a generalized unavailable period to a wireless network may include one or more transceivers, one or more memories, and one or more processors communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to transmit a reporting capability to a network entity of the wireless network via the one or more transceivers, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailable period to the wireless network for multiple different events, wherein the generalized unavailable period includes a time period when the UE does not have wireless communication access to the wireless network. The one or more processors may be further configured to, after transmitting the reporting capability, determine an upcoming unavailable period for the UE due to one or more of the multiple events. The one or more processors may be further configured to, in response to determining the upcoming unavailable period, transmit an unavailable period report to the network entity of the wireless network via the one or more transceivers, wherein the unavailable period report is transmitted before the unavailable period and indicates the unavailable period.

[0009] According to the present disclosure, an example network entity for a wireless network for enabling a generalized unavailable period of a user equipment (UE) to be indicated to the wireless network may include one or more transceivers, one or more memories, one or more processors communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to receive a reporting capability from the UE via the one or more transceivers, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailable period to the wireless network for a plurality of different events, wherein the generalized unavailable period includes a period of time when the UE does not have wireless communication access to the wireless network. The one or more processors may be further configured to receive an unavailable period report from the UE after receiving the reporting capability, wherein the unavailable period report is received before the upcoming unavailable period of the UE and indicates the unavailable period. The one or more processors may be further configured to transmit at least one message to the UE via the one or more transceivers in response to receiving the unavailable period report, wherein the at least one message indicates a periodic registration timer or a periodic tracking area update (TAU) timer having a value equal to or greater than the duration of the unavailable period. The present disclosure is neither intended to identify key or important features of the subject matter protected by the claims, nor is it intended to be used alone to determine the scope of the subject matter protected by the claims. The subject matter should be understood by reference to appropriate portions of the entire specification of the present disclosure, any or all drawings, and each claim.The foregoing and other features and examples will be described in more detail in the following specification, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 illustrates an example diagram of a communication system utilizing a network architecture with a transparent space vehicle (SV) that is capable of supporting satellite access to a wireless network.

[0011] 2 illustrates an example diagram of a communication system utilizing a network architecture with regenerative SVs that is capable of supporting satellite access to a wireless network.

[0012] 3 illustrates an example diagram of a communication system utilizing a network architecture with regenerative SVs and a split satellite Node B (gNB) architecture capable of supporting satellite access to a wireless network.

[0013] FIG. 4 illustrates an example of SV generating a plurality of beams over an area including a plurality of countries.

[0014] FIG. 5 illustrates an example of a satellite cell generated by an SV over an area including a plurality of fixed cells.

[0015] FIG. 6 illustrates an example of assigning a satellite cell generated by a SV to a fixed tracking area (TA).

[0016] FIG. 7A illustrates an example of a UE being in or out of coverage of a SV at different times and at different locations.

[0017] FIG. 7B illustrates a coverage map and a coverage bitmap of a UE.

[0018] FIG. 7C illustrates another example of a coverage map and a coverage bitmap of a UE.

[0019] Figure 7D illustrates an example signal power heat map that may be used to indicate satellite coverage availability according to some embodiments.

[0020] 7E and 7F illustrate different types of grid point arrays that may be used to indicate satellite coverage availability according to some embodiments.

[0021] 8A-8C illustrate examples of a process supporting transfer of coverage data from a server to a UE based on an obtained server address according to aspects of the present disclosure.

[0022] 9 illustrates an example of a process for charging / charging a UE for access to coverage data in accordance with aspects of the present disclosure.

[0023] 10 illustrates a block diagram of a UE that supports obtaining coverage data to assist the UE in accessing a serving public land mobile network (PLMN) in accordance with aspects of the present disclosure.

[0024] 11 illustrates a block diagram of network entities supporting provision of coverage data to assist UEs in accessing a serving PLMN in accordance with aspects of the present disclosure.

[0025] 12 illustrates a block diagram of a server supporting provision of coverage data to assist UEs in accessing a serving PLMN in accordance with aspects of the present disclosure.

[0026] 13 is a diagram of registration of a UE with a PLMN, which may assist in providing coverage data to the UE.

[0027] 14 is a diagram of a procedure that may be performed to report generalized unavailability periods, according to one embodiment.

[0028] 15 illustrates a flow chart of a method for indicating a generalized unavailability period to a wireless network in accordance with aspects of the present disclosure.

[0029] 16 illustrates a flow chart of a method for enabling indication of a generalized period of unavailability of a UE to a wireless network in accordance with aspects of the present disclosure.

[0030] Similar reference symbols in the various drawings indicate similar elements according to certain example implementations. In addition, multiple instances of an element may be indicated by adding a letter or hyphen and a second number after the first number of the element. For example, multiple instances of element 102 may be indicated as 102-1, 102-2, 102-3, etc. When only the first number is used to refer to such an element, it will be understood as any instance of the element (e.g., element 102 in the previous example will refer to elements 102-1, 102-2, 102-3). DETAILED DESCRIPTION

[0031] In some deployment scenarios, wireless communication may be performed between a user equipment (UE) and a satellite to enable the UE to access a wireless network via a satellite. For example, a satellite may be deployed so that the UE is located within a coverage area of ​​the satellite to support such communications. However, during initial deployment and / or in some coverage areas, the UE may be located outside the satellite coverage area, which may interrupt such satellite-based communications. For example, due to the orbital motion of the satellite, the UE may traverse the coverage area and non-coverage area of ​​the satellite, which may affect various operations of the UE, such as cell search, mobile station calling service, mobile station called service, power saving mode, etc. Therefore, it may be desirable to improve the UE's support for the coverage area and non-coverage area of ​​the satellite to improve the UE operation with satellite-based communications. Similarly, a wireless communication network may benefit from improved support for the coverage area and non-coverage area of ​​the satellite, which may enable more efficient use of network resources and better communication services for the UE. In order to support coverage areas and non-coverage areas, coverage information may be provided to the UE so that the UE can know when there will be coverage of one or more RATs for non-terrestrial networks (NTNs) and possible terrestrial networks (TNs) at a specific location. The type of coverage information needs to be defined as well as the method of transmitting the coverage information to the UE. The coverage information may indicate when satellite coverage will be available for UEs at different locations and at different times, and may be referred to as "coverage data", "satellite coverage data", "coverage information", "satellite coverage information", "satellite coverage availability information" (SCAI), "coverage map" or other names.

[0032] Satellites (also known as space vehicles (SVs) or communication satellites) can be used in communication systems, for example, using gateways (also known as earth stations or ground stations) and one or more satellites to relay communication signals between these gateways and one or more UEs. For example, a UE can access a satellite (rather than a ground base station), and the satellite can be connected to an earth station (ES), which is also known as a ground station or a non-terrestrial network (NTN) gateway. The earth station will then be connected to an element in a 5G (or 4G or future 6G) network, such as a modified base station (without a ground antenna) or a network node in a 5G core network (5GCN) or a 4G or future 6G core network. This element will then provide access to other elements in the 5G (or 4G or future 6G) network, and ultimately provide access to entities outside the 5G (or 4G or future 6G) network (such as Internet web servers and other user devices).

[0033] The basic principle of 5G (or other cellular network) satellite access for UEs may include providing ubiquitous outdoor coverage for both users and mobile network operators (MNOs). For example, in many countries, including the United States, unavailable or poor cellular network coverage is a common problem. In addition, even if there is generally good cellular coverage, cellular access is not always possible. For example, cellular access may be hindered by congestion, physical obstacles, local cellular outages caused by weather (e.g., hurricanes or tornadoes), or local power outages. Satellite access to cellular networks can provide a new type of independent access that is potentially available everywhere outdoors. Current satellite-enabled phones for low-Earth orbit (LEO) SVs may have similar sizes to cellular smartphones, and thus mobile NR support using satellite-enabled phones does not require a significant increase in phone size. In addition, satellite-enabled smartphones may help drive mobile phone sales and may increase operator revenues. For example, potential users may include anyone with limited or no cellular access, anyone who wants a backup for lack of cellular access, and anyone involved in public safety or otherwise requiring (almost) 100% reliable mobile communications. Additionally, some users may desire improved or more reliable E911 service, e.g., for medical emergencies or traffic breakdowns in remote areas. Additional user scenarios may include providing wireless communication access to UEs located outdoors and associated with automation or Internet of Things (IoT) devices, such as UEs that enable communication with and possibly control of unmanned aerial vehicles (UAVs), unmanned vehicles, automated machinery used in agriculture, forestry, or mining, smart meters, and monitoring equipment (e.g., for monitoring weather, traffic, crowds, hazardous conditions).

[0034] Using 5G satellite access can provide other benefits. For example, 5G satellite access can reduce mobile network operator (MNO) infrastructure costs. For example, MNOs can use satellite access to reduce the number of ground base stations (such as NR NodeBs, also known as gNBs) that need to be deployed and backhaul deployment in sparsely populated areas. In addition, 5G satellite access can be used to overcome Internet congestion in certain countries, for example. Additionally, 5G satellite access can provide diversification for spacecraft operators (SVOs). For example, 5G NR satellite access can provide another revenue stream for SVOs that would otherwise only provide fixed Internet access.

[0035] As a term, when there is previous context information that a "cell" is a "satellite cell", a wireless cell supported by a satellite (or SV) is referred to herein as a "satellite cell", "radio cell", "NTN cell" or simply a "cell". A satellite cell is to be distinguished from wireless cells supported by ground base stations and access points, which are referred to herein as terrestrial cells or terrestrial network (TN) cells.

[0036] Note that the terms spacecraft (SV), communication satellite, and satellite may be synonymous and are therefore used interchangeably herein. In some cases, an SV (or satellite) may be a navigation SV (or satellite), such as an SV for GPS, Galileo, GLONASS, or BeiDou. SVs that function as navigation SVs but may not function as communication SVs are labeled and explicitly referred to herein to avoid confusion with communication SVs that may not support navigation.

[0037] Aspects of the present disclosure as a whole relate to a UE reporting (e.g., signaling) one or more upcoming periods in which the UE does not have wireless communication access to a wireless network. This reporting can be applied not only to satellite coverage gaps, but also more generally to other types of events that may cause the UE to lose access to the wireless network, such as a software update or reboot of the UE. These periods in which the UE does not have wireless communication access due to any of a variety of reasons are referred to herein as "generalized unavailability periods." Enabling the UE to report generalized unavailability periods in the manner described herein may allow the UE and the network to prepare for the upcoming unavailability. According to some embodiments, a common reporting procedure may be used for each type or each cause of unavailability, thereby reducing the impact compared to using different reporting procedures for each different type or each different cause of unavailability. After the unavailability period begins, the network may buffer the UE's incoming data and avoid paging the UE. When the unavailability period ends, the UE may transmit another report (e.g., a registration update or a tracking area update) to the network indicating that the UE is now available. The network may then resume paging the UE when necessary and may transmit any buffered data to the UE.

[0038] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, by reporting generalized unavailable periods, UEs and networks may prepare for unavailable periods, thereby performing tasks before and / or after the unavailable periods. This may, for example, help mitigate the impact of unavailable periods by improving functionality and performance of UEs and networks and / or helping to ensure efficiency within wireless networks and UEs.

[0039] Aspects of the disclosure are initially described in the context of communication systems, including wireless communication systems. Aspects of the disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to supporting reporting of generalized unavailability periods.

[0040] FIG. 1 illustrates an example of a communication system 100 capable of supporting satellite access using 5G NR or some other wireless access type such as CDMA, 4G, or future 6G according to some examples. FIG. 1 illustrates a network architecture with a transparent SV. A transparent SV may implement frequency conversion and radio frequency (RF) amplifiers in both uplink (UL) and downlink (DL) directions, and may correspond to an analog RF repeater. A transparent SV may, for example, receive UL signals from all served UEs, and may redirect the combined signal DL to an earth station without demodulating or decoding the signals. Similarly, a transparent SV may receive UL signals from an earth station and redirect the signal DL to a served UE without demodulating or decoding the signal. However, the SV may frequency convert the received signals, and may amplify and / or filter the received signals before transmitting them.

[0041] The communication system 100 includes multiple UEs 115, multiple SVs 102 (e.g., SVs 102-1, 102-2, 102-3, and 102-4), multiple non-terrestrial network (NTN) gateways 104-1 to 104-4 (collectively referred to herein as NTN gateways 104) (and sometimes referred to herein simply as gateways 104, earth stations 104, or ground stations 104), and multiple satellite NodeBs (gNBs) 106-1 to 106-3 (collectively referred to herein as gNBs 106) that are capable of communicating with the UEs 115 via the SVs 102 and are part of a next generation (NG) radio access network (RAN) (NG-RAN) 112.

[0042] Note that the term "gNB" (or "gNodeB") traditionally refers to an NR NodeB base station used for terrestrial access utilizing the NR radio interface. The same term (gNB) can also be used to refer to a base station that supports satellite access utilizing the NR radio interface. The two variants of gNB (satellite and terrestrial) can support many of the same functions, protocols, and interfaces, but are also different in other aspects. In order to distinguish between gNBs supporting terrestrial access and gNBs supporting satellite access, different notations are used in this article. gNBs can also support terrestrial and satellite NR access, but for simplicity, this is not discussed further here.

[0043] The communication system 100 is illustrated as further including components of multiple fifth generation (5G) networks, including 5G core networks (5GCN) 110-1 to 110-3 (collectively referred to herein as 5GCN 110). 5GCN 110 may be a public land mobile network (PLMN) that may be located in the same or different countries. Figure 1 illustrates various components within 5GCN1 110-1 that may operate with NG-RAN 112. It should be understood that 5GCN2 110-2 and 5GCN3 110-3 may include the same, similar or different components and associated NG-RANs, which are not illustrated in Figure 1 to avoid unnecessary confusion. 5G networks may also be referred to as NR networks; NG-RAN 112 may be referred to as 5G RAN or NR RAN; and 5GCN 110 may be referred to as NG core network (NGC). The communication system 100 may further utilize information from a spacecraft (SV) 190 of a satellite positioning system (SPS), including a global navigation satellite system (GNSS), such as the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), Galileo, or BeiDou, or some other local or regional SPS such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Overlay Service (EGNOS), or the Wide Area Augmentation System (WAAS), all of which are sometimes referred to herein as GNSS. It is noted that the SV 190 acts as a navigation SV and is separate and distinct from the SV 102 acting as a communication SV. However, it is not excluded that some of the SVs 190 may also act as some of the SVs 102 and / or that some of the SVs 102 may also act as some of the SVs 190. In some implementations, for example, the SVs 102 may be used for both communication and positioning. Additional components of the communication system 100 are described below. The communication system 100 may include additional or alternative components.

[0044] The connectivity permitted in the communication system 100 having a network architecture with transparent SV illustrated in FIG1 allows a gNB 106 to access multiple earth stations 104 and / or multiple SVs 102. A gNB 106 (e.g., illustrated by gNB 106-2) may also be shared by multiple PLMNs (5GCN 110), which may all be in the same country or may be in different countries, and an NTN gateway 104 (e.g., illustrated by NTN gateway 104-1) may be shared by more than one gNB 106.

[0045] It should be noted that FIG. 1 provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only three UEs 115 are illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100. Similarly, the wireless communication system 100 may include a larger (or smaller) number of SVs 190, SVs 102, earth stations 104, gNBs 106, NG-RAN 112, ng-eNBs 114, 5GCNs 110, external clients 140, and / or other components. The illustrated connections connecting the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0046] Although FIG. 1 illustrates a 5G-based network, similar network implementations and configurations may be used for other communication technologies, such as 3G, 4G LTE, etc.

[0047] UE 115 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), terminal (SET) enabled with secure user plane location (SUPL), or some other name. In addition, UE 115 may correspond to a cellular phone, a smart phone, a laptop computer, a tablet, a PDA, a tracking device, a navigation device, an Internet of Things (IOT) device, or some other portable or movable device. Typically, although not necessarily, UE 115 may support wireless communications using one or more radio access technologies (RATs) such as GSM, CDMA, Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE802.11 WiFi (also known as Wi-Fi), Bluetooth® (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 112 and 5GCN 110), etc. UE 115 may also support wireless communications using a wireless local area network (WLAN), which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or a packet cable. UE 115 further supports wireless communications using spacecraft such as SV 102. Use of one or more of these RATs may allow UE 115 to communicate with external clients 140 (eg, via user plane function (UPF) 130, or possibly via gateway mobile location center (GMLC) 126).

[0048] UE 115 may comprise a single entity or may comprise multiple entities, such as in a personal area network where a user may employ audio, video, and / or data I / O devices and / or body sensors and separate wired or wireless modems.

[0049] UE 115 may, for example, use signals and information from spacecraft 190 in an SPS (such as GPS, GLONASS, Galileo, or BeiDou) or some other local or regional SPS (such as IRNSS, EGNOS, or WAAS) to support position determination, all of which may be generally referred to as GNSS herein. Position measurement using SPS is based on measurement of propagation delay times of SPS signals broadcast from multiple orbiting satellites to an SPS receiver in UE 115. Once the SPS receiver has measured the signal propagation delay for each satellite, the distance to each satellite may be determined, and the measured distances and the known positions of these satellites may then be used to determine precise navigation information (including 3-dimensional positioning, velocity, and time of day of the SPS receiver). Positioning methods that may be supported using SV 190 may include Assisted GNSS (A-GNSS), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), and Differential GNSS (DGNSS). Information and signals from SV 102 may also be used to support positioning. The UE 115 may further support positioning using terrestrial positioning methods such as downlink (DL) time difference of arrival (DL-TDOA), enhanced cell ID (ECID), round trip signal propagation time (RTT), multi-cell RTT, angle of arrival (AOA), angle of departure (AOD), time of arrival (TOA), receive time-transmit time difference (RxTx), and / or other positioning methods.

[0050] The estimate of the location of the UE 115 may be referred to as a geodetic position, position, position estimate, position bearing, bearing, position fix, position estimate, or position fix, and may be geodetic, thereby providing position coordinates (e.g., latitude and longitude) of the UE 115, which may or may not include an altitude / altitude component (e.g., height above sea level, height above or depth below ground level, floor level, or basement level). Alternatively, the location of the UE 115 may be expressed as a civic location (e.g., a postal address or a designation of a point or smaller area in a building, such as a particular room or floor). The location of the UE 115 may also be expressed as an area or volume (geodetically or civically defined) in which the UE 115 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of the UE 115 may also be a relative location, including, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location, which may be defined geodetically, in municipal terms, or by reference to a point, area, or volume indicated on a map, floor plan, or building plan. 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 the UE, local x, y, and possibly z coordinates are typically solved, and then the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level) if necessary.

[0051] UE 115 is configured to communicate with 5GCN 110 via SV 102, earth station 104, and gNB 106. As illustrated by NG-RAN 112, the NG-RAN associated with 5GCN 110 may include one or more gNBs 106. NG-RAN 112 may also include multiple terrestrial gNBs (not shown in FIG. 1 ) that are not capable of communicating with UEs via SV 102. Pairs of terrestrial and / or satellite base stations (e.g., terrestrial gNBs and gNB 106-1 in NG-RAN 112) may be connected to each other using terrestrial links (e.g., directly or indirectly via other terrestrial gNBs or gNB 106) and communicate using an Xn interface. Access to the 5G network is provided to UE 115 via wireless communications between each UE 115 and a serving gNB 106, via SV 102 and NTN gateway 104. The gNB 106 may use 5G NR to provide wireless communication access to the 5GCN 110 on behalf of each UE 115. 5G NR radio access may also be referred to as NR radio access or 5G radio access and may be defined by the Third Generation Partnership Project (3GPP).

[0052] The base station (BS) in the NG-RAN 112 shown in FIG. 1 may also include or alternatively include a next generation evolved Node B 114 (also referred to as ng-eNB 114). The ng-eNB 114 may be connected to one or more gNBs 106 and / or terrestrial gNBs in the NG-RAN 112 (e.g., directly or indirectly via other gNBs 106, terrestrial gNBs, and / or other ng-eNBs 114). The ng-eNB 114 may provide LTE wireless access and / or evolved LTE (eLTE) wireless access to the UE 115. The ng-eNB 114 may be connected to the NTN gateway 104 and support satellite wireless access for the UE 115 (e.g., IOT UE) using enhanced machine type communication (eMTC) (also referred to as LTE-M or narrowband IOT (NB-IOT)). eMTC and NB-IOT are variants of LTE in which lower bandwidth is provided to and supported by UE 115, and these variants enable support for UE 115 with low resource capabilities (e.g., lower processing and memory availability) and limited power availability (e.g., UE 115 with a battery that should provide power to UE 115 for 2 to 10 years before being replaced or recharged). NB-IOT and eMTC may be preferred over NR to support IOT UEs with very limited resources and power availability.

[0053] The term "satellite NodeB" is used herein to refer to a gNB (e.g., gNB 106) or ng-eNB (e.g., ng-eNB 114) that provides satellite wireless access, for example, as illustrated in FIG. 1. The satellite NodeB may be regenerative, as described later with respect to FIG. 2 and FIG. 3, and / or in some embodiments may correspond to an evolved NodeB (eNB) that provides satellite wireless access to a core network that is an EPC (e.g., using LTE, eMTC, or NB-IOT). The satellite NodeB may be referred to by other nomenclature or terminology, such as an sNB or "satellite node" or "satellite access node". The satellite NodeB corresponding to the gNB 106 is distinct from a terrestrial gNB, but may be based on a terrestrial gNB with additional capabilities. For example, the gNB 106 may terminate at a radio interface and associated radio interface protocol to the UE 115, and may send DL signals to the UE 115 and receive UL signals from the UE 115 via the SV 102 and the earth station 104. The gNB 106 may also support signaling connections and voice and data bearers to the UE 115, and may support handover of the UE 115 between different satellite cells of the same SV 102, between different SVs 102, and / or between different gNBs 106. In some systems, the gNB 106 may be referred to as a gNB or an enhanced gNB. The gNB 106 may be configured to manage mobile satellite beams (for LEOSV) and the associated mobility of the UE 115. The gNB 106 may assist in the handover (or transfer) of the SV 102 between different earth stations 104, between different gNBs 106, and between different countries. The gNB 106 may hide or mask certain aspects of the connected SV 102 from the 5GCN 110, for example, by interfacing with the 5GCN 110 in the same or similar manner as a terrestrial gNB, and may avoid the 5GCN 110 having to maintain configuration information for the SV 102 or perform mobility management related to the SV 102. The gNB 106 may further facilitate sharing of the SV 102 across multiple countries. The gNB 106 may communicate with one or more earth stations 104, e.g., as illustrated by gNB 106-2 communicating with earth stations 104-2 and 104-1. The gNB 106 may be separate from the earth station 104, e.g., as illustrated by gNBs 106-1 and 106-2 and earth stations 104-1 and 104-2. The gNB 106 may include one or more earth stations 104 or may be combined with the one or more earth stations, e.g., using a split architecture. For example, gNB 106-3 is illustrated as having a split architecture in which a gNB central unit (gNB-CU) 107 and earth stations 104-3 and 104-4 act as distributed units (DUs). The gNB 106 may typically be fixed on the ground using transparent SV operation.In one implementation, a gNB 106 may be physically combined with or physically connected to an NTN gateway 104 to reduce overall complexity and cost.

[0054] The satellite NodeB corresponding to ng-eNB 114 is different from the terrestrial ng-eNB, but may be based on the terrestrial ng-eNB with additional capabilities. The differences between ng-eNB 114 and the terrestrial ng-eNB and the additional satellite-related functions, capabilities, and uses of ng-eNB 114 may be similar to those described above for gNB 106.

[0055] The earth station 104 may be shared by more than one gNB 106 and / or more than one ng-eNB 114 and may communicate with the UE 115 via the SV 102. The NTN gateway 104 may be dedicated to only one SVO and one associated constellation of the SV 102, and may therefore be owned and managed by the SVO. Although the earth station 104 may be included within a ng-eNB 114 or gNB 106, for example, as a gNB-DU within gNB 106-3, this may only occur when the same SVO or the same MNO owns both the ng-eNB 114 or gNB 106 and the included earth station 104. The earth station 104 may communicate with the SV 102 using control plane and user plane protocols that are proprietary to the SVO. The control plane and user plane protocols between the earth station 104 and the SV 102 can: (i) establish and release the communication link from the NTN gateway 104 to the SV 102, including authentication and encryption; (ii) update the SV software and firmware; (iii) perform SV operations and maintenance (O and M); (iv) control satellite beams (e.g., direction, power, on / off status) and the mapping between satellite beams and earth station UL and DL payloads; and (v) assist in the handover of an SV 102 or satellite cell to another NTN gateway 104.

[0056] As noted, while FIG. 1 depicts nodes configured to communicate in accordance with 5G NR and LTE communication protocols for NG-RAN 112, nodes configured to communicate in accordance with other communication protocols, such as, for example, an LTE protocol for an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) (e.g., supporting UE 115 satellite access using eMTC or NB-IOT) or an IEEE 802.11x protocol for WLAN, may also be used. For example, in a 4G Evolved Packet System (EPS) providing LTE wireless access to UE 115, the RAN may include an E-UTRAN, which may include base stations having evolved Node Bs (eNBs) supporting LTE wireless access. The core network for the EPS may include an Evolved Packet Core (EPC). The EPS may then include an E-UTRAN plus an EPC, where in FIG. 1 , the E-UTRAN corresponds to the NG-RAN 112 and the EPC corresponds to the 5GCN 110. In this case, the satellite NodeB may include an eNB in ​​the E-UTRAN connected to the NTN gateway 104 and the EPC. The methods and techniques described herein for supporting satellite acquisition assistance may be applicable to such other networks.

[0057] The gNB 106, ng-eNB 114, and terrestrial gNBs may communicate with an access and mobility management function (AMF) 122 in the 5GCN 110, which may communicate with a location management function (LMF) 124 for positioning functionality. For example, the gNB 106 and ng-eNB 114 may provide an N2 interface to the AMF 122. The N2 interface between the gNB 106 or ng-eNB 114 and the 5GCN 110 may be the same as the N2 interface supported between the terrestrial gNB or terrestrial ng-eNB and the 5GCN 110 for terrestrial NR or terrestrial LTE access by the UE 115, and the Next Generation Application Protocol (NGAP) defined in 3GPP Technical Specification (TS) 38.413 may be used between the gNB 106 or ng-eNB 114 and the AMF 122. The AMF 122 may support mobility of the UE 115, including satellite cell changes and handovers, and may participate in supporting signaling connections to the UE 115 and possibly data and voice bearers for the UE 115. The LMF 124 may support positioning of the UE 115 when the UE accesses the NG-RAN 112, and may support positioning procedures / methods such as A-GNSS, DL-TDOA, 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 SVs 102. The LMF 124 may also process location service requests for the UE 115 received, for example, from the AMF 122 or from a Gateway Mobile Location Center (GMLC) 126. The LMF 124 may be connected to the AMF 122 and / or the GMLC 126. In some embodiments, a node / system implementing LMF 124 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobile Location Center (E-SMLC). Note that in some embodiments, at least a portion of the positioning functionality (including the derivation of the position of UE 115) may be performed at UE 115 (e.g., using signal measurements obtained by UE 115 for signals transmitted by SV 102, SV 190, terrestrial gNBs, and assistance data provided to UE 115, for example, by LMF 124).

[0058] The GMLC 126 may support a location request for the UE 115 received from the external client 140, and may forward the location request to the AMF 122 for forwarding by the AMF 122 to the LMF 124, or may forward the location request directly to the LMF 124. A location response (e.g., containing a location estimate of the UE 115) from the LMF 124 may similarly be returned to the GMLC 126 directly or via the AMF 122, and the GMLC 126 may then return the location response (e.g., containing the location estimate) to the external client 140. The GMLC 126 is shown as being connected to both the AMF 122 and the LMF 124 in FIG. 2 , but in some implementations, only one of these connections may be supported by the 5GCN 110.

[0059] A network opening function (NEF) 128 may be included in the 5GCN 110, for example connected to the GMLC 126 and the AMF 122. In some implementations, the NEF 128 may be connected to communicate directly with the external client 140. The NEF 128 may support secure opening of capabilities and events about the 5GCN 110 and the UE 115 to the external client 140, and may enable secure provisioning of information from the external client 140 to the 5GCN 110.

[0060] A user plane function (UPF) 130 may support voice and data bearers for UE 115 and may enable voice and data access for UE 115 to other networks, such as the Internet 175. UPF 130 may be connected to gNB 106 and ng-eNB 114. UPF 130 functions may include: external protocol data unit (PDU) session interconnection points to data networks, packet (e.g., IP) routing and forwarding, user plane portion of packet inspection and policy rule enforcement, quality of service (QoS) handling of the user plane, downlink packet buffering, and downlink data notification triggering. UPF 130 may be connected to a secure user plane location (SUPL) location platform (SLP) 132 to implement support for locating UE 115 using SUPL. SLP 132 may also be connected to or accessible from external client 140.

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

[0062] The external client 140 may be connected to the 5GCN 110 via the GMLC 126 and / or the SLP 132, and / or the NEF 128. The external client 140 may optionally be connected to the 5GCN 110 and / or to a location server via the Internet 175, which may be, for example, an SLP external to the 5GCN 110. The external client 140 may be connected to the UPF 130 directly (not shown in FIG. 1 ) or through the Internet 175. The external client 140 may be a server, a web server, or a user device, such as a personal computer, a UE, etc.

[0063] As noted, while the communication system 100 is described with respect to 5G technology, the communication system 100 may be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) that are used to support and interact with mobile devices (such as UE 115) (e.g., to implement voice, data, positioning, and other functionality). In some such embodiments, the 5GCN 110 may be configured to control different air interfaces. For example, in some embodiments, the 5GCN 110 may be connected to a WLAN directly or using a non-3GPP interworking function (N3IWF, not shown in FIG. 1) in the 5GCN 110. For example, the WLAN may support IEEE 802.11 WiFi access for the UE 115 and may include one or more WiFi APs. Here, the N3IWF may be connected to the WLAN as well as other elements in the 5GCN 110, such as the AMF 122.

[0064] Support for transparent SV 102 utilizing the network architecture shown in FIG. 1 may affect the communication system as follows. 5GCN 110 may treat satellite RATs as a new type of terrestrial RAT with longer latency, reduced bandwidth, and higher error rates. Therefore, while there may be some impact on PDU session establishment and mobility management (MM) and connection management (CM) procedures, the impact on AMF 122 (or LMF 124) may be small, such as providing pre-configured data of fixed tracking areas (TAs) and cells to UE 115 during registration. There may be no impact on SV 102. SV 102 may be shared with other services (e.g., satellite TV, fixed Internet access) utilizing 5G NR mobile access of UE 115 added in a transparent manner. This may enable legacy SV 102 to be used and may avoid the need to deploy a new type of SV 102. In addition, gNB 106 and ng-eNB 114 may be fixed and may be configured to support a country and one or more PLMNs in that country. gNB 106 and ng-eNB 114 may need to assist in the assignment and transfer of SV 102 and satellite cells between gNB 106 or ng-eNB 114 and earth station 104, and support handover of UE 115 between satellite cells, SV 102, other gNB 106, and / or other ng-eNB 114. Thus, gNB 106 may be different from a terrestrial gNB and ng-eNB 114 may be different from a terrestrial ng-eNB. Additionally, the coverage area of ​​gNB 106 or ng-eNB 114 may be much larger than the coverage area of ​​a terrestrial gNB or terrestrial ng-eNB.

[0065] In some implementations, the satellite beam coverage of the SV 102 may be large, e.g., up to or greater than 1000 kilometers (km), and may provide access to more than one country. The NTN gateway 104 may be shared by multiple gNBs 106 and / or by multiple ng-eNBs 114 (e.g., NTN gateway 104-1 may be shared by gNBs 106-1 and 106-2 and by ng-eNB 114), and the gNB 106 and / or ng-eNB 114 may be shared by multiple core networks located in separate PLMNs in the same country or in different countries (e.g., gNB 106-2 may be shared by 5GCN1 110-1 and 5GCN2 110-1, which may be in different PLMNs in the same country or in different countries).

[0066] To simplify later references to satellite NodeBs supporting transparent SV wireless access, as an alternative, any references to gNB 106 later in this document may also be considered to refer to ng-eNB 114 or a satellite NodeB including an eNB accessing the EPC.

[0067] 2 illustrates an example of a communication system 200 capable of supporting satellite access using 5G NR or some other wireless access type such as CDMA, 4G, or future 6G, according to one embodiment. The communication system 200 may implement aspects of the communication system 100.

[0068] The network architecture shown in FIG. 2 is similar to the network architecture shown in FIG. 1 , as designated elements are similar or identical. However, in contrast to the transparent SV 102 shown in FIG. 1 , FIG. 2 illustrates a network architecture utilizing regenerated SVs 202-1, 202-2, 202-3, and 202-4 (collectively referred to as SVs 202). Unlike the transparent SVs 102, the regenerated SVs 202 include an onboard satellite NodeB (referred to as gNB 202), which may include the functional capabilities of the gNB 106 and is sometimes referred to herein as SV / gNB 202. The NG-RAN 112 is illustrated as including the SV / gNB 202. Reference to the gNB 202 is used herein when referencing the SV / gNB 202 functionality associated with communications with the UE 115 and the 5GCN 110, while reference to the SV 202 is used when referencing the SV / gNB 202 functionality associated with communications with the earth station 104 and the UE 115 at the physical radio frequency level. However, there may not be an exact boundary between SV 202 and gNB 202.

[0069] The onboard gNB 202 may perform some or all of the same functions as the gNB 106 as previously described. For example, the gNB 202 may terminate at a radio interface and associated radio interface protocol to the UE 115, and may send DL signals to the UE 115 and receive UL signals from the UE 115, which may include encoding and modulation of the transmitted signals and demodulation and decoding of the received signals. The gNB 202 may also support signaling connections to the UE 115 and voice and data bearers, and may support handover of the UE 115 between different satellite cells of the same gNB 202 and between different gNBs 202. The gNB 202 may assist in the handover (or transfer) of the SV 202 between different earth stations 104, between different 5GCNs 110, and between different countries. The gNB 202 may hide or obscure certain aspects of the SV 202 from the 5GCN 110, for example, by interfacing with the 5GCN 110 in the same or similar manner as terrestrial gNBs. The gNB 202 may further facilitate sharing of SVs 202 in multiple countries. The gNB 202 may communicate with one or more earth stations 104, and via the earth stations 104, with one or more 5GCNs 110. In some implementations, the gNB 202 may communicate directly with other gNBs 202 using an inter-satellite link (ISL) (not shown in FIG. 2 ), which may support an Xn interface between any pair of gNBs 202.

[0070] In the case of LEO SV, SV / gNB 202 may need to manage mobile satellite cells with coverage of different countries at different times. Earth station 104 may be directly connected to 5GCN 110, as illustrated. For example, as illustrated, NTN gateway 104-1 may be connected to AMF 122 and UPF 130 of 5GCN1 110-1, while NTN gateway 104-2 may be similarly connected to 5GCN2 110-2, and earth stations 104-3 and 104-4 are connected to 5GCN3 110-3. For example, in the case where earth station 104 is limited, earth station 104 may be shared by multiple 5GCN 110. For example, in some implementations (illustrated with dashed lines), NTN gateway 104-2 may be connected to both 5GCN1 110-1 and 5GCN2 110-2, and NTN gateway 104-3 may be connected to both 5GCN2 110-2 and 5GCN3 110-3. 5GCN 110 may need to know the SV 202 coverage area to page UE 115 and manage handover. Thus, as can be seen, the network architecture with regenerative SV may have greater impact and complexity than the network architecture with transparent SV 102 shown in FIG. 1 with respect to both gNB 202 and 5GCN 110.

[0071] Support for regenerated SVs utilizing the network architecture shown in FIG. 2 may impact the communication system 200 as follows. The 5GCN 110 may be impacted in the absence of support for fixed TAs and cells, as core components of mobility management and regulatory services that are typically based on fixed cells and fixed TAs for terrestrial PLMNs may have to be replaced by a new system (e.g., based on UE 115 location). In the absence of support for fixed TAs and fixed cells, the 5GCN 110 (e.g., AMF 122) may need to map any fixed TA to one or more SVs 202 with current radio coverage of that TA when performing paging of a UE 115 located in any TA. This may require configuration of long-term orbit data of the SV 202 (e.g., obtained from the SVO of the SV 202) in the 5GCN 110, and may add significant new impacts to the 5GCN 110.

[0072] Legacy SVs may require significant software (SW) updates to support gNB 202 functionality, which may not be feasible. SV 202 will also need to fully support all UEs 115 accessing the SV 202, which may be problematic for legacy SVs due to limited processing and storage capabilities. Therefore, SV 202 will likely need to include new hardware (HW) and SW, rather than being based on a SW upgrade to an existing SV. New SV / gNB 202 may need to support regulatory and other requirements of multiple countries. A GEO SV 202 coverage area will typically include several or many countries, while a LEO or medium earth orbit (MEO) SV 202 will typically orbit over many countries. Thus, support for fixed tracking areas (TAs) and fixed cells may require that the SV / gNB 202 be configured with fixed TAs and fixed cells for the entire global coverage area. Alternatively, the AMF 122 (or LMF 124) in a single 5GCN 110 may support fixed TA and fixed cells for the associated PLMN to reduce SV / gNB 202 complexity at the expense of more 5GCN 110 complexity. Additionally, the SV / gNB 202 to SV / gNB 202 ISL will typically change dynamically as the relative SV / gNB 202 location changes, making the Xn-related procedures more complex.

[0073] To support satellite access using LTE, NB-IOT, or eMTC, the regenerated SV 202 may include an onboard satellite NodeB that may include the functional capabilities of an ng-eNB 114 or an eNB instead of the functional capabilities of a gNB 106 supporting NR access. The functions of the SV 202 and the onboard satellite NodeB and the impact on the 5GCN 110 may then be the same or similar to those described above for an SV 202 having an onboard satellite NodeB corresponding to a gNB 202 supporting NR access, but with the difference that any reference to the gNB 106 will refer to the ng-eNB or eNB, and any reference to the 5GCN 110 or a 5GCN 110 entity (e.g., AMF 122 or UPF 130) will refer to the EPC of the gNB 202 corresponding to the eNB or a corresponding EPC entity (e.g., a mobility management entity (MME) or a serving gateway (SGW) plus a packet data gateway (PDG)), respectively. Therefore, references herein to gNB 202, SV / gNB 202, or SV 202 may be considered to allow the satellite NodeB components of SV 202 to support the functionality of ng-eNB 114 or eNB.

[0074] 3 illustrates an example diagram of a communication system 300 capable of supporting satellite access using 5G NR or some other wireless access type such as CDMA, 4G, or future 6G, according to one embodiment. Communication system 300 may implement aspects of communication systems 100 and / or 200.

[0075] The network architecture shown in FIG3 is similar to the network architecture shown in FIG1 and FIG2, as designated elements are similar or identical. However, in contrast to the transparent SV 102 shown in FIG1 and utilizing a split architecture of satellite NodeBs, FIG3 illustrates a network architecture utilizing regeneration SVs 302-1, 302-2, 302-3, and 302-4 (collectively referred to as SVs 302). The satellite NodeBs referred to as gNBs 307 (e.g., gNBs 307-1, 307-2, and 307-3) include a central unit and may sometimes be referred to as a gNB-CU 307, and unlike the transparent SV 102, the regeneration SV 302 includes an onboard gNB distributed unit (gNB-DU) 302 and is sometimes referred to herein as a SV / gNB-DU 302. References to gNB-DU 302 are used herein when referencing SV / gNB 302 functionality related to communication with UE 115 and gNB-CU 307, and references to SV 302 are used when referencing SV / gNB-DU 302 functionality related to communication with earth station 104 and UE 115 at the physical radio level. However, there may not be a precise boundary between SV 302 and gNB-DU 302.

[0076] Each gNB-DU 302 communicates with a ground-based gNB-CU 307 via one or more earth stations 104. A gNB-CU 307, together with one or more gNB-DUs 302 in communication with the gNB-CU 307, performs functions and may use internal communication protocols similar to or the same as those of a gNB using a split architecture as described in 3GPP TS 38.401. Here, the gNB distributed unit (gNB-DU) 302 corresponds to and performs functions similar to or the same as those of a gNB-DU defined in TS 38.401, and the gNB central unit (gNB-CU) 307 corresponds to and performs functions similar to or the same as those of a gNB-CU defined in TS 38.401. For example, the gNB-DU 302 and the gNB-CU 307 may communicate with each other using the F1 Application Protocol (F1AP) defined in 3GPP TS 38.473, and may together perform some or all of the same functions as the gNB 106 or gNB 202 as previously described. To simplify references to different types of gNBs in the following description, the gNB-DU 302 may sometimes be referred to as gNB 302 (without the "DU" tag), and the gNB-CU 307 may sometimes be referred to as gNB 307 (without the "CU" tag).

[0077] The gNB-DU 302 may terminate at the radio interface to the UE 115 and the associated lower-level radio interface protocols, and may send DL signals to the UE 115 and receive UL signals from the UE 115, which may include encoding and modulation of the transmitted signals and demodulation and decoding of the received signals. The gNB-DU 302 may support and terminate at the radio link control (RLC), medium access control (MAC), and physical (PHY) protocol layers of the NR RF interface to the UE 115, as defined in 3GPP TS 38.201, 38.202, 38.211, 38.212, 38.213, 38.214, 38.215, 38.321, and 38.322. The operation of the gNB-DU 302 is controlled in part by the associated gNB-CU 307. One gNB-DU 302 may support one or more NR satellite cells for the UE 115. The gNB-CU 307 may support and terminate the Radio Resource Control (RRC) protocol, Packet Data Convergence Protocol (PDCP), and Service Data Protocol (SDAP) of the NR RF interface to the UE 115, as defined in 3GPP TS 38.331, 38.323, and 37.324, respectively. The gNB-CU 307 may also be split into separate control plane (gNB-CU-CP) and user plane (gNB-CU-UP) portions, wherein the gNB-CU-CP uses the NGAP protocol to communicate with one or more AMFs 122 in one or more 5GCNs 110, and wherein the gNB-CU-UP uses the General Packet Radio System (GPRS) Tunneling Protocol (GTP) User Plane Protocol (GTP-U) to communicate with one or more UPFs 130 in one or more 5GCNs 110, as defined in 3GPP TS 29.281. The gNB-DU 302 and the gNB-CU 307 may communicate over the F1 interface to: (a) support control plane signaling for the UE 115 using IP, Stream Control Transmission Protocol (SCTP), and F1 Application Protocol (F1AP) protocols; and (b) support user plane data transfer for the UE using IP, User Datagram Protocol (UDP), PDCP, SDAP, GTP-U, and NR User Plane Protocol (NRUPP) protocols.

[0078] The gNB-CU 307 may use terrestrial links to communicate with one or more other gNB-CUs 307 and / or with one or more other terrestrial gNBs to support an Xn interface between any paired gNB-CUs 307 and / or between any gNB-CU 307 and any terrestrial gNB.

[0079] The gNB-DU 302 together with the gNB-CU 307 may: (i) support signaling connections and voice and data bearers to the UE 115; (ii) support handover of the UE 115 between different satellite cells of the same gNB-DU 302 and between different gNB-DUs 302; and (iii) assist in the handover (or transfer) of the SV 302 between different earth stations 104, different 5GCNs 110, and between different countries. The gNB-CU 307 may hide or mask certain aspects of the SV 302 from the 5GCN 110, for example, by interfacing with the 5GCN 110 in the same or similar manner as terrestrial gNBs. The gNB-CU 307 may further assist in sharing the SV 302 in multiple countries.

[0080] In the communication system 300, the gNB-DU 302 that communicates with and is accessible from any gNB-CU 307 will change over time along with the LEOSV 302. In the case of a split gNB architecture, the 5GCN 110 may be connected to a fixed gNB-CU 307 that does not change over time and may reduce the difficulty of paging the UE 115. For example, the 5GCN 110 may not need to know which SV / gNB-DU 302 is needed to page the UE 115. The network architecture with regenerated SV 302 with a split gNB architecture may therefore reduce the 5GCN 110 impact at the expense of additional impact on the gNB-CU 307.

[0081] Support for regenerated SVs 302 using a split gNB architecture as shown in FIG. 3 may impact the communication system 300 as follows. The impact on the 5GCN 110 may be limited as discussed above for the transparent SV 102. For example, the 5GCN 110 may treat the satellite RATs in the communication system 300 as a new type of terrestrial RAT with longer latency, reduced bandwidth, and higher error rates. The impact on the SV / gNB-DU 302 may be less than the impact on the SV / gNB 202 (with a non-split architecture) as discussed above with reference to FIG. 2. The SV / gNB-DU 302 may need to manage changing associations with different (fixed) gNB-CUs 307. In addition, the SV / gNB-DU 302 may need to manage satellite beams and satellite cells. For a network architecture with transparent SV 102, the gNB-CU 307 impact may be similar to the gNB 106 impact, as discussed above, except for the impact on supporting satellite cells and satellite beams (these impacts may affect the gNB-DU 302 but not the gNB-CU 307).

[0082] To support satellite access using LTE, NB-IOT or eMTC, a regenerated SV 302 with a split architecture for satellite NodeBs may also be used. However, unlike the split architecture for terrestrial gNBs supporting 5G NR, no split architecture is defined for terrestrial ng-eNBs or terrestrial eNBs. However, in principle, a split architecture is possible using CUs and DUs that perform similar functions to gNB-Cu and gNB-DU for terrestrial ng-eNBs or terrestrial eNBs. In this case, the gNB-CU 307 shown in FIG. 3 may be replaced by a CU for ng-eNB 114 (shown as ng-eNB-CU 308 in FIG. 3 ) or a CU for eNB (not shown in FIG. 3 ), and the gNB-DU 302 in the SV 302 may be replaced by a DU for ng-eNB 114 or eNB. In this case, references herein to gNB-DU 302 may refer to a DU for ng-eNB 114 or eNB, references herein to gNB 307 or gNB-CU307 may refer to ng-eNB-CU 308 or a CU for eNB, and references to SV 302 may refer to an SV having onboard functionality of a DU for ng-eNB 114 or eNB.

[0083] There are several SVOs currently in operation and several additional SVOs in preparation for commencement of operation that may be capable of supporting satellite access using 5G NR or some other wireless access type such as CDMA. The various SVOs may employ different numbers of LEO SVs and earth gateways, and may use different technologies. For example, currently operating SVOs include those that use transparent ("bent pipe") LEO SVs utilizing CDMA and regenerative LEO SVs with ISL capabilities. New SVOs have recently been announced with plans for large constellations of LEO SVs to support fixed Internet access. These various SVOs are well known in the industry.

[0084] When supporting satellite access to a wireless network, the SV 102 / 202 / 302 may transmit satellite beams (also referred to as "radio beams" or just "beams") over multiple countries. For example, the beams transmitted by the SV 102 / 202 / 302 may overlap two or more countries. However, sharing beams over two or more countries may cause complexity. For example, in a situation where a beam is shared by two or more countries, an earth station 104 and a gNB 106 / 202 / 302 / 307 in one country may need to support access by UE 115 from other countries. Sharing beams over multiple countries may cause security issues for the privacy of both data and voice. In addition, sharing SV beams over multiple countries may cause regulatory conflicts. For example, regulatory services including wireless emergency alerts (WEA), lawful interception (LI), and emergency services (EM) calls in a first country may require support from a gNB 106 / 202 / 307 and an earth station 104 in a second country that share the same SV beam.

[0085] One solution to the complexity caused by beam sharing between multiple countries may be to assign one beam to one country. Exceptions to assigning one beam to one country may exist for small nearby countries. Assigning a beam to a single country additionally implies assigning each satellite cell to one country.

[0086] 4 illustrates an example of a communication system 400, which illustrates, by way of example, that SVs 102, 202, 302 generate multiple beams, identified as beams B1, B2, B3, B4, B5, and B6, over an area 405 that includes portions of multiple countries (e.g., country A, country B, country C). The communication system 400 may implement aspects of the wireless communication systems 100, 200, and / or 300. In the case where each beam is assigned to only one country, beams B1, B3, B5 are assigned to country A, beams B4 and B6 are assigned to country B, and beam B2 is assigned to country C.

[0087] In one implementation, individual beams may be assigned to a single country by steering or steer- ing the beam. Although non-geostationary orbit (NGEO) SVs have mobile coverage areas, relative beam directions may be moved via steerable antenna arrays (sometimes referred to as "steerable beams") to remain or mostly remain within a country. For example, beam coverage may move slowly within a country and then jump to a new country, for example, after the SV 102, 202, 302 has been transferred to a new NTN gateway 104 or a new gNB 106 or 307.

[0088] In another specific implementation, satellite cells and satellite beams may be allowed to support access by different UEs 115 in two or more countries at the same time. For example, beam B1 may support access from UEs 115 in countries A and C, and beams B4 and B5 may support access from UEs 115 in countries A and B. In such cases, support for regulatory services may be important where the gNB 106 / 202 / 307 and / or AMF 122 can determine the country in which the UE 115 is located.

[0089] 5 illustrates an example of a communication system 500 including a satellite cell generated by an SV 102, 202, 302 over an area 505 including multiple earth-fixed cells 502. The communication system 500 may implement aspects of the communication systems 100, 200, 300, and / or 400. The satellite cell may include a single beam or multiple beams, for example, all beams in a satellite cell may use the same frequency or the satellite cell may include one beam for each frequency in a set of different frequencies. For example, beams B1, B2, and B3 may support three separate satellite cells (one beam per satellite cell) or may collectively support a single satellite cell (e.g., satellite cell 504 shown in dashed lines). Preferably, the satellite cells cover adjacent areas.

[0090] The satellite beams and satellite cells generated by the SVs 102, 202, 302 may not be aligned with cells used by terrestrial wireless networks (e.g., 5GCN 110 terrestrial cells or LTE terrestrial cells). For example, in an urban area, the satellite beams or satellite cells generated by the SVs 102, 202, 302 may overlap with many 5GCN fixed terrestrial cells. When supporting satellite access to a wireless network, information about the satellite beams and satellite cells generated by the SVs 102, 202, 302 may be hidden from the 5GCN 110 (e.g., not configured in the 5GCN or not provided to the 5GCN).

[0091] As illustrated in FIG. 5 , area 505 may include multiple earth-fixed cells 502, and fixed tracking areas (TAs) such as TA 506. Fixed cells are not "real cells" such as for terrestrial NR and LTE access, and may be referred to as "virtual cells" or "geographic cells". Fixed cells such as fixed cell 502 have a fixed geographical coverage area that may be defined by a PLMN operator. For example, the coverage area of ​​a fixed cell or fixed TA may include the interior of a circle, an ellipse, or a polygon. The coverage area is fixed relative to the surface of the earth and does not change over time, which is different from the coverage area of ​​a satellite cell that generally changes over time for LEO or MEO SVs. Fixed cells 502 may be considered by 5GCN 110 to be the same as real cells supporting terrestrial NR access. A group of fixed cells 502 may define a fixed TA 506, which may be considered by 5GCN to be the same as a TA defined for terrestrial NR access. Fixed cells and fixed TAs for 5G satellite wireless access may be used by 5GCN 110 to support mobility management and regulatory services for UE 115 with minimal new impact.

[0092] In the case of a regenerated SV 202 utilizing a non-split architecture as in the communication system 200, each satellite cell may be maintained using the same SV 202 and may have mobile coverage areas supporting different 5GCNs 110 at different times.

[0093] In the case of a transparent SV 102 and a regenerative SV 302 with a split architecture as in the communication system 300, each satellite cell may be assigned to and controlled by one gNB 106 or 307 representing one or more PLMNs in a country. For a GEO SV 102 / 302, the assignment to the gNB 106 / 307 may be permanent or temporary. For example, the assignment may change daily to allow peak traffic to occur at different times in different parts of the SV 102 / 302 radio footprint and / or may change over longer periods of time to accommodate changing regional traffic needs. For a non-geostationary (NGEO) SV 102 / 302, the assignment may last for a short time, for example, only 5 to 15 minutes. The non-permanent satellite cell may then be transferred to a new gNB 106 / 307 as needed (e.g., when access to the NGEO SV 102 / 302 is transferred to the new gNB 106 / 307). For example, each gNB 106 / 307 may have a fixed geographic coverage area, e.g., including multiple fixed cells 502 and a fixed tracking area (TA). Upon (or after) moving into the fixed coverage area of ​​a second gNB 106 / 307, the satellite cell of the first NGEO SV 102 / 302 may be transferred from the first gNB 106 / 307 to the second gNB 106 / 307. Prior to the transfer, a UE 115 accessing a satellite cell in a connected state may be moved to a new satellite cell of the first gNB 106 / 307 or may be handed over to the second gNB 106 / 307 as part of the transferred satellite cell. The SV 102 / 302 may be accessed from only one gNB 106 / 307 or from multiple gNBs 106 / 307 that may be in different countries. In one implementation, an SV 102 / 302 may be assigned to multiple gNBs 106 / 307 by partitioning the satellite cells generated by the SV 102 / 302 between different gNBs 106 / 307. The satellite cells may then be transferred to new gNBs 106 / 307 (and new countries) as the SV 102 / 302 moves or as traffic needs change. This implementation would be a form of soft handover, where the transfer of an SV 102 / 302 from one gNB 106 / 307 to another occurs in increments of satellite cells, rather than all at once.

[0094] 6 illustrates an example of assignment of satellite cells (eg, cell 1 and cell 2 in communication system 600) generated by one or more SVs 102, 202, 302 over an area 605. FIG.

[0095] In the communication system 600, and as illustrated, the area 605 includes a plurality of fixed TAs, such as TA1 to TA15, wherein TA4, TA5, TA8, and TA9 are assigned to gNB1 (which may be gNB 106, gNB 202, or gNB 307), and TA12, TA13, TA14, and TA15 are assigned to gNB2 (which may be another gNB 106, 202, or 307). In one implementation, a satellite cell may be considered to support a fixed TA if: the satellite cell is completely within the TA (e.g., cell 2 is within TA 12); the TA is completely within the satellite cell (e.g., TA4 is within cell 1); or the overlap of the coverage area of ​​the satellite cell and the TA exceeds a predetermined threshold fraction of the total coverage area of ​​the satellite cell or the total area of ​​the TA (e.g., cell 1 overlaps with TA1, TA3, TA5, TA8, or TA9). SV 102, 202, 302 may broadcast the identities (IDs) of supported PLMNs (e.g., where the PLMN ID includes a mobile country code (MCC) and a mobile network code (MNC)) and, for each supported PLMN, the IDs of supported TAs (e.g., where the ID of the TA includes a tracking area code (TAC)), for example, in a system information block type 1 (SIB1) or SIB type 2 (SIB2). For NGEO SVs, the supported PLMNs and TAs may change as the satellite cell coverage area changes. gNB 106 / 202 / 307 may determine PLMN and TA support (and therefore the PLMN ID and TAC broadcasted in the SIB for each satellite cell) based on the known ephemeris data of each SV 102 / 202 / 302 and the known directivity and angular range of the component satellite beams of each satellite cell (e.g., cell 1 and cell 2). gNB 106 / 202 / 307 may then update the SIB broadcast.

[0096] Thus, as illustrated in FIG6 , SV 102 / 202 / 302 may broadcast a SIB including TACs of TA4 and possibly TA1, TA3, TA5, TA8, and / or TA9 for cell 1. Similarly, SV 102 / 202 / 302 or another SV 102 / 202 / 302 may broadcast a SIB including TACs of only TA12 for cell 2. Cell 1 may be assigned to gNB1 (which has coverage of TA4, TA5, TA8, and TA9), and cell 2 may be assigned to gNB2 (which has coverage of TA12, TA13, TA14, and TA15). In the event that the cell coverage area moves from one gNB area to another gNB area, cell 1 and cell 2 may be transferred from gNB1 to gNB2 or from gNB2 to gNB1.

[0097] The coverage area of ​​a fixed TA may be defined in a simple, precise, flexible manner, and requires minimal signaling to communicate to the UE 115 or gNB 106 / 202 / 307 or entity in the 5GCN 110. The fixed TA area may be small enough to allow efficient paging by including an area supported by only a few (e.g., less than 10) satellite cells, and may also be large enough to avoid excessive UE registrations (e.g., may extend for at least several kilometers in any direction). The shape of the fixed TA area may be arbitrary, e.g., the shape may be defined by a PLMN operator, or may have one or more restrictions. For example, one restriction on the shape of the fixed TA area may be that a fixed TA along a country border is precisely aligned with the border to avoid serving a UE 115 in another country. Additionally, the fixed TA may be restricted to align with an area of ​​interest, such as a public safety answering point (PSAP) service area, an area of ​​a large campus, etc. Additionally, the fixed TA may be restricted so that a portion of the fixed TA is aligned with a physical obstacle, such as the shore of a river or lake.

[0098] The coverage area of ​​a fixed cell may also be defined in a simple, precise, and flexible manner, and requires minimal signaling to communicate to the UE 115 or gNB 106 / 202 / 307. The fixed cell coverage area may allow for a simple and precise association with a fixed TA, e.g., a fixed cell may unambiguously belong to a fixed TA.

[0099] For an entity in a communication system (e.g., a UE 115 and / or AMF 122 in the communication system 100, 200, or 300), it may be beneficial to know when satellite coverage will be available and when it will not be available at a particular location (e.g., the current location of the UE 115). Conventional satellite coverage information technologies utilize satellite orbit and ephemeris data to indicate to an entity (e.g., the UE 115) when each of a plurality of satellites will be visible at a particular location (e.g., the current location of the entity). Using these techniques, the entity will need to calculate the position of the satellite (using the orbit or ephemeris data) and determine at what time the satellite will be visible and will not be visible at a particular location, which may be processor intensive, require the implementation of complex programming logic, and be prone to errors. For example, even when a satellite is visible at a location, the location may not be within the coverage of a satellite cell supported by the satellite (e.g., in the case where the satellite does not have an antenna pointed at the location and capable of sending and receiving signals to and from the location). Additionally, the satellite may not always have a backhaul connection to an NTN gateway (eg, NNT gateway 104) during the time the satellite is visible at the location (eg, if the PLMN is not configured to provide coverage using the satellite while the satellite is visible at the location).

[0100] One way in which satellite coverage data may be provided to the UE is by broadcasting ephemeris data at the access stratum (AS) level for the NTN RAT. For example, for EPS, a base station such as an eNB may broadcast ephemeris for up to (for example) four satellites in a system information block (SIB) such as SIB32 of coverage information for a RAT (e.g., LTE LEO) supporting a particular AS. The base station may also broadcast orbital parameters (and possibly positions) for each satellite. The amount of data broadcast by each satellite may be about 18 octets (e.g., such as EPS in 3GPP Release 17 using SIB32). The total data for four satellites is therefore about 72 octets. The LEO satellite coverage at any location may be in the range of 5 minutes to 15 minutes. Therefore, the broadcast data of four satellites will provide coverage data for about the next 60 minutes at a minimum when there are almost no coverage gaps, or about 2 hours of coverage data in the case of 50% coverage, and about 10 hours of coverage data in the case of 10% coverage. The satellite may not return to cover the same location again for 12 hours or more, for example, due to the rotation of the earth. Therefore, SIB32 may only be used to indicate coverage for about 1 hour to 10 hours at any location. The amount of coverage data required for 24 hours coverage may therefore be as much as 500 to 1000 octets. Furthermore, the coverage data may not be completely reliable because radio cell information is not included, for example, radio cell coverage and areas where NTN is visible but not supported may not be addressed. Furthermore, the coverage data will not address the TN RAT. Additionally, there may also be security risks in the case of fake gNB / eNBs broadcasting SIB32 indicating lack of coverage when there is coverage.

[0101] Another way in which satellite coverage data can be provided to the UE is at the non-access stratum (NAS) level. For long-term coverage information at multiple locations, large amounts of data may be required, which may not be suitable for NAS transfer, which is typically used to control services and mobility to the UE rather than to provide large amounts of data to the UE.

[0102] Therefore, new techniques may be needed to provide more accurate and reliable satellite coverage information to entities such as UE 115, AMF 122 and MME (in the case of 4G LTE networks).Satellite coverage information (or data) may also be referred to as Satellite Coverage Availability Information (SCAI).

[0103] One way to provide coverage information (e.g., SCAI) to the UE 115 is a coverage map, which may be more advantageous than providing satellite orbit (ephemeris) data. When coverage data is provided as ephemeris / orbit data, the UE must perform its own coverage prediction. For example, in the case where the UE is at location L at time T, the UE needs to determine whether there will be coverage at that location and time. To determine this, the UE will use the ephemeris (and any radio cells) data and calculate whether there is satellite visibility (for L and T) and whether there may be radio cell coverage for L and T (in a known situation). The answer can be a binary yes / no (e.g., there may be a threshold probability between yes and no). With a coverage map, the UE 115 may only need to look up the answer, which may be a very simple operation. Because the coverage map provider may have much more information than is available to the UE, the coverage map lookup of the yes / no answer may be much more reliable than providing ephemeris data to the UE in only a few orbital parameters (e.g., the provider may know exactly how many satellites and radio cells will be supported for L and T).

[0104] 7A illustrates an example of assignment of satellite cells (e.g., cell 1 and cell 2 in communication system 700) generated by one or more SVs 102, 202, 302 over an area divided into grid squares / points. FIG7A may implement aspects of communication systems 100, 200, 300, 400, 500, and / or 600.

[0105] Aspects of the techniques described herein may include a server (e.g., an operations and maintenance (O and M) server) that may be associated with (e.g., owned and operated by) a serving PLMN for a UE or a spacecraft operator (SVO). The server may determine, preconfigure, and signal satellite coverage data showing times of satellite cell (NTN) coverage and lack of coverage (e.g., times without NTN coverage) at different locations and / or at different times. The satellite coverage data may be provided by the server to the UE 115, AMF 122, MME, gNB 106 / 202 / 307, and / or other entities to show when wireless coverage via one or more satellite cells is available and when it is not available at one or more locations. The satellite coverage data may be determined (e.g., by the server) in part using SV orbit or ephemeris data, SV support of the satellite cells, and knowledge of the availability of backhaul connections to the NTN gateway. However, the satellite coverage data itself may exclude all such original source information and may more directly indicate coverage versus lack of coverage, which may reduce processing complexity and processing load at the receiving entity (eg, UE 115 or AMF 122) and avoid errors.

[0106] In one embodiment, satellite coverage data may be provided in the form of a "coverage map", which may reference, indicate or include multiple individual locations (designated here as L1, L2, L3, ..., Ln) and / or a continuous time sequence (designated here as T1, T2, T3, ..., Tm). Thus, coverage data may be provided for one or more locations and at one or more times. Each location Li (1≤i≤n) may correspond to a single point on the surface of the earth or an area on the surface of the earth (e.g., where each area is between 1km and 20km long from one side to the other, or where each point is spaced 1km to 20km from the nearest other point). The sequence of continuous times may occur at intervals, such as fixed intervals, where each fixed interval is 10 seconds to 2 minutes. In a specific implementation, these areas may each correspond to a fixed cell or fixed tracking area as illustrated and described in Figures 5 and 6. The positions Li may also be arranged in a grid pattern as illustrated in FIG. 7A , where the positions Li may be points 702 corresponding to the intersections of the vertical and horizontal lines in FIG. 7A , or rectangular areas 704 corresponding to the areas defined by the vertical and horizontal lines in FIG. 7A . Although the grid pattern shown in FIG. 7A is rectangular, other grid patterns are also possible (e.g., based on triangles or hexagons). In addition, although FIG. 7A shows a rectangular area, the positions Li corresponding to the areas may have any shape, including, for example, circular, elliptical, and polygonal. In addition, the positions Li corresponding to the areas may be non-overlapping (e.g., as in FIG. 7A ) or may be overlapping. For each position Li (1≤i≤n) and time Tj (1≤j≤m), the coverage map may indicate whether satellite coverage is available at that position and time. In the case where Li corresponds to an area and the UE 115 is within the area, or in the case where Li corresponds to a point and is the closest point to the UE 115, it may be assumed that the UE 115 is at the position Li.

[0107] Satellite coverage available may correspond to a location Li being completely or partially within the coverage area of ​​at least one satellite cell that can provide access to a specific PLMN (e.g., the current serving PLMN of UE 115, the home PLMN of UE 115, or any PLMN that UE 115 is allowed to access). Similarly, satellite coverage unavailable may correspond to a location Li not being completely or partially within the coverage area of ​​at least one satellite cell that can provide access to a specific PLMN (e.g., the current serving PLMN of UE 115, the home PLMN of UE 115, or any PLMN that UE 115 is allowed to access). For a location Li corresponding to a point (e.g., point 702 in FIG. 7A ), the point is usually within the coverage area of ​​a satellite cell or not within the coverage area, and there is no difference whether it is partially or completely within the coverage area. For a location Li corresponding to an area (e.g., area 704 in FIG. 7A ), the location Li may be partially within the coverage area of ​​a satellite cell but not completely within the coverage area, and thus there may be a difference between a coverage map based on partial inclusion and a coverage map based on full inclusion. The UE 115 or other entity (eg, AMF 122 or MME) may then decide (eg, based on serving PLMN or home PLMN configuration data) whether to base the satellite coverage determination for location Li on partial inclusion or full inclusion.

[0108] The coverage map may indicate whether satellite coverage is available at a location Li and a time Tj using a binary one value or a Boolean TRUE value (e.g., corresponding to coverage available) or a binary zero value or a Boolean FALSE value (e.g., corresponding to coverage not available). The coverage map may then be represented by an array or string of binary values ​​of one and zero (or Boolean TRUE and FALSE values), and thus represented as a bitmap, which may include a bit string or bit array, and in which there is a known correspondence between each bit in the bitmap and a specific location Li and time Tj. Additional information may be provided as part of the coverage map or separately therefrom to indicate the locations L1, L2, L3, ..., Ln and the consecutive times T1, T2, T3, ..., Tm represented in the coverage map, and (where not implicit) to indicate the method used to encode the bit values. Thus, a coverage map (e.g., a bitmap) may include a plurality of bits, each of which corresponds to satellite coverage data for a specific location and a specific time.

[0109] 7A , at time T11, UE 115 may be located within or at a grid point location where UE 115 is within the coverage area of ​​cell 2. Thus, the bitmap may be encoded to indicate a "1" bit at a bit position corresponding to the current location of UE 115 at time T11. Thus, UE 115 may transition to or otherwise enter the coverage state of cell 2 via SV 102 / 202 / 302 at time T11.

[0110] However, the movement of SV 102 / 202 / 303 may cause the coverage area of ​​cell 2 to move, so that at time T22, UE 115 is no longer in the coverage area of ​​cell 2. UE 115 accessing the coverage map may determine that its current location is out of coverage at time T22 by finding a "0" bit in the bitmap corresponding to the bit position of the current location of UE 115 at time T22. Therefore, at time T22, UE 115 may transition or otherwise enter a no coverage state. Various power saving and resource saving techniques may be employed by UE 115 when operating in a no coverage state.

[0111] At time T33, the movement of the other SV 102 / 202 / 302 may result in the current location of the UE 115 being within the coverage area of ​​cell 1. Again, the bit in the bitmap corresponding to the current location of the UE 115 at time T33 may be encoded as a "1" bit to again indicate that the UE 115 has satellite coverage at time T33. Thus, the UE 115 may transition to or otherwise enter a coverage state and resume communications via the other SV 102 / 202 / 302.

[0112] The total number of bits in the bitmap may depend on the number of locations n and the number of times m for which coverage data is provided. For example, for a PLMN with a 2000 km×2000 km coverage area, 24 hours of coverage data, a 1 minute interval between consecutive times, and a 20 km square grid point spacing, the coverage map may be encoded as a bitmap containing (100×100×24×60) bits, which equal 1.8 megabytes (million octets) of uncompressed data. However, it is likely that, because coverage conditions are generally the same at nearby times and nearby locations, the bits in the bitmap corresponding to nearby locations and nearby times will generally have the same value (“1” or “0”). This may allow the bitmap to be compressed using one-dimensional, two-dimensional, or three-dimensional compression techniques (e.g., compression algorithms). For example, using one-dimensional technology, the run of continuous zero or one-bit value in the bitmap can be encoded as a different usually shorter bit sequence, which can be distinguished from any other bit sequence encoding (for example, using the one-dimensional decoding scheme defined in the ITU T.4 "Standardization of Group 3 faxterminals for document transmission" standard). This can significantly reduce the overall size of the bitmap. For example, using two-dimensional technology, a one-dimensional technology can be used to compress a bitmap applicable to one time (for example, T1), and then a bitmap for the next time (for example, T2) can be encoded by assigning a "0" bit value to any position Lj that has not changed since the previous time T1 and assigning a "1" bit value to any position Lk that has changed since the previous time T1. The bitmap can then be compressed using the same (or similar) one-dimensional technology as the bitmap at time T1. Additionally or alternatively, a bitmap may be provided to an entity (e.g., UE 115) for only a single location (e.g., the current location of UE 115) or for a small number of locations, which may significantly reduce the size of the bitmap. For example, the small number of locations may include: (i) locations near UE 115; (ii) locations recently visited by UE 115; (iii) locations that UE 115 habitually visits, such as work, home, or locations of friends or relatives; (iv) locations indicated by UE 115 as being of interest; (v) locations that UE 115 is expected to visit in the near future; or (vi) some combination of these locations. For the previous example, in the case of providing a bitmap for only one location, the uncompressed bitmap size would be reduced to 180 bytes, and in the case of providing a bitmap for an area of ​​100 km×100 km, the uncompressed bitmap size would be 4.5 kilobytes.

[0113] A separate time-location based coverage map may be provided for each RAT, or the coverage maps for each RAT may be combined, for example using a logical OR or by including separate bit values. Additionally, a coverage map for the TN RAT may be provided. In some implementations, the coverage map may provide two (or more) bits for each location and time to indicate the probability of coverage (e.g., zero, low, medium, high). For 24 hours of coverage at 2 minute intervals for one location, the uncompressed data size of the coverage data for one RAT may be approximately 90 octets.

[0114] FIG7B illustrates an example of a coverage map represented by a bitmap for a communication system 750 generated by one or more SVs 102, 202, 302 over an area covered with a square array of grid points, where compression may be used. FIG7B may implement aspects of the communication systems 100, 200, 300, 400, 500, 600, and / or 700. The grid point array in the communication system 750 includes 25 grid points (labeled L1, L2, L3, ..., L25) separated from each other by a distance D (e.g., where D is equal to 10 km to 50 km) and arranged around a central grid point 752 (corresponding to location L13), which may correspond to the current or most recent location of the UE 115. The grid point array may be used to provide the UE 115 with a coverage map for the current or most recent location of the UE 115 (corresponding to the grid point 752) and for a small number of locations at grid points near the current or most recent location. FIG. 7B shows satellite coverage 760 of a grid point array at time T1 and satellite coverage 770 of the same grid point array at a subsequent time T2 (e.g., where T2 may occur one or several minutes after time T1). Grid point locations with satellite coverage are represented by small solid black disks in FIG. 7B, and grid point locations without satellite coverage are represented by small disks with white interiors in FIG. 7B. In the case of using a bit string to represent coverage at a grid point location at time T1 (where a "1" bit value is used to indicate coverage, and a "0" bit value is used to indicate no coverage), the bit string for the locations in order L1, L2, L3, etc. would be "0000000011111000001100000". This bit string contains 25 bits (for 25 locations) in which there are 8 consecutive "0" values, 5 consecutive "1" values, 5 consecutive "0" values, 2 consecutive "1" values, and 5 consecutive "0" values. These values ​​can be compressed, for example, to "10011", "0011", "1100", "11", and "1100", respectively, using a one-dimensional decoding scheme defined in the ITU T.4 standard (and using white to represent "0" values ​​and black to represent "1" values). This allows the bit string to be compressed to "1001100111100111100", which now has 19 bits. A bit string representing the coverage 770 at time T2 can be created using a "0" bit value at any position whose coverage did not change at time T2 and a "1" bit value at any position whose coverage changed at time T2. In the example of Figure 7B, at time T2, the coverage only changes at positions L17 and L18. Therefore, the bit string showing the coverage 770 at time T2 would be "0000000000000000110000000". The bit string has 16 consecutive "0" values, 2 consecutive "1" values, and 7 consecutive "0" values.These values ​​may be compressed, for example, using the ITU T.4 one-dimensional coding scheme to "101010", "11", and "1111", respectively. This allows the bit string to be compressed to "101010111111", which now has only 12 bits. Compression may be particularly efficient when a large area including many grid point locations is either completely in coverage or completely out of coverage, and / or when coverage does not change from one time to the next, because there may be a large number of consecutive bits with the same bit value, which may allow for much higher compression than in the above two examples (e.g., using the ITU T.4 standard scheme or other schemes).

[0115] In another embodiment, satellite coverage data may be provided in the form of a "time series" that may include a sequence of times or time periods indicating when satellite coverage begins and ends at a particular location. For example, a sequence of consecutive times t1, t2, t3, ..., tr indicating when satellite coverage may begin or end at a certain location may be provided, wherein alternating times in the sequence alternately indicate the beginning or end of satellite coverage. For example, it may be indicated that satellite coverage begins at t1, ends at t2, begins again at t3, ends again at t4, and so on. There may be an implicit convention or an explicit indication that the first time in the sequence indicates the beginning (or end) of satellite coverage. In a variation of this embodiment, the consecutive times t1, t2, t3, ... may include time periods rather than moments. Then, there may also be an implicit start time T (e.g., which may be the current time at which the entity receives the consecutive times) or an explicitly provided start time T. The entity may then determine that satellite coverage will begin (or end) at time T+t1, end (or begin) at time T+t1+t2, start again (or end again) at time T+t1+t2+t3, and so on.

[0116] In some embodiments, the coverage map may be combined with a time series. For example, a coverage map (e.g., a bitmap) may be provided to the UE 115 indicating locations with and without satellite coverage at time T1. A second time T2 or duration D2 indicating a time or duration for the coverage map may also be provided to the UE 115. For example, providing time T2 may indicate that the satellite coverage indicated by the coverage map remains the same from time T1 to time T2 (for all locations in the coverage map). Similarly, providing duration D2 may indicate that the satellite coverage indicated by the coverage map remains the same for duration D2 (i.e., from time T1 to time T1+D2). In some embodiments, a coverage map and additional time or duration (e.g., T2 or D2 in the previous example) may be provided when all locations in the coverage map have satellite coverage or do not have satellite coverage.

[0117] FIG. 7C illustrates an example of a coverage map 780 illustrating locations 782 as grid points in a rectangular array. As discussed above, the coverage map 780 may enable the UE 115 to determine that it must remain without service or must attempt to register on a different RAT / PLMN that is available to receive normal service during discontinuous coverage in the current NTN RAT. By using the coverage map 780, the UE 115 may avoid attempting PLMN access when there is no network coverage. In addition, the coverage map 780 may inform the UE 115 when there is network coverage so that the UE 115 may attempt PLMN access as needed, such as to transfer signaling, transfer data, or receive paging, etc., where network coverage is provided by any RAT supported by the UE. The content of the coverage data in the coverage map 780 may be general enough to support both satellite (NTN) RAT and TN RAT, either alone or in combination.

[0118] The content of the coverage data included in the coverage map 780 may show the expected coverage of one or more satellite RATs and / or one or more terrestrial RATs at one or more locations and at a specific time in the future. A set of coverage maps may then be provided to the UE 115 for each time in a time series occurring at fixed periodic intervals (e.g., at one-minute intervals). The locations 782 supported by the coverage map 780 may correspond to grid points in a rectangular array, as illustrated in FIG. 7C , but other arrays are possible, such as a hexagonal array.

[0119] In FIG. 7C , each grid point (dot) 782 represents a location. These locations (i.e., grid points) can be spaced apart by fixed distances (e.g., 20 km to 400 km) horizontally and vertically. The absolute position of each grid point can then be learned by specifying an absolute (global) position for only one grid point in the array (e.g., a central grid point or a grid point at a corner). The expected (satellite and / or land) coverage at the location of each grid point can be indicated by a binary one value (e.g., when there is coverage) or a binary zero value (e.g., when there is no coverage), which will allow the entire coverage map to be represented and encoded as a binary array, as described above. This binary array may be applicable to only one time, and then may need to be repeated to indicate coverage at other times. For example, in the case of the grid point array shown in FIG. 7C , 36 bits will be required to indicate coverage at all 36 grid points. In case this coverage applies to time T1 and coverage of further times T2, T3, ... Tm is needed, a total of 36*m bits will need to be provided along with some encoding rules on how these bits are associated with different grid point locations and different times T1 to Tm.

[0120] Instead of providing a simple binary "yes / no" coverage indication, the expected coverage can be indicated by assigning two or more bits per location to indicate the coverage probability. For example, where 00 = zero coverage probability, 01 = low probability, 10 = medium probability, 11 = high coverage probability. The coverage map 780 can also indicate coverage for only one RAT, or can indicate the expected coverage for multiple RATs. For example, in the case where binary coverage values are assigned to multiple RATs R1, R2, ... Rn, a binary one can mean that there is coverage from at least one of RATs R1 - Rn, while a binary zero value can indicate that no RAT provides coverage.

[0121] Because it is likely that the coverage will generally be the same for nearby times and for nearby locations, there is a possibility of compressing the binary encoding of the coverage map to reduce the bit size.

[0122] In the case of one location (e.g., which may be suitable for a UE 115 that will not move more than about 200 km from some initial location), the size of the binary coverage map of 24 - hour coverage data at 2 - minute intervals can be 90 octets without compression and ignoring additional data such as a global location indication for one location.

[0123] The example in Figure 7C assumes that the coverage map 780 is spatial (for only one time), and as previously described, repeats the coverage map for subsequent times, i.e.:

[0124] Coverage map = <Coverage of locations L1 to Ln at T1> <Coverage of locations L1 to Ln at T2> <Coverage of locations L1 to Ln at T3>... <Coverage of locations L1 to Ln at Tm>

[0125] However, this can be reversed by providing a time coverage map for one location (grid point) of a time series and then repeating the time coverage map for each of the other locations (grid points), i.e.:

[0126] Coverage map = <Coverage of location L1 at T1, T2,... Tm> <Coverage of location L2 at T1, T2,... Tm> <Coverage of location L3 at T1, T2,... Tm> … <Coverage of location Ln at T1, T2,... Tm>

[0127] According to some embodiments, a smaller grid point spacing (e.g., 100 km instead of 400 km) and a smaller interval between consecutive times (e.g., 15 seconds instead of 1 minute) can be used to increase the accuracy (precision) of the coverage and no - coverage indications, but this is accompanied by an increase in the size of the coverage map.

[0128] According to some embodiments, in order to compress the data size of the coverage map, any sequence of repeated binary ones or repeated binary zeros in the coverage map can be indicated by including the number of repeated binary ones or binary zeros rather than by including all repeated values. For example, a time coverage map for one position X (grid point) of the time series can be represented as:

[0129] Overlay at position X = <start time> <1 / 0 duration 1> <1 / 0 duration 2> <1 / 0 duration 3> ... <1 / 0 duration N>

[0130] In this example, a leading 1 or 0 binary value may indicate whether there is coverage, and the value of the associated duration indicates how long the coverage or lack of coverage will last. The duration may be related to an actual period of time given a start time. In the case where the duration is encoded as a 7-bit value (e.g., in minutes), the coverage at position X will become an octet sequence rather than a binary sequence. In the case of no coverage and / or the duration of coverage tends to be quite large (e.g., greater than 20 minutes), such as when coverage is very sparse or highly available, this can result in a much smaller coverage map than using binary encoding. The duration may be further encoded using 2 alternative units (e.g., minutes versus seconds, as indicated by the use of an additional bit) to achieve higher accuracy and precision with only a small increase in the size of the coverage map data.

[0131] SCAI may also be provided to the MME or AMF (e.g. AMF 122) and the UE. For the AMF (or MME), SCAI may apply to a region and implicitly to a potentially large service area of ​​the AMF (or MME) (e.g., an entire country or region of a country). SCAI may also need to apply to the region for a certain period of time (e.g., 6 hours, 24 hours, 48 ​​hours, etc.) to enable an indication of when coverage is available or unavailable for different locations within the region.

[0132] A single UE (e.g., UE 115) does not typically require SCAI for the entire AMF (or MME) area. However, since the UE may move around and may move unpredictably within the AMF (or MME) service area, and may cross different AMF (or MME) service areas, a regional approach to supporting the UE's SCAI may also be appropriate. For example, in extreme cases where the UE is not expected to move a large distance (e.g., less than 25km), the UE SCAI may be minimized to a single location or a smaller area around a single location (e.g., a circle with a radius of 25km). In other cases where the UE may move longer distances, the possible future location of the UE (e.g., based on a maximum travel distance estimate) may be used to define a larger area for which SCAI is provided. When the UE may cross AMF (or MME) areas, either possibility will make the UE SCAI a subset of the SCAI for one AMF (or MME) or for several AMFs (or MMEs).

[0133] Additionally or alternatively, the UE SCAI may be based on a known or expected trajectory of the UE, where future UE locations may be defined together with the times at which the UE will be at these locations. When the time is unknown, the UE trajectory may define an area where SCAI may be provided as a subset of the SCAI for the AMF (or MME). When the time is known, the UE SCAI may be provided for a specific location at a specific time, which may reduce the amount of SCAI. However, by including coverage information of a subset of both the location and time of the SCAI for the AMF (or MME), the UE SCAI may remain a subset of the SCAI for the AMF (or MME).

[0134] With regard to the content of SCAI, according to some embodiments and as previously described, satellite coverage availability may be indicated by a Boolean "true" or "false" value (e.g., as described for Figures 7A to 7C), which may be provided for a set of locations (e.g., within an AMF or MME area or within an area applicable to the UE) and for a time series. At a particular location and time, the indication may simply mean that the UE will be able (true) or unable (false) to access at least one satellite of a particular satellite RAT at that location and time. This would mean being covered by at least one satellite radio cell with sufficient signal power and quality at the particular location and time to be considered a "suitable cell" by the UE (e.g., as required in 3GPP TS 38.304 for NR or 3GPP TS 36.304 for LTE). Radio cells that cannot provide coverage to a particular location due to regulatory requirements (e.g., in the case where a radio cell unintentionally provides coverage to a non-allowed country) or PLMN restrictions (e.g., in the case where a radio cell does not support a particular serving PLMN or equivalent PLMN at a particular location) will have to be disregarded (e.g., ignored).

[0135] However, not all UEs may be equal in their minimum signal received power and quality requirements for selecting a "suitable cell". Differences may exist between different types of UEs, such as Very Small Aperture Terminals (VSATs) with small (and movable) dish antennas, handheld UEs (e.g., smartphones) with integrated antennas, and UEs in vehicles or within buildings with access to external (e.g., non-dish) antennas. These differences may affect cell selection for satellites with low elevation angles (e.g., 15 degrees or less), where low signal levels may allow some UEs access but not others.

[0136] Since access to a suitable cell may depend on the UE's receiver sensitivity including the UE antenna gain or loss, the SCAI true and false indications may assume a standard minimum receiver sensitivity for the UE, e.g. as defined in 3GPP TS 38.101-5 for NR and 3GPP TS 36.102 for LTE. Any deviation from this (e.g., for VSAT UEs) may be indicated by the UE's receiver and antenna gain or loss relative to the standard minimum sensitivity.

[0137] Alternatively or additionally, the SCAI may distinguish between (e.g., based on) one or more of the following UE parameters:

[0138] - UE type (e.g. VSAT, handheld UE with integrated antenna, other UE with external antenna)

[0139] -Antenna Rx gain (or loss)

[0140] - Overall UE receiver and antenna gain (or loss)

[0141] -The minimum received power (and quality) level supported by the UE

[0142] The SCAI provided to the AMF or MME (e.g. provided by the O and M servers) may then include SCAI for each of the different allowed values ​​of the above parameters, while the SCAI provided to a single UE (e.g. provided by the server or by the AMF or MME) will include SCAI only for specific parameter values ​​applicable to that UE.

[0143] Additionally or alternatively, providing the SCAI (e.g., from a server to a UE, AMF, or MME) may include providing an indication of the maximum signal power (and quality) of all satellite radio cells available at any location and time to provide coverage to that location at that time. The signal power (and quality) may be in terms of intensity (i.e., dBm per unit area of ​​power) or in terms of power received by an ideal isotropic antenna (dBm). This indication of maximum signal power (and quality) may be provided over the entire area at any particular time in the form of a heat map, where locations with the same maximum signal power (and quality) level will have a common value (or values), which may be visually represented by a unique shading and / or color on a map of that area. Multiple instances of such a heat map may be provided to the UE, AMF, or MME for a series of separate times. For the UE, a small map with an indication of power levels only for a particular location (and time) may be sufficient.

[0144] 7D shows an example visual representation of a heat map. In this example, a heat map of region 782 is illustrated for SVs 102, 202, 302. In the heat map, region 782 is divided into regions having high 784, medium 786, and low 788 maximum signal powers, respectively. Other heat maps may vary in the number of levels of values, allowing for a coarser or finer mapping of signal power, depending on the desired functionality.

[0145] For UEs, according to some embodiments, SCAI may be provided for known or expected UE trajectories. In limited degradation situations, when the UE is not expected to move beyond a certain maximum distance (e.g., 25km), the trajectory may become a single location. The initial location may be provided using full coordinates (e.g., latitude, longitude), and subsequent locations (when present) may be indicated as locations relative to the initial location. SCAI indications may then be provided for each location, and may be provided one or more times when the UE is expected to have been or may be present at that location.

[0146] In accordance with some embodiments, in order to indicate different locations on an area (e.g., for an AMF or MME or for a UE whose future mobility is unknown), a grid point method may be used in which the locations are indicated for a set of grid points in a rectangular or hexagonal array with equal spacing (e.g., as described with respect to Figures 7B and 7C).

[0147] FIG. 7E illustrates an example rectangular grid point array 790, and FIG. 7F illustrates an example hexagonal grid point array 795. A Boolean coverage availability indication or digital signal power indication may be provided to each grid point and may be calculated (e.g., by a server) to apply to only that location (option A) or to an area around the grid point ("grid point area") (option B). As an example, the digital signal power indication for a grid point may be set to the signal power at the grid point location (for option A) or to the minimum signal power of all locations in the grid point area (for option B). The Boolean coverage availability indication may similarly be set to true if and only if there is coverage at the grid point location (for option A) or at all locations in the grid point area (for option B).

[0148] According to some embodiments, a SCAI indication for a set of grid points may be provided for a time series with a fixed periodic interval. There may be a convention that the SCAI indication remains valid for some minimum portion of the time interval. For example, for the time series T0-T, T0, T0+T, T0+2T (where T is a periodic interval), the SCAI indication provided for T0 may be calculated to be applied to some portion (up to 100%) of time T0 or the time interval T0-0.5T to T0+0.5T at a minimum. The decoding of SCAI may be based on location and then on time, wherein SCAI indications are provided for all grid point locations at a specific time, and then the data is repeated for each continuous time. Alternatively, the decoding may be based on time and then on location, wherein the opposite convention is used. The entire SCAI may be encoded as a bit string using a single bit to represent a Boolean coverage availability indication and a binary value to represent a digital signal power indication. In some cases, the SCAI indication may remain the same for different locations for a long time. This is generally applicable when satellite access availability is low (e.g., less than 15% of the time) or high (e.g., greater than 85% of the time). For these cases, providing a SCAI indication for a time series with a fixed periodic interval will typically repeat much of the same data at each periodic time. In this case, a more efficient way to provide a SCAI indication may be to provide the SCAI indication along with the period for which the indication applies. For a particular location and N durations, this would result in a sequence of the following type:

[0149] <Initial Time> <n><SCAI Indication 1><Period 1> <SCAI Indication 2><Period 2> ....<SCAI Indication N><Period N>

[0150] The initial time can indicate the start time. Each period can indicate how long a particular SCAI indication is applied, where the start time of the period is equal to the initial time plus all previous periods. According to some embodiments, this can be encoded as a bit string and repeated for each grid point or each location.

[0151] Regarding the encoding of SCAI, different types of SCAI content as described above can be combined and then encoded in different ways. Three examples that can be used according to some embodiments are provided below. Assume these examples are used to provide SCAI to a UE, where the UE first indicates a plurality of parameters (referred to as input parameters) and parameter values to an SCAI source such as a server, and then the server transmits the SCAI applicable to the parameters and parameter values received from the UE. However, these examples can also be applied to providing SCAI to an MME or an AMF instead of a UE, where the MME or AMF provides the same parameters and parameter values (instead of the UE) and receives back the SCAI applicable to these parameters and parameter values.

[0152] The first example of SCAI encoding involves using grid points with a boolean coverage availability indication. In this example, the UE can first indicate the following "input parameters" to an SCAI source (e.g., an external server):

[0153] • A list of registered PLMNs and / or supported PLMNs (in cases where it is not known or implied);

[0154] • One or more satellite RATs (where satellite availability is then based on the radio cell availability of any RAT);

[0155] • A list of supported frequency bands (in cases where it is not implied by a particular RAT);

[0156] • The location (e.g., latitude and longitude) of a reference grid point (e.g., the most southerly and then the most westerly grid point);

[0157] • Grid point spacing;

[0158] • Start time, periodic time interval, number of periodic times;

[0159] • Array type (e.g., rectangular or hexagonal);

[0160] • The number of grid points (e.g., the total number or individual numbers in the north - south and east - west directions);

[0161] • The parameter of the minimum received signal power includes one or more of the following:

[0162] ○ UE type (e.g., VSAT, handheld UE with integrated antenna, other UE with external antenna);

[0163] o UE category (e.g. category M1 or category NB1 / NB2 for UEs with E-UTRA access);

[0164] ○UE antenna Rx gain (or loss);

[0165] ○ Relative to the minimum required UE receiver and antenna gain or loss (e.g. in 3GPP TS 38.101-5 or 3GPP TS 36.102);

[0166] ○ The minimum received power (and quality) level supported by the UE; or

[0167] ○A combination of them.

[0168] As described above, the AMF or MME may provide the same set of input parameters when requesting SCAI (e.g., from a server or using O and M), but these parameters may be provided separately for each satellite RAT, each frequency band, and for different received signal power parameters.

[0169] Note that the grid point spacing defines the north-south and east-west straight-line distances between adjacent pairs of grid points. Due to the curvature of the Earth, this distance can be measured on a great circle that can be a line of longitude for that distance in the north-south direction, and can be measured on a great circle at right angles to that distance in the east-west direction (which approximates a line of latitude at lower latitudes but deviates from that line of latitude at higher latitudes).

[0170] Input parameter values ​​may be restricted to reduce complexity. For example, the reference position may be quantized to exact degrees or exact half degrees of latitude and longitude; the grid point spacing may be restricted to, for example, 20km, 50km, 100km, or 200km; the start time may be the current time rounded to the next minute boundary; the time interval may be restricted to, for example, 30 seconds, 1 minute, 2 minutes, or 5 minutes; the number of times may be 100 times a certain power of 2; only rectangular arrays may be supported; the number of grid points may be restricted to squares with 1, 2×2, 3×3, 4×4, etc. grid points; and the minimum received signal power parameter may indicate only one of only a few values ​​for UE type, UE category, or receiver and antenna gain or loss.

[0171] Based on the above input parameters, the SCAI (e.g., from an external server) may be delivered to the requesting UE or requesting AMF or MME as a sequence of bit strings, where each bit string is for a separate time and includes one bit for each grid point in the grid point array, where a value of one indicates coverage and a value of zero indicates no coverage for the UE to which the above input parameters apply. There may be a fixed order of grid point inclusion (e.g., from west to east, then from south to north, starting at the reference grid point). This may result in a combined bit string containing only the SCAI Boolean indication, without the need for delimiters, length indications, or parameter type indications. In one example (referred to as "Example 1"), for a 2000 km x 2000 km square area containing 1600 grid points spaced 50 km apart and with a periodic time interval of 1 minute, the combined bit string size for 24 hours of data may have the following size:

[0172] SCAI size = (1600 × 24 × 60) digits

[0173] = 2.3 megabits or 288 kilobytes

[0174] This may be reasonable for the AMF or MME, although in some embodiments it may not be the case for the UE. In another example, for only one mesh point and a periodic time interval of 1 minute in 24 hours, the SCAI data size may be reduced to 180 octets, which may be small enough for one UE even using transport by SMS.

[0175] A second example of SCAI encoding involves using mesh points with a Boolean coverage availability indication and a duration indication. Based on input parameters, which may be the same as the input parameters of the first example of SCAI encoding described above, SCAI may be delivered as a sequence of durations for each mesh point, where each duration includes a Boolean indication of coverage availability or unavailability. When there are N durations (Duration 1, Duration 2, Duration 3, etc. to Duration N), for each mesh point, the output may look as follows:

[0176] Output = <n><binary 0 or 1><duration 1> <binary 0 or 1><duration 2> <binary 0 or 1><duration 3> ....<binary 0 or 1><duration N>

[0177] The above initial value ( <n>) provides the number of durations, and each duration (e.g., <duration n>) may be encoded as a fixed length bit string (e.g., 8 bits). The above output for only one grid point may then be concatenated for all grid points according to some defined ordering of the grid points to produce the complete SCAI as a combined bit string. For example 1 above, and assuming that the average duration is 15 minutes and that 2 octets are used to encode the number of durations N, and 1 octet is used to encode each duration, the total SCAI size may be:

[0178] SCAI size = 1600 × (16 + (24 × 60 / 15) × 9) bits

[0179] = 1.41 megabits or 176 kilobytes.

[0180] For only one grid point in this example, the SCAI data size can be reduced to 110 octets.

[0181] A third example of SCAI encoding involves using grid points or tracks with signal power and duration indication. For grid points, the input parameters may be described as above for the first example of SCAI encoding. For tracks (where it is assumed that the time and duration of the UE at each location may be unknown), the UE may indicate the following input parameters to the SCAI source (e.g., an external server):

[0182] • List of supported PLMNs (where this is not known or implied);

[0183] • One or more satellite RATs (satellite availability is then based on radio cell availability of any RAT);

[0184] • List of supported frequency bands (in case not implied by a specific RAT);

[0185] • Reference location (e.g., latitude and longitude at the start of the trajectory);

[0186] • an additional position of the trajectory (e.g., relative to a reference position or relative to a previous additional position);

[0187] •Start time and total duration;

[0188] • Parameters for minimum received signal power as in the first example of SCAI encoding.

[0189] The above input parameters may be restricted to reduce complexity, as in the first SCAI example described above.

[0190] Based on the above input requirements, SCAI shall be delivered (eg to UE, AMF or MME) as a sequence of durations for each grid point or each location on the trajectory, where each duration comprises a numerical signal power (and quality) level for a supported frequency band.

[0191] For each grid point or each location and in case of N durations, the SCAI output may be as follows:

[0192] Output = <n><Signal power / quality level><Duration 1> <Signal power / quality level><Duration 2> .... <Signal power / quality level><Duration N>

[0193] This output may be encoded as a bit string and concatenated over all grid points or all positions based on a defined ordering of the grid points or positions to produce the final SCAI.

[0194] For the grid point example in the second example of SCAI encoding, and assuming that the signal power / quality level can be encoded in 2 octets and the average duration is 10 minutes, the total SCAI size may be:

[0195] SCAI size = 1600 × (16 + (24 × 60 / 10) × 24) bits

[0196] = 5.56 megabits or 694 kilobits.

[0197] For just one grid point in this example, the SCAI data size would be reduced to 434 octets. For a 2000 km long track containing positions at 50 km intervals (hence containing 41 positions), the SCAI size could be 17.8 kilobytes.

[0198] The coverage map (or set of coverage maps) can be provided to the UE by a server via the user plane or short message service (SMS), or can be provided to the UE by the MME or AMF using NAS. Two alternative solutions can be used for this:

[0199] • The first solution (referred to as "Solution A") is based on an HTTPS or SMS query from the UE to the server. The UE may include authorization data with the query that is meaningful to the server and was previously provided to the UE by the serving PLMM, also referred to as the Registered PLMN (RPLMN).

[0200] • The second solution (referred to as "Solution B") is based on a simple NAS request / response (eg, as part of a NAS Attach, Tracking Area Update (TAU), or Registration).

[0201] For example, a coverage map (or set of maps) may be provided from a server to a UE 115 via a user plane (e.g., as described later in FIGS. 8A and 8B ) based on an HTTPS query from the UE 115 to the server. This may be supported by a visited PLMN (VPLMN), a home PLMN (HPLMN), or by a satellite operator. The UE 115 may also provide the server with a temporary identifier (ID) that is preconfigured in the server and verifies the permission (e.g., subscription) of the UE 115 to receive coverage data. After verifying the UE subscription or other permission to receive coverage data, the temporary ID may be assigned to the UE by the VPLMN or HPLMN. The temporary ID may be or look like a large random number (e.g., 128 bits) to ensure security.

[0202] In another specific implementation, satellite coverage data, for example in the form of coverage maps and / or time series, may be provided to the AMF 112 and / or gNB 106 / 202 / 307 (e.g., by the O and M servers). The AMF 112 or gNB 106 / 202 / 307 may then filter, reformat, or otherwise modify the satellite coverage data for easier and faster access (e.g., by the UE 115), which may reduce the total satellite coverage data size (e.g., in the case where the AMF 112 or gNB 106 / 202 / 307 removes data for certain locations and / or times in the satellite coverage data that are not needed by the UE 115). The AMF 112 or gNB 106 / 202 / 307 may then provide the filtered, reformatted, or otherwise modified satellite coverage data to the UE 115, for example, only for the current UE 115 location, for all locations in the vicinity of the UE 115, or for the entire serving PLMN coverage area (e.g., as described above). For example, the AMF 122 may provide satellite coverage data to the UE 115 using a non-access stratum (NAS) message (e.g., when the UE 115 performs a NAS registration with the AMF 122). The gNB 106 / 202 / 307 may also broadcast satellite coverage data (e.g., in one or more SIB messages) in each satellite cell to all UEs 115 that have access to the satellite cell. The broadcast satellite coverage data may be limited to providing coverage information only for locations within the current coverage area of ​​the satellite cell, or in an extreme variant, may provide satellite coverage data only for a single location that includes the current coverage area of ​​the satellite cell or for a center location of the coverage area. The coverage information provided using this extreme variant may be approximate, because not all locations within the current coverage area of ​​the satellite cell will necessarily receive the same satellite coverage at a future time. However, a convention may then be used according to which, in the event that at least a portion of the entire current coverage area of ​​the satellite cell (e.g., the center location) receives satellite coverage at any future time, coverage is indicated as being available for the entire current coverage area of ​​the satellite cell at that future time. A UE 115 utilizing satellite coverage data for this extreme variation may then realize that, even when its current location is within a location area where satellite coverage is indicated as available at a future time, coverage may not always be available at the current location at the future time.

[0203] As described above, satellite coverage data may be provided to the UE 115, which may include one or more coverage maps (e.g., each coverage map including a bitmap) and / or a time series indicating satellite coverage availability for one or more locations and / or for one or more times. For example, the AMF 122 may transmit to the UE 115 satellite coverage data (e.g., in the form of a bitmap or a time series) only for the current UE 115 location, which current location may be based on the current serving fixed cell of the UE 115 or the current TA in which the UE 115 is located (e.g., as indicated to the AMF 122 by the serving gNB 106 / 202 / 307 of the UE 115). Alternatively, the UE 115 may transmit to the serving AMF 122 a request (e.g., a NAS request message) indicating one or more locations and time periods for which the UE 115 requests satellite coverage data. The AMF 122 may then transmit to the UE 115 the satellite coverage data for the indicated locations and time periods (e.g., in a NAS response message). For example, AMF 122 may determine satellite coverage data based on more complete and comprehensive satellite coverage data (e.g., for the entire PLMN coverage area) received by AMF 122 from O and M servers or from gNB 106 / 202 / 307. UE 115 may use the satellite coverage data, its current location, and the current time to determine when UE 115 will be in coverage of a satellite cell and out of coverage of a satellite cell.

[0204] As discussed above, in the case of limited satellite deployment (e.g., initially), there may be times when no satellite coverage (e.g., no satellite cells) is available to the UE at any given geographic location, which may be referred to as "coverage gaps" or "unavailable periods". For some UEs (e.g., cellular IOT (CIoT)), the UE may transition to a dormant state during a coverage gap and may not attempt to find a cell or initiate a mobile originating (MO) service such as initiating a voice call or data session or transmitting data or text messages. When the UE is within a coverage gap, the network may similarly not attempt to initiate any mobile terminated (MT) services for the UE, such as not attempting to initiate a voice call or data session from an external entity to the UE, and not attempting to transmit data or text messages from an external entity (e.g., an external client 140) to the UE. For non-IOT UEs, the user of the UE may want to minimize the out-of-coverage period by finding and using other available terrestrial network (TN) cells or NTN cells for other NTN RATs or other PLMNs. In this case, transitioning to a full dormant state may not be appropriate. Furthermore, in the case where the UE is moving, the coverage gap at the old location may become irrelevant at the new location where the satellite (or satellite cell) is available again. For MT services and for a moving UE, the network may be able to reach the UE at the new location (where the satellite is available), so again, transitioning to a full dormant state (with respect to the UE) on the network side may also not be appropriate.

[0205] In some embodiments, an operations and maintenance (O and M) manager or server (e.g., belonging to a PLMN) may be preconfigured and transferred to other entities (e.g., gNB 106 / 202 / 307 and / or AMF 122) satellite coverage data showing times of NTN coverage and lack of coverage (e.g., times without NTN coverage) at different locations in the PLMN coverage area. The satellite coverage data may be as described with respect to FIGS. 7A to 7F.

[0206] In one embodiment, the gNB 106 / 202 / 307 that receives satellite coverage data from the O and M servers or calculates satellite coverage data from other data received from the O and M servers (e.g., satellite orbit or ephemeris data and data about satellite cells) may broadcast satellite coverage data in each cell for a location in the cell, as discussed with respect to Figures 7A to 7F. The UE 115 access layer (AS) may then determine a period of satellite unavailability at the UE 115 location based on the received broadcast satellite coverage data. During the period of satellite unavailability (e.g., during a no-coverage state), the AS layer may report a no-cell-available state to the NAS layer in the UE 115. The NAS layer may then change the NAS state of the UE 115 to indicate that wireless coverage is unavailable (e.g., may enter a NAS 5GMM-REGISTERED.NO-CELL-AVAILABLE state), which may also be supported for terrestrial wireless access when the UE 115 UE loses wireless coverage. The AS layer may reduce or stop cell search (e.g., reduce satellite cell search frequency or stop cell search) during the no-coverage period / state. The AS layer may optionally be configured to periodically search for NTN or TN cells before the next satellite cell available time to allow for possible UE 115 movement to new locations.

[0207] In some other embodiments, the UE 115 NAS layer may obtain and / or otherwise determine the time T1 at which satellite coverage at the UE 115 location will cease (e.g., during a no coverage state) and the time T2 at which satellite coverage will resume (e.g., during a covered state). The period starting at time T1 (which may be referred to as a start time) and ending at time T2 (which may be referred to as an end time) may be referred to as a coverage gap or unavailable period, the duration of which may generally be equal to T2-T1. For example, the network (e.g., serving AMF 122) may provide satellite coverage data to the UE 115 during UE registration and / or in other NAS responses if requested by the UE 115, and the UE 115 may then calculate T1 and T2. In another example, the network (e.g., serving AMF 122) may determine the values ​​of T1 and T2 and then provide these values ​​to the UE 115 during UE 115 registration and / or in other NAS responses. In yet another example, the serving gNB 106 / 202 / 307 may broadcast satellite coverage data or values ​​of T1 and T2 in the SIB in the satellite cell. The broadcasted satellite coverage data or values ​​of T1 and T2 may then be received by the UE 115 AS layer and provided by the UE 115 AS layer to the UE 115 NAS layer, for example, upon acquisition of the satellite cell or shortly thereafter (e.g., during a covered state). The UE 115 NAS layer may provide the values ​​of T1 and T2 to applications and / or to a user of the UE 115 to indicate future loss and later restoration of satellite coverage. At time T1 (e.g., upon expiration of a timer for T1 and upon commencement of a no-coverage state), the NAS layer may enter a no-coverage state (e.g., 5GMM-REGISTERED.NO-COVERAGE state), may deactivate the AS layer, and may start a timer that will expire at time T2. At time T2 (e.g., upon expiration of a timer for T2, which may occur when a covered state is restored), the NAS layer may reactivate the AS layer. In some embodiments, the network-side NAS layer (e.g., the NAS layer in the serving AMF 122) may also enter a no-coverage state with respect to the UE 115 at time T1, and may prohibit mobile station called (MT) activities of the UE 115 until time T2. In other embodiments and as described later herein in conjunction with FIG. 14, the UE may determine the times T1 and T2 based on coverage data received earlier from the network or from an external server, and may then report the times T1, T2, and / or durations T1-T2 to the network (e.g., to the UE's serving AMF or MME) using procedures that support reporting of unavailable periods caused by loss of satellite coverage or caused by other events such as a UE reboot or software upgrade.

[0208] The different types of satellite coverage data and their use described above in conjunction with Figures 7A to 7F may enable UE 115 to determine at what times (e.g., times T1 and T2) UE 115 will and will not be in coverage of a satellite cell that enables access to a serving PLMN. However, the satellite coverage data may not indicate whether and at what times and locations UE 115 may be in coverage of a satellite cell that does not support the serving PLMN but supports a PLMN different from the serving PLMN (e.g., the home PLMN of UE 115). Additionally, the satellite coverage data may not indicate whether and at what locations (and possibly at what times) UE 115 may be in coverage of a TN cell (e.g., a TN cell supporting 5G NR access to a terrestrial gNB or a TN cell supporting LTE access to a terrestrial ng-eNB or terrestrial gNB) of the serving PLMN (or another PLMN, such as the home PLMN of UE 115). Therefore, when UE 115 determines that satellite coverage is not available for the serving PLMN (e.g., when UE 115 enters a no-coverage state for the serving PLMN), UE 115 may not know whether to continue searching for satellite cells of another PLMN (e.g., home PLMN) and / or whether to search for TN cells. This lack of knowledge by UE 115 may result in unnecessary power consumption if UE 115 continues searching for satellite cells of another PLMN and / or TN cell and no satellite cells are found. This lack of knowledge by UE 115 may also result in UE 115 instead entering a dormant state during the no-coverage state of the serving PLMN (wherein UE 115 deactivates all satellite and TN cell searches), and UE 115 unnecessarily lacking PLMN access if satellite cells of another PLMN or TN cell become available to UE 115 during the no-coverage state or later.

[0209] For UEs 115 that are subscribed or configured to access or are only able to access the satellite cell of the serving PLMN (e.g., where the serving PLMN is the home PLMN of the UE 115 and the UE 115 does not support TN access), this may not be a problem, and the UE 115 may then enter a fully dormant state during the period of no satellite coverage for the serving PLMN. However, for UEs 115 that support roaming to other PLMNs using satellite access and / or support TN access, it may be advantageous if the UE 115 can know whether satellite access and / or terrestrial wireless access for other PLMNs is available when it is in a no coverage state for the serving PLMN.

[0210] Extensions to the above-described techniques for providing satellite coverage data to the UE 115 may be used to provide this additional information about satellite coverage availability and TN coverage availability for other PLMNs to the UE 115. In one such extension, additional coverage data (e.g., a coverage map, bitmap, or time series as described with respect to FIGS. 7A to 7F ) may be provided to the UE 115 by the serving PLMN (e.g., by the AMF 112, MME, or gNB 106 / 202 / 307) or by another entity (e.g., a server accessed by the UE 115 via the Internet, such as by the home PLMN, SVO, or by a vendor or OEM of the UE 115) for one or more other PLMNs and in the same or similar manner as satellite coverage data is provided for the serving PLMN. The additional coverage data may be supported as described with respect to FIGS. 7A to 7F , but instead of indicating satellite availability and unavailability at different locations and / or at different times for the serving PLMN, the additional coverage data may instead indicate satellite availability and unavailability at different locations and / or at different times for the one or more other PLMNs. In another extension, additional coverage data may be provided for terrestrial wireless access and may indicate TN cell availability and TN cell unavailability at different locations and / or at different times for the serving PLMN and / or one or more other PLMNs. Since terrestrial cells do not typically move (although they may sometimes be switched on and off), a coverage map for a TN cell may include a bit string or bit array, wherein each bit in the bit string or bit array corresponds to a specific location in an array of locations (e.g., a rectangular grid point array of locations) and indicates whether the TN cell is available at that location and at any time rather than just at one specific time. Similar to the coverage map for satellite access, such a coverage map for a TN cell may also be compressed when nearby locations tend to have the same coverage or no coverage attributes and therefore have the same bit values.

[0211] In one extension that provides additional coverage data for terrestrial access, a binary value (e.g., 1 or 0) may be provided for each location in the coverage map to indicate coverage (e.g., binary value "1") versus no coverage (e.g., binary value "0"). In another type of extension for providing additional coverage data for terrestrial access, a ternary or quaternary value may be provided in the coverage map instead of a binary value. For example, in the case of a ternary value, a value of "0" may indicate that TN coverage is not available, a value of "1" may indicate that TN coverage is available, and a value of "2" may indicate that TN coverage is available but not guaranteed. A third value of "2" may be used to indicate locations where TN coverage is sometimes available (e.g., depending on the exact location of UE 115) but not always available, which may be used in locations where TN coverage of the serving PLMN may be blocked by buildings, natural obstacles (e.g., mountains, trees) but is generally available if UE 115 has line of sight to a terrestrial base station or access point. For the quaternary values, "0", "1" and "2" may have the meanings just described, and may include a fourth value "3" to indicate locations where TN coverage may sometimes be available as for value "2" but with a lower (or higher) probability than value "2".

[0212] In another type of extension, additional coverage data may be provided as a single coverage map combining coverage indications of the serving PLMN and other PLMNs and / or combining coverage indications of both satellite access and terrestrial access. The single coverage map may provide a string or array of binary, ternary, quaternary (or value-added) parameters, wherein each parameter in the string or array indicates whether there is satellite and / or TN cell coverage for the serving PLMN and possibly additional PLMNs at a specific location and / or a specific time. For example, in the simplest example, a string or array of binary values ​​may be provided using a bitmap as described for Figures 7A to 7F. Then, a bit set to "0" may indicate that no coverage from a satellite cell or TN cell is available for a specific location and time, while a bit set to "1" may indicate that coverage from at least one of a satellite cell or TN cell is available for that time and location. In another example using quaternary values, a quaternary value provided for a particular location and time may indicate no satellite and no TN coverage for a value of "0", satellite but no TN coverage for a value of "1", TN but no satellite coverage for a value of "2", and both satellite and TN coverage for a value of "3". A string or array of quaternary values ​​may also be encoded as a bit string or array by using 2 bits to encode each quaternary value. Such a bit string or array may then also be compressed when values ​​for nearby locations and / or times tend to be the same.

[0213] The above-described extensions for providing additional (satellite and / or terrestrial) coverage data for TN cells and / or other PLMNs to UE 115 may allow UE 115 to modify support for coverage gaps and satellite coverage such that UE 115 may access a satellite cell of another PLMN or TN cell during a (satellite) coverage gap for a serving PLMN and not expend power searching for other satellite cells or TN cells when no other satellite cells or TN cells are available.

[0214] In another specific implementation, the satellite coverage data may be provided to the UE 115 from a server. For example, the coverage information may be considered a network resource and accessed by the UE 115 using an address (such as a URI) for the server obtained by the UE 115 from a network entity (e.g., AMF 122, MME, or gNB 106 / 202 / 307). The UE 115 may then access the server based on the address to obtain the coverage information. For example, the UE 115 may transmit an HTTP or HTTPS (or other data) request to the server identified by the address. The request transmitted by the UE 115 to the server may indicate one or more input parameters that may be used to identify the requested information (e.g., as described above for the three SCAI examples). For example, the UE 115 may indicate the location of the requested coverage information or the area of ​​the requested coverage information, such as the radius of a circle centered at the location or the length and width of a rectangle associated with the location. The UE 115 may indicate the relevant time of the requested coverage information, such as the start time and the stop time. The UE 115 may indicate the relevant RAT and / or PLMN for the requested coverage information. UE 115 may indicate supported methods or encodings for receiving coverage information from the server. The server may identify the address association with the coverage data and return the requested coverage information to UE 115.

[0215] The server may belong to the serving PLMN or home PLMN (HPLMN) (e.g., when the UE is roaming) or to a separate third party, such as a space vehicle operator (SVO). The benefits of using an SVO server rather than a PLMN server to provide coverage data may be that: (a) there is no need to transfer the coverage map data to a PLMN (or multiple PLMNs), and (b) the SVO server will receive each request directly and can therefore charge for data more reliably. For example, in a scenario where one SVO supports 100 PLMNs, instead of transferring some or all of its coverage map data to each of the 100 separate PLMNs, the SVO may assign a URI ID to each PLMN and maintain a single server to provide coverage data on behalf of all 100 PLMNs. Thus, the total implementation cost of one server for the SVO may be reduced by up to 100 times compared to 100 separate servers for each of the 100 PLMNs.

[0216] The address (e.g., URI) of the server may be provided to the UE 115 by a network entity, such as in the HPLMN or VPLMN. The address may have limited use, such as the address may be used only once by the UE to request coverage data, or may be used multiple times within a limited period, and / or may be used for a maximum number of requests, or may be used indefinitely. The address may be provided to the UE 115 by the network entity using NAS (e.g., via a registration request and accept message), where the UE 115 may indicate in the NAS request one or more of the input parameters that may be used to identify the requested SCAI, as discussed above, to allow the network entity to select a server and address that may support these input parameters. The address may alternatively be provided to the UE 115 using an RRC unicast request / response or in a SIB (e.g., which may be encrypted to allow charging for configuration data), or the address may be provided by the HPLMN operator via pre-configuration on a Universal Subscriber Identity Module (USIM) of the UE 115.

[0217] It may be desirable to transfer coverage information in a secure manner that can protect UE privacy and that can allow for billing of coverage data. Coverage information may be transferred in a secure manner because a network entity in the serving or home PLMN provides an address and HTTPS may be used by the UE 115 to request and obtain coverage data. For billing of coverage data, an address (e.g., a URI) may need to identify the UE 115, but for possible privacy reasons, it may not be desirable to provide the real UE identity (e.g., a subscription permanent identifier (SUPI)) to the server. To achieve this, a temporary identifier may be assigned to the UE 115. For example, an address (e.g., a URI) may be assigned to a UE or a group of UEs having a random component (e.g., 128 or 256 random bits) in the least significant portion. In a variation, the random component may not be part of the address, but may be provided as a separate input parameter. The address (or random component) may be preconfigured in the server and the network entity (e.g., AMF or gNB) that provides the address. The server may record the use of the address or random component (e.g., the server records the address when receiving a request for coverage data from the UE). The network entity that provides the address also records the identity of the UE to which the address (or random component) was provided. The record can be evaluated offline, for example, by a network entity, a server, or a third-party charging entity to determine the address (or random component) provision to the UE and the UE's use. The random component can be used as a temporary identifier for the UE.

[0218] To avoid the need to preconfigure millions of addresses or random components at the server and network entity, the server and network entity may agree on a simple set of identifiers (e.g., a regularly spaced sequence of numbers such as (decimal) 1,000,000,000, 1,000,001,000, 1,000,002,000, 1,000,003,000, 1,000,004,000, 1,000,005,000, etc.), and encryption may be used to generate and verify temporary identifiers. The network entity may, for example, select a hitherto unused identifier from the set of identifiers for the UE (e.g., 1,000,004,000 in the above example), and may encrypt the identifier using a secret encryption key to generate a random component, which is then transmitted by the UE to the server. The server uses the same encryption key to decrypt the random component to obtain an initial identifier (e.g., 1,000,004,000 in this example), which can then be verified as legitimate if the initial identifier belongs to a set of identifiers. For example, an unauthorized UE that attempts to request SCAI from a server by providing a random component that was not legally obtained and decrypted by the server to produce a value that does not belong to the set of identifiers (e.g., the value 1,000,003,107 in the previous example) can be identified by the server as unauthorized to receive SCAI. The server and network entities can record the assignment and use of identifiers for billing purposes. Using encrypted temporary identifiers for UEs can achieve security, privacy, and the ability to charge for access to coverage data. For example, when the number of bits is about 128 or more, an attacker cannot guess a valid random component with any probability of success. In the event that the UE is lost or the user discloses the address and temporary identifier, other parties may benefit, but this is no different from the user giving away any other valuable item and does not need to affect billing.

[0219] The security of a server address (e.g., URI) can be enabled by a very large number of possible random components. In the case where the random component contains 128 bits, this number can be about 10 38 . Assume that 1 trillion (10 12 ) are reserved for coverage data provision, the probability that an attacker correctly guesses one of these reserved components (and thereby enables free access to the coverage data) will be 1 / 10 26 , which is a very low probability. Using encryption to determine the random component avoids having to assign and store the random component separately through some other process (e.g., using a random number generator). Instead, a secret key is used to generate the random component as needed, and an ID selected from a preconfigured sequence of integers (e.g., all integers between 1 and 1 trillion or all integers between 1 and 1 trillion multiplied by 1 trillion) is encrypted. In the event that the key is discovered in some way, the operator can change it. In the event that the coverage data itself is not considered sensitive (e.g., the coverage data will not include user or UE information), there may be no significant loss except for the operator losing a small amount of revenue before changing the key.

[0220] Data, such as the coverage data illustrated in the coverage diagrams illustrated in Figures 7A to 7F, may be obtained by the UE 115 using a query to a server. The procedure by which the UE 115 obtains the data may have two parts. First, the UE 115 obtains authorization data. The UE 115 then transmits a request (e.g., via HTTPS or SMS) to the server including the authorization data. The authorization data may be part of the address (URI) or may be a separate input parameter (e.g., in the body of an SMS message). In the case where billing will not be used (e.g., coverage data is available to all UEs without billing), the first part of the procedure may be omitted and the UE may construct a standard address (URI) associated with any serving PLMN (e.g., a VPLMN or HPLMN).

[0221] 8A and 8B together illustrate a procedure for a UE 115 to obtain coverage data from a server 187 based on authorization data obtained by the UE 115 according to various aspects of the present disclosure, wherein the first part is illustrated by the procedure 800 in FIG. 8A and the second part is illustrated by the procedure 850 in FIG. 8B. This corresponds to the aforementioned solution A. FIG. 8A shows a first procedure 800 for a 5G system (5GS). The procedure for EPS may similarly use NAS attachment or NAS tracking area update (TAU) instead of NAS registration. The procedure illustrated in FIG. 8A is based on NAS, but some other protocol layers, such as RRC, may also be used. Various aspects of the procedure 800 may be implemented by or at the communication systems 100, 200, 300, 400, 500, 600, and / or 700. Various aspects of the procedure 800 may be implemented by or at the UE 115 and / or the network entity 185, which may be examples of corresponding devices described herein. For example, the network entity 185 may include one or more entities within the core network, such as AMF 122, LMF 124, SMF 134, or MME, or may be a base station such as gNB 106 / 202 / 307, which may be separate from SV 102 / 202 / 302 or may be included as part of SV 202 as described above. The operations within the procedures in Figures 8A to 8C are shown as numbers and are referred to herein as phases (which may or may not be individually labeled in the figures). This convention is also used in other figures described below.

[0222] The coverage data transferred from the server 187 to the UE 115 may be coverage data that enables the UE 115 to determine whether the serving PLMN can be accessed at one or more locations of the UE, at one or more future times, using one or more radio access technologies (RATs), or for some combination of these. For example, the serving PLMN may have discontinuous satellite coverage, and the coverage data may include coverage data for one or more satellite RATs. The coverage data may additionally or alternatively apply to the TN RAT. In some specific implementations, the coverage data transferred from the server 187 to the UE 115 may be data other than coverage data. For example, for Figures 7A to 7F and for the first, second, and third SCAI examples, the coverage data may be as described above.

[0223] The procedure 800 shown in FIG. 8A may start with UE 115 being in satellite coverage of a serving PLMN. For example, UE 115 may be located within the coverage area of ​​at least one satellite cell supported by SV 102 / 202 / 302, as previously described. Note that references to serving PLMNs herein may correspond to private wireless networks (non-public wireless networks) and / or networks that provide Internet access and / or other satellite services in some cases. In addition, the UE may send and receive signals from the serving PLMN and / or otherwise access the serving PLMN via a communication satellite (e.g., SV 102 / 202 / 302 and NTN gateway 104). Thus, UE 115 may establish a connection with the serving PLMN (e.g., with network entity 185), or may already have a connection with the serving PLMN in order to perform wireless communications via SV 102 / 202 / 302. For example, UE 115 may perform an initial registration procedure with a serving PLMN (e.g., with network entity 185) via SV 102 / 202 / 302, NTN gateway 104, and gNB 106 / 202 / 307.

[0224] At 805, the UE 115 may transmit a request for coverage data to the network entity 185. In one implementation, the UE 115 transmits a registration request (e.g., for initial registration, periodic registration, or registration update) to the network entity 185 (e.g., the serving AMF 122) and includes a request for provision of coverage data from the server 187 (shown in FIG. 8B ) and whether HTTPS or SMS is preferred. In some implementations, the UE 115 may transmit the request using an RRC unicast request. The request may indicate, for example, one or more input parameters that may assist the network entity 185 in selecting an address of the server 187 to provide coverage data (e.g., as described above for the first, second, and third SCAI examples). Input parameters may be included to indicate the type of coverage data desired (e.g., one or more RATs) as well as applicable location, time, and satellite RAT. For example, the request may indicate one or more coverage parameters, such as the location for which the coverage information is requested, the area for which the coverage information is requested (such as the radius of a circle centered at the location, or the length and width of a rectangle associated with the location), the relevant time for which the coverage information is requested (such as a start time and a stop time), the relevant RAT and / or PLMN for the requested coverage information, and supported methods or encodings for receiving coverage information from the server.

[0225] At 810, the network entity 185 (e.g., the serving AMF 122) may authenticate the UE 115 and may verify that the UE is subscribed to receive coverage data (of the requested type and / or the requested location) and whether the requested location is supported (e.g., in a country supported by the AMF 122).

[0226] At 820, the network entity 185 (e.g., the serving AMF 122) determines (i) a server of the type applicable to the coverage data and location, and (ii) authorization data. The authorization data may be a text string address (URI) of the server or the content of an SMS message to be transmitted to the server. The authorization data may include a temporary identifier (ID) of the UE 115 and, optionally, details of the request received at step 1 (e.g., may indicate applicable location, time, and satellite RAT). In the case where the authorization data includes a temporary ID, the temporary ID may be assumed to have been pre-configured in the server 187 and pre-agreed between the serving PLMN (e.g., the network entity 185) and the server 187 when the server 187 is managed by another party (e.g., SVO). Thus, the temporary ID may be, for example, a reserved value pre-defined in the network entity 185 and the server 187. The temporary ID may be a large random number or pseudo-random number (e.g., 128 bits) having a set of (pseudo) random numbers pre-configured in the server 187 and in the serving PLMN (e.g., the network entity 185). Such randomization may make it nearly impossible for an unsubscribed UE to guess a valid temporary ID. In some implementations, the temporary ID may be encrypted (e.g., as described above). A pseudo-random temporary ID may be generated by encrypting a regular ID series (e.g., integers 1, 2, 3, 4, 5, etc.) using a secret encryption key known only to the serving PLMN and the server. For example, the network entity 185 and the server 187 may be preconfigured with a common set of identifiers and encryption keys. The network entity 185 may select one of these identifiers (e.g., a previously unused identifier) ​​from the set of identifiers of the UE 115, and may encrypt the identifier using the encryption key to generate a temporary identifier for the UE 115. The server 187 may later use the encryption key to decrypt the temporary identifier of the UE 115 to obtain an identifier selected by the network entity 185 (in process 850). The temporary identifier may be part of the address of the server 187. For example, the temporary ID may be appended to the address (URI) as an extension of the URI.

[0227] At 825, the network entity 185 (e.g., the serving AMF 122) may return the authorization data in the Registration Accept and, in the case of SMS, the SMS address of the server. In some implementations, the network entity 185 may provide the authorization data to the UE 115 using an RRC unicast response or in a SIB (e.g., which may be encrypted). The network entity 185 (e.g., the serving AMF 122) may also indicate usage restrictions on the authorization data, such as a maximum number of requests to the server or a maximum duration of use.

[0228] In some implementations, instead of receiving authorization data from the network entity 185, the UE 115 may obtain the authorization data without assistance from the network entity 185, thereby eliminating the need for stages 805, 810, 820, and 825 that may be used when a standard URI is used and charging is not applicable. For example, the UE 115 may obtain the authorization data from a USIM on the UE 115, which may be configured by the home PLMN of the UE 115 or by assembling a standardized address or a standardized temporary identifier. For example, the UE 115 may assemble the standardized address as "nameofdata.mnc <mnc>.mcc <mcc>.3gppnetwork.org", where <mnc>and <mcc>is replaced by the Mobile Country Code (MCC) and Mobile Network Code (MNC) numbers used for the serving PLMN, and "nameofdata" represents some fixed alphanumeric name standardized for the coverage type such as "satellitecoveragedata". Standardized temporary identifiers may be compiled in a similar manner.

[0229] FIG8B shows a second procedure 850, which may be the same for both 5GS and EPS. The procedure 850 shown in FIG8B may start after the UE 115 has obtained the address and temporary identifier of the server as discussed in FIG8A. Various aspects of the procedure 850 may be implemented by or at the communication systems 100, 200, 300, 400, 500, 600, and / or 700. Various aspects of the procedure 850 may be implemented by or at the UE 115 and / or server 187, which may be examples of corresponding devices described herein. For example, the server 187 may, for example, belong to the serving PLMN (e.g., VPLMN or HPLMN) of the UE 115, to a satellite operator (e.g., SVO) that provides access to the serving PLMN, or to a separate third party.

[0230] At 855, the UE 115 uses the authorization data received in the first procedure 800 to access the server 187. For example, as illustrated at 855, the UE 115 transmits an HTTP or HTTPS request (e.g., HTTPS GET) to the server 187 with a URI equal to the authorization data obtained in the first procedure 800, or transmits an SMS message with the authorization data in the SMS message body using the SMS destination address received in the first procedure. The request (HTTPS request) or SMS message may not need to include any additional data, because the authorization data may already include all data required by the server 187 (e.g., all input parameters). This may avoid any need for the UE 115 to have to support a proprietary server protocol related to the request or to standardize such a protocol. However, in another embodiment, the UE 115 may include input parameters in the HTTP or HTTPS request or in the SMS message transmitted at 855, such as those described above for the first, second, and third SCAI examples, and define the type of coverage data requested (e.g., such as applicable satellite RAT, location, and time). In this embodiment, the authorization data provided by the network entity 185 in the procedure 800 may not need to include any input parameters.

[0231] At 860, the server 187 verifies that the authorization data is valid (e.g., contains a valid temporary ID and satisfies any restrictions on the number of requests or request period) and records the details of the request. For example, as discussed in 820 of the procedure 800 shown in FIG. 8A, the authorization data may include a temporary ID of the UE 115 known to both the network entity 185 and the server 187. The temporary ID may, for example, be a reserved value predefined in the network entity 185 and the server 187. In some specific implementations, the temporary ID may be encrypted. For example, the network entity 185 and the server 187 may be preconfigured with a common temporary ID and encryption key. The server 187 may decrypt the temporary ID received from the UE 115 using the encryption key to obtain an initial temporary ID selected by the network entity 185, and may verify that the initial temporary ID belongs to a preconfigured common temporary ID. The temporary ID of the UE 115 may allow the UE 115 to access the server 187 and obtain coverage data therefrom under limited circumstances. For example, UE 115 may access server 187 and obtain coverage data a limited number of times, or obtain coverage data within a limited amount of time, or both. Server 187 may verify that the temporary ID does not exceed any such limits.

[0232] At 865, the server 187 returns the requested coverage data to the UE 115 in accordance with the request at 855. The returned coverage data may use an encoding known to both the UE and the server. For example, the coverage data may be provided in an HTTP or HTTPS 200OK message or an SMS message from the server 187. The coverage data may enable the UE 115 to determine whether the serving PLMN can be accessed at one or more locations of the UE, at one or more future times, using one or more radio access technologies (RATs), or for a certain combination of these, as described above. For example, the serving PLMN may have discontinuous satellite coverage, and the coverage data may include coverage data for one or more satellite RATs and may optionally apply to the TN RAT. In some implementations, the coverage data transferred from the server 187 to the UE 115 at 865 may be or may include data other than the coverage data.

[0233] To support charging and billing of UEs, the billing center may collect records of authorization data (e.g., the temporary ID assigned from the network entity 185 (e.g., AMF 122) and the corresponding UE identity and the temporary ID used to request coverage data from the server 187). This may allow the precise coverage data provided to each UE to be determined and billed.

[0234] Figure 8C shows the NAS procedure for obtaining coverage data for 5GS. The procedure for EPS can similarly use attachment or TAU. This procedure corresponds to the aforementioned solution B.

[0235] At 875, the UE 115 may transmit a NAS registration request (e.g., for an initial registration, a periodic registration, or a registration update) to a network entity 185 such as the serving AMF 122 and may include a request to provide coverage data. Additional input parameters may be included to indicate applicable location, time, and satellite RAT, such as those previously described for the first, second, and third SCAI examples.

[0236] At 880 , the network entity 185 may verify the UE subscription to receive coverage data and whether the requested input parameters (eg, location and time) may be supported (eg, in countries supported by the network entity 185 ).

[0237] At 885, the network entity 185 returns the requested coverage data in a NAS Registration Accept. The network entity 185 may obtain the coverage data from pre-configured data in the network entity 185, which may not require any interpretation or significant processing by the network entity 185 in the case where the coverage data is configured in the network entity 185 only for a limited set of locations and a small set of selected durations. Alternatively, the network entity 185 may transmit the request from the UE 115 to the server (e.g., using procedure 850 in FIG. 8B , where the network entity 185 acts as the UE 115 in procedure 850) and include the returned coverage data at 885.

[0238] The procedure shown in FIG. 8C may be similar to the procedure shown in FIG. 8A , except that coverage data is returned instead of authorization data. This may allow the serving PLMN to support either or both procedures based on a common request / response from / to UE 115. For example, UE 115 may indicate in a NAS registration request which procedure(s) the UE 115 supports, and then network entity 185 may attempt to match the UE support. Conflicts may only occur if UE 115 and network entity 185 each only support one procedure that is different from each other. This may avoid conflicts if one of the procedures is defined as a common mandatory default.

[0239] Compared to providing satellite orbit data using SIBs (e.g., as in SIB32 in 3GPP TS 36.331), the coverage map defined herein may have several advantages. For example, with a coverage map, the UE may not need to perform any complex calculations to determine the expected coverage, and may simply look up its current position and time in the coverage data map to see if there is coverage. The coverage data may also be prepared in advance (e.g., by a satellite operator or server) using complete and accurate knowledge of satellite orbit data and radio cell planning, and may therefore be more reliable than coverage data extrapolated by the UE from orbit data parameters. Coverage data for any period of time (e.g., 24 hours or 1 week or longer) may also be provided. In addition, the coverage data may be more complete. For example, SIB32 as defined in 3GPP TS 36.331 may include ephemeris data for only 4 satellites. It may then be the case that a UE close to a radio cell border may receive coverage from satellites not included in SIB32, or that satellites included in SIB32 that should be visible to the UE do not provide coverage to the UE due to restrictions on PLMN or country support or because the radio cell is not configured for the entire visible area of ​​the satellite.

[0240] In addition, the procedures 800 and 850 of Figures 8A and 8B for obtaining coverage data using HTTPS or SMS queries to a server can have many benefits. For example, these procedures allow the use of a server from a satellite operator that can avoid affecting the PLMN in determining coverage data and providing coverage data to the UE. The procedures can also support charging and billing for coverage data and secure transfer of coverage data. The procedures can also support UEs with and without an IP protocol stack, such as when the UE does not support HTTP and IP, by using SMS in procedure 850.

[0241] The procedure 870 of FIG. 8C for obtaining coverage data using NAS may have many benefits. For example, this may reduce the signaling impact on the UE as an extension of the existing NAS registration procedure for 5GS access and the existing NAS attachment and TAU procedures for EPS access. The procedure 870 may also support charging for coverage data and secure transfer of coverage data.

[0242] FIG. 9 illustrates a procedure 900 for charging a UE 115 for accessing and obtaining coverage data. As illustrated, after a server 187 receives a request for coverage data including an identifier of the UE (e.g., as at 855 in FIG. 8B ) (e.g., a temporary identifier) ​​from a UE 115, the server 187 records the identifier and provides the identifier to a charging entity 910 along with possible details of the coverage data provided to the UE 115 (e.g., at 865 in FIG. 8B ). The charging entity 910 may belong to the serving PLMN or may belong to a third party. The network entity 185 that determines the identifier and provides it to the UE 115 (e.g., as at 820 and 825 in FIG. 8A ) provides the same identifier of the UE 115 and a permanent identifier (e.g., SUPI) (e.g., their association) to the charging entity 910. The charging entity 910 may then identify the UE 115 that accessed the server 187 and obtained coverage data therefrom (using the association of the identifier and the permanent identifier) ​​and charge the UE 115 accordingly.

[0243] FIG. 10 is a diagram illustrating an example of a hardware implementation of a UE 1000, such as the UE 115 shown in FIG. 1 , FIG. 2 , and FIG. 3 , FIG. 7A , FIG. 8A , FIG. 8B , FIG. 8C , and FIG. 16 . The UE 1000 may be configured to perform the signal flows shown in FIG. 8A , FIG. 8B , and FIG. 8C , and any of the method 1500 of FIG. 15 , and the techniques disclosed herein. The UE 1000 may include, for example, a hardware component for wirelessly communicating with a SV 102 / 202 / 302 via a wireless antenna (not shown in FIG. 10 ), such as a satellite transceiver 1003 , for example, as shown in FIG. 1 , FIG. 2 , and FIG. 3 . The UE 1000 may also include a wireless transceiver 1002 for wirelessly communicating with a ground base station (e.g., a base station, such as a gNB or ng-eNB) in the NG-RAN 112 via a wireless antenna (not shown in FIG. 10 ). UE 1000 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 SPS SV 190 (shown in Figures 1, 2, and 3) via a wireless antenna (not shown in Figure 10). In some specific implementations, UE 1000 may receive data from a satellite, for example, via a satellite transceiver 1003, and may respond to a ground base station, for example, via a wireless transceiver 1002 or via a WLAN transceiver 1006. Thus, UE 1000 may include one or more transmitters, one or more receivers, or both, and these may be integrated, discrete, or a combination of both. UE 1000 may also include one or more sensors 1010, such as a camera, an accelerometer, a gyroscope, an electronic compass, a magnetometer, a barometer, etc. UE 1000 may also include a user interface 1012 through which a user may interface with UE 1000, which may include, for example, a display, a keypad, or other input device (such as a virtual keypad on a display). UE 1000 also includes one or more processors 1004, a memory 1016, and a non-transitory computer-readable medium 1018, which may be coupled together using a bus 1014. One or more processors 1004 and other components of UE 1000 may be similarly coupled together using bus 1014, a separate bus, or may be directly connected together, or coupled using a combination of the foregoing.

[0244] The one or more processors 1004 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 1004 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 1020 on a non-transitory computer-readable medium such as the medium 1018 and / or the memory 1016. In some embodiments, the 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 computing procedure or process related to the operation of the UE 1000.

[0245] The medium 1018 and / or the memory 1016 may store instructions or program codes 1020 containing executable codes or software instructions that, when executed by one or more processors 1004, cause the one or more processors 1004 to operate as a special-purpose computer programmed to perform the techniques disclosed herein (e.g., such as the signal flows shown in Figures 8A, 8B, and 8C and the method 1500 of Figure 15 and the algorithms disclosed herein). As illustrated by the UE 1000, the medium 1018 and / or the memory 1016 may include one or more components or modules that may be implemented by one or more processors 1004 to perform the methodologies described herein. Although each component or module is illustrated as software in the medium 1018 that can be executed by one or more processors 1004, it should be understood that each component or module may be stored in the memory 1016 or may be dedicated hardware in or outside of the one or more processors 1004.

[0246] Several software modules and data tables may reside in the medium 1018 and / or memory 1016 and be utilized by the one or more processors 1004 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of the medium 1018 and / or memory 1016 as shown by the UE 1000 is exemplary only, and thus the functionality of the modules and / or data structures may be combined, separated and / or configured in different ways depending on the specific implementation of the UE 1000. Although the components or modules are illustrated as software in the medium 1018 and / or memory 1016 that can be executed by the one or more processors 1004, it should be understood that the components or modules may be firmware or dedicated hardware in or outside of the one or more processors 1004.

[0247] As illustrated, program code 1020 stored on medium 1018 and / or memory 1016 may include a PLMN access module 1022, which, when implemented by one or more processors 1004, configures one or more processors 1004 to receive and send wireless signals via wireless transceiver 1002 or satellite transceiver 1003 to access a PLMN, such as 5GCN 110 shown in Figures 1 to 3. One or more processors 1004, for example, may be configured to access a PLMN and request, receive, and use coverage data.

[0248] As illustrated, program code 1020 stored on medium 1018 and / or memory 1016 may include a data access module 1024 that, when implemented by one or more processors 1004, configures one or more processors 1004 to request and receive coverage data from a network entity or server, as described herein and particularly with respect to Figures 8A, 8B, and 8C.

[0249] As illustrated, program code 1020 stored on medium 1018 and / or memory 1016 may include an unavailability reporting module 1026, which, when implemented by one or more processors 1004, configures one or more processors 1004 to report an upcoming unavailability period and / or the end of an unavailability period to a network entity, as described herein and particularly with respect to FIG. 14 .

[0250] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 1004 may 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 combinations thereof.

[0251] For specific implementations of UE 1000 involving firmware and / or software, these methodologies can be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software codes can be stored in medium 1018 or memory 1016 and executed by one or more processors 1004, so that one or more processors 1004 operate as a dedicated computer programmed to perform the techniques disclosed herein. Memory can be implemented within one or more processors 1004 or external to one or more processors 1004. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which the memory is stored.

[0252] In the case of implementation in firmware and / or software, the functions performed by UE 1000 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as medium 1018 or memory 1016). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. The combination of the above should also be included in the scope of computer-readable media.

[0253] In addition to being stored on a computer-readable storage medium, instructions and / or data for UE 1000 may also be provided as a signal on a transmission medium included in a communication device. For example, a communication device including part or all of UE 1000 may include a transceiver having a signal indicating instructions and data. These instructions and data are stored on a non-transitory computer-readable medium 1018 or a memory 1016, and are 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 a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.

[0254] 11 is a diagram illustrating an example of a hardware implementation of a network entity 1100 that may correspond to the network entity 185 illustrated in FIGS. 8A , 8C and 9 . The network entity 1100 may be, for example, one or more entities within the core network, such as AMF 122, SMF 134, LMF 124, or MME, or may be a base station such as gNB 106 / 202 / 307, which may be separate from SV 102 / 202 / 302 or may be included as part of SV 202 as described above. The network entity 1100 may execute the signal flows illustrated in FIGS. 8A , 8C and 16 , the method 1600 of FIG. 16 , and the algorithm disclosed herein. The network entity 1100 may include, for example, hardware components such as an external interface 1102, which may include one or more wired and / or wireless interfaces that can be connected to and communicate with the UE 115 directly or through one or more intermediate networks and / or one or more network entities, and connected to and communicate with one or more entities in the core network in the PLMN (such as the AMF 122, NTN gateway 104 and other gNBs in the 5GCN 110), and connected to other elements in the wireless network, as shown in Figures 1, 2 and 3. The external interface 1102 may include one or more antennas to support the wireless interface and / or wireless backhaul to elements in the wireless network. The network entity 1100 also includes one or more processors 1104, a memory 1116 and a non-transitory computer-readable medium 1118, which can be coupled together using a bus 1107. The network entity 1100 may include a gNB-DU 1112 and / or a gNB-CU 1114, which may be hardware components or implemented by one or more specially configured processors 1104 (e.g., in the case where the network entity 1100 corresponds to the gNB 202 in FIG. 2 and the gNB 202 includes a gNB-CU and one or more gNB-DUs). When the network entity 1100 itself corresponds to a gNB-DU (e.g., gNB-DU 302) or a gNB-CU (e.g., gNB-CU 307) or corresponds to a core network entity (such as AMF 122, LMF 124, or MME), the gNB-DU 1112 and the gNB-CU 1114 may not be present.

[0255] The one or more processors 1104 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 1104 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 1120 on a non-transitory computer-readable medium such as the medium 1118 and / or the memory 1116. In some embodiments, the 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 computing procedure or process related to the operation of the network entity 1100.

[0256] The medium 1118 and / or the memory 1116 may store instructions or program code 1120 containing executable code or software instructions that, when executed by one or more processors 1104, cause the one or more processors 1104 to operate as a special-purpose computer programmed to perform the techniques disclosed herein (e.g., such as the signal flows illustrated in FIG. 8A , FIG. 8B , and FIG. 12 , and the method 1600 of FIG. 16 , and the algorithms disclosed herein). As illustrated in the network entity 1100 , the medium 1118 and / or the memory 1116 may include one or more components or modules that may be implemented by one or more processors 1104 to perform the methodologies described herein. Although each component or module is illustrated as software in the medium 1118 that is executable by one or more processors 1104 , it should be understood that each component or module may be stored in the memory 1116 or may be dedicated hardware in or outside of the one or more processors 1104 .

[0257] Several software modules and data tables may reside in the media 1118 and / or memory 1116 and be utilized by the one or more processors 1104 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of the media 1118 and / or memory 1116 as shown for the network entity 1100 is exemplary only, and thus the functionality of the various modules and / or data structures may be combined, separated, and / or configured in different ways depending on the specific implementation of the network entity 1100. Although the various components or modules are illustrated as software in the media 1118 and / or memory 1116 that can be executed by the one or more processors 1104, it should be understood that the various components or modules may be firmware or dedicated hardware in the one or more processors 1104 or external to the processors.

[0258] As illustrated, program code 1120 stored on medium 1118 and / or memory 1116 may include a data access module 1122, which, when implemented by one or more processors 1104, configures one or more processors 1104 to support providing coverage data from a server or from a network entity 1100 to a UE, as described herein and in particular with respect to Figures 8A, 8B, 8C, and 9.

[0259] As illustrated, program code 1120 stored on medium 1118 and / or memory 1116 may include an unavailability reporting module 1124, which, when implemented by one or more processors 1104, configures one or more processors 1104 to support receiving reports from a UE regarding periods of unavailability of the UE, as described herein and particularly with respect to FIG. 14 .

[0260] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 1104 may 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 combinations thereof.

[0261] For specific implementations of the network entity 1100 involving firmware and / or software, these methodologies can be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software codes can be stored in the medium 1118 or the memory 1116 and executed by one or more processors 1104, so that one or more processors 1104 operate as a special-purpose computer programmed to perform the techniques disclosed herein. The memory can be implemented within one or more processors 1104 or external to one or more processors 1104. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which the memory is stored.

[0262] In the case of implementation in firmware and / or software, the functions performed by the network entity 1100 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as medium 1118 or memory 1116). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0263] In addition to being stored on a computer-readable storage medium, instructions and / or data for the network entity 1100 may also be provided as a signal on a transmission medium included in a communication device. For example, a communication device including part or all of the network entity 1100 may include a transceiver with a signal indicating instructions and data. These instructions and data are stored on a non-transitory computer-readable medium (e.g., 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 with a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.

[0264] FIG. 12 is a diagram illustrating an example of a hardware implementation of a server 1200 belonging to a serving PLMN, a home PLMN of a UE, a satellite operator providing access to a serving PLMN or a separate third party. The server 1200 may be, for example, the server 187 illustrated in FIG. 8B and FIG. 9 . The server 1200 may execute the signal flows of FIG. 8B and FIG. 9 and the techniques disclosed herein. The server may operate as a network node in a communication network (e.g., a wireless network, a PLMN, etc.). The server 1200 includes, for example, hardware components, such as an external interface 1202 configured to communicate with network components in the PLMN and the UE 115, for example, using HTTP, HTTPs, or SMS. The server 1200 includes one or more processors 1204, a memory 1216, and a non-transitory computer-readable medium 1218, which may be coupled together using a bus 1207.

[0265] The one or more processors 1204 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 1204 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 1220 on a non-transitory computer-readable medium such as the medium 1218 and / or the memory 1216. In some embodiments, the 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 computing procedure or process related to the operation of the server 1200.

[0266] The medium 1218 and / or memory 1216 may store instructions or program code 1220 containing executable code or software instructions that, when executed by one or more processors 1204, cause one or more processors 1204 to operate as a special-purpose computer programmed to perform the techniques disclosed herein (e.g., such as the signal flows of Figures 8B and 9 and the techniques disclosed herein). As illustrated by the server 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 perform the methodologies described herein. Although each component or module is illustrated as software in the medium 1218 that can be executed by one or more processors 1204, it should be understood that each component or module may be stored in the memory 1216 or may be dedicated hardware in one or more processors 1204 or external to the processor. The medium 1218 and / or the memory 1216 (or another medium including an external storage medium accessed by the server 1200) may store data that may be provided to the UE upon request, such as coverage data that may enable the UE to determine whether access to the serving PLMN is possible at one or more locations of the UE, at one or more or more future times, using one or more radio access technologies (RATs), or for some combination of these. The coverage data may be for an NTN RAT and / or a TNRAT.

[0267] Several software modules and data tables may reside in the media 1218 and / or memory 1216 and be utilized by the one or more processors 1204 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of the media 1218 and / or memory 1216 as shown for the server 1200 is exemplary only, and thus the functionality of the various modules and / or data structures may be combined, separated, and / or configured in different ways depending on the specific implementation of the server 1200. Although the various components or modules are illustrated as software in the media 1218 and / or memory 1216 that is executable by the one or more processors 1204, it should be understood that the various components or modules may be firmware or dedicated hardware in the one or more processors 1204 or external to the processors.

[0268] As illustrated, program code 1220 stored on medium 1218 and / or memory 1216 may include a data access module 1222 that, when implemented by one or more processors 1204, configures one or more processors 1204 to support providing coverage data to a UE as described herein and particularly with respect to FIGS. 8B and 9.

[0269] The methodologies described herein may be implemented by various means depending on the application. For example, these methodologies may be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 1204 may 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 combinations thereof.

[0270] For specific implementations of the server 1200 involving firmware and / or software, these methodologies may be implemented with modules (e.g., procedures, functions, etc.) that perform the individual functions described herein. Any machine-readable medium that tangibly embodies instructions may be used to implement the methodologies described herein. For example, software code may be stored in the medium 1218 or the memory 1216 and executed by one or more processors 1204, thereby causing one or more processors 1204 to operate as a special-purpose computer programmed to perform the techniques disclosed herein. The memory 1216 may be implemented within one or more processors 1204 or external to one or more processors 1204. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any particular amount of memory, or the type of medium on which the memory is stored.

[0271] In the case of implementation in firmware and / or software, the functions performed by the server 1200 may be stored as one or more instructions or codes on a non-transitory computer-readable storage medium (such as medium 1218 or memory 1216). Examples of storage media include computer-readable media encoded with data structures and computer-readable media encoded with computer programs. Computer-readable media include physical computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices, semiconductor storage devices or other storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer; as used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0272] In addition to being stored on a computer-readable storage medium, instructions and / or data for server 1200 may also be provided as signals on a transmission medium included in a communication device. For example, a communication device including part or all of server 1200 may include a transceiver having signals indicating instructions and data. These instructions and data are stored on a non-transitory computer-readable medium (e.g., 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 a signal indicating information for performing the disclosed functions. At a first time, the transmission medium included in the communication device may include a first portion of information for performing the disclosed functions, and at a second time, the transmission medium included in the communication device may include a second portion of information for performing the disclosed functions.

[0273] FIG. 13 illustrates a procedure that enables a UE (e.g., UE 115) to register with a serving PLMN that may provide 5G NR satellite access to the UE, wherein a serving AMF (e.g., AMF 120) for the UE in the serving PLMN may provide authorization data to the UE. FIG. 13 shows a procedure similar to the procedure previously described with respect to FIG. 8A , but allows the authorization data to be provided by the serving AMF for the UE (as in FIG. 8A ) or by the UDM in the HPLMN of the UE. After the UE uses the procedure shown in FIG. 13 , the UE may use the authorization data obtained thereby to obtain coverage data from a server (hereinafter referred to as an external server), as described with respect to FIG. 8B .

[0274] In FIG. 13 , the authorization data may come from (e.g., may be determined by) a unified data management (UDM) in the serving AMF or the HPLMN of the UE. The authorization data provides information to the UE to enable the UE to access an external server (e.g., a server belonging to a satellite network operator) and obtain satellite coverage data (e.g., satellite coverage map data) from the server. For example, the satellite coverage data may indicate when satellite coverage is available and unavailable at one or more locations and at one or more times, as described elsewhere herein. The UE may provide input parameters, such as a minimum signal level or minimum signal power, to the external server, and when no satellite is visible at any location and time or when the signal level or signal power of all visible satellites from that location and time is lower than the minimum signal level or minimum signal power provided by the UE, the external server then determines that satellite coverage is unavailable at that location and time. However, when the signal level or signal power of at least one visible satellite from any location and time is equal to or greater than the minimum signal level or minimum signal power provided by the UE, the external server may determine that satellite coverage is available at that location and time. The minimum signal level or minimum signal power level provided by the UE may be equal to the minimum signal level or signal power required for the UE to access the satellite to communicate with the serving PLMN. When the serving AMF (e.g., AMF122) provides authorization data to the UE, the external server may be associated with the serving PLMN. When the UDM will provide authorization data to the AMF for forwarding to the UE, the external server may be associated with the HPLMN of the UE. The authorization data may include the address of the server (e.g., IP address, URI, fully qualified domain name (FQDN), SMS address), may indicate the protocol or transport protocol (e.g., HTTP, HTTPS, SMS) to be used by the UE to access the external server and obtain satellite coverage data from the server, may include a temporary identifier (or identity) of the UE that can be verified or authenticated by the external server (e.g., as described elsewhere herein), and may indicate the type of satellite coverage data that can be obtained from the external server and the period or duration during which the UE is allowed to access the external server to obtain satellite coverage data.

[0275] The UE may initiate a registration procedure using any of a variety of registration types, including when the UE requires authorization to obtain coverage availability information for NR satellite access. The various stages of the procedure of Figure 13 are discussed below, with the portions most relevant to obtaining authorization to receive coverage data shown in italics.

[0276] Phase 1: The UE transmits a NAS registration request to the AMF (e.g., as shown at 805 in FIG. 8A ). The details include UE to (R)AN: AN message (AN parameters, registration request (registration type, SUCI or 5G-GUTI or PEI, [last visited TAI (if applicable)], security parameters, [requested NSSAI], [mapping of requested NSSAI], [default configured NSSAI indication], [UE radio capability update], [UE MM core network capabilities], [PDU session status], [list of PDU sessions to be activated], [follow-up request], [MICO mode preference], [requested active time], [requested DRX parameters for E-UTRA and NR], [requested DRX parameters for NB-IoT], [extended idle mode DRX parameters], [LADN [Indicator of DNN or requested LADN information], [NAS message container], [Indication of support for use of enhanced coverage], [Preferred network behavior], [UE paging probability information], [Paging subgroup support indication], [UE policy container (PSI list, indication that UE supports ANDSP and operating system identifier)] and [UE radio capability ID], [Release request indication], [Paging restriction information], PEI, [PLMN with disaster conditions], [Requested periodic update time], [Unavailable period duration], [Request authorization for obtaining satellite coverage availability information]). The UE policy container and its use are defined in 3GPP TS 23.503.

[0277] In the case of NG-RAN, the AN parameters may include, for example, 5G-S-TMSI or GUAMI, the selected PLMN ID (or PLMNID and NID, see clause 5.30 of 3GPP TS 23.501) and NSSAI information, and the AN parameters also include the establishment cause. The establishment cause provides the reason why the RRC connection establishment is requested. Whether and how the UE includes the NSSAI information as part of the AN parameters depends on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, as specified in clause 5.15.9 of 3GPP TS 23.501.

[0278] In the case where the UE is an IAB node accessing 5GS, the AN parameters may also include an IAB indication.

[0279] The registration type indicates whether the UE wants to perform an initial registration (i.e. the UE is in RM-DEREGISTERED state), a mobility registration update (i.e. the UE is in RM-REGISTERED state and the registration procedure is initiated due to mobility or because the UE needs to update its capabilities or protocol parameters or requests a change in the set of network slices it is allowed to use), a periodic registration update (i.e. the UE is in RM-REGISTERED state and the registration procedure is initiated due to expiration of the periodic registration update timer, see clause 4.2.2.2.1 of 3GPPTS 23.502), an emergency registration (i.e. the UE is in restricted service state), a disaster roaming initial registration or a disaster roaming mobility registration update.

[0280] When the UE is using E-UTRA, the UE may indicate its support for CIoT 5GS Optimizations which may be related to AMF selection in the RRC connection establishment signaling associated with the Registration Request.

[0281] When the UE is performing an initial registration or a disaster roaming registration, the UE may indicate its UE identity in the Registration Request message as follows, listed in descending order of preference in the case of registration with a PLMN:

[0282] i) in case the UE has a valid EPS GUTI, the 5G-GUTI mapped from the EPS GUTI;

[0283] ii) the native 5G-GUTI assigned by the equivalent SNPN to the SNPN to which the UE is attempting to register and the NID of the SNPN that assigned the 5G-GUTI (where available);

[0284] iii) the native 5G-GUTI assigned by the PLMN to which the UE is attempting to register (where available);

[0285] iv) the native 5G-GUTI assigned by the equivalent PLMN to the PLMN the UE is attempting to register to (where available);

[0286] iv) Native 5G-GUTI assigned by any other PLMN (where available). According to some embodiments, this may also be a 5G-GUTI assigned via another access type.

[0287] v) Otherwise, the UE may include its SUCI in the Registration Request as defined in 3GPP TS 33.501.

[0288] In the case where the UE is registering with the SNPN, when the UE is performing an initial registration, the UE may indicate its UE identity in the Registration Request message as follows, listed in descending order of preference:

[0289] i) the native 5G-GUTI assigned by the same SNPN that the UE is attempting to register to (where available);

[0290] ii) The native 5G-GUTI assigned by any other SNPN and the NID of the SNPN that assigned the 5G-GUTI (where available).

[0291] iii) Otherwise, the UE may include its SUCI in the Registration Request as defined in 3GPP TS 33.501.

[0292] When the UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE may also indicate the native 5G-GUTI as an additional GUTI. In the event that more than one native 5G-GUTI is available, the UE may select a 5G-GUTI in descending order of preference from items (ii)-(iv) in the above list.

[0293] In the case where the UE is transmitting a Registration Request message as an initial NAS message and the UE has a valid 5G NAS security context and the UE needs to transmit non-plaintext IEs (see clause 4.4.6 in 3GPP TS 24.501), a NAS message container may be included. In the case where the UE does not need to transmit non-plaintext IEs, the UE may transmit the Registration Request message without including a NAS message container.

[0294] In the event that the UE does not have a valid 5G NAS security context, the UE may transmit a Registration Request message without including a NAS message container. The UE may include the entire Registration Request message (i.e., including plaintext IEs and non-plaintext IEs) in a NAS message container transmitted as part of the Security Mode Complete message in Phase 9b.

[0295] When the UE is performing an initial registration with a native 5G-GUTI (i.e., the UE is in RM-DEREGISTERED state), the UE may indicate relevant GUAMI information in the AN parameters. When the UE is performing an initial registration with its SUCI, the UE may not indicate any GUAMI information in the AN parameters.

[0296] When the UE is performing an initial registration or mobility registration and in the case of supporting CIoT 5GS optimization, the UE can indicate its preferred network behavior (see clause 5.31.2 of 3GPP TS 23.501). In the case of supporting S1 mode, the UE's EPC preferred network behavior is included in the S1 UE network capabilities in the registration request message, see clause 8.2.6.1 of 3GPP TS 24.501.

[0297] For emergency registration, SUCI may be included if the UE does not have a valid 5G-GUTI available; PEI may be included when the UE does not have SUPI and does not have a valid 5G-GUTI. In other cases, 5G-GUTI is included and indicates the last serving AMF.

[0298] The UE may provide the UE's usage settings based on its configuration as defined in clause 5.16.3.7 of 3GPP TS 23.501. The UE provides the requested NSSAI (as described in clause 5.15.5.2.1 of 3GPP TS 23.501) and, in the case where the UE supports subscription-based restriction on simultaneously registered network slices, also considers the NSSRG information constraints as described in clause 5.15.12 of 3GPP TS 23.501 and, in case of initial registration or mobility registration update, the UE includes a mapping of the requested NSSAI (where available) which is a mapping of each S-NSSAI of the requested NSSAI to the HPLMN S-NSSAI to ensure that the network can verify whether the S-NSSAI in the requested NSSAI is allowed based on the subscribed S-NSSAI. In case of inter-PLMN mobility, in the event that the serving PLMN S-NSSAI corresponding to the established PDU session is not present in the UE, the associated HPLMN S-NSSAI associated with the established PDU session may be provided in the mapping of the requested NSSAI as described in clause 5.15.5.2.1 of 3GPP TS 23.501.

[0299] In the case where the UE is using a default configured NSSAI, the UE includes a default configured NSSAI indication as defined in 3GPP TS 23.501.

[0300] In case the UE supports assignment of WUS assistance information or AMF PEIPS assistance information from the AMF, the UE may include UE paging probability information (see 3GPP TS 23.501).

[0301] The UE may include a paging subgroup support indication as defined in 3GPP TS 23.501.

[0302] In case of a mobility registration update, the UE includes in the list of PDU sessions to be activated the PDU sessions for which there is pending uplink data. When the UE includes the list of PDU sessions to be activated, the UE may indicate only the PDU sessions associated with the access to which the registration request relates. As defined in 3GPP TS 24.501, the UE may include in the list of PDU sessions to be activated the always-open PDU sessions accepted by the network, even if there is no pending uplink data for those PDU sessions.

[0303] Note 3: When the UE is outside the availability area of ​​the LADN, the PDU session corresponding to the LADN is not included in the list of PDU sessions to be activated.

[0304] UE MM Core Network Capabilities are provided by the UE and processed by the AMF as defined in clause 5.4.4a of 3GPP TS 23.501. The UE includes in the UE MM Core Network Capabilities an indication of whether it supports the request type flag "Handover" for PDN connectivity requests during the attach procedure as defined in clause 5.17.2.3.1 of 3GPP TS 23.501. In the case where the UE supports "Strict Periodic Registration Timer Indication", the UE indicates its capability for "Strict Periodic Registration Timer Indication" in the UE MM Core Network Capabilities. In the case where the UE supports CAG, the UE indicates its capability for "Support CAG" in the UE MM Core Network Capabilities. In the case where a UE operating two or more USIMs supports and intends to use one or more multi-USIM features, the UE indicates in the UE MM Core Network Capabilities one or more multi-USIM specific features described in clause 5.38 of 3GPP TS 23.501. In the case where the UE supports equivalent SNPN, the UE indicates its "equivalent SNPN" capability in the UE MM core network capabilities. In the case where the UE supports unavailable periods, the UE indicates its "unavailable period support" capability in the UE MM core network capabilities.

[0305] The UE may provide a LADN DNN or an indication to request LADN information as described in clause 5.6.5 of 3GPP TS 23.501.

[0306] Where available, the last visited TAI may be included to help the AMF generate a registration area for the UE.

[0307] NOTE 4: With NR satellite access, determine the last visited TAI as specified in clause 5.4.11.6 of 3GPP TS 23.501.

[0308] The security parameters are used for authentication and integrity protection, see 3GPP TS 33.501. The requested NSSAI indicates the Network Slice Selection Assistance Information (as defined in clause 5.15 of 3GPP TS 23.501). The PDU Session Status indicates the previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, then the PDU Session Status indicates the established PDU session of the current PLMN in the UE.

[0309] A follow-up request is included when the UE has pending uplink signaling and the UE does not include a list of pending PDU sessions to be activated or the registration type indicates that the UE wants to perform an emergency registration. In initial registration and mobility registration update, the UE provides UE requested DRX parameters as defined in clause 5.4.5 of 3GPP TS 23.501. The UE may provide extended idle mode DRX parameters as defined in clause 5.31.7.2 of 3GPP TS 23.501 to request extended idle mode DRX.

[0310] The UE provides a radio capability update indication as described in 3GPP TS 23.501.

[0311] In case the UE wants to use MICO mode with active time, the UE includes a MICO mode preference and optionally a requested active time value and a requested periodic update time value.

[0312] The UE may indicate its service gap control capability in the UE MM Core Network Capabilities, see clause 5.31.16 of 3GPP TS 23.501.

[0313] For a UE with a service gap timer running in the UE, the UE may not set the Follow-up Request Indication or the Uplink Data Status in the Registration Request message (see clause 5.31.16 of 3GPP TS 23.501), except for network access for regulatory prioritization services such as emergency services or exception reporting.

[0314] In case the UE supports RACS and has been assigned a UE radio capability ID, the UE may indicate the UE radio capability ID as defined in clause 5.4.4.1a of 3GPP TS 23.501 as a non-plain text IE.

[0315] The PEI may be retrieved from the UE in the initial registration as described in clause 4.2.2.2.1 of 3GPP TS 23.502.

[0316] In case the UE supports subscription-based restriction on simultaneous registration of network slices feature, it includes NSSRG handling support indication in the UE 5GMM Core Network Capabilities as per clause 5.15.12 of 3GPP TS 23.501. The AMF stores whether the UE supports this feature in the UE context.

[0317] When a multi-USIM UE wants to enter CM-IDLE state immediately, for example after having performed mobility or periodic registration, it includes a release request indication and optionally provides paging restriction information.

[0318] When the UE is performing disaster roaming registration, the UE may indicate the disaster condition to the PLMN for situations as defined in 3GPP TS 24.501.

[0319] In the case where the UE and the network have indicated support for unavailable periods and an event is triggered in the UE that will make the UE unavailable for a certain period, the UE indicates the unavailable period by including the unavailable period duration as described in clause 5.4.1.4 of 3GPP TS 23.501.

[0320] In the case of registering for NR satellite access, and in the case that the UE supports receiving satellite coverage availability information (SCAI) and requires authorization or further authorization to obtain satellite coverage availability information from an external server, the UE includes an authorization request for obtaining satellite coverage availability information in the Registration Request transmitted in Phase 1.

[0321] Stage 2: In the case where the 5G-S-TMSI or GUAMI is not included, or the 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI (if available).

[0322] The (R)AN selects the AMF as described in clause 6.3.5 of 3GPP TS 23.501. In the case where the UE is in the CM-CONNECTED state, the (R)AN may forward the Registration Request message to the AMF based on the UE's N2 connection.

[0323] In case the (R)AN cannot select a suitable AMF, it forwards the Registration Request to the AMF that has been configured in the (R)AN to perform AMF selection.

[0324] Phase 3: (R)AN to new AMF: N2 message (N2 parameters, Registration Request (as described in Phase 1) and [LTE-M Indication].

[0325] When NG-RAN is used, the N2 parameters include the selected PLMN ID (or PLMN ID and NID, see clause 5.30 of 3GPP TS 23.501), location information and cell identity related to the cell in which the UE is camped, and a UE context request indicating that a UE context including security information needs to be established at the NG-RAN.

[0326] When using NG-RAN, the N2 parameters may also include the establishment cause and the IAB-Indication in case an indication is received in the AN parameters at stage 1.

[0327] The mapping for the requested NSSAI is provided only if available.

[0328] In the case where the registration type indicated by the UE is periodic registration update, stages 4 to 19 may be omitted.

[0329] When the establishment cause is associated with a priority service (e.g., MPS, MCS), the AMF includes a message priority header to indicate the priority information. Other NFs relay the priority information by including a message priority header in the service-based interface, as specified in 3GPP TS 29.500.

[0330] Determine the RAT type that the UE is using (see clause 4.2.2.2.1 of 3GPP TS 23.502), and based on this, the AMF determines whether the UE is performing inter-RAT mobility to or from NB-IoT. In the event that the AMF receives an LTE M indication, it considers the RAT type to be LTE-M and stores the LTE-M indication in the UE context.

[0331] In the case where the UE includes a preferred network behavior, this defines the network behavior that the UE supports and expects to be available in the network as defined in clause 5.31.2 of 3GPP TS 23.501.

[0332] In the event that the UE has included a preferred network behavior and the content that the UE indicates it supports in the preferred network behavior is incompatible with the network support, the AMF may reject the Registration Request with an appropriate cause value (e.g. a cause value to avoid retrying on this PLMN).

[0333] In the case where there is a service gap timer running in the UE context in the AMF for the UE and a follow-up request indication or uplink data status is included in the registration request message, the AMF may ignore the follow-up request indication and uplink data status and not perform any action related to the status.

[0334] In case the UE has included the UE radio capability ID in Phase 1 and the AMF supports RACS, the AMF stores the radio capability ID in the UE context.

[0335] For NR satellite access, the AMF may verify the UE location and determine whether a PLMN is allowed to operate at that UE location, as described in clause 5.4.11.4 of 3GPP TS 23.501. In the event that the UE receives a Registration Reject message with a cause value indicating that the PLMN is not allowed to operate at the current UE location, the UE may attempt to select a PLMN, as specified in 3GPP TS 23.122.

[0336] For disaster roaming registration, the AMF determines whether disaster roaming services can be provided based on the ULI (including cell ID) received from the NG-RAN, the PLMN with disaster conditions derived from the UE's 5G-GUTI, derived from the UE's SUCI or indicated by the UE, and local configuration. In the case that the current location is not subject to disaster roaming services, or disaster roaming services are not provided to the PLMN with disaster conditions derived from the UE's 5G-GUTI, derived from the UE's SUCI or indicated by the UE, the AMF shall reject the Registration Request indicating an appropriate cause value.

[0337] Phase 4: [Conditional] New AMF to old AMF: Namf_Communication_UEContextTransfer (complete registration request) or new AMF to UDSF: Nudsf_Unstructured Data Management_Query().

[0338] The new AMF uses the UE's 5G-GUTI to determine the old AMF. In the event that the new AMF receives the NID in the Registration Request, it determines that the 5G-GUTI is assigned by the SNPN and uses the SNPN's 5G-GUTI and NID to determine the old AMF.

[0339] (With UDSF deployment): In the case where the UE's 5G-GUTI is included in the Registration Request and the serving AMF has changed since the last registration procedure, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using the Nudsf_UnstructuredDataManagement_Query service operation if the new and old AMFs are in the same AMF set and UDSF is deployed, or they may share the stored UE context via implementation specific means if UDSF is not deployed. This also includes event subscription information for each NF consumer for a given UE. In this case, the new AMF performs and verifies integrity protection using the integrity protected full Registration Request NAS message.

[0340] (Without UDSF deployment): In the case where the UE's 5G-GUTI is included in the Registration Request and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation on the old AMF including a complete Registration Request NAS message that may be integrity protected and the access type to request the UE's SUPI and UE context. See clause 5.2.2.2.2 of 3GPP TS 23.502 for details of this service operation. In this case, the old AMF verifies the integrity protection using the 5G-GUTI and the integrity protected complete Registration Request NAS message, or using the SUPI and an indication from the new AMF that the UE is verified, in the case where the context transfer service operation invocation corresponds to the requested UE. The old AMF also transfers the event subscription information of each NF consumer to the new AMF. In the case where the old AMF has not reported a non-zero MO Exception Data counter to the (H-)SMF, the context response also includes the MO Exception Data counter.

[0341] In case the old AMF has a PDU Session for another access type (different from the access type indicated at stage) and in case the old AMF determines that it is not possible to relocate the N2 interface to the new AMF, the old AMF returns the UE's SUPI and indicates that the Registration Request has been verified for integrity protection, but does not include the rest of the UE context.

[0342] For inter-PLMN mobility, the UE context information includes the HPLMNS-NSSAI corresponding to the allowed NSSAI for each access type, but does not include the allowed NSSAI of the old PLMN.

[0343] NOTE 5: In the case where the new AMF has performed a successful UE authentication after a previous integrity check failure in the old AMF, the new AMF sets an indication that the UE is verified according to operation 9a.

[0344] Note 6: After the UE successfully registers with the new AMF, the NF consumer does not need to subscribe to events with the new AMF again.

[0345] In case the new AMF has received the UE context from the old AMF during the handover procedure, phases 4, 5 and 10 may be skipped.

[0346] For emergency registration, in the case where the UE identifies itself with a 5G-GUTI that is unknown to the AMF, nodes 4 and 5 are skipped and the AMF immediately requests a SUPI from the UE. In the case where the UE identifies itself with a PEI, the SUPI request may be skipped. Allowing emergency registration without user identity depends on local regulations.

[0347] Phase 5: [Conditional] Old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE Context in AMF (as per Table 5.2.2.2.2-1)) or UDSF to new AMF: Nudsf_UnstructuredData Management_Query(). The old AMF may start implementation specific (protection) timers for the UE context.

[0348] In case the UDSF is queried at phase 4, the UDSF responds to the new AMF for Nudsf_Unstructured Data Management_Query call with the relevant context including the established PDU session, the old AMF includes the SMF information DNN, S-NSSAI and PDU session ID, the active NGAP UE-TNLA binding to the N3IWF / TNGF / W-AGF, and the old AMF includes information about the NGAP UE-TNLA binding. In case the old AMF is queried at phase 4, the old AMF responds to the new AMF for Namf_Communication_UEContextTransfer call by including the UE's SUPI and UE context.

[0349] In case the old AMF holds information about the established PDU session and it is not an initial registration, the old AMF includes SMF information, DNN, S-NSSAI and PDU session ID.

[0350] In the case where the old AMF maintains the UE context established via N3IWF, W-AGF or TNGF, the old AMF includes the CM state via N3IWF, W-AGF or TNGF. In the case where the UE is in CM-CONNECTED state via N3IWF, W-AGF or TNGF, the old AMF includes information about NGAP UE-TNLA binding.

[0351] In the case where the old AMF fails the integrity check of the Registration Request NAS message, the old AMF may indicate that the integrity check failed. In the case where the new AMF is configured to allow emergency services for unauthenticated UEs, the new AMF behaves as follows:

[0352] - In the case where the UE has only an emergency PDU session, the AMF skips the authentication and security procedures, or accepts that authentication may have failed and continues with the mobility registration update procedure; or

[0353] - In case the UE has both emergency and non-emergency PDU Sessions and authentication fails, the AMF continues with the Mobility Registration Update procedure and deactivates all non-emergency PDU Sessions as specified in clause 4.3.4.2 of 3GPP TS 23.502.

[0354] Note 7: The new AMF can determine whether the PDU Session is used for emergency services by checking whether the DNN matches the emergency DNN.

[0355] In the case where the old AMF maintains information about AM policy association and information about UE policy association (i.e., policy control request trigger for updating UE policy as defined in 3GPP TS23.503), the old AMF includes information about AM policy association, UE policy association and PCF ID. In the case of roaming, it includes V-PCF ID and H-PCF ID.

[0356] In the case where the old AMF is a consumer of UE-related NWDAF services, the old AMF includes information about active analytics subscriptions in the Namf_Communication_UEContextTransfer response, i.e., the subscription correlation ID, the NWDAF identifier (i.e., the instance ID or set ID), the analytics ID and the associated analytics specific data. The use of analytics information by the new AMF is specified in 3GPP TS 23.288.

[0357] During inter-PLMN mobility, the handling of UE Radio Capability ID in the new AMF is as defined in 3GPP TS 23.501.

[0358] NOTE 8: When the new AMF uses UDSF for context retrieval, the interaction between the old AMF, new AMF and UDSF due to simultaneous UE signalling on the old AMF is an implementation specific issue.

[0359] Phase 6: [Conditional] New AMF to UE: Identity Request ().

[0360] In case the SUCI is not provided by the UE or retrieved from the old AMF, the Identity Request procedure is initiated by the AMF to transmit an Identity Request message to the UE requesting the SUCI.

[0361] Phase 7: [Conditional] UE to new AMF: Identity Response ().

[0362] The UE responds with an Identity Response message including the SUCI. The UE derives the SUCI by using the provided public key of the HPLMN as specified in 3GPP TS 33.501.

[0363] Phase 8: AMF may decide to initiate UE authentication by invoking AUSF. In this case, AMF selects AUSF based on SUPI or SUCI as described in clause 6.3.4 of 3GPP TS 23.501.

[0364] In case the AMF is configured to support Emergency Registration for an unauthenticated SUPI and the UE indicates Registration Type Emergency Registration, the AMF skips authentication or the AMF accepts that authentication may have failed and continues with the registration procedure.

[0365] Phase 9a: In case authentication is required, the AMF requests authentication from the AUSF; in case tracking requirements about the UE are available at the AMF, the AMF provides the tracking requirements in its request to the AUSF. For disaster roaming registration, the AMF may provide an indication of disaster roaming services in its request to the AUSF. Based on the request from the AMF, the AUSF may perform authentication of the UE. Authentication is performed as described in 3GPP TS 33.501. The AUSF selects the UDM and obtains authentication data from the UDM as described in clause 6.3.8 of 3GPP TS 23.501.

[0366] Upon receiving an indication from the AMF, the AUSF may provide an indication to the UDM regarding disaster roaming services. For disaster roaming registration, the AUSF performs authentication of the UE based on local policy and / or local configuration, as specified in clause 5.40.4 of 3GPP TS 23.501 and in 3GPP TS 33.501.

[0367] Once the UE has been authenticated, the AUSF provides the relevant security related information to the AMF. In the case where the AMF provides the SUCI to the AUSF, the AUSF may return the SUPI to the AMF only after successful authentication.

[0368] After successful authentication in the new AMF (which was triggered by the integrity check failure in the old AMF in stage 5), the new AMF invokes stage 4 above again and indicates that the UE is verified (i.e. via the cause parameter as specified in clause 5.2.2.2.2 of 3GPP TS 23.502).

[0369] Phase 9b: In case NAS security context does not exist, NAS security initiation may be performed as described in 3GPP TS 33.501. In case the UE does not have NAS security context at Phase 1, the UE includes a complete Registration Request message as defined in 3GPP TS 24.501.

[0370] The AMF decides whether the Registration Request needs to be re-routed as described in clause 4.2.2.2.3 of 3GPP TS 23.502, where the Initial AMF refers to this AMF.

[0371] Phase 9c: In the event that the 5G-AN has requested a UE context, the AMF initiates an NGAP procedure to provide a security context to the 5G-AN as specified in 3GPP TS 38.413. In addition, in the event that the AMF decides to support EPS fallback (e.g., based on UE capabilities, subscription data and local policies that support the request type flag "handover" for PDN connectivity requests during the attach procedure as defined in clause 5.17.2.3.1 of 3GPP TS 38.413), the AMF may transmit an indication "Voice EPS fallback can be redirected" towards the 5G-AN as specified in 3GPP TS 23.501. Otherwise, the AMF indicates "Voice EPS fallback cannot be redirected". In addition, in the event that a tracing requirement regarding the UE is available at the AMF, the AMF provides the tracing requirement for the 5G-AN in the NGAP procedure.

[0372] Phase 9d: 5G-AN stores the security context and acknowledges it to AMF. 5G-AN uses the security context to protect messages exchanged with the UE as described in 3GPP TS 33.501.

[0373] Phase 10: [Conditional] New AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (e.g. PDU Session ID released due to not supporting slicing).

[0374] In case the AMF has changed, the new AMF notifies the old AMF that the UE's registration in the new AMF is complete by calling the Namf_Communication_RegistrationStatusUpdate service operation.

[0375] In case the authentication / security procedures fail, the registration may be rejected and the new AMF invokes a Namf_Communication_RegistrationStatusUpdate service operation with a reject indication towards the old AMF. The old AMF continues as if the UE Context Transfer service operation had never been received.

[0376] The new AMF determines that PDU Sessions cannot be supported in the new registration area in the following cases:

[0377] - In the case where one or more S-NSSAIs used in the old registration area cannot be served in the target registration area.

[0378] - When continuity of PDU sessions cannot be supported between networks (e.g. SNPN-SNPN mobility, inter-PLMN mobility where no HR agreement exists).

[0379] In the event that any of the conditions are met, the new AMF calls the Namf_Communication_RegistrationStatusUpdate service operation including the rejected PDU Session ID towards the old AMF. The new AMF then modifies the PDU Session status accordingly. The old AMF notifies the corresponding SMF to release the UE's SM context locally by calling the Nsmf_PDUSession_ReleaseSMContext service operation.

[0380] In the case where the new AMF receives information about AM policy association and UE policy association in UE context transfer in stage 5 and decides not to use the PCF identified by the PCF ID used for AM policy association and UE policy association based on local policy, it will notify the old AMF that the AM policy association and UE policy association in the UE context are no longer used and then perform PCF selection in stage 15.

[0381] In case the new AMF receives information about the UE related analysis subscriptions in the UE context transfer in phase 5, the new AMF may take over the analysis subscriptions from the old AMF. Otherwise, in case the new AMF decides to create a new analysis subscription instead, it informs the old AMF of the no longer needed analysis subscriptions (identified by their subscription correlation IDs) and the old AMF may now unsubscribe the UE from those NWDAF analysis subscriptions according to 3GPP TS 23.288.

[0382] Stage 11: [Conditional] New AMF to UE: Identity Request / Response (PEI).

[0383] In the case where the PEI is not provided by the UE or is not retrieved from the old AMF, the Identity Request procedure is initiated by the AMF to transmit an Identity Request message to the UE to retrieve the PEI. The PEI may be transferred encrypted unless the UE performs an emergency registration and cannot be authenticated.

[0384] For emergency registration, the UE may have included the PEI in the Registration Request. If so, PEI retrieval is skipped.

[0385] In case the UE supports RACS as indicated in the UE MM Core Network Capabilities, the AMF may use the UE's PEI to obtain the IMEI / TAC for RACS operation purposes.

[0386] Stage 12: Optionally, the new AMF initiates a ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation (see clause 5.2.4.2.2 of 3GPP TS 23.502).

[0387] Perform a PEI check as described in clause 4.7 of 3GPP TS 23.502.

[0388] For emergency registration, in the event that PEI is blocked, operator policy determines whether the emergency registration procedure continues or stops.

[0389] Stage 13: In case stage 14 is to be performed, the new AMF selects the UDM based on the SUPI, and the UDM may then select the UDR instance. See clause 6.3.9 of 3GPP TS 23.501.

[0390] The AMF selects UDM as described in clause 6.3.8 of 3GPP TS 23.501.

[0391] Phase 14a-c: In case the AMF has changed since the last registration procedure, in case the UE Registration Type indicates Initial Registration or Emergency Registration, or in case the UE provides a SUPI which does not refer to a valid context in the AMF, or in case the UE registers to the same AMF with which it is already registered to a non-3GPP access (i.e. the UE is registered on a non-3GPP access and this Registration procedure is initiated to add a 3GPP access), the new AMF registers with the UDM using Nudm_UECM_Registration for the access to be registered (and subscribes to be notified when the UDM deregisters the AMF). According to 3GPP TS 23.122, the SoR information that the UDM can act on based on the "Registration Type" in the Nudm_UECM_Registration request. In this case, the AMF indicates this to the UDM in case the AMF does not have event exposure subscription information for this UE. Then, in case the UDM has an existing applicable event exposure subscription for an event detected in the AMF for this UE or for any group to which the UE belongs (possibly retrieved from the UDR), the UDM calls the Namf_EventExposure_Subscribe service to recreate the event exposure subscription.

[0392] The AMF provides the "Homogeneous support for IMS Voice over PS sessions" indication to the UDM (see clause 5.16.3.3 of 3GPP TS 23.501). The "Homogeneous support for IMS Voice over PS sessions" indication may not be included unless the AMF has completed its evaluation of its support for "IMS Voice over PS sessions" as specified in clause 5.16.3.2 of 3GPP TS 23.501.

[0393] During initial registration, in case the AMF and UE support SRVCC from NG-RAN to UTRAN, the AMF provides the UE SRVCC capability to the UDM.

[0394] In case the AMF determines that only the UE SRVCC capability has changed, the AMF transmits the UE SRVCC capability to the UDM.

[0395] NOTE 9: At this stage, the AMF may not have all the information needed to determine the setup of an indication of support for IMS Voice over PS sessions for this UE (see clause 5.16.3.2 of 3GPP TS 23.501). Therefore, the AMF may communicate "Homogeneous support for IMS Voice over PS sessions" later in this procedure.

[0396] After the AMF has successfully completed the Nudm_UECM_Registration operation, and in the case where the AMF does not have subscription data for the UE, the AMF uses Nudm_SDM_Get to retrieve access and mobility subscription data, SMF selection subscription data, UE context in SMF data, and LCS mobile station calling. In the case where the AMF already has subscription data for the UE, but the SoR update indicator in the UE context requires the AMF to retrieve SoR information according to the NAS registration type ("initial registration" or "emergency registration") (see Annex C of 3GPP TS 23.122), the AMF uses Nudm_SDM_Get to retrieve roaming steering information. This requires the UDM to retrieve this information from the UDR via Nudr_DM_Query. After receiving a successful response, the AMF uses Nudm_SDM_Subscribe to subscribe to be notified when the requested data is modified, and the UDM can subscribe to the UDR via Nudr_DM_Subscribe. In case GPSI is available in UE subscription data, GPSI is provided to AMF in access and mobility subscription data from UDM. UDM may provide indication to UE to update subscription data for network slice. In case UE subscribes to MPS in serving PLMN, "MPS priority" shall be included in access and mobility subscription data provided to AMF. In case UE subscribes to MCX in serving PLMN, "MCX priority" shall be included in access and mobility subscription data provided to AMF. UDM also provides AMF with indication of allowed IAB operation as part of access and mobility subscription data. AMF may trigger establishment of UE context in NG-RAN or modification of UE context in NG-RAN (in case of initial establishment in phase 9c), including indication that IAB node is authorized. In case the registration request transmitted in phase 1 is for NR satellite access and includes authorization request for obtaining satellite coverage availability information, in phase 14b, AMF retrieves subscription data for satellite coverage availability information from UE's UDM in UE's HPLMN using Nudm_SDM_Get service operation.

[0397] For disaster roaming registration, the AMF may provide an indication of disaster roaming services to the UDM. The UDM provides subscription data for disaster roaming services to the AMF based on local policy and / or local configuration, as specified in clause 5.40.4 of 3GPP TS 23.501.

[0398] In case the UE includes the MINT support indication in the 5GMM capabilities as specified in clause 5.40.2 of 3GPP TS 23.501, or in case the MINT support indication in the 5GMM capabilities changes, the AMF provides the MINT support indication to the UDM via Nudm_UECM_Registration.

[0399] In the case where the AMF receives a priority indication as part of the access and mobility subscription data (e.g. MPS, MCX), but the UE does not provide an establishment cause associated with a priority service, the AMF may include a message priority header to indicate the priority information for all subsequent messages. Other NFs relay the priority information by including a message priority header in the service-based interface, as specified in 3GPP TS 29.500.

[0400] The new AMF provides the UDM with the access type it serves for the UE, and the access type is set to "3GPP access". The UDM stores the associated access type with the serving AMF and does not remove the AMF identity associated with other access types (if any). The UDM can store the information provided during AMF registration in the UDR via Nudr_DM_Update.

[0401] In the case where the UE is registered for access in the old AMF and the old AMF and the new AMF are in the same PLMN, after the old AMF relocation is successfully completed, the new AMF transmits a separate / independent Nudm_UECM_Registration to update the UDM with the access type set to the access used in the old AMF.

[0402] The new AMF creates a UE context for the UE after obtaining the access and mobility subscription data from the UDM. The access and mobility subscription data includes whether the UE is allowed to include NSSAI in clear text in the 3GPP access RRC connection establishment. The access and mobility subscription data may include enhanced coverage restriction information. In the case where it is received from the UDM and the UE includes support for restricting the use of enhanced coverage in stage 1, the AMF determines whether enhanced coverage is restricted for the UE as specified in clause 5.31.12 of 3GPP TS 23.501 and stores the updated enhanced coverage restriction information in the UE context.

[0403] Access and mobility subscription data may include NB-IoT UE priority.

[0404] The subscription data may include a service gap time parameter. In the case of receiving from the UDM, the AMF stores the service gap time in the UE context in the AMF for the UE.

[0405] For emergency registrations where the UE is not successfully authenticated, the AMF may not register with the UDM.

[0406] The AMF implements mobility restrictions as specified in clause 5.3.4.1.1 of 3GPP TS 23.501. For emergency registration, the AMF may not check mobility restrictions, access restrictions, area restrictions or subscription restrictions. For emergency registration, the AMF may ignore any unsuccessful registration response from the UDM and continue with the registration procedure.

[0407] NOTE 10: Instead of the Nudm_SDM_Get service operation, the AMF may use the Nudm_SDM_Subscribe service operation with an immediate reporting indication which triggers the UDM to return the subscribed data immediately if the corresponding feature is supported by both the AMF and the UDM.

[0408] Phase 14d: When the UDM stores the associated access type (e.g. 3GPP) with the serving AMF as indicated in phase 14a, this phase will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2 of 3GPP TS 23.502) to the old AMF (if present) corresponding to the same (e.g. 3GPP) access. In the event that the timer started in phase 5 is not running, the old AMF may remove the UE context of the same access type. Otherwise, when the timer expires, the AMF may remove the UE context of the same access type. In the event that the serving NF removal reason indicated by the UDM is initial registration, the old AMF invokes the Nsmf_PDUSession_ReleaseSMContext(SM Context ID) service operation towards all associated SMFs of the UE as described in clause 4.2.2.3.2 of 3GPP TS 23.502 to notify the UE to deregister from the old AMF for the same access type. The SMF may release the PDU session upon receiving this notification.

[0409] In the case where the old AMF has established AM Policy Association and UE Policy Association with the PCF and the old AMF has not transferred the PCF ID to the new AMF (e.g. the new AMF is in a different PLMN), the old AMF performs the AMF-initiated Policy Association Termination procedure as defined in clause 4.16.3.2 of 3GPP TS 23.502 and performs the AMF-initiated UE Policy Association Termination procedure as defined in clause 4.16.13.1 of 3GPP TS 23.502. In addition, in the case where the old AMF transferred the PCFID in the UE context, but the new AMF notified the UE in stage 10 that the AM policy association information and UE policy association information in the UE context will not be used, the old AMF performs the AMF-initiated policy association termination procedure as defined in clause 4.16.3.2 of 3GPP TS 23.502 and performs the AMF-initiated UE policy association termination procedure as defined in clause 4.16.13.1 of 3GPP TS 23.502.

[0410] In the case where the old AMF has an N2 connection for the UE (e.g. because the UE was in RRC Inactive state but has now moved to E-UTRAN or moved to an area not served by the old AMF), the old AMF may perform AN release with a cause value indicating that the UE has locally released the RRC connection to the NG-RAN (see clause 4.2.6 of 3GPP TS 23.502).

[0411] In case the UE context in the old AMF contains an allowed NSSAI including one or more S-NSSAIs subject to NSAC, the old AMF, upon receiving Nudm_UECM_DeregistrationNotification from UDM, transmits an Update Request message for each S-NSSAI subject to NSAC to the corresponding NSACF, with the Update Flag parameter set to Reduce (see clause 4.2.11.2 of 3GPP TS23.502).

[0412] At the end of the registration procedure, the AMF may initiate synchronization of the event exposure subscription with the UDM, provided that the AMF has not indicated in phase 14a that the event exposure subscription is unavailable.

[0413] NOTE 11: The AMF may initiate synchronization with the UDM even if events are available in the UE context at any given time (e.g. as received from the old AMF) and based on local policy. This may be done during subscription change related events.

[0414] Stage 14e: [Conditional] In case the old AMF does not have UE context for another access type (i.e. non-3GPP access), the old AMF uses Nudm_SDM_unsubscribe to unsubscribe the subscription data to the UDM.

[0415] Phase 15: In case AMF decides to initiate PCF communication, AMF operates as follows.

[0416] In the case where the new AMF decides to use the (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF in Phase 5, the AMF contacts the (V-)PCF identified by the (V-)PCF ID to obtain the policy. In the case where the AMF decides to perform PCF discovery and selection, the AMF selects the (V)-PCF and may select the H-PCF (for roaming scenarios) as described in clause 6.3.7.1 of 3GPP TS 23.502 and in accordance with the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3 of 3GPP TS 23.501.

[0417] Phase 16: [Optional] New AMF performs AM policy association establishment / modification. For emergency registration, this phase is skipped.

[0418] In the case that the new AMF selects a new (V-)PCF at stage 15, the new AMF performs an AM policy association establishment with the selected (V-)PCF as defined in clause 4.16.1.2 of 3GPP TS 23.502.

[0419] In case of using a (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF, the new AMF performs an AM policy association modification with the (V-)PCF as defined in clause 4.16.2.1.2 of 3GPP TS 23.502.

[0420] In the case where the AMF notifies the PCF of mobility restrictions (e.g. UE location) for adjustment, or in the case where the PCF updates its own mobility restrictions due to some conditions (e.g. applications in use, time and date), the PCF may provide the updated mobility restrictions to the AMF. In the case where the subscription information includes tracking requirements, the AMF provides the tracking requirements to the PCF.

[0421] In case AMF supports DNN replacement, AMF provides the allowed NSSAI and the mapping of allowed NSSAI (where available) to PCF.

[0422] In the case where PCF supports DNN replacement, PCF provides a trigger for DNN replacement to AMF.

[0423] Phase 17: [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext().

[0424] For emergency registered UEs (see 3GPP TS 23.501), this phase applies when the Registration Type is Mobility Registration Update.

[0425] The AMF calls Nsmf_PDUSession_UpdateSMContext in the following scenarios (see clause 5.2.8.2.6 of 3GPP TS 23.502):

[0426] - In case the list of PDU sessions to be activated is included in the Registration Request of phase 1, the AMF transmits a Nsmf_PDUSession_UpdateSMContext request to the SMF associated with the PDU sessions in order to activate the user plane connection for these PDU sessions. The phases from phase 5 onwards as described in clause 4.2.3.2 of 3GPP TS 23.502 are performed to complete the user plane connection activation without transmitting RRC Inactive Assistance Information and without transmitting MM NAS Service Accept from the AMF to the (R)AN as described in phase 12 of clause 4.2.3.2 of 3GPP TS 23.502. The AS layer in the UE indicates to the NAS layer when the user plane connection for the PDU session is activated.

[0427] - In case the AMF has determined in stage 3 that the UE is performing inter-RAT mobility to or from NB-IoT, the AMF transmits a Nsmf_PDUSession_UpdateSMContext request to the SMF associated with the UE PDU sessions so that the SMF can update them according to the "PDU Session Continuity at Inter-RAT Mobility" subscription data. The stages from stage 5 onwards as described in clause 4.2.3.2 are performed instead of transmitting the MMNAS Service Acceptance from the AMF to the (R)AN as described in stage 12 of clause 4.2.3.2 of 3GPP TS 23.502.

[0428] When the serving AMF has changed, the new serving AMF informs the SMF for each PDU Session that it has taken over the responsibility for the signalling path towards the UE: the new serving AMF calls the Nsmf_PDUSession_UpdateSMContext service operation using the SMF information received from the old AMF in stage 5. It also indicates whether the PDU Session is to be reactivated.

[0429] NOTE 12: In the case where the UE moves into a different PLMN, the AMF in the serving PLMN may insert or change the V-SMF in the serving PLMN for the home routed PDU session. In addition, in the case where the UE moves from a VPLMN into an HPLMN, the V-SMF is removed. In these cases, the same procedures described in clause 4.23.3 of 3GPP TS 23.502 are applied for V-SMF changes as for I-SMF changes (i.e., by replacing the I-SMF with the V-SMF). During inter-PLMN changes, session continuity may be supported depending on operator policy in the case where the same SMF is used.

[0430] The stages from stage 5 onwards described in clause 4.2.3.2 of 3GPP TS 23.502 are performed. In the case of an intermediate UPF insertion, removal or change for a PDU session not included in the "PDU session to be reactivated", this procedure is performed without N11 and N2 interaction to update the N3 user plane between the (R)AN and 5GC.

[0431] The AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF in the following scenarios:

[0432] - In any case where the PDU Session status indicates that it is released at the UE, the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF in order to release any network resources associated with the PDU Session.

[0433] In the case of a change of serving AMF, the new AMF may wait until all SMFs associated with the UE are completed by phase 18. Otherwise, phases 19 to 22 may continue in parallel with this phase.

[0434] Stage 18: [Conditional] In case the new AMF and the old AMF are in the same PLMN, the new AMF transmits a UE Context Modification Request to the N3IWF / TNGF / W-AGF as specified in 3GPP TS 29.413.

[0435] In case the AMF has changed and the old AMF has indicated by the N3IWF, W-AGF or TNGF that the UE is in CM-CONNECTED state, and in case the new AMF and the old AMF are in the same PLMN, the new AMF creates a NGAP UE association towards the N3IWF / TNGF / W-AGF to which the UE is connected. This automatically releases the existing NGAP UE association between the old AMF and the N3IWF / TNGF / W-AGF.

[0436] Phase 19: N3IWF / TNGF / W-AGF transmits UE Context Modification Response to the new AMF.

[0437] Phase 19a: [Conditional] After the new AMF receives a response message from the N3IWF, W-AGF or TNGF in phase 19, the new AMF registers with the UDM using Nudm_UECM_Registration as in phase 14a, but the access type is set to "Non-3GPP Access". The UDM stores the associated access type with the serving AMF and does not remove the AMF identity associated with other access types (if any). The UDM can store the information provided during AMF registration in the UDR via Nudr_DM_Update.

[0438] Phase 19b: [Conditional] When the UDM stores the associated access type (e.g. non-3GPP) with the serving AMF as indicated in phase 19a, this phase shall cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2 of 3GPP TS 23.502) to the old AMF corresponding to the same (e.g. non-3GPP) access. The old AMF removes the UE context for the non-3GPP access.

[0439] Phase 19c: The old AMF uses Nudm_SDM_unsubscribe to unsubscribe the subscription data from UDM.

[0440] Phase 20a (not shown in FIG. 16 ): empty.

[0441] Phase 21: AMF returns NAS Registration Accept to the UE (e.g., as shown at 825 in Figure 8A). The details are: New AMF to UE: Registration Accept (5G-GUTI, Registration Area, [Mobility Restrictions], [PDU Session State], [Allowed NSSAI], [Mapping of Allowed NSSAI], [Configured NSSAI for Serving PLMN], [Mapping of Configured NSSAI], [NSSRG Information], [NSAG Information], [Rejected S-NSSAI], [Pending NSSAI], [Mapping of Pending NSSAI], [Periodic Registration Update Timer], [Active Time], [Strict Periodic Registration Timer Indication], [LADN Information], [Accepted MICO Mode], [Indication of Support for IMS Voice over PS Session]) ], [Emergency Services Support Indicator], [Accepted DRX parameters for E-UTRA and NR], [Accepted DRX parameters for NB-IoT], [Extended Idle Mode DRX parameters], [Paging Time Window], [Interworking Network Support without N26], [Access Stratum Connection Establishment NSSAI Including Mode], [Network Slice Subscription Change Indication], [Operator Defined Access Class Definition], [List of Equivalent PLMNs], [Enhanced Coverage Limited Information], [Supported Network Behaviors], [Service Gap Time], [PLMN Assigned UE Radio Capability ID], [PLMN Assigned UE Radio Capability ID Removal], [WUS Assistance Information], [AMF [PEIPS assistance information], [truncated 5G-S-TMSI configuration], [support connection release], [support paging cause indication for voice service], [support paging restriction], [support rejection of paging request], [paging restriction information acceptance / rejection], ["List of PLMNs to be used in disaster conditions"], [disaster roaming waiting range information], [disaster return waiting range information], [prohibited TAI], [list of equivalent SNPNs], [registered NID], [support unavailable period], [authorization for obtaining satellite coverage availability information]). The authorization for obtaining satellite coverage availability information included in the NAS registration acceptance may correspond to the authorization data described in 820 and 825 of Figure 8A.

[0442] In case the requested NSSAI does not include an S-NSSAI mapped to the S-NSSAI of the HPLMN subject to network slice specific authentication and authorization, and the AMF determines that the S-NSSAI cannot be provided among the allowed NSSAIs of the UE in the tracking area of ​​the current UE, and in case a default S-NSSAI that has not been involved in the current UE registration procedure cannot be further considered, the AMF may reject the UE registration and may include a list of rejected S-NSSAIs in the rejection message, each of them with an appropriate rejection cause value.

[0443] The allowed NSSAI for the UE's access type is included in the N2 message carrying the Registration Accept message. The allowed NSSAI contains only the S-NSSAIs that do not require network slice specific authentication and authorization based on the subscription information, and those S-NSSAIs for which network slice specific authentication and authorization have previously succeeded based on the UE context in the AMF, regardless of the access type. The mapping of pending NSSAIs is a mapping of each S-NSSAI in the pending NSSAI for the serving PLMN to the HPLMN S-NSSAI.

[0444] In case the UE has indicated its support for network slice specific authentication and authorization procedures in the UE MM Core Network Capabilities in the Registration Request, the AMF includes in the pending NSSAIs the S-NSSAI mapped to the S-NSSAI of the HPLMN (which has an indication in the subscription information that it is subject to network slice specific authentication and authorization) as described in clause 4.6.2.4 of 3GPP TS 24.501. In this case, the AMF may then trigger the network slice specific authentication and authorization procedures specified in clause 4.2.9.2 of 3GPP TS 23.502 at stage 25, except that, based on network policy, for those S-NSSAIs, network slice specific authentication and authorization has already been initiated on another access type for the same S-NSSAI. The UE may not attempt to re-register with the S-NSSAI included in the pending NSSAI list until the network slice specific authentication and authorization procedures have been completed, regardless of the access type.

[0445] In case the UE does not indicate its support for network slice specific authentication and authorization procedures in the UE 5GMM Core Network Capabilities in the Registration Request, and the requested NSSAI includes S-NSSAIs that map to HPLMN S-NSSAIs that are subject to network slice specific authentication and authorization, the AMF may include those S-NSSAIs in the requested NSSAIs among the rejected S-NSSAIs.

[0446] In the case where S-NSSAI cannot be provided in the allowed NSSAI because:

[0447] - All S-NSSAIs in the requested NSSAI will be subject to network slice specific authentication and authorization; or

[0448] - The requested NSSAI is not provided, or no S-NSSAI in the requested NSSAI matches any subscribed S-NSSAI, and all S-NSSAIs marked as default in the subscribed S-NSSAI will be subject to network slice specific authentication and authorization.

[0449] The AMF may provide an empty Allowed NSSAI. Upon receiving an empty Allowed NSSAI and a pending NSSAI, the UE registers in the PLMN but may wait for completion of network slice specific authentication and authorization procedures without attempting to use any services provided by the PLMN on any access, except for example emergency services (see 3GPP TS 24.501), until the UE receives the Allowed NSSAI.

[0450] The AMF stores the NB-IoT priority retrieved in stage 14 and associates it with the 5G-S-TMSI assigned to the UE.

[0451] In the event that the Registration Request message received over the 3GPP access does not include any paging restriction information, the AMF may delete any stored paging restriction information for the UE and stop restricting paging accordingly.

[0452] In the case where the registration request message received via 3GPP access includes paging restriction information, the AMF may accept or reject the paging restriction information requested by the UE based on the operator policy. In the case where the AMF rejects the paging restriction information, the AMF removes any stored paging restriction information from the UE context and discards the paging restriction information requested by the UE. In the case where the AMF accepts the paging restriction information from the UE, the AMF stores the paging restriction information from the UE in the UE context and notifies the UE of the acceptance / rejection of the requested paging restriction information in the registration accept message.

[0453] In the event that the registration request message received via the 3GPP access includes a release request indication, then:

[0454] - The AMF updates the UE context with any received paging restriction information and then performs the network triggered service request procedure as described in clause 4.2.3.3 of 3GPP TS 23.502;

[0455] - After the registration procedure is completed, the AMF does not establish user plane resources and triggers the AN release procedure as described in clause 4.2.6 of 3GPP TS 23.502.

[0456] The AMF transmits a Registration Accept message to the UE indicating that the registration request has been accepted. In the case where the AMF allocates a new 5G-GUTI, the 5G-GUTI is included. When a Registration Request message of type "Initial Registration", "Mobility Registration Update", "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update" is received from the UE, the AMF may include the new 5G-GUTI in the Registration Accept message. When a Registration Request message of type "Periodic Registration Update" is received from the UE, the AMF shall include the new 5G-GUTI in the Registration Accept message. In the case where the UE is already in the RM-REGISTERED state via another access in the same PLMN, the UE may use the 5G-GUTI received in the Registration Accept for two registrations. In the case where the 5G-GUTI is not included in the Registration Accept, the UE shall also use the 5G-GUTI assigned for the existing registration for the new registration. In the case where the AMF allocates a new registration area, it may transmit the registration area to the UE via the Registration Accept message. For disaster roaming registration, the AMF allocates a registration area limited to areas with disaster conditions as specified in clause 5.40 of 3GPP TS 23.501. In the event that the registration area is not included in the registration accept message, the UE may regard the old registration area as valid. In the event that mobility restrictions are applied to the UE and the registration type is not an emergency registration, mobility restrictions are included. The AMF indicates the established PDU session to the UE in the PDU session state. The UE locally removes any internal resources related to the PDU session that is not marked as established in the received PDU session state. In the event that the AMF calls the Nsmf_PDUSession_UpdateSMContext procedure for UP activation of the PDU session in stage 18 and receives a rejection from the SMF, the AMF indicates to the UE the PDU session ID and the reason why the user plane resources are not activated. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes any internal resources related to the PDU session that is not marked as established in the received PDU session state in the current PLMN. In case the PDU session status information is in the registration request, the AMF may indicate the PDU session status to the UE.

[0457] In the case where the RAT type is NB-IoT and the network is configured to use the control plane relocation indication procedure, the AMF may include in the Registration Accept message a truncated 5G-S-TMSI configuration used by the UE optimized using control plane CIoT 5GS to create a truncated 5G-S-TMSI, see clause 5.31.4.3 of 3GPP TS 23.501.

[0458] The allowed NSSAI provided in the Registration Accept is valid in the Registration Area and it applies to all PLMNs that have the tracking area of ​​the PLMN included in the Registration Area. The mapping of the allowed NSSAI is a mapping of each S-NSSAI in the allowed NSSAI to the HPLMN S-NSSAI. The mapping of the configured NSSAI is a mapping of each S-NSSAI in the configured NSSAI for the serving PLMN to the HPLMN S-NSSAI.

[0459] In case the UE has indicated in the UE 5GMM Core Network Capabilities its support for the subscription-based restriction of simultaneously registered network slices feature, the AMF includes (where available) the NSSRG information defined in clause 5.15.12 of 3GPP TS 23.501.

[0460] In the case where the UE has not indicated its support for subscription-based restriction of simultaneous registration of network slices feature and the subscription information for the UE includes NSSRG information and the AMF is providing the configured NSSAI to the UE, the configured NSSAI may include S-NSSAI in accordance with clause 5.15.12 of 3GPP TS 23.501.

[0461] In case the UE has indicated its support for the NSAG feature in the 5G MM Core Network Capabilities, the AMF includes (where available) the NSAG information defined in clause 5.15.14 of 3GPP TS 23.501.

[0462] The AMF may include in the Registration Accept message the LADN information of the list of LADNs available within the registration area determined by the AMF for the UE as described in clause 5.6.5 of 3GPP TS 23.501. The AMF may include the operator-defined access class definition to let the UE determine the applicable operator-specific access class definition as described in 3GPP TS 24.501.

[0463] In the case where the UE includes MICO mode in the Registration Request, the AMF responds in the Registration Accept message whether the MICO mode should be used. When the UE allows MICO mode, the AMF may include an active time value and / or a strict periodic registration timer indication in the Registration Accept message. The AMF determines the periodic registration update timer value, the active time value and the strict periodic registration timer indication based on local configuration, expected UE behavior (where available), UE indicated preferences, UE capabilities, UE subscription information and network policies or any combination thereof to achieve UE power saving, as described in clause 5.31.7 of 3GPP TS 23.501. In the case where the UE indicates its capability of strict periodic registration timer indication in the Registration Request message, the AMF determines that the strict periodic registration timer indication is applied to the UE as described in stage 1. In the case where the AMF provides the UE with a periodic registration update timer value with a strict periodic registration timer indication, the UE and the AMF start the periodic registration update timer after this stage, as described in clause 5.31.7.5 of 3GPP TS 23.501.

[0464] In case of registration on 3GPP access, the AMF sets the indication of support for IMS Voice over PS session as described in clause 5.16.3.2 of 3GPP TS 23.501. In order to set the indication of support for IMS Voice over PS session, the AMF may need to perform the UE Capability Match Request procedure in clause 4.2.8a to check the compatibility of the UE and NG-RAN radio capabilities related to IMS Voice over PS. In the event that the AMF does not receive the Voice Support Match Indicator from the NG-RAN in time, based on the specific implementation, the AMF may set the indication of support for IMS Voice over PS session and update the indication at a later stage.

[0465] In case of registration over 3GPP access and the AMF has retrieved or determined the target NSSAI and corresponding RFSP index according to local configuration in order to allow the NG-RAN to redirect the UE to a cell supporting a network slice that is not available in the current TA, the AMF provides the target NSSAI and corresponding RFSP index to the NG-RAN as described in clause 5.3.4.3.3 of 3GPP TS 23.501.

[0466] In case of registration on non-3GPP access, the AMF sets an indication of support for IMS Voice over PS session as described in clause 5.16.3.2a of 3GPP TS 23.501.

[0467] The Emergency Services Support Indicator informs the UE that emergency services are supported, i.e. the UE is allowed to request a PDU session for emergency services. In the case where the AMF receives "MPS Priority" as part of the Access and Mobility Subscription Data from the UDM based on operator policy, the "MPS Priority" is included in the Registration Accept message to the UE to inform the UE whether the configuration of Access Identity 1 is valid within the selected PLMN, as specified in 3GPP TS 24.501. In the case where the AMF receives "MCX Priority" as part of the Access and Mobility Subscription Data from the UDM based on operator policy and the UE's subscription to MCX services, the "MCX Priority" is included in the Registration Accept message to the UE to inform the UE whether the configuration of Access Identity 2 is valid within the selected PLMN, as specified in 3GPP TS 24.501. The Accepted DRX parameters are defined in clause 5.4.5 of 3GPP TS 23.501. In the case where the UE includes the requested DRX parameters for NB-IoT in the Registration Request message, the AMF includes the Accepted DRX parameters for NB-IoT. The AMF sets the interworking network support parameters without N26 as described in clause 5.17.2.3.1 of 3GPP TS 23.501. In case the AMF accepts the use of extended idle mode DRX, the AMF includes the extended idle mode DRX parameters and paging time window as described in clause 5.31.7.2 of 3GPP TS 23.501.

[0468] In cases where the UDM is intended to indicate to the UE that a subscription has changed, a network slice subscription change indication is included. In cases where the AMF includes a network slice subscription change indication, the UE may locally erase all network slice configurations for all PLMNs and, where applicable, update the configuration of the current PLMN based on any received information.

[0469] Include the Access Stratum Connection Establishment NSSAI Include Mode as specified in clause 5.15.9 of 3GPP TS 23.501 to instruct the UE what NSSAI to include in the Access Stratum Connection Establishment (where available). The AMF may set the value to operation modes a, b, c as defined in clause 5.15.9 of 3GPP TS 23.501 in 3GPP Access only if it is allowed to do so by including the NSSAI indication in the Allow RRC Connection Establishment.

[0470] For UEs registered in a PLMN, the AMF may provide a list of equivalent PLMNs that are handled as specified in 3GPP TS 24.501. The AMF may not provide a list of equivalent SNPNs to the UE.

[0471] For a UE registered in a SNPN and which has included support for equivalent SNPNs in stage 1, the AMF may provide a list of equivalent SNPNs that are handled as specified in 3GPP TS 24.501. The AMF may not provide a list of equivalent PLMNs to the UE.

[0472] In case the UE includes support for limiting the use of enhanced coverage in phase 1, the AMF transmits enhanced coverage limitation information to the NG-RAN in the N2 message. The AMF also transmits enhanced coverage limitation information to the UE in the Registration Accept message.

[0473] In the case where the UE receives the enhanced coverage limited information in the registration accept message, the UE may store the information and may use the value of the enhanced coverage limited information to determine whether the enhanced coverage feature should be used.

[0474] In case the UE and AMF have negotiated to enable MICO mode and the AMF uses the extended connection timer, the AMF provides the NG-RAN with the extended connection timer value at this stage (see clause 5.31.7.3 of 3GPP TS 23.501). The extended connection timer value indicates the minimum time that the RAN should keep the UE in RRC connected state (regardless of whether it is inactive).

[0475] In the case where the UE includes a preferred network behavior in its Registration Request, the AMF indicates in the Supported Network Behavior Information (see clause 5.31.2 of 3GPP TS 23.501) the CIoT 5GS optimizations that it supports and accepts.

[0476] The AMF may redirect the UE away from 5GC by rejecting the Registration Request. Before redirecting the UE away from 5GC, the AMF shall consider the preferred and supported network behaviors (see clause 5.31.2 of 3GPP TS 23.501) and the availability of EPC for the UE.

[0477] In case the AMF accepts MICO mode and is aware that there may be mobile station called data or signalling pending, the AMF maintains the N2 connection for at least the extended connection time as described in clause 5.31.7.3 of 3GPP TS 23.501 and provides the extended connection time value to the RAN.

[0478] The AMF includes the Service Gap Time in the case where it is present in the subscription information (stages 14a-c) or the Service Gap Time has been updated by the Subscriber Data Update Notification to AMF procedures (see clause 4.5.1 of 3GPP TS 23.502) and the UE has indicated the UE Service Gap Control capability.

[0479] In case the UE receives the service gap time in the Registration Accept message, the UE may store the parameter and apply the service gap control (see clause 5.31.16 of 3GPP TS 23.501).

[0480] In case the network supports WUS grouping (see 3GPP TS 23.501), the AMF may transmit WUS assistance information to the UE. In case the UE provides UE paging probability information in Phase 1, the AMF considers this information to determine the WUS assistance information.

[0481] In case the UE provides a paging subgroup support indication in stage 1, the supporting AMF may provide AMF PEIPS assistance information including the paging subgroup ID as defined in 3GPP TS 23.501.

[0482] When the UE and AMF support RACS as defined in clause 5.4.4.1a of 3GPP TS 23.501 and the AMF needs to configure the UE with the UE radio capability ID and the AMF has provided the UE with UE radio capabilities other than NB-IoT radio capabilities, the AMF may provide the UE with the UE radio capability ID of the UE radio capabilities returned to the AMF by the UCMF when performing the Nucmf_assign service operation for the UE. Alternatively, when the UE and AMF support RACS, the AMF may provide the UE with an indication to delete the UE radio capability ID assigned by any PLMN in the PLMN (see clause 5.4.4.1a of 3GPP TS 23.501).

[0483] In the case where the UE is "CAG capable" and the AMF needs to update the UE's CAG information, the AMF may include the CAG information as part of the mobility restriction in the Registration Accept message.

[0484] In the case where the UE has indicated support for unavailable periods, the AMF may indicate to the UE whether the corresponding feature is supported by providing an indication of support for unavailable periods.

[0485] In the case where the UE has provided the unavailable period duration in phase 1, the AMF may store the received unavailable period duration and consider the UE to be unreachable until the UE enters the CM-CONNECTED state. The AMF may provide a periodic registration update timer based on the unavailable period duration indicated by the UE, as described in clause 5.4.1.4 of 3GPP TS 23.501.

[0486] In the case where the multi-USIM UE has indicated support for one or more multi-USIM specific capabilities in the UE 5GMM core network capabilities in stage 1, the AMF may indicate to the multi-USIM UE whether the corresponding one or more multi-USIM specific features described in clause 5.38 of 3GPP TS 23.501 are supported, based on the network capabilities and preferences of the network (i.e. based on local network policies), by providing one or more of the paging cause indication of support for connection release, support for voice services, support for paging restriction and rejection of support for paging request indication. The AMF may only indicate support for paging restriction and support for connection release or rejection of support for paging request. The UE may only use the multi-USIM specific features indicated by the AMF as supported.

[0487] In the case where the UE and AMF support disaster roaming services, the AMF may include the "List of PLMNs to be used under disaster conditions", disaster roaming waiting range information and disaster return waiting range information as specified in 3GPP TS 23.501.

[0488] In the event that the AMF receives multiple TAIs from the NG-RAN in Phase 3 and determines that some but not all of them are subscribed or prohibited by operator policy, the AMF may include the prohibited TAIs in the Registration Accept message.

[0489] In case of Emergency Registration, the AMF may not indicate support of any multi-USIM specific features to the UE.

[0490] In the case where the UE has included support for equivalent SNPNs in Phase 1 and the serving SNPN changes, the AMF may include the registered NID in the Registration Accept message as specified in 3GPP TS 23.501.

[0491] In the case where the registration is for NR satellite access, and in the case where the UE includes an authorization request for obtaining satellite coverage availability information in the NAS Registration Request in stage 1, and in the case where the UDM has indicated in stage 14b that the UE has subscribed to the authorization for obtaining satellite coverage availability information, the AMF may include the authorization for obtaining satellite coverage availability information in the NAS Registration Accept transmitted in stage 21. The included authorization may be provided to the AMF by the UDM in stage 14b. Alternatively, the included authorization may be determined by the AMF (e.g., as described with respect to 820 in Figure 8A). The authorization may indicate an external server (e.g., which may include a URI, IP address, or FQDN of the external server), a user plane transport protocol (e.g., HTTP, HTTPS, or SMS), and a temporary identifier of the UE that may be authenticated by the external server. The authorization may also include the type of satellite coverage data that can be obtained and the period during which the UE can obtain such data from the external server. The authorization may be as described with respect to the authorization data in Figure 8A.

[0492] Phase 21b: [Optional] The new AMF performs UE policy association establishment as defined in clause 4.16.11 of 3GPP TS 23.502. For emergency registration, this phase is skipped.

[0493] The new AMF transmits an Npcf_UEPolicyControl create request to the PCF. The PCF transmits an Npcf_UEPolicyControl create response to the new AMF.

[0494] The PCF triggers the UE configuration update procedure as defined in clause 4.2.4.3 of 3GPP TS 23.502.

[0495] Phase 22: [Conditional] UE to new AMF: Registration Complete ().

[0496] When the UE successfully updates itself after receiving any of the [Configured NSSAI for Serving PLMN], [Mapping of Configured NSSAI], [NSSRG information], [NSAG information] and Network Slice Subscription Change Indication or CAG information in Phase 21, the UE transmits a Registration Complete message to the AMF.

[0497] The UE transmits a Registration Complete message to the AMF to confirm whether the new 5G-GUTI is assigned.

[0498] In the case where a new 5G-GUTI is assigned, when the lower layers (3GPP access or non-3GPP access) indicate to the UE's RM layer that the registration complete message has been successfully transferred over the radio interface, the UE passes the new 5G-GUTI to the lower layers of its 3GPP access.

[0499] Note 13: The above is necessary because the NG-RAN may use the RRC Inactive state and part of the 5G-GUTI is used to calculate the paging frame (see 3GPP TS 38.304 and 3GPP TS 36.304). It is assumed that the Registration Complete is reliably delivered to the AMF after the 5G-AN confirms its receipt to the UE.

[0500] When the list of PDU sessions to be activated is not included in the Registration Request and the Registration procedure is not initiated in the CM-CONNECTED state, the AMF releases the signalling connection with the UE according to clause 4.2.6 of 3GPP TS 23.502.

[0501] When a Follow-up Request is included in a Registration Request, the AMF shall not release the signalling connection after the registration procedure is completed.

[0502] In the case where the AMF knows that some signalling is pending in the AMF or between the UE and the 5GC, the AMF shall not release the signalling connection immediately after completing the registration procedure.

[0503] In case the UE has provided the duration of the unavailable period in Phase 1, the AMF may release the signalling connection immediately after completing the registration procedure.

[0504] In case stage 21 includes the UE radio capability ID assigned by the PLMN, then upon receiving the registration complete message, the AMF stores the UE radio capability ID assigned by the PLMN in the UE context.

[0505] In case the UE receives a PLMN-assigned UE radio capability ID deletion indication in stage 21, the UE may delete the PLMN-assigned UE radio capability ID for the PLMN.

[0506] Phase 23: [Conditional] AMF to UDM: In case the access and mobility subscription data provided by the UDM to the AMF in 14b includes roaming steering information with an indication that the UDM requests confirmation of receipt of the information from the UE, the AMF uses Nudm_SDM_Info to provide the UE confirmation to the UDM. For more details on the handling of roaming steering information, refer to 3GPP TS 23.122.

[0507] Phase 23a: For registration on 3GPP access, the AMF transmits RRC Inactive Assistance Information to the NG-RAN without releasing the signalling connection.

[0508] For registration on non-3GPP access, the AMF transmits RRC Inactive Assistance Information to the NG-RAN in case the UE is also in CM-CONNECTED state on 3GPP access. In case the multi-USIM UE has indicated support for Paging Cause Indication for Voice Services feature and the network supports Paging Cause Indication for Voice Services, the AMF may include in the RRC Inactive Assistance Information an indication that the UE supports Paging Cause Indication for Voice Services directed to the NG-RAN, to enable the NG-RAN to apply the Paging Cause Indication for Voice Services feature for RAN-based paging.

[0509] The AMF also uses the Nudm_SDM_Info service operation to provide the UDM with confirmation that the UE received the CAG information or network slice subscription change indication (see stage 21 and stage 22) and acts on it.

[0510] Phase 24: [Conditional] AMF to UDM: After phase 14a and in parallel with any of the preceding phases, the AMF may transmit a "Homogeneous support for IMS Voice over PS sessions" indication to the UDM using Nudm_UECM_Update:

[0511] - in case the AMF has evaluated support for IMS Voice over PS sessions, see clause 5.16.3.2 of 3GPP TS 23.501, and

[0512] - In case the AMF determines that it needs to update the homogeneous support for IMS Voice over PS sessions, see clause 5.16.3.3 of 3GPP TS 23.501.

[0513] Phase 25: [Conditional] In case the UE indicates its support for network slice specific authentication and authorization procedures in the UE MM Core Network Capabilities in the Registration Request and any S-NSSAI of the HPLMN is subject to network slice specific authentication and authorization, the relevant procedures are performed in this phase (see clause 4.2.9.1 of 3GPP TS 23.502). Once the network slice specific authentication and authorization procedures are completed for all S-NSSAIs, the AMF may trigger the UE Configuration Update procedure to deliver the allowed NSSAIs which also include the S-NSSAI for which the network slice specific authentication and authorization was successful and include any rejected NSSAI with an appropriate rejection cause value.

[0514] The AMF stores in the UE context an indication of any S-NSSAI for the HPLMN that was subject to network slice specific authentication and authorization and for which the network slice specific authentication and authorization was successful.

[0515] Once the network slice specific authentication and authorization procedures are completed, in the event that the AMF determines that an S-NSSAI cannot be provided among the allowed NSSAIs for a UE that has been successfully authenticated and authorized by the PLMN, and in the event that a default S-NSSAI cannot be further considered, the AMF may perform the network-initiated deregistration procedure described in clause 4.2.2.3.3 of 3GPP TS 23.502 and may include a list of rejected S-NSSAIs, each of which has an appropriate rejection cause value, in the explicit deregistration request message.

[0516] Stage 26: (not shown in Figure 13) [Conditional] In the event that the UE has requested authorization for obtaining satellite coverage availability information in stage 1, and in the event that the authorization for obtaining satellite coverage availability information is included in the NAS Registration Accept received in stage 21, the UE may obtain satellite coverage availability information from an external server indicated by the authorization for obtaining satellite coverage availability information, for example as described for Figure 8B.

[0517] In case an Unavailable Period Duration is received from the UE and there is a "Connectivity Loss" monitoring event subscription for the UE, the AMF triggers a "Connectivity Loss" monitoring event report and includes the remaining value of the Unavailable Period Duration as described in clause 4.15 of 3GPP TS 23.502.

[0518] For the case as described in clause 4.15.4 of 3GPP TS 23.502, a mobility-related event notification towards the NF consumer is triggered at the end of this procedure.

[0519] As previously described, embodiments herein provide techniques in which a UE may indicate that the UE is unavailable due to different types of events that may prevent the UE from accessing a wireless network, such as discontinuous satellite coverage (which may be referred to as "satellite discontinuous coverage") or UE power saving in combination with discontinuous satellite coverage. UE power saving in combination with discontinuous satellite coverage refers to a power saving period of the UE that includes one or more periods of (expected) no satellite coverage. The UE may then determine a preferred unavailability period that starts at or before a first period of no satellite coverage and ends after that period and possibly after a subsequent period of no satellite coverage has ended and therefore during a period of satellite coverage. The network (e.g., AMF or MME) may then not need to know the details of the one or more periods of no satellite coverage and may only support a single overall period of UE unavailability. In the case where the UE instead indicates unavailability for each individual period of no satellite coverage, the UE power saving may be much less (e.g., due to reporting each individual period of no satellite coverage), and the network (AMF or MME) may need to process a much larger number of individual unavailability reports and associated individual unavailability periods.

[0520] It may be noted that while the examples provided below and in the accompanying drawings may describe the use of AMF (e.g., in a 5G NR network), embodiments are not limited thereto. For example, embodiments may additionally or alternatively use MME (e.g., in a 4G LTE network) instead of AMF and / or components having functionality similar to AMF or MME.

[0521] To support reporting of generalized unavailability periods (also referred to simply as "unavailability periods"), a UE (e.g., UE 115) may determine an upcoming unavailability period based on one or more of: data on satellite coverage availability indicating one or more upcoming coverage gaps, a power saving requirement of the UE, a known or expected software (SW) upgrade to the UE or to a USIM in the UE, a patch or reboot of the UE, some other event resulting in network unavailability or UE unavailability, or some combination thereof. The UE may then indicate the unavailability period to an AMF (e.g., AMF 122) in a registration update request or to an MME in a TAU request.

[0522] According to some embodiments, the UE may also indicate one or more events that caused the unavailability. The indication of events may be useful, for example, for data analysis, although may not necessarily affect the support of the AMF or MME. The AMF or MME may then set the UE's periodic registration or TAU timer to a value equal to or slightly greater than the unavailability period provided by the UE. During this unavailability period, the AMF or MME may maintain the UE context in a CM-IDLE or ECM-IDLE state, and the UE may be considered unreachable. According to some embodiments, the AMF or MME may use the functionality of high latency communication (HLCom) to buffer the UE's incoming data, or the AMF or MME may use functionality applicable to mobile initiated connection only (MICO) mode or power saving mode (PSM), respectively (for example, for very long unavailability periods).

[0523] When the unavailability period ends or in the event that the UE becomes available before the unavailability is expected to end (e.g., in the event that the UE obtains satellite access or access using a TN RAT before the satellite coverage gap is expected to end), the UE may trigger a registration update or TAU and may not provide an indication of the unavailability period. The AMF or MME may then provide the UE with a normal periodic registration or TAU timer (e.g., a timer that does not reflect the unavailability period). In the event that the UE is now using a different RAT, the context in the previous AMF or MME may be transferred.

[0524] In the event that the UE is aware that the unavailability period will change (e.g., where the start time, end time and / or duration may change) and the unavailability period has not yet started, the UE may trigger a registration update or TAU and provide the details of the new unavailability period to the AMF or MME. The AMF or MME may then provide the UE with a modified periodic registration or TAU timer suitable for the changed unavailability period.

[0525] When the unavailable period ends at the expected time and is due to an event common to many UEs (e.g., discontinuous satellite coverage), the UE may delay the transmission of the registration update or TAU by a time delay (e.g., a random time delay) indicated by the MME or AMF, if requested by the MME or AMF. In some embodiments, the time delay may be small (e.g., 1 minute or less in the case of discontinuous satellite coverage), and may avoid a large number of UEs transmitting registration updates or TAUs at the same time, which may otherwise cause network congestion.

[0526] When the unavailability is due to lack of satellite coverage, the procedure may be used for longer unavailability periods to reduce additional signaling. For shorter periods of no satellite coverage (e.g., 5 minutes or less), the UE may not need to notify the core network (CN) (e.g., AMF in 5GCN) in order to reduce network load and signaling. The lack of coverage may then be handled by the CN in the same way as a temporary loss of coverage of the TN, which may result in some failed paging attempts but not in deregistration of the UE. The serving PLMN (e.g., serving AMF or MME) may also indicate to the UE (e.g., in a registration accept message or an attach accept message) the minimum period of lack of satellite coverage, or the minimum unavailability period caused by any event for which the procedure should be used, and that the procedure should not be used for shorter periods.

[0527] FIG. 14 shows a procedure 1400 performed by the UE 115 and the AMF 122 to support a generalized UE unavailable period for NR satellite access. The procedure for LTE or NB-IoT satellite access would be similar. A procedure similar to procedure 1400 may be used for EPS, where the initial registration is replaced by the initial attach and the registration for unavailability is replaced by the TAU. Referring to FIG. 14 , the enumeration phase of procedure 1400 is discussed below.

[0528] Phase 1: During the initial registration procedure, the UE 115 may transmit a NAS Registration Request message to the AMF 122, which includes an indication that the UE 115 supports "generalized unavailable period" or only "unavailable period". The AMF 122 may then return a NAS Registration Accept message to the UE 115 and may indicate in the Registration Accept whether the AMF 122 also supports "generalized unavailable period" or "unavailable period". The AMF 122 may also indicate in the Registration Accept the minimum unavailable period that needs to be notified according to phases 2 to 4. For an unavailable period shorter than this, the UE 115 may not notify the AMF 122 (e.g., phases 3 to 7 may not be initiated).

[0529] Phase 2: UE 115 may determine the period of impending unavailability based on the event causing the unavailability, such as: satellite coverage unavailability, power saving requirements (when combined with satellite unavailability), SW upgrade or reboot of UE 115, or some other event. The determination of unavailability may depend on the specific implementation, and it may be assumed that UE 115 has the necessary data to make the determination (e.g., in the case of satellite coverage unavailability, UE 115 has satellite coverage data).

[0530] Phase 3: UE 115 may transmit a NAS registration request message indicating an unavailable period to AMF 122 at some time before the unavailability begins and may indicate one or more events that caused the unavailability. In some embodiments, the registration request may be a mobility registration request or a periodic registration request. UE 115 may include the start time of the unavailable period, the end time of the unavailable period, and / or the duration of the unavailable period in the registration request. It should be noted that UE 115 may implicitly indicate the end time of the unavailable period by including the start time and duration of the unavailable period. In the event that the UE does not include the start time of the unavailable period, AMF 122 may assume that the unavailable period will start at the current time or immediately after UE 115 enters the IDLE state.

[0531] In some embodiments, in phase 3 and when the unavailable period is due to a satellite coverage gap, the UE 115 may transmit a NAS Registration Request message to the AMF 122 at a time interval T (e.g., 0 to 5 minutes) before the unavailable period will start. This may avoid overloading the AMF 122 when other UEs in the same local area as the UE 115 also transmit similar registration requests to the AMF 122 for the same satellite coverage gap. The time interval T may be randomized by the UE 115 so that it is different from other similar time intervals used by other UEs. For example, the AMF 122 may transmit a maximum time interval Tmax to the UE 115 in the Registration Accept of phase 1, and the UE 115 may set the time interval T to a random time interval between zero and the maximum time interval Tmax.

[0532] Phase 4: AMF 122 may respond by transmitting a NAS Registration Accept message to UE 115. AMF 122 may indicate in the NAS Registration Accept a periodic registration timer having a value equal to or slightly greater than the duration of the unavailable period provided by the UE. For events common to many UEs (e.g., discontinuous satellite coverage), AMF 122 may indicate to UE 115 a time delay (e.g., fixed or random) for re-accessing the PLMN. AMF 122 may also indicate in the Registration Accept whether UE 115 is required to transmit a registration update after the unavailable period ends (as in phase 6). In the event that the start time, end time, or duration of the unavailable period of UE 115 changes, and in the event that a new unavailable period has not yet begun,...

Claims

1. A method performed by a user equipment (UE) for indicating a generalized unavailability period to a wireless network, the method comprising: transmitting a reporting capability to a network entity of the wireless network, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailability period to the wireless network for a plurality of different events, wherein the generalized unavailability period includes a time period during which the UE does not have wireless communication access to the wireless network; after transmitting the reporting capability, determining an upcoming period of unavailability for the UE due to one or more of the plurality of events; as well as In response to determining the upcoming unavailability period, an unavailability period report is transmitted to the network entity of the wireless network, wherein the unavailability period report is transmitted prior to the unavailability period and indicates the unavailability period.

2. The method of claim 1 , further comprising transmitting a registration update or a tracking area update to the network entity of the wireless network after the UE detects one of the following events: the end of the unavailability period, or Modification or cancellation of the unavailability period before the unavailability period begins.

3. The method of claim 1 , further comprising including in the unavailability period report an indication of at least one of: the one or more of the plurality of events causing the period of unavailability, the start time of the unavailable period, the duration of the unavailability period, the end time of the unavailability period, or Some combination of them.

4. The method of claim 1, wherein the plurality of different events comprises at least one of: Satellite coverage is unavailable, Power saving events, software upgrade of the UE, a reboot of the UE, or Some combination of them. 5 . The method of claim 1 , wherein the network entity of the wireless network comprises an access and mobility management function (AMF) or a mobility management entity. 6 . The method of claim 1 , wherein the unavailable period report is included in a non-access stratum (NAS) registration request or a NAS tracking area update (TAU) request.

7. The method of claim 6, further comprising receiving a NAS Registration Accept or a NAS TAU Accept from the network entity of the wireless network, wherein the NAS Registration Accept or the NAS TAU Accept comprises a periodic registration timer or a periodic TAU timer that is equal to or greater than a duration of the unavailable period.

8. The method of claim 1, wherein the one or more of the plurality of events comprises a satellite coverage unavailable event, and the method further comprises transmitting the unavailable period report to the network entity at a time interval before the unavailable period will begin, wherein the time interval is random.

9. The method according to claim 8, further comprising: receiving a maximum time interval from the network entity; as well as The time interval is determined to be a random time interval between zero and the maximum time interval.

10. A method performed by a network entity of a wireless network for enabling indication of a generalized unavailability period of a user equipment (UE) to the wireless network, the method comprising: receiving a reporting capability from the UE, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailability period to the wireless network for a plurality of different events, wherein the generalized unavailability period includes a time period during which the UE does not have wireless communication access to the wireless network; receiving, after receiving the reporting capability, an unavailability period report from the UE, wherein the unavailability period report is received prior to an upcoming unavailability period of the UE and indicates the unavailability period; as well as In response to receiving the unavailable period report, at least one message is transmitted to the UE, wherein the at least one message indicates a periodic registration timer or a periodic tracking area update (TAU) timer having a value equal to or greater than a duration of the unavailable period.

11. The method of claim 10, further comprising receiving, from the UE, a registration update or a tracking area update indicating one of the following events: the end of the unavailability period, or Modification or cancellation of the unavailability period before the unavailability period begins.

12. The method of claim 10, wherein the unavailable period report includes an indication of at least one of: the one or more of the plurality of events causing the period of unavailability, the start time of the unavailable period, the duration of the unavailability period, the end time of the unavailability period, or Some combination of them.

13. The method of claim 10, wherein the plurality of different events comprises at least one of: Satellite coverage is unavailable, Power saving events, software upgrade of the UE, a reboot of the UE, or Some combination of them.

14. The method of claim 10, wherein the network entity of the wireless network comprises an access and mobility management function (AMF) or a mobility management entity.

15. The method of claim 10, wherein the unavailable period report is included in a non-access stratum (NAS) registration request or a NAS TAU request.

16. The method of claim 15, wherein the at least one message comprises a NAS Registration Accept or a NAS TAU Accept.

17. A user equipment (UE) capable of indicating a generalized unavailability period to a wireless network, the UE comprising: one or more transceivers; one or more memories; and one or more processors communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to: transmitting, via the one or more transceivers, a reporting capability to a network entity of the wireless network, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailability period to the wireless network for a plurality of different events, wherein the generalized unavailability period includes a time period during which the UE does not have wireless communication access to the wireless network; after transmitting the reporting capability, determining an upcoming period of unavailability for the UE due to one or more of the plurality of events; as well as In response to determining the upcoming unavailability period, transmitting an unavailability period report to the network entity of the wireless network via the one or more transceivers, wherein the unavailability period report is transmitted prior to the unavailability period and indicates the unavailability period.

18. The UE of claim 17, wherein the one or more processors are further configured to transmit a registration update or a tracking area update to the network entity of the wireless network after the UE detects one of the following events: the end of the unavailability period, or Modification or cancellation of the unavailability period before the unavailability period begins.

19. The UE of claim 17, wherein the one or more processors are further configured to include in the unavailability period report an indication of at least one of: the one or more of the plurality of events causing the period of unavailability, the start time of the unavailable period, the duration of the unavailability period, the end time of the unavailability period, or Some combination of them.

20. The UE of claim 17, wherein the plurality of different events comprises at least one of the following: Satellite coverage is unavailable, Power saving events, software upgrade of the UE, a reboot of the UE, or Some combination of them.

21. The UE of claim 17, wherein the one or more processors are further configured to include the unavailable period report in a non-access stratum (NAS) registration request or a NAS tracking area update (TAU) request.

22. The UE of claim 21, wherein the one or more processors are further configured to receive a NAS Registration Accept or a NAS TAU Accept from the network entity of the wireless network, wherein the NAS Registration Accept or NAS TAU Accept includes a periodic registration timer or a periodic TAU timer that is equal to or greater than a duration of the unavailable period.

23. The UE of claim 17, wherein the one or more of the plurality of events comprises a satellite coverage unavailable event, and the method further comprises transmitting the unavailable period report to the network entity at a time interval before the unavailable period will begin, wherein the time interval is random.

24. The UE of claim 23, wherein the one or more processors are further configured to: receiving a maximum time interval from the network entity; and The time interval is determined to be a random time interval between zero and the maximum time interval.

25. A network entity for a wireless network for enabling indication of a generalized period of unavailability of a user equipment (UE) to the wireless network, the network entity comprising: one or more transceivers; one or more memories; and one or more processors communicatively coupled to the one or more transceivers and the one or more memories, wherein the one or more processors are configured to: receiving, via the one or more transceivers, a reporting capability from the UE, wherein the reporting capability indicates that the UE is capable of reporting a generalized unavailability period to the wireless network for a plurality of different events, wherein the generalized unavailability period includes a time period during which the UE does not have wireless communication access to the wireless network; receiving, after receiving the reporting capability, an unavailability period report from the UE, wherein the unavailability period report is received prior to an upcoming unavailability period of the UE and indicates the unavailability period; as well as In response to receiving the unavailable period report, transmitting at least one message to the UE via the one or more transceivers, wherein the at least one message indicates a periodic registration timer or a periodic tracking area update (TAU) timer having a value equal to or greater than a duration of the unavailable period.

26. The network entity of claim 25, wherein the one or more processors are further configured to receive, from the UE, a registration update or a tracking area update indicating one of the following events: the end of the unavailability period, or Modification or cancellation of the unavailability period before the unavailability period begins.

27. The network entity of claim 25, wherein the unavailability period report comprises an indication of at least one of: the one or more of the plurality of events causing the period of unavailability, the start time of the unavailable period, the duration of the unavailability period, the end time of the unavailability period, or Some combination of them.

28. The network entity of claim 25, wherein the plurality of different events comprises at least one of: Satellite coverage is unavailable, Power saving events, software upgrade of the UE, a reboot of the UE, or Some combination of them.

29. The network entity of claim 25, wherein the network entity of the wireless network comprises an access and mobility management function (AMF) or a mobility management entity.

30. The network entity of claim 25, wherein the unavailable period report is included in a non-access stratum (NAS) registration request or a NAS TAU request.

Citation Information

Patent Citations

  • Systems and methods for reporting a generalized unavailability period for access to a wireless network

    US20230362704A1