Satellite data collection and NTN coverage analysis estimation method

Abstract

The network entity (116) generates (1320) an analysis estimate of NTN coverage associated with the UE (102) based on the satellite-related information, the UE-related information, and the UE-related analysis. A network entity may perform a network data analysis function that generates a UE-related analysis. A network entity may obtain satellite-related information and UE-related information from various network functions, base stations, and / or UEs. The network entity outputs (1330) the analysis estimate of NTN coverage to a network function of the user equipment (102), the base station (104), or the core network (110).

Description

Technical Field

[0001] This document generally describes communication methods related to devices communicating using non-terrestrial networks (NTNs) and more specifically to techniques for satellite data collection and NTN coverage analysis. Background Art

[0002] This background section generally introduces the context of the improvement. The work of the presently named inventors, to the extent it is described in this section, and aspects of the specification that otherwise might not have been prior art at the time of filing, are neither explicitly nor implicitly admitted to be prior art.

[0003] User Equipment (UE), which is a device that enables (mobile) users to access network services, disconnects from the Radio Access Network (RAN) when out of RAN coverage. The RAN provides services to UEs located within a cell associated with the RAN. Depending on the location and subscription of the UE, it can connect to different networks, such as the Home Public Land Mobile Network (HPLMN) (where the user's profile is saved), the Visited PLMN (VPLMN) (when roaming), etc. Even within a RAN cell, if the UE and RAN do not use the same Radio Access Technology (RAT), the obstacle to UE connectivity may be the RAT.

[0004] UEs located in terrestrial cells are served by terrestrial network entities without using NTN. Terrestrial cells are associated with fixed areas, and UEs in such cells are able to be continuously connected to the RAN. NTN cells that provide services via satellite may be associated with different areas at different times due to the evolution of the position of the satellite relative to the surface of the earth. Therefore, UEs that can only be connected to the RAN via satellite may experience discontinuous coverage due to "mobile" NTN cells, that is, the UE experiences a period of time during which it cannot connect and communicate with the RAN via satellite. For example, the UE may be able to connect to the RAN via satellite during a 20-minute in-coverage period every 10 hours. The Mobility Management Entity (MME) may take NTN coverage into account when issuing commands and configurations (e.g., due to the remote location of the UE) that can only be connected to the RAN via satellite (e.g., for mobility management, power saving, etc.).

[0005] The UE may receive satellite-related ephemeris data from the RAN (e.g., the ephemeris data may be broadcast via a system information block such as a SIB19 information element (IE), which includes an ntn-Config field described in the 3GPP technical specification) and / or other satellite assistance information. The UE may use such satellite-related information to evaluate satellite coverage (i.e., in-coverage periods and out-of-coverage periods) in an area of ​​interest where the UE is or will be located. The UE may implement a timer to measure out-of-coverage periods during a dedicated (AS) idle mode.

[0006] There is room for improvement and demand for the perception of NTN coverage by UEs, base stations, and core network entities. The broadcasted ephemeris data associated with a few neighboring cells provides limited NTN coverage. UEs that communicate only via satellites (i.e., non-terrestrial networks (NTNs)) may be temporarily unable to communicate due to discontinuous NTN coverage. UEs and various network entities may attempt to predict NTN coverage individually and share their estimates of the UE's out-of-coverage period based on satellite ephemeris information and the UE's location. However, the ability of individual devices to collect information and accurately assess NTN coverage is limited, and attempts to enhance local estimates may generate a certain amount of unnecessary overhead. Summary of the invention

[0007] A dedicated network entity (NE) generates and outputs an analysis estimate of NTN coverage associated with a UE based on satellite-related information, user equipment (UE)-related information, and UE-related analysis. The NE may execute a network data analysis function (NWDAF) (as defined in the 3GPP technical specification) that generates UE-related analysis. The analysis estimate of NTN coverage may include NTN coverage periods and / or coverage-out periods for an area of ​​interest, which may be associated with a validity period, a confidence metric, and a list of one or more of subscribers associated with the analysis estimate of NTN coverage.

[0008] The NE may obtain satellite related information from (A) an operation, administration and maintenance function (OAM), (B) a next generation radio access network (NG-RAN) node and / or (C) an application function (AF). The NE may output an estimate of NTN coverage to a network function such as an access and mobility management function (AMF) for delivery to a UE or NG-RAN node. The output of the analysis estimate of NTN coverage may occur periodically or may be triggered by an event. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments and, together with the description, explain these embodiments.

[0010] Figure 1is a block diagram of a wireless communication system according to an embodiment, the wireless communication system comprising a user equipment (UE) and a network entity (NE) configured to generate and use an analysis estimate of non-terrestrial network (NTN) coverage in an area of ​​interest (AOI).

[0011] Figure 2 is through Figure 1 Schematic representation of the communication between the UE and the NE via satellite.

[0012] Figure 3 It is shown Figure 1 Diagram of discontinuous NTN coverage for UE in .

[0013] Figure 4 is an input / output representation of a NE (eg, a network analysis data function (NWADF)) configured to generate an analytical estimate of NTN coverage in an AOI according to an embodiment.

[0014] Figure 5A , Figure 5B and Figure 5C It is shown Figure 4 Block diagram of the NE for collecting satellite data.

[0015] Figure 6 is a signal diagram illustrating a NE (eg, NWDAF) subscribing to a client (eg, Operations, Administration, Maintenance (OAM)) to receive an analytical estimate of NTN coverage in an AOI according to an embodiment.

[0016] Figure 7 is a signal diagram illustrating a first satellite data acquisition scenario according to an embodiment.

[0017] Figure 8 is a signal diagram illustrating a process for collecting satellite related data from an application function (AF) according to an embodiment.

[0018] Fig. 9 is a signal diagram of a process for data collection from a NF according to an embodiment.

[0019] Fig.10 is a signal diagram of a process performed by a NE to provide an analytical estimate of NTN coverage in an AOI to a customer network function (NF) according to an embodiment.

[0020] Fig.11 is a signal diagram of a process performed by a NE to provide an analytical estimate of NTN coverage in an AOI to a NG-RAN node according to an embodiment.

[0021] Fig.12 is a signal diagram of a process performed by a NE to provide an analytical estimate of NTN coverage in an AOI to a UE according to an embodiment.

[0022] Fig.13 is a flow chart of a method for providing analytical estimation of NTN coverage according to an embodiment. DETAILED DESCRIPTION

[0023] The methods and network entities described in this section perform various techniques for satellite-related data collection and NTN coverage analysis estimation.

[0024] Figure 1 1 is a block diagram of a wireless communication system according to an embodiment, the wireless communication system including UEs and NEs configured to generate an analysis estimate of NTN coverage in an area of ​​interest (AOI). The wireless communication system 100 includes a UE 102, an NTN base station 104 communicating with the UE 102 via a satellite, another base station 106, and a core network (CN) 110. The base stations 104 and 106 operate in a radio access network (RAN) 105 connected to the CN 110. Figure 1 In the present invention, CN 110 includes 5G core functions and is therefore a 5G core (5GC), but it can also be implemented as a sixth generation core (6GC) or an LTE core.

[0025] NTN base station 104 provides services for UEs within cell 124, and base station 106 provides services for UEs within cell 126. If base station 104 and / or 106 are gNBs, cells 124 and / or 126 are new radio (NR) cells, respectively. If base station 104 and / or 106 are ng-eNBs or eNBs, cells 124 and / or 126 are evolved universal terrestrial radio access (E-UTRA) cells. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 includes any number of base stations, and each of the base stations covers one, two, three, or any other suitable number of cells (i.e., provides services for the UEs therein). UE 102 supports at least one of 5G NR (or simply "NR") or E-UTRA air interfaces to communicate with one or both of base stations 104 and 106. Each of the base stations 104, 106 is connected to the 5GC 110 via an interface (e.g., an S1 or NG interface). The base stations may also be interconnected via an interface (e.g., an X2 or Xn interface for interconnecting NG RAN nodes).

[0026] 5G CN 110 may be hosted by one or more physical devices that may be co-located. In this document, base stations and physical devices that host core network functions / modules may be referred to as network entities (NEs), but more generally, the term "network entity" represents a RAN device with well-defined network functionality (e.g., base station functionality is to connect the UE to the core network, including managing communications to and from the UE). Among other components, 5GC 110 includes operations, administration, and maintenance (OAM) 111, network functions (NFs) 112, policy control functions (PCFs) 113, unified data management (UDM) 114, access and mobility management functions (AMFs) 115, network data analysis functions (NWDAFs) 116, application functions (AFs) 117, network repository functions (NRFs) 118, network open functions (NEFs) 119, and session management functions (SMFs) 120. OAM 111 acts as an intermediary for one or more NEs and manages them. NF 112 represents a core network function that is not explicitly specified. PCF 113 is a function that provides policy rules to the control plane function. UDM 114 performs subscription management. AMF 164 is configured to manage UE authentication, registration, paging and other similar functions. NWDAF 116 is configured for analysis functions for various types of data. AF 117 is configured to influence application service routing. NRF 118 is configured to allow NF to register network services. NEF 119 is configured to provide secure and robust access to the open part of the network, and SMF 120 is configured to manage packet data unit (PDU) sessions.

[0027] like Figure 1 As shown, base station 104 supports cell 124 (i.e., covers UEs therein, provides services for UEs therein), and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 selects, reselects, or switches from one of cells 124 and 126 to the other. In order to exchange messages or information directly, base station 104 and base station 106 support X2 or Xn interfaces. In general, 5GC core network 110 is connected to any suitable number of base stations supporting NR cells and / or EUTRA cells using, for example, S1 or NG interfaces.

[0028] As discussed in detail below, UE 102 and / or NE of RAN 105 (e.g., BS 104 and / or 106) can utilize the techniques described in this section for enhanced NWDAF analysis to support estimation of NTN out-of-coverage events and NTN in-coverage events for UE 102.

[0029] The base station 104 is equipped with processing hardware 130, which includes one or more general-purpose processors (e.g., CPUs) 132 and a non-transitory computer-readable medium (CRM) 134 storing instructions executed by the one or more general-purpose processors. In addition or alternatively, the processing hardware 130 may include a dedicated processing unit. The processor 132 is configured to process data received in the uplink direction or sent in the downlink direction by the base station 104 according to the various techniques described in this section. The processing hardware 130 also includes a transceiver 136 (the term here also represents antennas and RF front-end electronic devices not shown separately in this figure), which is configured to send data in the downlink direction and receive data in the uplink direction. The base station 106 includes substantially similar components. Specifically, the components 140, 142, 144, and 146 of the base station 106 are similar to the components 130, 132, 134, and 136, respectively.

[0030] UE 102 is equipped with processing hardware 150, which includes one or more general-purpose processors 152 (such as CPUs) and non-transitory computer-readable memory 154 storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or dedicated processing units. Processor 152 is configured to process data sent in the uplink direction and / or data received in the downlink direction by UE 102. Processing hardware 150 may also include a transceiver 156 (the term here also represents antennas and RF front-end electronic devices that are not separately shown in this figure) that is configured to send and receive data.

[0031] Figure 2 A certain type of NTN deployment, referred to as a transparent payload architecture, is shown, which involves a satellite gateway (also referred to as an NTN gateway) 203 and a "transparent" satellite 204 for extending the range of the Uu interface. The satellite 204 implements frequency conversion and radio frequency RF amplifiers in both the uplink direction and the downlink direction. The satellite functions are similar to those of an analog RF repeater. Therefore, the satellite 204 relays the Uu radio interface from the feeder link (between the NTN gateway and the satellite) to the service link (between the satellite and the UE) in the downlink direction, and vice versa in the uplink direction. The satellite radio interface SRI on the feeder link is Uu, and the NTN gateway 203 supports all functions necessary to forward the signals of the Uu interface. The NTN gateway 203 can be placed at the same location as the base station (e.g., eNB or gNB) 104, or can be connected to the base station 104 via a wired link. More than one NTN gateway can also be connected to the base station. Different transparent satellites can be connected to the same base station on the ground via the same NTN gateway or via different NTN gateways.

[0032] Figure 31 is a diagram illustrating discontinuous NTN coverage of a UE. UE 102 is stationary and located within a geographic area of ​​interest, experiencing discontinuous coverage. Figure 3 As shown in the upper part of FIG. , UE 102 is in a cell served by a low earth orbit (LEO) satellite 204 from t1 to t2, and then Figure 3 As shown in the lower part of FIG, UE 102 is served by another LEO satellite 304 from t3 to t4. In the period between t2 and t3, UE 102 is not served by any satellite or any ground base station and is therefore disconnected from the RAN. The UE may begin to seek to connect to other cells when it loses connection with the serving cell. However, in Figure 3 In the example shown, the UE 102 is unable to find a cell between t2 and t3 (which may last for several minutes or hours). The cell search results in additional, unnecessary power consumption in the UE 102.

[0033] To avoid additional power consumption, when UE 102 is not within the coverage area of ​​the satellite, the UE can be configured not to perform cell search and deactivate its access stratum AS function. In some implementations, the UE has information about the length of time the UE has no NTN coverage (i.e., out-of-coverage period) and in which area (AOI) the UE has no NTN coverage, and thus can reactivate its cell search or AS function when NTN coverage begins.

[0034] In terms of satellite mobility patterns, three types of service links are supported in NTN: (1) geo-fixed satellites (e.g., GEO / GSO satellites), which provide beams that continuously cover the same geographic area; (2) quasi-geo-fixed satellites (e.g., low earth orbit (LEO) / medium earth orbit (MEO) satellites capable of using steerable beams), which provide beams that cover one geographic area for a limited period of time and a different geographic area during another period of time; and (3) geo-mobile satellites (e.g., LEO / MEO satellites using fixed or non-steerable beams), which provide beams whose coverage areas slide above the surface of the Earth.

[0035] Therefore, the eNB connected via the NTN can provide quasi-Earth fixed cell coverage or Earth mobile cell coverage using LEO / MEO satellites. The eNB provides Earth fixed cell coverage using GEO satellites.

[0036] The interactions between network functions (NFs) can be represented in two ways. For example, first, a service-based representation, where a network function enables other authorized network functions to access its services (such a representation also includes point-to-point reference points when necessary); and second, a reference point representation, which indicates that there are interactions between network functions, where reference points between those network functions are depicted.

[0037] The currently defined NWDAF (e.g., in 3GPP TS 23.288) collects UE mobility related information from NFs and OAMs to perform data analysis to produce UE mobility statistics or predictions. The various embodiments described in this section enhance conventional NWDAFs and other nodes / NFs by generating improved estimates (predictions) of NTN coverage by expanding the quantity and quality of input data used to generate analytical estimates of NTN coverage. Providing analytical estimates of NTN coverage to UE 102, NG-RAN 104, and / or 5G CN 110 enables mobility management enhancements and more efficient power saving scheduling. Various embodiments also illustrate techniques for providing analytical estimates of NTN coverage to service consumers (e.g., UE / NG-RAN / AMF) for assisting in deciding power saving mechanisms to stay outside of current PLMN / satellite RAT and NTN coverage.

[0038] The following embodiments describe the use of one or more of the following assumptions: (1) NTN is a non-GEO (non-geostationary satellite) network, and satellite motion causes NTN cells to temporarily cover different parts of the area. The embodiments can use the data collection architecture and network data analysis open architecture from any 5GCNF, and the embodiments can also be applied to the data collection architecture and analysis open architecture using data collection coordination as described in the 3GPP technical specification (e.g., 3GPP TS 23.288).

[0039] An embodiment of an OAM mechanism deployed in a 5G network has an interface (e.g., a proprietary interface) between the NWDAF 116 and the OAM 111. The OAM has management functionality for producing / consuming satellite data services to / from the 5G CN 110 and the NG-RAN 104. The OAM provides the required mechanisms to ensure continuous data collection requested by the NWDAF. Although the OAM functions and mechanisms are not described in detail in this document, they are described in the 3GPP technical specifications and are otherwise well known.

[0040] Another assumption is that the UE 102 has the capability to determine its location (e.g., via a global navigation satellite system (GNSS), or via a positioning process at the UE as indicated in the 3GPP technical specifications), and is consented by the user to provide its location to the NG-RAN / 5G CN / AF. For the NG-RAN's awareness of the UE's location, it is assumed that the NG-RAN 104 can obtain an estimate of the UE's location information from the 5G CN 110 or from the UE 102. For the AMF 115's awareness of the UE's location, it is assumed that the AMF 115 can obtain an estimate of the UE's location information from other NFs 112 in the 5G CN 110 or from the UE 102 or the NG-RAN node 104.

[0041] Figure 4 is an input / output representation of a NE (e.g., NWDAF) configured to generate an analytical estimate of NTN coverage in an AOI according to an embodiment. The NWDAF 116 uses an analytical model to predict, estimate, and / or generate an analytical estimate of NTN coverage. The input data may include one or more of the following information: (1) satellite related data (e.g., ephemeris data from OAM 111, NG-RAN 104, or AF 117 for one or more satellites); (2) available UE related analysis (e.g., expected UE behavior parameters, which may include one or both of UE mobility and UE communicability analysis); and (3) UE related information obtained, for example, using event open acquisition from 5GC NF 112, NG-RAN 104 (via AMF 115), or UE 102 (via AMF 115 or AF117).

[0042] In an embodiment, the output analysis of NTN coverage may include: (1) Analysis ID: NTN coverage; and (2) NTN coverage type, including ephemeris data, estimates of periods in NTN coverage, and / or estimates of periods outside NTN coverage.

[0043] In another embodiment, different analysis IDs may be applied, for example, analysis ID: NTN coverage of ephemeris data, and / or analysis ID: estimated NTN coverage for periods in NTN coverage, estimated NTN coverage for periods outside NTN coverage.

[0044] like Figure 4 As shown, NWDAF 116 receives available analysis as input data in addition to satellite-related information input data obtained from OAM / NG-RAN / AF 411 and / or UE-related information obtained from 5GCN / NG-RAN / UE 412. NWDAF 116 outputs the analysis estimate of NTN coverage to one or more of AMF / NG_RAN / AF / UE 420.

[0045] Figure 5A , Figure 5B and Figure 5C is a block diagram illustrating NWDAF 116 collecting satellite data in different deployment scenarios. Figure 5A In the example, OAM 111 provides satellite related information directly to NWDAF 116. OAM 111 can provide the same information to NG-RAN node 104.

[0046] exist Figure 5B In the present invention, the first OAM (OAM-CN 111a) manages the NF in the RAN that provides services to the UE, but the satellite that enables the UE to connect to the RAN is related to another network with another second OAM (OAM-S 111b). The second OAM (OAM-S 111b) can provide satellite-related information to the NG-RAN node 104. The NWDAF 116 collects satellite-related information from the NG-RAN node 104 via the AMF 115.

[0047] exist Figure 5C In, similar to Figure 5B In the scenario shown, OAM-CN 111a manages NFs in the RAN that provide services to the UE, but the satellite that enables the UE to connect to the RAN is related to another network managed by OAM-S 111b. In this scenario, NWDAF 116 collects satellite-related information from OAM-S 111b via AF 117. OAM-S 111b can also provide satellite-related information to NG-RAN node 104.

[0048] In order to obtain more accurate satellite related information (such as FIG. 5A to FIG. 5C As shown in the exemplary embodiment, the NWDAF 116 must subscribe to the services of OAM, NG-RAN via AMF, and AF. To this end, in one embodiment, the features of the event open functionality between AMF / AF and NWDAF are enhanced to enable the event ID to specify "satellite data" and event filter parameters related to satellite data.

[0049] The event filter parameters corresponding to the event ID satellite data may include: (A) ephemeris information (provided periodically or on demand), describing the orbital track information or coordinates of the NTN carrier information; (B) ephemeris format type, such as position velocity type (e.g., satellite position and velocity state vector: position, velocity) and orbit type (e.g., semi-major axis; eccentricity; perigee argument; ascending node longitude; inclination; and mean anomaly angle at epoch time provided in orbit parameter ephemeris format); (C) explicit epoch time: associated with the ephemeris data; (D) area of ​​interest (AOI) information (which may refer to a predefined area represented by a tracking area list, a cell list, or a (R) AN node identifier list, and for Naf_EventExposure related service operations, AOI may be converted from NEF to a geographic area and vice versa); and (E) the location of the NTN gateway (which may be used for uplink timing, frequency synchronization, and may also be used for random access and mobility management purposes). The event filter parameters may further include additional information, such as information used to implement NG-RAN node operations. For example, for feeder / serving link switching, the information sent to the NG-RAN node may depend on the type of serving link supported (e.g., Earth-fixed beam, quasi-Earth-fixed beam, Earth-mobile beam, etc.).

[0050] Figure 6 6 is a signal diagram illustrating a process for enabling the NWDAF 116 to subscribe to receive management data related to generating an analytical estimate of NTN coverage from the OAM 111. The NWDAF 116 initiates 610 the process by indicating (inputting) the following information: (1) data type: satellite data; (2) subscription type: one-time or periodic subscription based on periodicity or duration, etc.; (3) validity conditions: time, accuracy, confidence level, resolution, etc.; and (4) input filters: multiple parameters can be provided based on the requirements of the satellite data. In addition, the input can specify parameters for the input filters, which parameters include: (1) ephemeris information (orbital trajectory information or coordinates that describe the NTN vehicle provided regularly or on demand); (2) ephemeris format type (e.g., position velocity type and orbit type as described above for ephemeris data); (3) explicit epoch time associated with the ephemeris data; and (4) AOI information, which can be a geographic area or refer to a predefined area represented by a tracking area list, a cell list, or a (R)AN node identifier list.

[0051] OAM 111 responds to NWDAF 116 with the subscription request result as subscription (output) 612. OAM 111 performs data processing 614 to process the required data. Then, when the requested data is ready, OAM 111 notifies (notifyFileReady) 618 NWDAF 116. As a final step (not shown), NWDAF 116 obtains the data by using, for example, File Transfer Protocol (FTP).

[0052] In an embodiment, the NWDAF subscribes to NG-RAN via AMF to obtain satellite data, such as Figure 5B As shown. The AMF described in the 3GPP technical specification is modified to provide delegation functionality to the NG-RAN 104, because the NG-RAN node 104 (at least in this embodiment) is not a NF in the 5G CN 110. The AMF service used by the NWDAF 116 for data collection invokes a Namf_EventExposure procedure similar to the procedure described in the 3GPP technical specification (e.g., in 3GPP TS 23.502).

[0053] The AMF 115 may identify its delegate role to the NG-RAN based on a new event ID associated with the NG-RAN. When the AMF 115 receives an event exposure request from the NWDAF 116, the AMF 115 may: (1) identify the target NG-RAN node based on the target UE identifier or NG-RAN node ID indicated by the NWDAF 116 in the Namf_EventExposure_Subscribe message; and (2) if the event exposure requires information from the NG-RAN (e.g., a new event ID for satellite data), the AMF 115 activates the delegation functionality to initiate the N2 procedure for retrieving information from the NG-RAN node. The NG-RAN 104 establishes a mechanism to ensure continuous data collection requested by the NWDAF via the AMF using UE-associated or non-UE-associated NGAP messages. When the target of the event report indicates a target UE ID, a UE-associated NGAP message is used. When the target of the event report indicates any UE, a non-UE-associated NGAP message is used.

[0054] Figure 77 is a signal diagram illustrating a first satellite data acquisition scenario according to an embodiment. NWDAF 116 subscribes to the AMF 115 service by issuing a Namf_EventExposure_Subscribe message 718. Namf_EventExposure_Subscribe message 718 may include the following information: (1) event ID of the satellite data; (2) event filter as described above (i.e., ephemeris information, ephemeris format type, explicit epoch time associated with the ephemeris data, AOI); (3) target of the event report (indicating the target UE ID, which may be a UE ID including a general public subscription identifier (GPSI), a subscription permanent identifier (SUPI), a UE IPv4 address, a UE IPv6 prefix, an internal / external group identifier, or an indication of any UE targeted); (4) notification target address; (5) event report information (e.g., event reporting mode, maximum number of reports, periodic reporting together with periodicity, etc., as defined, for example, in 3GPP TS 23.502 Table 4.15.1-1); and (6) expiration time of the subscription.

[0055] The AMF provides the NG-RAN with a delegated service for the event exposure requested by the NWDAF in the following steps: (1) The AMF handles the event exposure of the NG-RAN node 720. If the required information is available, the AMF 115 and the NG-RAN node 104 do not send / receive messages 722 and 724, but respond to the NWDAF 116 by issuing the required information in the Namf_EventExposure_Notify message 726.

[0056] If the required information is not available, the AMF 115 AMF issues a Next Generation Application Protocol (NGAP) message 722 (e.g., N2 Satellite Data Request) to the target NG-RAN node 104. Such a message based on the NWDAF 116 request may include the following information based on the NWDAF 116 request: (1) an event ID for satellite data (optionally, if the N2 UE-associated NGAP message or the non-UE-associated NGAP message is not specifically for satellite data, the event ID is included), (2) an event filter as described above (e.g., ephemeris information, ephemeris format type, explicit epoch time associated with the ephemeris data, AOI, etc.), and (3) an event report target (indicating the target UE ID (as described above)).

[0057] The NG-RAN node 104 then processes the request to provide the required data to the AMF 115 due to the subscription request. The NG-RAN node 104 provides the information to the AMF 115 using a UE-associated NGAP message 722 or a non-UE-associated message (e.g., N2 Satellite Data Response). The message may include an event ID (optionally, if the N2 UE-associated NGAP message or the non-UE-associated NGAP message is not specifically for satellite data, then the event ID is included), a target UE ID (external UE ID, or internal / external group identifier, or UE IP v4 address or UE IP v6 prefix), satellite data corresponding to the settings indicated in the event filter (AOI is converted by the NEF before sending the message 726), and a timestamp. The process may be completed when the AMF 115 responds to the NWDAF 116 in a Namf_EventExposure_Notify 726 message (including available information or information received from the NG-RAN node 104).

[0058] Figure 8 is a signal diagram illustrating a process for collecting satellite related data from an application function (AF) according to an embodiment. The process enables receiving third party data and Figure 5C The operation is schematically shown. This process is similar to the process for the NWDAF to obtain AF services using the service operation of the Naf_EventExposure type described in the 3GPP technical specification (eg, 3GPP TS 23.502).

[0059] The conventional AF 117 is enhanced to handle the new event ID for satellite data. The initial phase implements the registration of AF available data 830. The NEF 118 issues a Nnrf_NFManagement_NFUpdate_request message 832 to the NRF 119, which then stores 834 the NF profile. The NRF 119 issues a Nnrf_NFManagement_ NFUPdate_response message 836 to the NEF 118. In order to discover 840 the satellite related data that the AF can provide, the NWDAF 116 sends a Nnrf_NFDiscovery_Request _request 842 to the NRF 119, which in turn sends a Nnrf_NFDiscovery_Request_response 844 to the NWDAF 116. The response indicates the satellite related data that the AF can provide.

[0060] The NWDAF 116 sends a Nnef_EventExposure_Subscribe (or Nnef_EventExposure_Unsubscribe) message 850 to the NEF, which in turn sends a Naf_EventExposure_Subscribe (or Naf_EventExposure_Unsubscribe) message 852 to the AF 117. The Nnef_EventExposure_Subscribe message 850 and the Naf_EventExposure_Subscribe message 852 may include the following information: (1) event ID of the satellite data; (2) event filters as described above (e.g., ephemeris information, ephemeris format type, explicit epoch time associated with the ephemeris data, AOI that may be converted by the NEF before sending message 852, etc.); (3) target of the event report, which indicates the target UE ID, which may be a UE ID including GPSI or SUPI, or a UE IPv4 address, or a UE IPv6 prefix, or an internal / external group identifier, or any indication targeted by the UE; (4) notification target address; (5) event reporting information, such as event reporting mode, maximum number of reports, periodic reporting together with periodicity, etc., as defined in 3GPP technical specifications (e.g., 3GPP TS 23.502); and (6) expiration time of the subscription.

[0061] Optionally, AF 117 may then send an Nnef_EventExposure_Notify message 854 to NEF 118, and NEF 118 may then send a Naf_EventExposure_Notify message 856 to NWDAF 116. These notification messages may include the following information: (1) event ID; (2) target UE ID (external UE ID, or internal / external group identifier, or UEIP v4 address, or UE IP v6 prefix); (3) satellite data corresponding to the settings indicated in the event filter (AOI is converted by NEF 118 sending message 856); and (4) timestamp.

[0062] The NWDAF 116 may collect UE-related information from the 5GC NFs for NTN coverage analysis using the procedures described in the 3GPP technical specifications (eg, 3GPP TS 23.288). Fig. 9 is a signal diagram of the process used for data collection from NF.

[0063] 960. The NWDAF 116 first sends a Nudm_SDM_Get request message 960 to the UDM 114. The UDM 114 replies with a Nudm_SDM_Get response message 962. The NWDAF 116 then sends a Nudm_SDM_Subscribe request message 964 to the UDM 114, which responds with a Nudm_SDM_Subscribe response message 966. In addition, the NWDAF 116 sends a Nnf_EventExposure_Subscribe (or Unsubscribe) request message 968 to the NF 112. The NF 112 responds with a Nnf_EventExposure_Subscribe (or Unsubscribe) response message 970. The NWDAF 116 may later send a Nnf_EventExposure_Notify message 972 to the NF 112. The UDM 114 may send a Nudm_SDM_Notify message 974 to the NWDAF 116. NWDAF 116 then sends a Nnf_EventExposure_Unsubscribe request message 976 to NF 112. NF 112 responds with a Nnf_EventExposure_Unsubscribe response message 978. NWDAF 116 sends a Nudm_SDM_Unsubscribe request message 980 to UDM 114, which responds with a Nudm_SDM_Unsubscribe response message 982.

[0064] UE related data collection from AF via NEF can be used with Figure 8 Same process as shown. UE Access and Mobility Information Events (Event ID) are defined in 3GPP TS 23.502 clause 4.15.1 and table 4.15.3.1-1. If data is collected from AMF, the AMF service operation of Namf_EventExposure is defined in 3GPP TS 23.502 clause 5.2.2.3, where the Event ID and Event Filter are used to specify the list of conditions / parameters to match to notify the event identified by the Event ID.

[0065] The following UE 102 access and mobility information events may be applicable to estimation / prediction of NTN coverage (event IDs are defined in 3GPP technical specifications): (A) location report (TAI, cell ID); (B) UE moving into or out of the subscribed AOI, as described in the 3GPP technical specifications; (C) number of UEs served by the AMF and located in the AOI; (D) registration state change (e.g., REGISTERED or DERELECTRICAL); (E) connection state change (e.g., IDLE or CONNECTED); (F) UE communication loss; UE reachability state; (G) frequent mobility re-registration; (H) UE access behavior trends in accordance with 3GPP technical specifications (see, for example, 3GPP TS 23.502 Section 4.15.4.2); and (I) UE location trends in accordance with 3GPP technical specifications (see, for example, 3GPP TS 23.502 Section 4.15.4.2).

[0066] The parameters of the AMF open event for UEs using satellite RAT may be enhanced to support RAN node and cell levels. For example, Event ID: Location Report may include an event filter: <parameter type= location filter, value= TA1>. In another example, Event ID: Access Type may include an event filter that includes one or more of the following: <parameter type= AN type, value= 3GPP access">; and <parameter type= 3GPP access type, value= satellite access">.

[0067] In another example, event ID: UE moves into or out of the area of ​​interest; and the event filter may include one or more of the following (RAN node ID, cell ID may refer to, for example, 3GPP TS 38.413): <parameter type=TAI, value=TA2>; <parameter type=global RAN node ID or RAN node ID (no PLMN ID), value=global gNBID#X>; and <parameter type=global cell-ID or cell ID (no PLMN ID), value=cell-ID#X>.

[0068] Additionally, for Event ID: Location, the event filter may include one or more of the following: <parameter type=TAI, value=wildcard> (to report any TAI changes); <parameter type= Global RAN Node ID, value=wildcard> (to report any RAN node changes); and <parameter type= Global Cell-ID or Cell ID (no PLMNID), value=wildcard> (to report any Cell-ID changes).

[0069] To support data collection of non-satellite data from NG-RAN nodes, the AMF 115 is enhanced with the delegation functionality of the NG-RAN 104, since the NG-RAN node 104 is not a NF in the 5G CN 110.

[0070] To enable the AMF 115 to identify its delegated role to the NG-RAN, a new event ID associated with the NG-RAN may be provided, or an existing event ID with parameters related to NG-RAN level information may be indicated in the event filter.

[0071] When the AMF 115 receives 718 the Event Exposure Request from the NWDAF 116, the AMF 115 may identify the target NG-RAN node based on the target UE identifier or NG-RAN node ID indicated by the NWDAF in the Namf_EventExposure_Subscribe message 718. If the Event Exposure 720 requires (satellite-related or UE-related) information from the NG-RAN node 104, the AMF 115 activates the delegation functionality to initiate an N2 procedure for retrieving information from the NG-RAN node, stores the Event ID and one or more target RAN node IDs with the relevant EventExposure information, and sets an event trigger for the Event ID and initiates the N2 procedure if the required information is not available.

[0072] Return to Figure 7 , first the NWDAF 116 subscribes to the AMF 115 service, thereby activating the AMF delegated function to handle the event exposure of the NG-RAN node 104. Therefore, the Namf_EventExposure_Subscribe message 718 includes one or more event IDs and the following information for each event ID (the event ID may be a new event ID for NG-RAN or an existing event ID defined in a 3GPP technical specification such as 3GPP TS23.502): event filter, target indication target UE ID for event reporting (the target UE ID may be a UE ID including GPSI or SUPI, or UE IPv4 address, or UE IPv6 prefix, or internal / external group identifier, or any indication targeted by the UE), notification target address, event reporting information (e.g., event reporting mode, maximum number of reports, periodic reporting together with periodicity, etc., as defined in the 3GPP technical specification (e.g., 3GPP TS 23.502 Table 4.15.1-1)) and expiration time of the subscription.

[0073] The AMF 115 provides a delegation service to the NWDAF 116. When providing the delegation service, the AMF 115 handles the event exposure 720 of the NG-RAN node. If the required information is available, messages 722 and 724 are not sent / received, but the AMF 115 responds to the NWDAF 116 by sending a Namf_EventExposure_Notify message 726. Otherwise, the AMF 115 sends message 722.

[0074] The AMF initiates an NGAP message (e.g., N2 satellite data request message 722) to the target NG-RAN node 104 based on the NWDAF request. For example, the request message may specify: (1) an event ID of the requested information (optionally, if the N2 UE-associated NGAP message or the non-UE-associated NGAP message is not specifically for the requested information, the event ID is included); (2) an event filter, such as AOI information; and a target of the event report, which indicates a target UE ID (the target UE ID may be a UE ID including a GPSI or SUPI, or a UE IPv4 address, or a UE IPv6 prefix, or an internal / external group identifier, or any indication targeted by the UE).

[0075] The NG-RAN node 104 provides information to the AMF 115 based on the target UE identifier or non-UE associated information, as shown in the N2 Satellite Data Response message 724. The AMF 115 responds to the NWDAF 116 in a Namf_EventExposure_Notify message 726 (including available information or information received from the NG-RAN node 104).

[0076] After collecting satellite-related data, UE-related data, and UE-related analysis, the NWDAF is able to generate an analysis estimate of NTN coverage. The analysis estimate of NTN coverage can be associated with a new analysis ID. The NWDAF 116 can generate an analysis estimate of NTN coverage based on analysis filter information requested by a service consumer. The analysis filter information can provide the following information: (A) NTN coverage type; (B) UE location; (C) validity period; (D) spatial validity; (E) SUPI list; and (F) confidence information. The NTN coverage type may include ephemeris data, an estimate of the period in NTN coverage, and an estimate of the period outside NTN coverage. The UE location indicates reference UE location information (e.g., based on a TAI list, gNB ID, cell ID, etc.) for NTN coverage derived based on a preferred granularity of location information and a consumer's analysis request for a target UE identifier (e.g., one UE or a list of UEs). The validity period indicates the duration for which the NTN coverage information is valid. The spatial validity indicates the area to which the NTN coverage analysis applies. If the customer provides an AOI (e.g. a set of TAIs, NG-RAN Node IDs, Cell IDs for which analysis information is subscribed or requested), this information is provided. A SUPI list indicating a list of SUPIs for UEs to which the same ephemeris data may apply. Confidence information indicating the confidence percentage or level of the estimate of NTN coverage.

[0077] Fig.10 1 is a signal diagram showing that the enhanced NWDAF collects input data, generates and delivers an analysis estimate of NTN coverage related to the UE. The service consumer is a network function (i.e., NF consumer 112a), which can be (A) AF, (B) 5G CN or OAM, (C) AMF for delegating RAN nodes, or (D) AMF for delegating UEs.

[0078] First, the 5GC NF (consumer) 112a sends a request message 1010 to the NWDAF 116 based on a one-time request or an analysis event notification. For analysis, the request message 1010 indicates the requirements for the target of the analysis report to be established for analysis and the criteria for filtering information. For example, the NWDAF 116 can use Nnwdaf_AnalyticsInfo_Request 1010 (analysis ID, target of the analysis report, analysis filter information) for one-time analysis or subscription analysis notification.

[0079] The request message 1010 includes the following information: (1) an analysis ID associated with the NTN coverage; (2) a target of the analysis report, which indicates a target UE ID for which the analysis information is requested (e.g., an entity such as a specific UE, a group of UEs, or any UE (i.e., all UEs)); (3) analysis filter information corresponding to the analysis ID of the NTN coverage (indicating conditions to be met for reporting the analysis information). The set of optional parameter types and values ​​enables selection of which type of analysis information is requested.

[0080] The request message 1010 also includes: notification target address and analysis report information. The analysis report information may include the following parameters: (i) analysis target period (e.g., past or future time interval [start..end]); (ii) time when analysis information is required (if applicable, and indicates to the NWDAF the latest time when the analysis consumer is expected to receive analysis data provided by the NWDAF); and (iii) preferred granularity of location information, for example, tracking area (TA) level or cell level.

[0081] Unless the information is already available, the NWDAF collects data 1020 from the OAM, NG-RAN via the AMF, and / or AF, as described above in various embodiments. The NWDAF derives the requested analysis 1025. Depending on the service used in the message / process 1010, the NWDAF 116 provides the requested analysis information of the NTN coverage to the NF consumer 112a using the Nnwdaf_AnalyticsInfo_Request response or the Nnwdaf_AnalyticsSubscription_Notify, as shown in the message 1012. The Nnwdaf_AnalyticsInfo_Request response or the Nnwdaf_AnalyticsSubscription_Notify message 1012 may include the following information: (1) Analysis ID of the NTN coverage; (2) Analysis information of the NTN coverage based on the target, analysis filter information, and analysis report information of the analysis report; (3) Timestamp of analysis generation, which allows the consumer to decide until when the received information will be used. For example, the NF may consider the received notification from the NWDAF 116 for a given feedback as invalid based on the timestamp.

[0082] NWDAF 116 receives Nnf_EventExposure_Notify message 1031 from NF 112, Naf_EventExposure_Notify message 1033 from AF 117, and notification message 1035 from OAM 111. NWDAF may determine to generate new analysis 1027. If NF 112a is subscribed via message / process 1010, for example, if AMF and / or NWDAF generates new analysis of analysis information for NTN coverage, it provides the newly generated analysis to NF 112 (e.g., AMF 115).

[0083] In an embodiment, the NWDAF service consumer is the NG-RAN node 104 via the AMF 115, where the AMF 115 is Fig.10 NF consumer 112a in.

[0084] For NG-RAN awareness of NTN coverage, the NG-RAN node may obtain strict NTN coverage information from the NWDAF 116 via the AMF 115, and the AMF 115 delegates a subscription to the NWDAF 116. The NG-RAN 104 establishes the required mechanisms to ensure continuous data collection requested by the NWDAF 116 via the AMF 115 using UE-associated or non-UE-associated NGAP messages. When the target of the analysis report indicates a target UE ID, the UE-associated NGAP message is used. When the target of the analysis report indicates any UE, the non-UE-associated NGAP message is used.

[0085] Fig.111 is a signal diagram of a process performed by a NE to provide an analysis estimate of NTN coverage in an AOI to an NG-RAN node according to an embodiment. The NG-RAN node 104 is an analysis client of the NWDAF 116. First, the NG-RAN node 104 issues an N2 AnalyticsInfo request message 1111 to the AMF 115. The N2 AnalyticsInfo request message 1111 includes the following information: an analysis ID; a target for the analysis report; analysis filter information; a notification target address; and analysis report information. The analysis ID indicates the NTN coverage (optionally, if the N2 UE-associated NGAP message or the non-UE-associated NGAP message is not specifically for NTN coverage, the NTN coverage is included). The target of the analysis report indicates the target UE ID for which the analysis information is requested (such as a specific UE, a group of UEs, or an entity of any UE, i.e., all UEs). The analysis filter information corresponding to the analysis ID of the NTN coverage indicates the conditions to be met for reporting the analysis information. The set of optional parameter types and values ​​enables selection of the types of analysis information, notification target address, and analysis report information. The analysis report information may include the following parameters: (A) analysis target period: time interval [start..end] (a time interval between both the start time and the end time in the past or the start time and the end time in the future); (B) the time when the analysis information is required (if applicable, indicating to the NWDAF the latest time when the analysis consumer is expected to receive the analysis data provided by the NWDAF); and (C) the preferred granularity of location information, for example, TA level or cell level.

[0086] The AMF 115 then sends a request message 1121 to the NWDAF 116 based on a one-time request or an analytics event notification (the message 1121 may include the same or similar content as the message 1010). The NWDAF 116 collects data and derives the requested analytics 1123 (this is performed in the same or similar manner as described with respect to events 1020 and 1025). Depending on the service indicated in the message / process 1121, the NWDAF 116 provides the requested analytics information of the NTN coverage to the AMF 115 using a Nnwdaf_AnalyticsInfo_Request response or a Nnwdaf_AnalyticsSubscription_Notify message 1124.

[0087] The AMF issues an N2 AnalyticsInfo notification message 1113 including analysis information to the NG-RAN node 104. The notification message 1113 may include: (1) an analysis ID for NTN coverage (optionally, if the N2 UE-associated NGAP message or non-UE-associated NGAP message is not specifically for NTN coverage, the analysis ID is included); (2) analysis information for NTN coverage based on the target of the analysis report, analysis filter information, and analysis report information; and (3) a timestamp of analysis generation, allowing the consumer to decide until when to use the received information. The NF may determine that the received notification from the NWDAF is invalid based on the timestamp.

[0088] Multiple notification messages may be sent when appropriate. Fig.11 In the example, repeated notification messages are through messages 1126 and 1115. For example, when a request is made based on a subscription, the NWDAF 116 can send new information to the AMF 115, which then forwards the new information to the NG-RAN node 104.

[0089] In an embodiment, UE 102 is a NWDAF analysis service consumer, and the UE receives information via AMF 115, which is a NF consumer, such as Fig.10 As shown. In order to perceive the NTN coverage, the UE 102 may receive NTN coverage information based on the analyzed estimated NTN coverage output by the NWDAF 116. In an embodiment, the subscription to the NWDAF 116 is delegated by the AF 117, and the analyzed estimate of the NTN coverage is delivered to the UE 102 via the user plane (e.g., the AnalyticsInfo generated by the embodiments described herein may be delivered using the method described in the 3GPP technical specification (e.g., in 3GPP TS 23.288 Section 6.2.8.2.3)).

[0090] As about Fig.12 As described above, NAS messages are used to provide analysis of NTN coverage to UE 102. Fig.12 During the registration request message (not shown in FIG), the registration request message includes an indication of NTN coverage. Based on the NTN coverage indication, AMF 115 discovers the NWDAF instance and associates UE 102 with NWDAF 116.

[0091] exist Fig.12In the embodiment, UE 102 issues a NAS message 1211 to AMF 115 to request disclosure of analysis information from NWDAF 116. In an embodiment, NAS message 1211 is a new type of NAS message. In another embodiment, NAS message 1211 is a UL NAS transport message. NAS message 1211 includes the following information: if the new type of NAS message is dedicated to NTN coverage or the container is dedicated to NTN coverage, or if NAS message 1211 is a new type of NAS message with NTN coverage indication, then the NTN coverage indication or Analytics ID indication includes the NTN coverage of the UE. AMF 115 identifies the analysis ID; the target of the analysis report, indicating the target UE ID for which the analysis information is requested, such as a specific UE, a group of UEs, or any UE (i.e., all UEs); and analysis filter information corresponding to the analysis ID of the NTN coverage, indicating the conditions to be met for reporting the analysis information. The set of optional parameter types and values ​​indicates the requested analysis information.

[0092] In addition, the NAS message 1211 may include a notification target address and / or analysis report information. The analysis report information includes the following parameters: (A) analysis target period (e.g., a time interval [start..end] of both the start time and the end time in the past or both the start time and the end time in the future); (B) time when analysis information is required (if applicable), indicating to the NWDAF the latest time when the analysis consumer is expected to receive analysis data provided by the NWDAF; and (C) preferred granularity of location information: TA level or cell level.

[0093] The AMF 115 sends a request message 1221 to the NWDAF 116 based on a one-time request or an analysis event notification (the message 1221 may include the same or similar content as the message 1010). The NWDAF 116 collects data and derives the requested analysis 1223 (this is performed in the same or similar manner as described with respect to events 1020 and 1025). Depending on the service indicated in the message / process 1221, the NWDAF 116 provides the requested analysis information of the NTN coverage to the AMF 115 using a Nnwdaf_AnalyticsInfo_Request response or a Nnwdaf_AnalyticsSubscription_Notify message 1224.

[0094] AMF 115 issues a NASAnalyticsInfo notification message 1213 including analysis information (i.e., NTN coverage estimated through analysis) to UE 102. In an embodiment, NAS AnalyticsInfo notification message 1213 is a new type of NAS message. In an embodiment, NAS AnalyticsInfo notification message 1213 is a DL NAS transport message having a new container IE for delivering AnalyticsInfo and a new container type IE for the container of the analysis information. In another embodiment, NAS AnalyticsInfo notification message 1213 is based on a UE configuration update command message (e.g., AnalyticsInfo generated by the embodiments described herein) issued to UE 102, which AnalyticsInfo may use the information described in the 3GPP technical specifications (such as in 3GPP TS 23.502 Figure 4 In yet another embodiment, the NAS AnalyticsInfo notification message 1213 is a DL NAS transport message for delivering UE policies, for example, AnalyticsInfo generated by the embodiments described herein, which AnalyticsInfo may be delivered using the method described in the 3GPP standard (such as in 3GPP TS 23.502 Figure 4 In this case, AMF 115 notifies PCF 113 to trigger the process by delivering analysis information as UE policy.

[0095] In an embodiment, when appropriate, AMF 115 sends multiple notification messages, such as messages 1226 and 1215. Sending multiple notification messages can be based on subscription or new information is available. NWDAF 116 sends new information to AMF 115, which then forwards the new information to UE 102.

[0096] Fig.13 1 is a flow chart of a method 1300 performed by a NE for providing an analysis estimate of NTN coverage according to an embodiment. The method 1300 includes: obtaining 1310 satellite related information. The method 1300 further includes generating 1320 an analysis estimate of NTN coverage associated with the UE based on the satellite related information, the UE related information and the UE related analysis. The method 1300 finally includes outputting 1330 the analysis estimate of NTN coverage.

[0097] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., a code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and may be configured or arranged in a particular manner. A hardware module may include a dedicated circuit or logic that is permanently configured to perform certain operations (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)). A hardware module may also include a programmable logic or circuit system (e.g., as contained in a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., a circuit system configured by software) may be driven by cost and time considerations.

[0098] When implemented in software, the techniques may be provided as part of an operating system, as a library used by multiple applications, as a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A communication method (1300) performed by a network entity NE of a core network, the method comprising: generating (1320) an analysis estimate of non-terrestrial network NTN coverage associated with the UE based on the satellite-related information, the user equipment UE-related information and the UE-related analysis; and The analytical estimate of the NTN coverage is output (1330).

2. The method of claim 1, wherein the NE executes a network data analysis function (NWDAF) that generates the UE-related analysis as defined in 3GPP technical specifications.

3. The method of any one of claims 1 or 2, wherein generating the analytical estimate of the NTN coverage comprises estimating a period of NTN coverage mid-term and / or a period of NTN coverage out-term for a region of interest.

4. The method of claim 3, wherein generating the analytical estimate of the NTN coverage further comprises associating at least one of: a validity period, a confidence metric, or a list of one or more subscribers associated with the analytical estimate of the NTN coverage.

5. The method according to any one of claims 1 to 4, further comprising: The satellite-related information is obtained from at least one of the following: Operation, administration and maintenance functions OAM, A Next Generation Radio Access Network (NG-RAN) node via the Access and Mobility Management Function (AMF), or Application function AF, The OAM, the AMF, and the AF are defined in the 3GPP technical specifications.

6. The method of claim 5, wherein obtaining the satellite-related information comprises: An OAM subscription process is performed to enable acquisition of the satellite related information from the OAM.

7. The method of claim 5, further comprising: An AMF subscription process is performed to enable acquisition of the satellite related information from the AMF.

8. The method of claim 5, further comprising: An AF subscription process is performed to enable acquisition of the satellite related information from the AF.

9. The method according to any one of claims 1 to 8, further comprising: The UE-related information is obtained from at least one of: the UE, a base station providing service for the UE, or a network function of the core network.

10. The method according to any one of claims 1 to 9, further comprising: Subscribe at the network function via the unified data management function to collect UE related information.

11. The method of claim 9, wherein outputting the analytical estimate of the NTN coverage comprises: Upon receipt of an event opening notification, the analyzed estimate of the NTN coverage is provided to the network function.

12. The method of any one of claims 1 to 9, wherein outputting the analytical estimate of the NTN coverage comprises: Said analyzed estimate of said NTN coverage is provided to an Access and Mobility Management Function, AMF, as defined in 3GPP Technical Specifications to be delivered to the Radio Access Network, RAN node requesting the information.

13. The method of any one of claims 1 to 9, wherein outputting the analytical estimate of the NTN coverage comprises: The analyzed estimate of the NTN coverage is provided to an Access and Mobility Management Function, AMF, as defined in 3GPP Technical Specifications to be delivered to the UE.

14. The method of claim 12, wherein providing the analysis estimate of the NTN coverage to the AMF is triggered by a non-access stratum (NAS) request message sent by the UE via the AMF.

15. The method of any one of claims 1 to 12, wherein outputting the analyzed estimate of NTN coverage occurs periodically.

16. A core network entity device (140), comprising: A transceiver (146), a processor (142), and a computer-readable storage medium (144) storing executable instructions for the processor to use the transceiver to perform any of the methods of claims 1 to 15.

Images