Method performed by user equipment (UE), user equipment (UE), method performed by radio access network (RAN) and method performed by access and mobility management function (AMF)

Abstract

An aspect of this disclosure includes a method of a Radio Access Network (RAN), Core Network (CN) and User Equipment (UE). The method includes selection and usage with the best Satellite among multi-orbit satellites for cellular communication in 3GPP system.

Description

METHOD PERFORMED BY USER EQUIPMENT (UE), USER EQUIPMENT (UE), METHOD PERFORMED BY RADIO ACCESS NETWORK (RAN) AND METHOD PERFORMED BY ACCESS AND MOBILITY MANAGEMENT FUNCTION (AMF)

[0001] The present disclosure relates to a method of a User Equipment (UE), a method of a radio access network communication apparatus and a method of a core network communication apparatus and etc.

[0002] The future of satellite communications is moving toward hybrid satellite networks that combine the services from low-Earth orbit satellites (LEO) and high-altitude satellites in medium-Earth (MEO) and geostationary orbits (GEO). It is being driven by the commercial sectors including maritime and aviation, which are increasingly pursuing multi-orbit satellite solutions.

[0003] NPL 1: [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V18.0.0 (2024-03) NPL 2: [2] SP-240198: https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGS_103_Maastricht_2024-03 / Docs / SP-240198.zip NPL 3: [3] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V19.0.0 (2024-06) NPL 4: [4] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V19.0.0 (2024-06) NPL 5: [5] 3GPP TS 23.003: "Numbering, addressing and identification". V19.0.0 (2024-06) NPL 6: [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD) ". V18.1.0 (2023-09) NPL 7: [7] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". V18.1.0 (2024-06) NPL 8: [8] 3GPP TS 38.101-5: "Part 5: Satellite access Radio Frequency (RF) and performance requirements". V18.5.0 (2024-03) NPL 9: [9] IETF RFC 5580: https: / / www.rfc-editor.org / rfc / rfc5580 NPL 10:

[0010] ITU-T Recommendation E.212: https: / / www.itu.int / rec / dologin_pub.asp?lang=e&id=T-REC-E.212-202012-S!Amd3!PDF-E&type=items NPL 11:

[0011] 3GPP TS 37.340: "Multi-connectivity Stage 2". V18.1.0 (2024-03) NPL 12:

[0012] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS) Stage 3". V18.6.0 (2024-03) NPL 13:

[0013] 3GPP TS 38.413: "NG Application Protocol (NGAP)". V18.2.0 (2024-06) NPL 14:

[0014] 3GPP TS 38.304: "User Equipment (UE) procedures in Idle mode and RRC Inactive state". V18.2.0 (2024-06) NPL 15:

[0015] 3GPP TS 38.331: "Radio Resource Control (RRC) protocol specification" V18.2.0 (2024-06) NPL 16:

[0016] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS) Stage 3". V18.7.0 (2024-06)

[0004] In 3GPP, the 3GPP SA working group 1 has started a feasibility study, in SP-240198 [2] on how the 3GPP system utilizes the multi-orbit satellites for cellular communication.

[0005] As each satellite, for example LEO, MEO and GEO has its own service characteristic, choosing right satellite for cellular communication becomes very important. 　　For example, if satellite is used as a suppliant to the Terrestrial Network coverage for Cellular IoT (C-IoT) service, satellites with high-altitude can be a choice as the CIoT service can work with delay and latency.

[0006] In another example, if satellite is used as a suppliant to the Terrestrial Network coverage for multimedia services, satellites with low-altitude can be a choice as the multimedia services require high-rate data communication.

[0007] On the other hand, communication cost varies with the satellite-type and a with the contract with a satellite service provider.

[0008] 3GPP system should provide a mechanism for selecting the best satellite for cellular communication taking end user service and its const into account. Otherwise, 3GPP operators might lose business opportunity for providing connectivity services with satellite access.

[0009] In order for 3GPP system to choose the best satellite for cellular communication taking end user service and its const into account, the 3GPP system should support the following function: 　　- 3GPP system should provide a mobility management mechanism to choose the best suitable satellite to end users.

[0010] The disclosure has a method performed by a user equipment (UE), the method comprising receiving, from a Radio Access Network (RAN), a first message comprising first satellite information and / or second satellite information sending, to an Access and Mobility Management Function (AMF) via the RAN, a first Non-Access-Stratum (NAS) message; and receiving, from the AMF, a second NAS message.

[0011] The disclosure has a user equipment (UE) comprising one or more memories storing instructions; and one or more processors configured to process the instructions to control the UE to receive, from a Radio Access Network (RAN), a first message comprising first satellite information and / or second satellite information send, to an Access and Mobility Management Function (AMF) via the RAN, a first Non-Access-Stratum (NAS) message and receive, from the AMF, a second NAS message.

[0012] The disclosure has a method performed by a Radio Access Network (RAN), the method comprising sending, to a user equipment, a first message comprising first satellite information and / or second satellite information sending, to an Access and Mobility Management Function (AMF), a first Non-Access-Stratum (NAS) message received from the UE; and sending, to the UE, a second NAS message received from the AMF.

[0013] The disclosure has a method performed by an Access and Mobility Management Function (AMF), the method comprising receiving, from a user equipment (UE) via a Radio Access Network (RAN), a first Non-Access-Stratum (NAS) message, the first NAS message being sent by the UE in response to a first message sent by the RAN, the first message comprising first satellite information and / or second satellite information; and sending, to the UE via the RAN, a second NAS message.

[0014] Fig. 1 is a diagram illustrating an architecture.Fig. 2 is a diagram illustrating an architecture.Fig. 3 is an example signaling diagram of this disclosure.Fig. 4 is an example signaling diagram of this disclosure.Fig. 5 is an example signaling diagram of this disclosure.Fig. 6 is an example signaling diagram of this disclosure.Fig. 7 is an example signaling diagram of this disclosure.Fig. 8 is an example signaling diagram of this disclosure.Fig. 9 is an example signaling diagram of this disclosure.Fig. 10 is an example signaling diagram of this disclosure.Fig. 11 is an example signaling diagram of this disclosure.Fig. 12 is an example signaling diagram of this disclosure.Fig. 13 is an example signaling diagram of this disclosure.Fig. 14 is an example signaling diagram of this disclosure.Fig. 15 is an example signaling diagram of this disclosure.Fig. 16 is an example signaling diagram of this disclosure.Fig. 17 is an example signaling diagram of this disclosure.Fig. 18 is an example signaling diagram of this disclosure.Fig. 19 is an example signaling diagram of this disclosure.Fig. 20 is an example signaling diagram of this disclosure.Fig. 21 is an example signaling diagram of this disclosure.Fig. 22 is an example signaling diagram of this disclosure.Fig. 23 is an example signaling diagram of this disclosure.Fig. 24 is a diagram illustrating a system overview.Fig. 25 is a block diagram illustrating a UE.Fig. 26 is a block diagram illustrating an (R)AN node.Fig. 27 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 28 is a block diagram illustrating an RU.Fig. 29 is a block diagram illustrating a DU.Fig. 30 is a block diagram illustrating a CU.Fig. 31 is a block diagram illustrating an AMF.Fig. 32 is a block diagram illustrating an SMF.Fig. 33 is a block diagram illustrating a UPF.Fig. 34 is a block diagram illustrating a PCF.Fig. 35 is a block diagram illustrating an NWDAF.Fig. 36 is a block diagram illustrating a UDM.Fig. 37 is a block diagram illustrating an AUSF.Fig. 38 is a block diagram illustrating an AAnF.Fig. 39 is a block diagram illustrating an NRF.Fig. 40 is a block diagram illustrating an NEF.Fig. 41 is a block diagram illustrating a UDR.Fig. 42 is a block diagram illustrating an OAM.Fig. 43 is a block diagram illustrating an AF.

[0015] <Abbreviations> 　　For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. 4G-GUTI　　4G Globally Unique Temporary UE Identity 5GC　　5G Core Network 5GLAN　　5G Local Area Network 5G HE AV　　5G Home Environment Authentication Vector 5G SE AV　　5G Serving Environment Authentication Vector 5GS　　5G System 5G-AN　　5G Access Network 5G-AN PDB　　5G Access Network Packet Delay Budget 5G-EIR　　5G-Equipment Identity Register 5G-GUTI　　5G Globally Unique Temporary Identifier 5G-BRG　　5G Broadband Residential Gateway 5G-CRG　　5G Cable Residential Gateway 5G GM　　5G Grand Master 5G-RG　　5G Residential Gateway 5G-S-TMSI　　5G S-Temporary Mobile Subscription Identifier 5G VN　　5G Virtual Network 5QI　　5G QoS Identifier AAnF　　AKMA Anchor Function ABBA　　Anti-Bidding down Between Architectures AF　　Application Function A-KID　　AKMA Key Identifier AKMA　　Authentication and Key Management for Applications AMBR　　Aggregated Maximum Bit Rate AMF　　Access and Mobility Management Function AMF-G　　Geographically selected Access and Mobility Management Function AMF-NG　　Non-Geographically selected Access and Mobility Management Function ANDSF　　Access Network Discovery and Selection Function AP　　Authentication Proxy AR　　Augmented Reality ARFCN　　Absolute radio-frequency channel number AS　　Access Stratum ASN　　Abstract Syntax Notation A-TID　　AKMA Temporary UE Identifier ATSSS　　Access Traffic Steering, Switching, Splitting ATSSS-LL　　ATSSS Low-Layer AuC　　Authentication Centre AUSF　　Authentication Server Function AUTN　　Authentication token BCCH　　Broadcast Control Channel BMCA　　Best Master Clock Algorithm BSF　　Binding Support Function CAG　　Closed Access Group CAPIF　　Common API Framework for 3GPP northbound APIs CDR　　Charging Data Record CHF　　Charging Function CN PDB　　Core Network Packet Delay Budget CP　　Control Plane CSG　　Closed Subscriber Group DAPS　　Dual Active Protocol Stacks DL　　Downlink DN　　Data Network DNAI　　DN Access Identifier DNN　　Data Network Name DRX　　Discontinuous Reception DSATSSS　　Dual Steer Access Traffic Steering, Switching, Splitting DSATSSS-LL　　Dual Steer Access Traffic Steering, Switching, Splitting- Low-Layer DSMA　　Dual Steer Multi Access DS-TT　　Device-side TSN translator ePDG　　evolved Packet Data Gateway EBI　　EPS Bearer Identity ECGI　　E-UTRAN Cell Global Identifier EPS　　Evolved Packet System EUI　　Extended Unique Identifier FAR　　Forwarding Action Rule FN-BRG　　Fixed Network Broadband RG FN-CRG　　Fixed Network Cable RG FN-RG　　Fixed Network RG FQDN　　Fully Qualified Domain Name GCI　　Global Cable Identifier GEO　　Geostationary Earth Orbit GFBR　　Guaranteed Flow Bit Rate GMLC　　Gateway Mobile Location Centre GNSS　　Global Navigation Satellite System G-PDU　　GTP encapsulated user Plane Data Unit GPS　　Global Positioning System GPSI　　Generic Public Subscription Identifier GSO　　Geosynchronous Orbit GUAMI　　Globally Unique AMF Identifier GUTI　　Globally Unique Temporary UE Identity HPLMN　　Home Public Land Mobile Network HR　　Home Routed (roaming) HSS　　Home Subscriber Server IAB　　Integrated access and backhaul IEC　　International Electrotechnical Commission IMEI / TAC　　IMEI Type Allocation Code IMSI　　International Mobile Subscriber Identity IPsec　　Internet Protocol Security IPUPS　　Inter PLMN UP Security I-SMF　　Intermediate SMF ISO　　International Organization for Standardization I-UPF　　Intermediate UPF KAF　　AKMA Application Key KAKMA　　AKMA Anchor Key LADN　　Local Area Data Network LBO　　Local Break Out (roaming) LCS　　Location Service LEO　　Low Earth Orbit LMF　　Location Management Function LoA　　Level of Automation LPP　　LTE Positioning Protocol LRF　　Location Retrieval Function MA　　Multi Access MCC　　Mobile country code MCX　　Mission Critical Service MDBV　　Maximum Data Burst Volume ME　　Mobile Equipment MFBR　　Maximum Flow Bit Rate MIB　　Master Information Block MICO　　Mobile Initiated Connection Only MINT　　Minimization of service interruption MITM　　Man In the Middle MME　　Mobility Management Entity MN　　Master Node MNC　　Mobile Network Code MNO　　Mobile Network Operator MOCN　　Multiple Operator Core Network MPS　　Multimedia Priority Service MPTCP　　Multi-Path TCP Protocol MR　　Mixed Reality MT　　Mobile Termination, Mobile Terminating, Mobile terminated N3IWF　　Non-3GPP InterWorking Function N3GPP　　Non-3GPP access N5CW　　Non-5G-Capable over WLAN NAI　　Network Access Identifier NAS　　Non-Access-Stratum NCGI　　NR Cell Global Identity NCI　　NR Cell Identity NEF　　Network Exposure Function NF　　Network Function NGAP　　Next Generation Application Protocol NGSO　　Non-Geosynchronous Orbit NID　　Network identifier NMEA　　National Marine Electronics Association NPN　　Non-Public Network NR　　New Radio NSAG　　Network Slice Access Stratum Group NRF　　Network Repository Function NSAC　　Network Slice Admission Control NSACF　　Network Slice Admission Control Function NSI ID　　Network Slice Instance Identifier NSSAA　　Network Slice-Specific Authentication and Authorization NSSAAF　　Network Slice-Specific Authentication and Authorization Function NSSAI　　Network Slice Selection Assistance Information NSSF　　Network Slice Selection Function NSSP　　Network Slice Selection Policy NSSRG　　Network Slice Simultaneous Registration Group NTN　　Non-Terrestrial Networks NW-TT　　Network-side TSN translator NWDAF　　Network Data Analytics Function OAM　　Operations, Administration, and Maintenance PCF　　Policy Control Function PCO　　Protocol Configuration Options PCRF　　Policy and Charging Rules Function PDB　　Packet Delay Budget PDR　　Packet Detection Rule PDU　　Protocol Data Unit PEI　　Permanent Equipment Identifier PER　　Packet Error Rate PFD　　Packet Flow Description PLMN　　Public Land Mobile Network PNI-NPN　　Public Network Integrated Non-Public Network PPD　　Paging Policy Differentiation PPF　　Paging Proceed Flag PPI　　Paging Policy Indicator ProSe　　Proximity based Services PSA　　PDU Session Anchor PTP　　Precision Time Protocol QFI　　QoS Flow Identifier QoE　　Quality of Experience QoS　　Quality of Service RACS　　Radio Capabilities Signalling optimisation (R)AN　　(Radio) Access Network RAT　　Radio Access Technology RFID　　Radio Frequency Identification RG　　Residential Gateway RID　　Routing Indicator RIM　　Remote Interference Management RQA　　Reflective QoS Attribute RQI　　Reflective QoS Indication RRC　　Radio Resource Control RSC　　Relay Service Code RSD　　Route Selection Descriptor RSN　　Redundancy Sequence Number RSRP　　Reference Signal Received Power RSRQ　　Reference Signal Received Quality RTT　　Round-Trip Time RVAS　　Roaming Value Added Service SA NR　　Standalone New Radio SBA　　Service Based Architecture SBI　　Service Based Interface SCP　　Service Communication Proxy SD　　Slice Differentiator SEAF　　Security Anchor Functionality SENSE　　Signal Level Enhanced Network Selection SEPP　　Security Edge Protection Proxy SGW　　Serving Gateway SIB　　System Information Block SINR　　Signal to Interference plus Noise Ratio SLA　　Service Level Agreement SMF　　Session Management Function SMS　　Short Message Service SMSF　　Short Message Service Function SN　　Sequence Number SN　　Secondary Node SN name　　Serving Network Name. SNPN　　Stand-alone Non-Public Network S-NSSAI　　Single Network Slice Selection Assistance Information SOR　　Steering of Roaming SSC　　Session and Service Continuity SSCMSP　　Session and Service Continuity Mode Selection Policy SST　　Slice / Service Type SUCI　　Subscription Concealed Identifier SUPI　　Subscription Permanent Identifier SV　　Software Version TAI　　Tracking Area Identity TAU　　Tracking Area Update TEID　　Tunnel Endpoint Identifier TMGI　　Temporary Mobile Group Identity TMSI　　Temporary Mobile Subscriber Identity TNAN　　Trusted Non-3GPP Access Network TNAP　　Trusted Non-3GPP Access Point TNGF　　Trusted Non-3GPP Gateway Function TNL　　Transport Network Layer TNLA　　Transport Network Layer Association TSC　　Time Sensitive Communication TSCAI　　TSC Assistance Information TSN　　Time Sensitive Networking TSN GM　　TSN Grand Master TSP　　Traffic Steering Policy TT　　TSN Translator TWIF　　Trusted WLAN Interworking Function UCMF　　UE radio Capability Management Function UCU　　UE Configuration Update UDM　　Unified Data Management UDR　　Unified Data Repository UDSF　　Unstructured Data Storage Function UE　　User Equipment UL　　Uplink UL CL　　Uplink Classifier UPF　　User Plane Function UPSI　　UE Policy Section Identifier URLLC　　Ultra Reliable Low Latency Communication URRP-AMF　　UE Reachability Request Parameter for AMF URSP　　UE Route Selection Policy USIM　　User Services Identity Module VID　　VLAN Identifier VLAN　　Virtual Local Area Network VPLMN　　Visited Public Land Mobile Network VR　　Virtual Reality W-5GAN　　Wireline 5G Access Network W-5GBAN　　Wireline BBF Access Network W-5GCAN　　Wireline 5G Cable Access Network W-AGF　　Wireline Access Gateway Function WPT　　Wireless Power Transfer

[0016] <Definitions> 　　For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].

[0017] <General> 　　Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0018] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspect illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

[0019] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an Aspect", "in another Aspect" and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

[0021] In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.

[0022] As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.

[0023] Each of Aspects and elements included in the each of Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.

[0024] Any lists described in following aspects include at least one parameter or multiple parameters.

[0025] An example object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problem.

[0026] In this disclosure, two architectures for satellite access are assumed. One is a satellite access as Uu transport and the other one is RAN on Satellite.

[0027] Fig. 1 illustrates the architecture for satellite access as Uu transport. 　　This architecture has the following characteristics: 　　- A RAN 5 and a Gateway are at the ground. 　　- The Gateway communicates with a Satellite over the Feeder link while the Satellite communicates with the UE 3s over the Service link. 　　- The Service link, the Gateway link and a dedicated link between the Gateway and RAN 5 provide the Uu interface (reference point). 　　- RAN 5 may communicate with multiple Satellites. 　　- Satellite may communicate with multiple RAN 5s. 　　- It is assumed that the RAN 5 has configuration data of all connected Satellites.

[0028] Fig. 2 illustrates the architecture for RAN on Satellite.

[0029] This architecture has the following characteristics: 　　- RAN 5 is located on the satellite. 　　- RAN 5 on the satellite communicate with the Gateway over the Feeder link. The Feeder link may support N2 and N3 interfaces (reference points). 　　- Some functionalities of a core network node or some core network nodes may be located at the Satellite. In this case, the Feeder link may support SBI (Service Based Interface) between core network nodes. 　　- The Service link, the Gateway link and a dedicated link between the Gateway and RAN 5 provide the N1 interface (reference point). 　　- RAN 5 may communicate with multiple Core Network nodes. 　　- Satellite may have multiple RAN 5s on board.

[0030] In this disclosure, the Satellite, Satellite access, NTN and NTN access imply a space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO) typically at an altitude between 500 km to 2000 km, Medium-Earth Orbit (MEO) typically at an altitude between 8000 to 20000 km, or Geostationary-satellite Earth Orbit (GEO) at 35786 km altitude.

[0031] In addition, the Satellite, Satellite access, NTN and NTN access may imply Highly Elliptical Orbiting (HEO) satellites as well as Unmanned Aircraft Systems (UAS) encompassing tethered UAS (TUA), Lighter than Air UAS (LTA), Heavier than Air UAS (HTA), all operating in altitudes typically between 8 and 50 km including High Altitude Platforms (HAPs).

[0032] In this disclosure, the Satellite, the Satellite access, the NTN and the NTN access may be interpreted as a multi-orbit satellite or a multi-orbit satellite access.

[0033] In this disclosure, the Satellite and Satellite access may be interpreted as the NTN and the NTN access, respectively. 　　In this disclosure, the NTN and the NTN access may be interpreted as the Satellite and Satellite access respectively.

[0034] <First Aspect> 　　This aspect includes mechanisms for UE 3 to discover a satellite adequate for access with 3GPP cellular system.

[0035] If the UE 3 considers the discovered satellite as adequate for access with 3GPP cellular system, the UE 3 may register to the 3GPP system through the discovered satellite.

[0036] Note that the First Aspect focuses on provisioning satellite related information to the UE 3 for satellite discovery. The disclosed mechanisms in the First Aspect will be referred and used by both Second Aspect and Third Aspect in their disclosing procedures.

[0037] <First example of the First Aspect> 　　This example discloses mechanisms for satellite discovery in 3GPP system.

[0038] The UE 3 obtains satellite information from the RAN 5, AMF 70, PCF 73 or AF 201.

[0039] Fig. 3 depicts examples of satellite information provisioning for the satellite access.

[0040] The following bullets explain assumptions in Fig. 3. 　　- RAN 501 provides access with a Satellite as non-terrestrial network access or cells at grand as a terrestrial network access (TN access). 　　- RAN 502 provides access with a Satellite as non-terrestrial network access. Cells with RAN 502 may be accessible by the UE 3 as neighbouring cells for UE 3. 　　- UE 3 may be an idle mode or inactive mode or active mode camping on a cell with the RAN 501.

[0041] <Example 1> 　　In this Example, the RAN 501 provides satellite information for both its own satellite information and neighbouring satellite information.

[0042] Step 1-1. Cells with the RAN 501 broadcast the following information to the UE 3 as the system information to covering area. 　　In case that cells with the RAN 501 are at the ground as a Terrestrial Network (TN), the cells broadcast only those of information related to neighbouring satellite(s).

[0043] The system information may be broadcast over the MIB, existing SIB or new SIB. 　　- NTN profile: The NTN profile indicates a profile of the satellite. The NTN profile may be expressed by other ways. For example, Satellite profile, Satellite access profile, RAT profile or any other notation for the information that defines the profile of a satellite. 　　- The NTN profile may include the following information: 　　- RAT type: The RAT type may be referred as Radio Access Technology (RAT) type. The RAT type indicates the radio access technology that serves the UE 3. The RAT type may be the RAT type as defined in 3GPP TS 29.212 [7] Section 5.3.31. 　　In one example if the UE 3 is acting as Relay Node (RN) and the UE 3 is acting as RN then the UE 3 will broadcast the same RAT type as the serving cell of the UE 3. For example, if the UE 3 is served by a GEO satellite cell, then the UE 3 broadcasts RAT type GEO as RN. 　　- Satellite Service provider: The Satellite Service provider indicates the Service provider of the satellite access. The Satellite Service provider may have a contract with the PLMN operator for providing the Uu interface over the satellite for a connectivity service by the PLMN. For example, a Satellite Service provider may be expressed by a normalized numeric number of the Service provider or Service provider name with the FQDN format. 　　- Satellite Service name: The Satellite Service name indicates the Service name of the satellite access provided by the Service provider. For example, a Satellite Service name may be expressed by a normalized numeric number for the Service name or Service name with the FQDN format. 　　- Satellite identifier: The Satellite identifier identifies the satellite. The Satellite identifier may be defined by the Service provider or a satellite related organization. 　　- For example, the Satellite identifier may be a Satellite Catalog Number (SATCAT, also known as NORAD (North American Aerospace Defense) Catalog Number, NORAD ID, USSPACECOM (United States Space Command) object number or simply catalog number) 　　- Frequency band: The Frequency band indicates the frequency band that the satellite communicates with UE 3. The Frequency band may be called as NTN frequency range. The Frequency band may include NR-ARFCN and the global frequency channel raster as defined in 3GPP TS 38.101-5 [8]. 　　- Altitude: Average altitude of the satellite. For example, Altitude of GEO is 35 786 km. 　　- Altitude offset: The Altitude offset is a relative priority for cell selection and reselection based on altitude of the satellite. For example, this value is referred by the UE 3 for cell selection and reselection resulting with boost for cells with lower altitude satellite. The Altitude offset can be expressed another way. For example, mobility priority, target cell priority, TAI priority, TAC priority, target TAI priority, target TAC priority, cell selection / reselection priority. 　　- Motion characteristics: The Motion characteristics provides a motion related information of the satellite. It may include the following information: 　　　　-- Moving cell pattern: The Moving cell pattern indicates the relative motion of the cell pattern with respect to the tracking area. 　　　　-- Doppler shift related parameter: The Doppler shift related parameter indicates characteristics of the Doppler shift due to the relative velocity between the satellite and the UE 3. the Doppler shift related parameter helps the UE 3 for the Initial downlink synchronization. 　　　　-- Cell size: The Cell size indicates a size of cell. 　　- Obit information: The Obit information provides the Obit information of the satellite. The Obit information helps the UE 3 to tune to the satellite. The Obit information may be expressed by Obit parameters with the Two-Line Elements (TLE) method. The Obit parameters with the TLE method may be used by the UE 3 to find the location and velocity using the SGP4 (Simplified General Perturbations Satellite Orbit Model 4) calculation algorism. 　　- Elevation angle: The Elevation angle defines a minimum Elevation angle that the UE 3 can take for a communication with the satellite. 　　- Moving reference location - reference location of the serving cell at a time reference, which may be used in the evaluation of events / conditional events for handover and location-based measurement initiation in RRC_IDLE / RRC_INACTIVE when distanceThresh is also configured, as defined in TS 3GPP 38.304

[0014] . 　　- Validity time: The Validity time indicates a time duration which the satellite is available for a coverage area of a cell in the satellite. The Validity time may include the following information: 　　　　-- Starting time: The time which the satellite becomes available. 　　　　-- Ending time: The time which the satellite becomes unavailable available. 　　- Incompatible service: This Incompatible service indicates connectivity services that the satellite does not provide. The Incompatible service may be indicated by the APN, DNN, S-NSSAI, S-NSSAI with Slice / Service type (SST), Connection capability identifier as defined in 3GPP TS 24.526

[0016] , or 5G QoS characteristics as defined in the 3GPP TS 23.501 [3] or application id not supported in the cell of the satellite. 　　- Compatible service: This is opposite to the incompatible service. This compatible service indicates connectivity services that the satellite provides. The compatible service may be indicated by the APN, DNN, S-NSSAI, S-NSSAI with Slice / Service type (SST), Connection capability identifier as defined in 3GPP TS 24.526

[0016] , or 5G QoS characteristics as defined in the 3GPP TS 23.501 [3] or application id not supported in the cell of the satellite. 　　- Prohibited area for satellite: The Prohibited area for satellite indicates Prohibited area for use of satellite. The Prohibited area for satellite is referred as a geographical location where the satellite Service is prohibited to provide or cannot be provided. For example, Prohibited area for satellite can be a Tracking Area Identity (TAI), NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5], NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5], E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5], Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5], a general City name, zip-code, formed with GPS location, a location expressed with civic and geospatial location formats as defined in IETF RFC 5580 [9] or Mobile Country Code (MCC) as defined by the ITU-T Recommendation E.212

[0010] . 　　- The Prohibited area for satellite may be expressed by another ways. For example, Prohibited area list, Prohibited country list or Black country list. 　　- Allowed area for satellite: The Allowed area for satellite indicates Allowed area for use of satellite. The Allowed area for satellite is referred as a geographical location where the satellite Service is Allowed to provide or can be provided. For example, Allowed area for satellite can be a Tracking Area Identity (TAI), NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5], NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5], E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5], Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5], a general City name, zip-code, formed with GPS location, a location expressed with civic and geospatial location formats as defined in IETF RFC 5580 [9] or Mobile Country Code (MCC) as defined by the ITU-T Recommendation E.212

[0010] . 　　- The Allowed area for satellite may be expressed by another ways. For example, Allowed area list, Allowed country list or White country list. The allowed area for the satellite may be associated with the satellite id of the satellite. In this case the allowed area is sent together with the satellite id and the allowed area is applicable in the area handled by the satellite identified with the satellite identifier. 　　- NTN performance status: The NTN performance status indicates the performance status of the satellite. The NTN performance status may be expressed by other ways. For example, Satellite performance status, Satellite access performance status, RAT performance status, NTN QoS, Satellite QoS and etc. 　　- The NTN performance status may include the following information: 　　- Propagation delay: The Propagation delay indicates an expected delay time for communication between the UE 3 and the satellite with the Typical minimum Elevation Angle for the UE 3. 　　- Congestion level: The Congestion level indicates that the Congestion level in the satellite. The Congestion level may be expressed by a Weight Factors. 　　- Backoff time: The Backoff time indicates a time period for the UE 3 not to contact the satellite after the last uplink signalling has been rejected with a Backoff time provided by the satellite due to a congestion in the satellite. 　　- Total serving cell capacity: The serving cell capacity indicates maximum number of the UEs that can be served by the cell e.g. registration and providing service in the cell (total number of IMS call). It can also broadcast maximum limit of each service supported by the cell. for example, the cell has capacity to support 100 IMS call, 100 browsing sessions, etc. 　　- Available cell capacity: The available cell capacity indicates the number of the UE the cell can provide the service at the moment e.g. registration procedure, service request procedure or possible number of IMS calls. It can also broadcast for each services the total number of the service can be made. For example, 50 IMS calls can be made or 50 browsing sessions possible. In one example if the available cell capacity is full or the cell or RAT or TAC or PLMN is congested or capacity is full then the cell broadcasts or RAN or the network function (e.g. AMF) sends an information element indicating the current cell, RAT, TAC, system (e.g. 5GS or EPS) or registered or current PLMN is congested or no resource available respectively. The cell or the RAN or a NF may also broadcast or send alternate RAT, TAC, system (e.g. 5GS or EPS) or alternate PLMN. 　　- Data bearer performance status: The Data bearer performance status indicates the expected data bearer performance that one UE or one PDU Session can obtain. The Data bearer performance status may include the following information: 　　　　-- Expected Aggregate Maximum Bit Rate (EAMBR) - UL and DL: The Expected AMBR that one UE or one PDU Session may be provided by the satellite at present time. This parameter may be referred by the UE 3 in case the UE 3 tries to hand over to the satellite. 　　　　-- Expected Guaranteed Flow Bit Rate (EGFBR) - UL and DL: The Expected GFBR that one UE or one PDU Session may be provided by the satellite at present time. This parameter may be referred by the UE 3 in case the UE 3 tries to hand over to the satellite. 　　　　-- Expected Maximum Flow Bit Rate (EMFBR) - UL and DL: The Expected MFBR that one UE or one PDU Session may be provided by the satellite at present time. This parameter may be referred by the UE 3 in case the UE 3 tries to hand over to the satellite. 　　- List of Neighbouring NTN profile: The List of Neighbouring NTN profile indicates a profile of the neighbouring satellite(s) that the UE 3 may be able to access. The List of Neighbouring NTN profile may be referred by the UE 3 when the UE 3 considers a neighbouring satellite as a target cell for the Mobility Management and the Session Management. 　　- The List of NTN profile may include the following information per NTN entity in this list: 　　- All information in the NTN profile as disclosed in Step 1-1 for neighbouring satellite(s) that the UE 3 may be able to access with. 　　- List of Neighbouring NTN performance status: The List of Neighbouring NTN performance status indicates the performance status of the neighbouring satellite(s) that the UE 3 may be able to access. The List of Neighbouring NTN performance status may be referred by the UE 3 when the UE 3 considers a neighbouring satellite as a target cell for the Session Management. 　　- The NTN performance status may include the following information per NTN entity in this list: 　　- All information in the NTN performance status as disclosed in Step 1-1 for neighbouring satellite(s) that the UE 3 may be able to access with.

[0044] Step 1-2. The RAN 501 sends the RRC message to the UE 3 when the UE 3 has a dedicated RRC signalling connection with the RAN 501.

[0045] The RRC message carries the following information to the UE 3. The RRC message may be new RRC message or an existing RRC message. Refer to 3GPP TS 38.331

[0015] Section 6.2 for details. 　　- NTN profile: The NTN profile indicates the profile of the satellite. Refer to Step 1-1 for the NTN profile in detail. 　　- NTN performance status: The NTN performance status indicates the performance status of the satellite. Refer to Step 1-1 for the NTN performance status in detail. 　　- List of Neighbouring NTN profile: The List of Neighbouring NTN profile indicates the profile of the neighbouring satellite. Refer to Step 1-1 for the List of Neighbouring NTN profile in detail. 　　- The contents of the List of Neighbouring NTN profile over the RRC message may be screened (trimmed down) based on the UE 3 context in the RAN 5. For example, if the UE 3 is restricted to access with GEO satellite, satellites with RAT type equals to GEO may not be included. 　　- List of Neighbouring NTN performance status: The List of Neighbouring NTN performance status indicates the performance status of the neighbouring satellite. Refer to Step 1-1 for the Neighbouring NTN performance status in detail. 　　- The contents of the List of Neighbouring NTN performance status over the RRC message may be screened (trimmed down) based on the UE 3 context in the RAN 5. For example, if the UE 3 is restricted to access with GEO satellite, satellites with RAT type equals to GEO may not be included.

[0046] Alternatively, the satellite information for both, the current satellite's satellite information (its own satellite information) and the neighbouring satellite's satellite information, as described in step 1-1, may be provided by the RAN 501 to the UE 3 in a dedicated RRC signalling, especially when the UE 3 is already in an RRC connected mode. The satellite information can be related to the UE 3 within one of the existing RRC messages, like RRC Setup message or RRC Connection Reconfiguration message, for example or in a new RRC message. Refer to 3GPP TS 38.331

[0015] Section 6.2 for details.

[0047] In one example when the RAN 501 is congested or has limited resource then the RAN 501 sends neighbouring NTN cells list or neighbouring TN cells, frequency of the neighbouring NTN cell or satellite IDs to which the UE should camp in an existing RRC message or a new RRC message e.g. RRC Release or RRC Reject or RRC reconfiguration message. When the UE 3 receives the RRC message, the UE 3 tries to camp on the cells associated with the received satellite ids, frequencies or NTN cell. The UE 3 doesn't try to camp on the current cell where it has received the RRC message for an implementation time or in one example the RAN 501 also includes back off timer and the UE 3 shall not consider the serving cell for the cell selection or reselection till the back off timer expires.

[0048] In one example, when the UE 3 reads the serving cell the performance status and the available cell capacity indicates that the service is not possible e.g., total number of IMS call is zero then the UE 3 reads neighbouring cell performance status and selects the neighbouring cell which can provide the IMS call. The UE 3 then initiates service request procedure on the selected cell to establish IMS call. After the IMS call is finished the UE 3 can perform the cell reselection or selection procedure. Similarly, when the UE3 a selects a cell to camp on and perform registration procedure to get a service, if the cell indicates that it is not possible to register another UE 3, then the UE 3 selects another cell where the registration is possible. If the UE 3 knows that the cell as per information received in available cell capacity that the current cell, RAT, TAC, system (e.g. 5GS or EPS) or registered or current PLMN is congested or no resource available respectively the UE 3 may perform at least one of the following actions: 　　- selects a cell as per information sent in the alternative cell. 　　- selects a cell on a RAT as per the information present in alternate RAT. 　　- selects a cell on another TAC as per information present in the alternate TAC. 　　- selects a cell of a system as per the information present in the alternate system. 　　- selects a cell of a PLMN as per the information present in the alternate PLMN.

[0049] The UE 3 may disable the RAT capability of the current congested RAT or congested system capability or TAC in the forbidden TAI list or PLMN ID in the forbidden PLMN list or a new list called congested or barred PLMN list. When the UE 3 initiates a NAS procedure (e.g., registration procedure) on the selected cell as per the above procedure or any other cell at any other time, the UE includes at least one of the congested cell, disabled RAT, disable system or forbidden PLMN or forbidden TAI as per the above procedure or any 5GMM back off timer (e.g T3346) or 5GSM back off timer (T3396 for an DNN) running as defined in 3GPP TS 24.501

[0012] to the AMF 70 in an existing NAS message (Registration Request message) or a new NAS message. If the network decides to re-enable the RAT, remove PLMN ID from the congested PLMN list or forbidden PLMN list or remove the TAI from the forbidden TAI list or re enable the RAT or system for the cell selection procedure, then the AMF 70 indicates this to the UE 3 by including an existing information element or new information element including at least one of the following value, forbidden or congested PLMN ID, or back off timer or forbidden or congested TAI, or disable RAT or disable system as per value received in this embodiment from the UE 3 in an existing NAS message or a new NAS message during an existing NAS procedure (UE Configuration Update (UCU) command message during UCU procedure or Registration accept message during registration update procedure) or a new NAS procedure to send the information element to the UE 3. The UE 3 receives the information element in the NAS message the UE 3 takes one of the following actions: 　　- if the information element includes RAT, then the UE re-enable the RAT. The UE 3 may select a cell on this RAT. The RAT is removed from the forbidden RAT list or congested RAT list. 　　- if the information element includes PLMN ID then the UE may select a cell of this PLMN. This PLMN ID is removed from the forbidden PLMN ID list or congested PLMN ID list. 　　- if the information element includes System, then UE 3 may select the cell of the system. The UE 3 removes this system from congested system list. 　　- if the information element includes a 5GSM back off timer or 5GMM back off timer then UE 3 stops the back off timer and may take action when the back off timer expires as defined in 3GPP TS 24.501

[0012] .

[0050] When the resource in the congested cell is available for the UE 3s as the congestion mitigated, the cell either stops broadcasting cell is congested or set the value to 0 in the corresponding field in the available cell capacity. When The UE 3 reads this information element indicating that the cell is no longer congested then the UE 3 may consider this cell for cell selection or reselection.

[0051] <Example 2> 　　In this Example, the AMF 70 provides satellite information for both its own satellite information and neighbouring satellite's satellite information over the NAS message.

[0052] Step 2-1. The AF 201 sends the Naf service notification message to the UDM 75 including a List of NTN profile. In case that the AF 201 is located outside of the PLMN domain, the AMF 201 sends the Naf service notification message to the UDM 75 via the NEF 79.

[0053] Note that the UDM 75 subscribes for the AF service provided by the AF 201 beforehand. Similarly, the NEF 79 subscribes for the AF service provided by the AF 201 beforehand.

[0054] The List of NTN profile may be sent to the UDM 75 or to the NEF 79 based on a business agreement between the Satellite service provider and the PLMN operator.

[0055] The List of NTN profile includes all satellite information that are available to use by the PLMN operator based on the business agreement.

[0056] The List of NTN profile includes the NTN profile as disclosed in Step 1-1 for relevant satellite(s) for the PLMN operator.

[0057] Step 2-2. Upon reception of the Naf service notification message from the AF 201, the UDM 75 sends the Nudm service notification message to the AMF 70 including the List of NTN profile. The list of NTN profile may be the one received from the AF 201 at Step 2-1 or a screened (trimmed down) list from the one received from the AF 201 taking a coverage area of the AMF 70 into account by the UDM 75.

[0058] Th UDM 75 may send multiple Nudm service notification messages to the AMF 70 that are relevant for the connectivity service using NTN.

[0059] In addition, the UDM 75 further screens and possible trims down the list of NTN profile taking other aspects into account. For example, if the AMF 70 covers only an area that is subject for Prohibited area for satellite, such satellite information should be removed from the NTN profile list.

[0060] Note that the AMF 70 subscribes for the UDM service provided by the UDM 75 beforehand.

[0061] Step 2-3. Upon reception of the Nudm service notification message from the UDM 75, the AMF 70 sends a NAS message to the RAN 501 including the List of NTN profile. The list of NTN profile may be the one received from the UDM 75 or a screened (trimmed down) list from the one received from the UDM 75 taking a coverage area of the RAN 501 into account by the AMF 70.

[0062] Th AMF 70 may send multiple NAS messages to the RAN 501s that are relevant for the connectivity service using NTN.

[0063] In addition, the AMF 70 further screens and possible trims down the list of NTN profile taking other aspects into account. For example, if the RAN 501 covers only area that are subject for Prohibited area for satellite, such satellite information should be removed from the NTN profile list.

[0064] In another example, if the AMF 70 has a UE context of the UE 3 that indicates the allowed or / and prohibited satellite list such as downloaded from the UDM 75 as the subscriber data, the AMF 70 further screens and possible trims down the list of NTN profile taking the allowed or prohibited satellite list into account.

[0065] The NAS message may be a Registration accept message, DL NAS transport message, Configuration update command message, another existing NAS message or new NAS message. Refer to 3GPP TS 24.501

[0012] Section 8 for details.

[0066] Upon the UE 3 receives the NAS message including the list of NTN profile, the UE 3 use the list of NTN profile for discovering a satellite as a possible RAT to access with.

[0067] <Example 3> 　　In this Example, the PCF 73 provides satellite information as an access choice per application in the URSP rule.

[0068] Step 3-1. The same as Step 2-1. Refer to Step 2-1.

[0069] In addition, the UDM 75 may provide the List of NTN profile to individual subscriber data for relevant UE 3. the UDM 75 may refer to the allowed or / and prohibited satellite list in the subscription data for finding relevant UE 3. In this case, the UDM 75 sends the List of NTN profile to the UDR 7A in order to update a subscription profile in the UDR 7A.

[0070] Step 3-2. The UDM 75 sends the Nudm service notification message to the PCF 73 including the List of NTN profile.

[0071] Note that the PCF 73 subscribes for the UDM service provided by the UDM 75 beforehand.

[0072] In one example, the UDR 7A sends the Nudr service notification message to the PCF 73 including the List of NTN profile.

[0073] Note that the PCF73 subscribes to the UDR service provided by the UDM 7A beforehand.

[0074] Upon reception of the Nudm service notification message from the UDM 75 or Nudr service notification message from the UDR 7A, the PCF 73 generates a URSP rule based on the received List of NTN profile.

[0075] The PCF 73 may generate the URSP rule taking the UE 3 radio capability into account. For example, if the UE 3 radio capability indicates only Around 20 GHz for DL (Down Link) and Around 30 GHz for UL (Up Link)) as Ka band support, then the NTN profiles that uses Ka band are only listed in the URSP Rule.

[0076] The PCF 73 may generate the URSP rule taking the subscription information into account. For example, if the subscriber data for the UE 3 allows only Satellites provided by the Satellite Service provider A, then only the NTN profiles that provided by Satellite Service provider A are listed in the URSP Rule.

[0077] In one example, the URSP may structure as illustrated in Fig. 4.

[0078] In Fig. 4, The NTN profiles may be listed under the Route Selection Descriptor in the URSP Rule for the UE 3.

[0079] In one example, the NTN profiles are listed in order of decreasing priority, with the first NTN profile being the highest priority.

[0080] The NTN profile may be expressed by other ways. For example, Satellite profile, Satellite access profile, RAT profile and etc.

[0081] Each NTN profile may be composed of the NTN profile as defined in Step 1-1 or composed of only some parts of information that are relevant to the satellite selection.

[0082] Step 3-3. The PCF 73 sends the NAS message, via the AMF 70, including the URSP rule that includes the list of NTN profile.

[0083] The NAS message may be the Manage UE policy command message, DL NAS transport message, Configuration update command message, another existing NAS message or new NAS message.

[0084] Upon the UE 3 receiving the NAS message including the list of NTN profile, the UE 3 uses the list of NTN profile for discovering a satellite as a possible RAT to access with. The UE 3 sends the acknowledgement or response NAS message after the NAS message including NTN profile. For example, if the UE 3 receives Registration accept message containing the NTN profile, then the UE 3 sends Registration complete message letting the AMF 70 know that the UE 3 has received the NAS message carrying NTN profile.

[0085] <Example 4> 　　In this Example, the AF 201 provides satellite information as an access choice for the UE 3.

[0086] In one example, the AF 201 is an application that is managed by a Satellite Service provider.

[0087] Step 4. The AF 201 provides the NTN profile, NTN performance status, List of Neighbouring NTN profile and List of Neighbouring NTN performance status over the application layer to the UE 3.

[0088] In one example, as the AF 201 obtains an exact geographical location of the UE 3 over the application layer, the AF 201 provides above listed information that are only relevant to the UE 3 location.

[0089] Upon the UE 3 receiving the NAS message including the list of NTN profile, the UE 3 use the list of NTN profile for discovering a satellite as a possible RAT to access with.

[0090] In one example, for an APL -1 the priority order NTN access can be LEO>MEO>GEO. This implies when an APL-1 is active or accessed by the user and the UE 3 is under coverage of LEO, MEO and GEO, then the UE 3 selects a cell supported by LEO and establishes PDU session on the cell and data is transferred.

[0091] <Second Aspect> 　　This aspect discloses mechanisms for Mobility Management with Satellite access.

[0092] <First example of the Second Aspect> 　　The First example of the Second Aspect includes a mechanism for the UE 3 to obtain a list of preferred Radio Access Technology (RAT) in priority order based on an application that UE 3 may use.

[0093] The RAT may include all possible RATs or only NTN related RAT.

[0094] If the RAT is only NTN related RAT, the RAT can be referred as Satellite or NTN RAT.

[0095] Fig. 5 illustrates an example of a call flow for the Registration procedure with RAT priority provided to the UE 3.

[0096] The detailed processes of the First example of the Second Aspect are described below with reference to Fig. 5.

[0097] Step 0. The UDM 75 holds new subscriber data related to NTN access. New subscriber data includes the followings: 　　(The following data are mainly used in First example of the Second Aspect.) 　　- Prioritized RAT list: The Prioritized RAT list indicates the RAT priority for the UE 3. The UDM 75 may have the RAT priority per application id, APN, DNN, S-NSSAI, S-NSSAI with Slice / Service type (SST) or Connection capability identifier as defined in 3GPP TS 24.526

[0016] basis. 　　(The following data are mainly used in Second example of the Second Aspect.) 　　- Subscribed Satellite Service operator list: The Subscribed Satellite Service operator list includes Satellite Service operator(s) that the UE 3 subscribes to. The Subscribed Satellite Service operator list is used by the UDM 75 to provide possible NTNs (Satellites) to the AMF 70, RAN 5 and the UE 3 that the UE 3 is allowed to access. 　　- Subscribed Satellite Service name list: The Subscribed Satellite Service name list includes Satellite Service name(s) that the UE 3 subscribes to. The Subscribed Satellite Service name list is used by the UDM 75 to provide possible NTNs (Satellites) to the AMF 70, RAN 5 and the UE 3 that the UE 3 is allowed to access. 　　- NTN RAT restriction: The NTN RAT restriction is a list of RATs that indicates the RATs which the UE 3 is restricted to access. The NTN RAT restriction may be expressed by another way. For example, Satellite access restriction, Restricted Satellite, Restricted Satellite type, Restricted RAT or Restricted RAT type. If location information was provided within the NTN RAT restriction parameter, then the RATs access restrictions are valid only in the provided locations. If time information was provided within the NTN RAT restriction parameter, then the RATs access restrictions are valid only in the provided time windows. 　　- NTN RAT allowed: The NTN RAT allowed is a list of RATs that indicates the RAT(s) which the UE 3 is allowed to access. The NTN RAT allowed may have a priority among registered RATs in the NTN RAT allowed. The NTN RAT allowed may be expressed by another way. For example, Satellite access allowed, Allowed Satellite, Allowed Satellite type, Allowed RAT or Allowed RAT type. If location information was provided within the NTN RAT allowed parameter, then the RATs access priorities are valid only in the provided locations. If time information was provided within the NTN RAT allowed parameter, then the RATs access priorities are valid only in the provided time windows. 　　(The following data is mainly used in the Third Aspect.) 　　- Satellite handover type: The Satellite handover type defines how the handover to be executed with a cell with satellite. The Satellite handover type may be referred when the UE 3 hands over between a cell in TN and a cell in NTN, between cells in NTN but across different RAT type (i.e. across different obit type) 　　- The Satellite handover type may have following types: 　　- QoS adjustment before handover: With the knowledge of QoS after handover with new cell in different RAT type, the QoS for ongoing PDU Session is adjusted with a target QoS with a target cell in different RAT type. 　　- Redundant PDU session across two orbits: The PDU Session will be duplicated with appropriate QoS profiling with the RAT type before the handover over. Then, original PDU Session with the source cell is released after successful handover.

[0098] Step 1. A cell with RAN 5 broadcasts System Information including NTN profile, NTN performance status, List of Neighbouring NTN profile, List of Neighbouring NTN performance status. Refer to Step 1-1 in Fig. 3 for parameter details.

[0099] The System Information may be broadcasted over a MIB, existing SIB or new SIB. Refer to 3GPP TS 38.331

[0015] Section 5.2 for details.

[0100] Step 2. The UE 3 sends the RRC Setup Request message to the RAN 5 based on the received broadcast information in Step 1.

[0101] Step 3. The RAN 5 sends the RRC Setup message to the UE 3 including NTN profile, NTN performance status, List of Neighbouring NTN profile, List of Neighbouring NTN performance status. Refer to Step 1-1 in Fig. 3 for parameter details.

[0102] Step 4. The UE 3 sends the RRC Message number 3 message to the RAN 5 including Application specific prioritized RAT capability, UE NTN Radio capability and Dedicated NAS.

[0103] The following bullets explain each parameter in detail. For example, the RRC Message number 3 may correspond to RRC Setup Complete message. 　　- Application specific prioritized RAT capability: The Application specific prioritized RAT capability indicates that the UE 3 supports the Application specific prioritized RAT handling. The Application specific prioritized RAT handling enables the UE 3 to select or re-select a RAT taking Application into account. 　　- UE NTN Radio capability: The UE NTN Radio capability indicates the capability of equipped modem(s) in the UE 3 for accessing the NTN. The UE NTN Radio capability may be expressed by RAT(s), Satellite Service operator, Satellite Service name, or a combination of these parameters. 　　- Dedicated NAS: The Dedicated NAS is a container to convey NAS message from the UE 3 to RAN 5.

[0104] The RAN 5 may refer to the Application specific prioritized RAT capability and UE NTN Radio capability to select AMF 70 considering a capability of the AMF 70 for NTN related handling.

[0105] The Dedicated NAS includes the Registration Request message. The Registration Request message to the AMF 70 includes at least one of User ID, Application specific prioritized RAT capability, Application priority list, UE NTN Radio capability.

[0106] The following bullets explain each parameter in detail. 　　- User ID: User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI. 　　- Application specific prioritized RAT capability: Refer to the explanation of the RRC Message number 3 message in Step 4. 　　- Application priority list: The Application priority list indicates possible Applications that the UE 3 activates after this Registration procedure. The Application in the list may be listed in order of decreasing priority, with the first Application profile being the highest priority. The Application may be expressed by application id, APN, DNN, S-NSSAI, S-NSSAI with Slice / Service type (SST) or Connection capability identifier as defined in 3GPP TS 24.526

[0016] . 　　- UE NTN Radio capability: Refer to the explanation of the RRC Message number 3 message in Step 4.

[0107] Step 5. Upon reception of the RRC Message number 3 message from the UE 3, the RAN 5 sends the Initial UE message to the AMF 70 including NAS PDU. The NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 4.

[0108] Step 6. Upon reception of the Registration Request message in Step 5, the AMF 70 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, Application specific prioritized RAT capability, Application priority list and UE NTN Radio capability. 　　The following bullets explain each parameter in detail. 　　- SUPI: Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. 　　- Application specific prioritized RAT capability: Refer to Step 4. 　　- Application priority list: Refer to Step 4. 　　- UE NTN Radio capability: Refer to Step 4.

[0109] Step 7. Upon reception of the Nudm_UECM_Registration Request message in Step 6, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 70.

[0110] Step 8. After the completion of the Nudm_UECM_Registration service in Steps 6 and 7, the AMF 70 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI, Application specific prioritized RAT capability, Application priority list and UE NTN Radio capability. Refer to Step 6 for parameter details.

[0111] Step 9. The UDM 75 finds the Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3. The Subscriber data may include the Prioritized RAT list. 　　The following bullets explain each parameter in detail. 　　- Prioritized RAT list: The Prioritized RAT list indicates a priority of a RAT that the UE 3 is requested to select or re-select based on subscriber data. The Prioritized RAT list may include a list of RAT, Satellite Service operator, Satellite Service name, or a combination of these parameters. If location information was provided within the Prioritized RAT list, then the RATs access priorities are valid only in the provided locations. If time information was provided within the Prioritized RAT list, then the RATs access priorities are valid only in the provided time windows. 　　- The UDM 75 built up Prioritized RAT list based on the subscriber data of the UE 3 and referring to the received Application specific prioritized RAT capability, Application priority list and UE NTN Radio capability.

[0112] Step 10. The AMF 70 sends Npcf_policy_association Request message to a PCF 73 including SUPI, Application specific prioritized RAT capability, Application priority list, UE NTN Radio capability and Prioritized RAT list.

[0113] The following bullets explain each parameter in detail. 　　- SUPI: Refer to Step 6. 　　- Application specific prioritized RAT capability: Refer to Step 4. 　　- Application priority list: Refer to Step 4. 　　- UE NTN Radio capability: Refer to Step 4. 　　- Prioritized RAT list: Refer to Step 9

[0114] Steps 11 and 12. Upon reception of the Npcf_policy_association Request message in Step 10, The PCF 73 generates the URSP rule putting NTN related information based on the subscriber data of the UE 3 and referring to the received Application specific prioritized RAT capability, Application priority list, UE NTN Radio capability and Prioritized RAT list.

[0115] Refer to Fig. 4 for an example of the URSP rule for the UE 3.

[0116] Note that the PCF 73 obtains the subscriber data of the UE 3 from the UDR 7A as disclosed in Steps 3-1 and 3-2 in Fig. 3.

[0117] Step 13. The AMF 70 sends the Registration Accept message to the UE 3 including 5G-GUTI and Prioritized RAT list.

[0118] The following bullets explain each parameter in detail. 　　- 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3, Refer to 3GPP TS 23.003 [5] for details. 　　- Prioritized RAT list: Refer to Step 9.

[0119] Step 14. Upon reception of the Registration Accept message, the UE 3 sends the Registration Complete message to the AMF 70.

[0120] Step 15. The UE 3 stores the received Prioritized RAT list in the Registration Accept message into non-volatile memory in the UE 3.

[0121] UE 3 refers to the Prioritized RAT list when the UE 3 performs cell selection or re-selection.

[0122] Step 16. The PCF 73 sends Manage UE policy command message to the UE 3 including URSP Rule that has the NTN related information.

[0123] The UE 3 refers to the received NTN related information when an application in the UE 3 triggers to establish PDU Session.

[0124] <First Variant of First example of the Second Aspect> 　　In one example, whenever a current active application list in the UE 3 changes then the UE 3 sends the current active list to the AMF 70 in an existing NAS message (e.g., Service Request message UL NAS Transport message) or a new NAS message. The AMF 70 sends the current active application list to the PCF 73 or UDM 75 or PCF 73 in an existing message or a new message between the AMF 70 and PCF 73 or between AMF 70 and UDM 75 during an existing service or a new service operation. The PCF 73 or UDM 75 prioritizes the RATs for the current active application list depending on the current local condition, the UE 3 subscription and local policy. The PCF 73 or the UDM 75 sends the prioritize list to the AMF 70 which further sends it to the UE 3. The UE 3 uses the prioritize RAT list for RAT selection or reselection procedure to find suitable cell.

[0125] <Second example of the Second Aspect> 　　The Second example of the Second Aspect includes a mechanism for the UE 3 to obtain a list of NTN profile for satellite access.

[0126] Fig. 6 illustrates an example of call flow for the Registration procedure with List of NTN profile provided to the UE 3.

[0127] The detailed processes of the Second example of the Second Aspect are described below with reference to Fig. 6.

[0128] Step 1. Steps 0 to 3 in Fig. 5 take place.

[0129] Step 2. The UE 3 sends the RRC Message number 3 message to the RAN 5 including Dedicated NAS. The Dedicated NAS includes the Registration Request message. The Registration Request message to the AMF 70 includes at least one of User ID, NTN supported, Altitude based mobility supported, UE NTN Radio capability and GNSS location.

[0130] The following bullets explain each parameter in detail. 　　- User ID: User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI. 　　- NTN supported: The NTN supported indicates that the UE 3 support the NTN handling mechanism as disclosed by this disclosure. The NTN supported may be expressed another way. For example, Satellite access supported, multi-orbit satellite supported, multi-orbit satellite access supported. 　　- Altitude based mobility supported: The Altitude based mobility supported indicates that the UE 3 supports cell selection and reselection based on the Attitude of satellite. 　　- UE NTN Radio capability: Refer to Step 4 in Fig. 5. 　　- GNSS location: The GNSS location indicates a location of the UE 3 using the GNSS based notation. The GNSS location may be expressed by longitude and latitude or another notation. Example, a notation used by the GNSS.

[0131] Step 3. Upon reception of the RRC Message number 3 message from the UE 3, the RAN 5 sends the Initial UE message to the AMF 70 including NAS PDU. The NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 4.

[0132] Step 4. Upon reception of the Registration Request message in Step 5, the AMF 70 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, NTN supported, UE NTN Radio capability and GNSS location.

[0133] The following bullets explain each parameter in detail. 　　- SUPI: Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. 　　- NTN supported: Refer to Step 2. 　　- UE NTN Radio capability: Refer to Step 2. 　　- GNSS location: Refer to Step 2.

[0134] Step 5. Upon reception of the Nudm_UECM_Registration Request message in Step 4, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 70.

[0135] Step 6. After the completion of the Nudm_UECM_Registration service in Steps 4 and 5, the AMF 70 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI, NTN supported, UE NTN Radio capability and GNSS location. Refer to Step 4 for parameter details.

[0136] Step 7. The UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3. The Subscriber data may include the List of NTN profile.

[0137] The following bullets explain each parameter in detail. 　　- List of NTN profile: The List of NTN profile is a list of profiles of NTN that the UE 3 is allowed to access. For each entry of NTN profile, refer to Step 1-1 in Fig. 3. 　　- The List of NTN profile may be listed in order of decreasing priority, with the first NTN profile being the highest priority. 　　- The UDM 75 generates the List of NTN profile for the UE 3 taking the received NTN supported and UE NTN Radio capability in Step 6 into account. 　　- The UDM 75 generates the List of NTN profile for the UE 3 taking the received GNSS location in Step 6 into account. I.e., the UDM 75 generates a list of NTN profile that are available at UE 3's location. 　　- The UDM 75 generates the List of NTN profile for the UE 3 taking the UE 3 subscriber data. For example, the UDM 75 takes the Subscribed Satellite Service operator list as described in Step 0 of Fig. 5 and the Subscribed Satellite Service name list as described in Step 0 of Fig. 5 into account in UE 3's subscriber data. 　　- NTN RAT restriction: Refer to Step 0 in Fig. 5. 　　- NTN RAT allowed: Refer to Step 0 in Fig. 5.

[0138] Upon reception of the Nudm_SDM_Get Response message from the UDM 75, the AMF 70 generates the TAI list taking the received List of NTN profile, NTN RAT restriction and NTN RAT allowed in Step 7 into account.

[0139] In case that the AMF 70 received the Altitude based mobility supported in the Registration request message in Step 3, the AMF 70 generates the TAI list with the Altitude offset. In this case, each entry of the TAI in the TAI list may have an associated Altitude offset. Refer to Step 1-1 in Fig. 3 for detail of the Altitude offset.

[0140] Step 8. The AMF 70 sends the Initial Context Setup Request message to the RAN 5 including List of NTN profile, NTN RAT restriction, NTN RAT allowed and NAS PDU. The NAS PDU include the Registration Accept message that includes the 5G-GUTI, List of NTN profile, NTN RAT restriction, NTN RAT allowed and TAI list (TAI with Altitude offset).

[0141] The following bullets explain each parameter in detail. 　　- 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3, Refer to 3GPP TS 23.003 [5] for details. 　　- List of NTN profile: Refer to Step 7. 　　- NTN RAT restriction: Refer to Step 7. 　　- NTN RAT allowed: Refer to Step 7. 　　- TAI list (TAI with Altitude offset): The TAI list (TAI with Altitude offset) is a list of TAI indicating to the UE 3 as a Registration Area (RA) associating an Altitude offset o each TAI. Refer to Step 1-1 in Fig. 3 how the UE 3 uses an associated Altitude offset o each TAI.

[0142] The RAN 3 uses the received List of NTN profile, NTN RAT restriction, NTN RAT allowed for the handover procedure for selecting a target RAN.

[0143] The RAN 5 uses the received List of NTN profile, NTN RAT restriction, NTN RAT allowed for the SN Addition procedure as described in 3GPP TS 37.340

[0011] for selecting a Secondary Node (SN).

[0144] The NTN RAT restriction may be expressed by another ways, for example, NTN RAT restriction list, Satellite restriction list, Prohibited Satellite access list, RAT restriction for satellite access.

[0145] The NTN RAT allowed may be expressed by another ways, for example, NTN RAT allowed list, Satellite allowed list, Allowed Satellite access list, RAT allowed for satellite access.

[0146] One example, the NTN RAT restriction and NTN RAT allowed are sent from the AMF 70 to RAN 5 in sub fields of the Mobility Restriction list parameter in the Initial Context Setup Request message.

[0147] Step 9. The RAN 5 sends a RRC signalling includes NAS. The NAS includes the Registration Accept message that is received from the AMF in Step 8.

[0148] Step 10. Upon reception of the Registration Accept message, the UE 3 sends the Registration Complete message to the AMF 70.

[0149] Step 11. The UE 3 stores the received 5G-GUTI, List of NTN profile, NTN RAT restriction, NTN RAT allowed and TAI list (TAI with Altitude offset) in the Registration Accept message into non-volatile memory in the UE 3.

[0150] UE 3 refers to the List of NTN profile, NTN RAT restriction and NTN RAT allowed when the UE 3 performs cell selection or re-selection.

[0151] If the UE 3 received the TAI list (TAI with Altitude offset), the UE 3 scans neighbouring cells which has low Altitude offset from an Altitude offset of the current cell even the UE 3 has a good radio condition with the current cell.

[0152] In case that the UE 3 finds a neighbouring cell that has an Altitude offset lower than an Altitude offset of the current cell, the UE 3 may perform the cell selection or the cell reselect to that cell even the UE 3 has a good radio condition with the current cell.

[0153] With this Altitude offset based mobility management, the UE 3 is able to stay a cell with a satellite in the lowest altitude or a cell in the ground (I.e. a cell in the TN).

[0154] < First Variant of the Second Example of the Second Aspect> 　　In Step 11, although the UE 3 does not receive the TAI list (TAI with Altitude offset) in the Registration accept message in Step 9 but the UE 3 receives the Altitude offset in the NTN profile in the System information in Step 1-1 in Fig. 3 or RRC message in Step 1-2 in Fig. 3, the UE 3 may scan neighbouring cells which has low Altitude offset from an Altitude offset of the current cell even the UE 3 has a good radio condition with the current cell.

[0155] In case that the UE 3 finds a neighbouring cell that has an Altitude offset lower than an Altitude offset of the current cell, the UE 3 may perform the cell selection or the cell reselect to that cell even the UE 3 has a good radio condition with the current cell.

[0156] With this Altitude offset based mobility management, the UE 3 is able to stay a cell with a satellite in the lowest altitude or a cell in the ground (I.e. a TN cell).

[0157] <Second Variant of the Second Example of the Second Aspect> 　　In Step 8, List of NTN profile, NTN RAT restriction, NTN RAT allowed are sent from the AMF 70 to the RAN 5 by another NGAP message. For example, List of NTN profile, NTN RAT restriction, NTN RAT allowed are sent from the AMF 70 to the RAN 5 by Downlink NAS transport message, PDU Session Resource Setup message, PDU Session Resource Modify message, Handover request message, any existing NGAP message or new NGAP message.

[0158] <Third Variant of the Second Example of the Second Aspect> 　　In Step 1, In case that the UE 3 receives the Congestion level and Backoff timer over the system information or RRC message in Step 1-1 and Step 1-2 in Fig. 3 respectively, the UE 3 may use this information for the cell selection and the cell reselection in Step 11. For example, if the UE 3 finds a neighbouring cell that has an Altitude offset lower than an Altitude offset of the current cell but the found neighbouring cell is congested, then the UE 3 does not perform the cell selection and the cell reselection with that congested cell.

[0159] In Step 1, In case that the UE 3 receives the Congestion level and Backoff time over the system information or RRC message in Step 1-1 and Step 1-2 in Fig. 3 respectively, the UE 3 may use this information for the cell selection and the cell reselection in Step 11. For example, if the UE 3 performs the cell selection or the cell reselection with that congested cell but rejected due to congestion in that cell, the UE 3 starts a local timer in the UE 3 based on the received Backoff timer and reperforms next cell selection and the cell reselection when the local timer expires.

[0160] <Fourth Variant of the Second Example of the Second Aspect> 　　In case one or more UE 3 subscription information within the UDM changes, for example List of NTN profile, NTN RAT restriction, NTN RAT allowed, due to an update by the network operator via the OAM 8 or due to an update by the Service Provide, e.g. AF 201, via the NEF 79, then the UDM 75 would notify the change in the UE 3 subscription information to the PCF 73. The UDM 75 may notify the PCF 73 by sending the Nudr_DM_Notify message with the updated List of NTN profile and / or NTN RAT restriction and / or NTN RAT allowed. Then PCF 73 may update the URSP rules for the UE 3 with the updated List of NTN profile and / or NTN RAT restriction and / or NTN RAT allowed information and the PCF 73 would trigger UE Policy update procedure as specified in 3GPP TS 23.502 [4], Section 4.2.4.3 in order to update the UE with the latest List of NTN profile and / or NTN RAT restriction and / or NTN RAT allowed information which would be delivered to the UE2 within the UE configuration Update message triggered by the AMF 70.

[0161] <Third example of the Second Aspect> 　　The Third example of the Second Aspect includes a mechanism for a mobility management based on the GNSS location for satellite access.

[0162] Fig. 7 illustrates an example of call flow for the Registration procedure based on the GNSS location for satellite access.

[0163] The detailed processes of the Third example of the Second Aspect are described below with reference to Fig. 7.

[0164] Step 1. Steps 0 to 3 in Fig. 5 take place.

[0165] Step 2. The UE 3 sends the RRC Message number 3 message to the RAN 5 including Dedicated NAS. The Dedicated NAS includes the Registration Request message. The Registration Request message to the AMF 70 includes at least one of User ID, GNSS based mobility supported and GNSS location.

[0166] The following bullets explain each parameter in detail. 　　- User ID: User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI. 　　- GNSS based mobility supported: The GNSS based mobility supported indicates that the UE 3 support the GNSS location-based mobility management procedure. The GNSS location-based mobility management is a mobility management mechanism for the UE3 based on the GNSS location information instead of TAI based mobility management. The GNSS location-based mobility management may work without assigning TAC and TAI to cells and make the mobility management possible. Typically, the GNSS location-based mobility management may be used for mobility management using satellite for maritime communication. The GNSS location-based mobility management and conventional Tracking Area based mobility management may work together. 　　- GNSS location: Refer to Step 2 in Fig. 6.

[0167] Step 3. Upon reception of the RRC Message number 3 message from the UE 3, the RAN 5 sends the Initial UE message to the AMF 70 including NAS PDU. The NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 2.

[0168] Step 4. Upon reception of the Registration Request message in Step 5, the AMF 70 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, GNSS based mobility supported and GNSS location.

[0169] The following bullets explain each parameter in detail. 　　- SUPI: Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. 　　- GNSS based mobility supported: Refer to Step 2. 　　- GNSS location: Refer to Step 2.

[0170] Step 5. Upon reception of the Nudm_UECM_Registration Request message in Step 4, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 70.

[0171] Step 6. After the completion of the Nudm_UECM_Registration service in Steps 4 and 5, the AMF 70 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI, GNSS based mobility supported and GNSS location. Refer to Step 4 for parameter details.

[0172] Step 7. The UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3.

[0173] Step 8. The AMF 70 generates the GNSS based RA if the AMF 70 receives the GNSS based mobility supported from the UE 3 via the RAN 5 in Step 3. The AMF 70 refers the received GNSS location in Step 3 as the UE 3's current location and the received list of NTN profile from the UDM 75 for finding the best geographical area for the UE 3 as the Registration Area (RA). 　　Refer to Fig. 6 how the AMF 70 obtains the List of NTN profile from the UDM 75.

[0174] The AMF 70 sends the Initial Context Setup Request message to the RAN 5 including GNSS based RA, List of NTN profile and NAS PDU. The NAS PDU include the Registration Accept message that includes the 5G-GUTI, TAI list, GNSS based RA and List of NTN profile.

[0175] The following bullets explain each parameter in detail. 　　- 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3, Refer to 3GPP TS 23.003 [5] for details. 　　- TAI list: The TAI list indicates to the UE 3 as the Registration Area (RA) for the mobility management. The TAI list composed of a list of TAI. 　　- GNSS based RA: The GNSS based RA indicates to the UE 3 as Registration Area (RA) for the mobility management. The GNSS based RA indicate a geographical area of the RA without using the TAI. For example, the geographical area may be expressed as a shape as defined in the 3GPP TS 23.032 [6]. 　　- In addition, the GNSS based RA may have a validity period as an associated information. The validity period indicates a valid period of the GNSS based RA. If the validity period elapses, the GNSS based RA becomes invalid. 　　- List of NTN profile: Refer to Step 7 in Fig. 6.

[0176] The RAN 3 uses the received GNSS based RA for the handover procedure for selecting a target RAN in case a cell is located in the satellite and the satellite moving out from the received GNSS based RA.

[0177] Step 9. The RAN 5 sends a RRC signalling including NAS. The NAS includes the Registration Accept message that is received from the AMF in Step 8.

[0178] Step 10. Upon reception of the Registration Accept message, the UE 3 sends the Registration Complete message to the AMF 70.

[0179] Step 11. The UE 3 stores the received 5G-GUTI, TAI list and GNSS based RA in the Registration Accept message into non-volatile memory in the UE 3.

[0180] One example, if the UE 3 receives both TAI list and GNSS based RA in the Registration Accept message in Step 10, the GNSS based RA takes precedence over the TAI list for the mobility management.

[0181] One another example, if the UE 3 receives both TAI list and GNSS based RA in the Registration Accept message in Step 10, the UE 3 uses TAI list and GNSS based RA for the mobility management. In this case, the UE 3 refers the GNSS based RA only for the satellite access.

[0182] If the UE 3 received the GNSS based RA, the UE 3 monitors his location whether the UE 3 traverses the GNSS based RA boundary. If the UE 3 traverses the received GNSS based RA and locates outside of the GNSS based RA, the UE 3 sends a Registration Request message to the AMF 70 to obtain new TAI list or new GNSS based RA.

[0183] If the UE 3 received the GNSS based RA with a validity period, the UE 3 monitors current time whether the received validity period elapses or not. If the UE 3 finds that the received validity period elapses, the UE 3 sends a Registration Request message to the AMF 70 to obtain new TAI list or new GNSS based RA even the UE 3 is located inside of the received the GNSS based RA.

[0184] <Fourth example of the Second Aspect> 　　The Fourth example of the Second Aspect includes a mechanism for capability negotiation between the RAN 5 and the AMF 70 for the support of NTN access.

[0185] Fig. 8 illustrates an example of the RAN initiated capability negotiation between the RAN 5 and the AMF 70 for the support of NTN access.

[0186] The detailed processes of the Fourth example of the Second Aspect are described below with reference to Fig. 8.

[0187] Step 1. The RAN 5 sends the NG Setup Request message to the AMF 70 including NTN supported, GNSS based mobility supported, NTN profile and NTN performance status.

[0188] The following bullets explain each parameter in detail. 　　- NTN supported: The NTN supported indicates that the RAN 5 supports the NTN handling mechanism as disclosed by this disclosure. The NTN supported may be expressed another way. For example, Satellite access supported, multi-orbit satellite supported, multi-orbit satellite access supported. 　　- GNSS based mobility supported: The GNSS based mobility supported indicates that the RAN 5 supports a mobility management based on the GNSS location for satellite access as disclosed by this disclosure. 　　- Hierarchical mobility supported: The Hierarchical mobility supported indicates that the RAN 5 supports a mobility management based on a priority of a cell for satellite access as disclosed by this disclosure. 　　- In one example, Hierarchical mobility supported may indicate a support of the hierarchical mobility procedure based on TAI with priority as disclosed in Fig. 11 or the Hierarchical Registration procedure based on TAI with priority as disclosed in Fig. 12. 　　- List of NTN profile: The list of NTN profile is a list of profile of NTN that the RAN 5 supports. For each entry of NTN profile, refer to Step 1-1 in Fig. 3. 　　- In case cells that the RAN 5 manages are only located at the satellite, the RAN 5 gets the NTN profile from local configuration or obtains by interrogating with the OAM 8 or obtains by interrogating with the cells at the satellite. 　　- List of NTN performance status: The List of NTN performance status is a list of performance status of the NTN that are listed in the NTN profile. For each entry of performance status, refer to Step 1-1 in Fig. 3. 　　- In case cells that the RAN 5 manages are only located at the satellite, the RAN 5 gets the NTN performance status from local configuration or obtains by interrogating with the OAM 8 or obtains by interrogating with the cells at the satellite.

[0189] Step 2. Upon reception of the NG Setup Request message from the RAN 5 in Step 1, the AMF 70 saves the received information and uses them for the mobility management with RAN 5 for the NTN access.

[0190] The AMF 70 sends the NG Setup Response message to the RAN 5 including NTN supported and GNSS based mobility supported.

[0191] The following bullets explain each parameter in detail. 　　- NTN supported: The NTN supported indicates that the AMF 70 supports the NTN handling mechanism as disclosed by this disclosure. The NTN supported may be expressed another way. For example, Satellite access supported, multi-orbit satellite supported, multi-orbit satellite access supported. 　　- GNSS based mobility supported: The GNSS based mobility supported indicates that the AMF 70 supports the mobility management based on the GNSS location for satellite access as disclosed by this disclosure. 　　- Hierarchical mobility supported: The Hierarchical mobility supported indicates that the AMF 70 supports a mobility management based on a priority of a cell for satellite access as disclosed by this disclosure. 　　- In one example, Hierarchical mobility supported may indicate a support of the hierarchical mobility procedure based on TAI with priority as disclosed in Fig. 11 or the Hierarchical Registration procedure based on TAI with priority as disclosed in Fig. 12.

[0192] Upon reception of the NG Setup Response message from the AMF 70 in Step 2, the RAN 5 saves the received information and uses them for the mobility management with the AMF 70 for the NTN access.

[0193] <First Variant of the Fourth example of the Second Aspect> 　　In Step 1 in Fig. 8, the NG Setup Request message may be a RAN Configuration Update message or an existing NGAP message or a new NGAP message.

[0194] In Step 2 in Fig. 8, the NG Setup Response message may be a RAN Configuration Update Acknowledge message or an existing NGAP message or a new NGAP message.

[0195] <Second Variant of the Fourth example of the Second Aspect> 　　In Step 1 in Fig. 8, if the NG Setup Request message includes the GNSS based mobility supported, the NG Setup Request message may also include a GNSS based coverage area for each Tracking Area Code (TAC). The GNSS based coverage area indicates a geographical area corresponds to a coverage where the TAC corresponds to. For example, the geographical area may be expressed as a shape as defined in the 3GPP TS 23.032 [6].

[0196] One example, the GNSS based coverage area may be included to a TAC that is connected with the GEO satellite.

[0197] <Third Variant of the Fourth example of the Second Aspect> 　　In Step 1 in Fig. 8, if the NG Setup Request message includes the GNSS based mobility supported, the NG Setup Request message may also include an NTN profile as defined in the Step 1-1 in Fig. 3 for each Tracking Area Code (TAC).

[0198] One example, the NTN profile may be included to a TAC that is connected with the MEO satellite, LEO satellite or HAPs.

[0199] <Fourth Variant of the Fourth example of the Second Aspect> 　　In Step 1 in Fig. 8, if the NG Setup Request message may include a list of the GNSS based mobility supported or / and a list of NTN profile without corresponding TAC.

[0200] In this case, Both Tracking area and Registration area for the UE 3 (GNSS based RA in Step 9 in Fig. 7) are managed without TAC.

[0201] <Fifth scenario in Second example of the First Aspect> 　　The Fifth example of the Second Aspect includes a mechanism for capability negotiation between the RAN 5 and the AMF 70 for the support of NTN access.

[0202] Fig. 9 illustrates an example of the AMF initiated capability negotiation between the RAN 5 and the AMF 70 for the support of NTN access.

[0203] The detailed processes of the Fifth example of the Second Aspect are described below with reference to Fig. 9.

[0204] Step 1. The AMF 70 sends the AMF Configuration Update message to the RAN 5 including NTN supported, GNSS based mobility supported and Hierarchical mobility supported.

[0205] Refer to the Step 2 in Fig. 8 for parameter details.

[0206] Upon reception of the AMF Configuration Update message from the AMF 70 in Step 2, the RAN 5 saves the received information and uses them for the mobility management with the AMF 70 for the NTN access.

[0207] Step 2. Upon reception of the AMF Configuration Update message from the AMF 70 in Step 1, The RAN 5 sends the AMF Configuration Update Acknowledge message to the AMF 70 including NTN supported, GNSS based mobility supported, Hierarchical mobility supported, NTN profile and NTN performance status. Refer to Step 1 in Fig. 8 for parameter details.

[0208] The AMF 70 saves the received information and uses them for the mobility management with RAN 5 for the NTN access.

[0209] <First Variant of the Fifth example of the Second Aspect> 　　In Step 2 in Fig. 9, if the AMF Configuration Update Acknowledge message includes the GNSS based mobility supported, the AMF Configuration Update Acknowledge message may also include a GNSS based coverage area for each Tracking Area Code (TAC). The GNSS based coverage area indicates a geographical area corresponds to a coverage where the TAC corresponds to. For example, the geographical area may be expressed as a shape as defined in the 3GPP TS 23.032 [6].

[0210] One example, the GNSS based coverage area may be included to a TAC that is connected with the GEO satellite.

[0211] <Second Variant of the Fifth example of the Second Aspect> 　　In Step 2 in Fig. 9, if the AMF Configuration Update Acknowledge message includes the GNSS based mobility supported, the AMF Configuration Update Acknowledge message may also include an NTN profile as defined in the Step 1-1 in Fig. 3 for each Tracking Area Code (TAC).

[0212] One example, the NTN profile may be included to a TAC that is connected with the MEO satellite, LEO satellite or HAPs.

[0213] <Third Variant of the Fifth example of the Second Aspect> 　　In Step 1 in Fig. 8, if the AMF Configuration Update Acknowledge message may include a list of the GNSS based mobility supported or / and a list of NTN profile without corresponding TAC.

[0214] In this case, Both Tracking area and Registration area for the UE 3 (GNSS based RA in Step 9 in Fig. 7) are managed without TAC.

[0215] < Sixth example of the Second Aspect> 　　The Sixth example of the Second Aspect includes a mechanism for capability negotiation between the RAN 5s for the support of NTN access.

[0216] Fig. 10 illustrates an example of the RAN initiated capability negotiation between the RAN 5s for the support of NTN access.

[0217] The detailed processes of the Sixth example of the Second Aspect are described below with reference to Fig. 10.

[0218] Step 1. The RAN1 501 sends the XN Setup Request message to the RAN2 502 including NTN supported, GNSS based mobility supported, Hierarchical mobility supported, NTN profile and NTN performance status.

[0219] The following bullets explain each parameter in detail. 　　- NTN supported: The NTN supported indicates that the RAN1 501 supports the NTN handling mechanism as disclosed by this disclosure. The NTN supported may be expressed another way. For example, Satellite access supported, multi-orbit satellite supported, multi-orbit satellite access supported. 　　- GNSS based mobility supported: The GNSS based mobility supported indicates that the RAN1 501 supports a mobility management based on the GNSS location for satellite access as disclosed by this disclosure. 　　- Hierarchical mobility supported: The Hierarchical based mobility supported indicates that the RAN1 501 supports a mobility management based on a priority of a cell for satellite access as disclosed by this disclosure. 　　- In one example, Hierarchical mobility supported may indicate a support of the hierarchical mobility procedure based on TAI with priority as disclosed in Fig. 11 or the Hierarchical Registration procedure based on TAI with priority as disclosed in Fig. 12. 　　- List of NTN profile: The list of NTN profile is a list of profile of NTN that the RAN1 501 supports. For each entry of NTN profile, refer to Step 1-1 in Fig. 3. 　　- In case cells that the RAN 5 manages are only located at the satellite, the RAN1 501 gets the NTN profile from local configuration or obtains by interrogating with the OAM 8 or obtains by interrogating with the cells at the satellite. 　　- List of NTN performance status: The List of NTN performance status is a list of performance status of the NTN that are listed in the NTN profile. For each entry of performance status, refer to Step 1-1 in Fig. 3. 　　- In case cells that the RAN1 501 manages are only located at the satellite, the RAN1 501 gets the NTN performance status from local configuration or obtains by interrogating with the OAM 8 or obtains by interrogating with the cells at the satellite.

[0220] Step 2. Upon reception of the XN Setup Request message from the RAN1 501 in Step 1, the RAN2 502 saves the received information and uses them for the mobility management with RAN1 501 for the NTN access.

[0221] The RAN2 502 sends the NG Setup Response message to the RAN1 501 including NTN supported, GNSS based mobility supported, Hierarchical mobility supported, NTN profile and NTN performance status.

[0222] The following bullets explain each parameter in detail. 　　- NTN supported: The NTN supported indicates that the RAN2 502 supports the NTN handling mechanism as disclosed by this disclosure. The NTN supported may be expressed another way. For example, Satellite access supported, multi-orbit satellite supported, multi-orbit satellite access supported. 　　- GNSS based mobility supported: The GNSS based mobility supported indicates that the RAN2 502 supports a mobility management based on the GNSS location for satellite access as disclosed by this disclosure. 　　- Hierarchical mobility supported: The Hierarchical mobility supported indicates that the RAN2 502 supports a mobility management based on a priority of a cell for satellite access as disclosed by this disclosure. 　　- In one example, Hierarchical mobility supported may indicate a support of the hierarchical mobility procedure based on TAI with priority as disclosed in Fig. 11 or the Hierarchical Registration procedure based on TAI with priority as disclosed in Fig. 12. 　　- List of NTN profile: The list of NTN profile is a list of profile of NTN that the RAN2 502 supports. For each entry of NTN profile, refer to Step 1-1 in Fig. 3. 　　- In case cells that the RAN 5 manages are only located at the satellite, the RAN2 502 gets the NTN profile from local configuration or obtains by interrogating with the OAM 8 or obtains by interrogating with the cells at the satellite. 　　- List of NTN performance status: The List of NTN performance status is a list of performance status of the NTN that are listed in the NTN profile. For each entry of performance status, refer to Step 1-1 in Fig. 3. 　　- In case cells that the RAN2 502 manages are only located at the satellite, the RAN2 502 gets the NTN performance status from local configuration or obtains by interrogating with the OAM 8 or obtains by interrogating with the cells at the satellite.

[0223] Upon reception of the XN Setup Response message from the RAN2 502 in Step 2, the RAN1 501 saves the received information and uses them for the mobility management with the RAN2 502 for the NTN access.

[0224] <Seventh example of the Second Aspect> 　　The seventh example handles a scenario when a UE 3 is moving from a place where there is a coverage of GEO satellite only to a place of mixed coverage of GEO satellite and LEO satellite or / and MEO satellite. In this case, the UE 3 selects a cell of either MEO or LEO and performs the Registration procedure although the UE 3 is under the good coverage of the cell with GEO satellite.

[0225] With this example, the UE 3 may get better quality of service though a LEO cell or a MEO cell than a GEO cell.

[0226] In this scenario the RAN 501, RAN 502 and RAN 503 broadcasts the TAI along with priority associated with the TAI. At a place of mix coverage of the LEO, MEO or GEO satellite the UE 3 selects a cell with the highest priority and initiates the registration procedure over the selected cell. During the NG Setup procedure, the 501, RAN 502 and RAN 503 indicate their priority of the current TAC to the AMF in a NG SETUP REQUEST message. The AMF also indicates the Support of hierarchical mobility support in NG SETUP RESPONSE message. Refer to Fig. 9 and Fig. 10 in details.

[0227] Note that the Altitude offset in the NTN profile in both Fig. 9 and Fig. 10 may be referred as the priority of TAC.

[0228] The following bullets explain assumptions in Fig. 11. 　　- The priority is in the order of LEO (Priority 1) > MEO (Priority 2) > GEO (Priority 3). 　　- Cells with RAN 501 broadcast TAC 1 (TAI 1) and priority 3 (The lowest priority in this example) in the system information. 　　- Cells with RAN 502 broadcast TAC 1 (TAI 1) and priority 2 (Middle priority in this example) in the system information. 　　- Cells with RAN 503 broadcast TAC 1 (TAI 1) and priority 1 (The highest priority in this example) in the system information.

[0229] Fig. 11 illustrates an example of the hierarchical mobility procedure based on system information.

[0230] The detailed processes of the seventh example of the Second Aspect are described below with reference to Fig. 11.

[0231] Step 0. RAN 501 broadcasts priority of the TAI in a MIB or existing SIB or a new SIB. The priority may be the Altitude offset as disclosed in Step 1-1 in Fig. 3.

[0232] In one example, a satellite with high altitude has low priority. The priority may be expressed as mobility priority, target cell priority, TAI priority, TAC priority, target TAI priority, target TAC priority, cell selection / reselection priority.

[0233] Step 1. At t1 (time 1), there is coverage of cell corresponding to RAN 501 only. The UE selects a cell of the RAN 501 and initiates registration procedure.

[0234] Step 2. The UE 3 sends Registration Request message to the AMF 70 via the RAN 501 including Hierarchical mobility supported, Current priority, Satellite identifier, list of nonboring satellite.

[0235] The following bullets explain each parameter in detail. 　　- Hierarchical mobility supported: The Hierarchical based mobility supported indicates that the UE 3 supports a mobility management based on a priority of a cell for satellite access as disclosed by this disclosure. 　　- Current priority: The Current priority indicates a current priority level that the UE 3 being engaged for the mobility management. 　　- One example, the Current priority may be expressed with a numeric number. For example, 1 as the highest priority in the range of 1 to 10. Note that this example is used in Fig. 11. 　　- One another example, the Current priority may be expressed by the Altitude offset in the NTN profile with a higher altitude referred by lower priority. 　　- Satellite identifier: The Satellite identifier identifies a Satellite that a current tuned cell is on board or used for communication over the Uu interface with UE 3. Refer to Step 1-1 in Fig. 3 for details. 　　- list of nonboring satellite: The list of nonboring satellite includes a list of Satellite identifier that the UE 3 can see. This information may be used by the AMF 70 to structure the TAI list for the UE 3.

[0236] Step 3. When the AMF 70 receives the Registration Request message it executes the registration procedure as defined in 3GPP TS 23.502 [4] Section 4.2.2.2. The AMF 70 allocates a Registration area set to TAI 1 for the UE 3.

[0237] The AMF 70 sends Registration Accept message to the UE 3 including 5G-GUTI, TAI list and Hierarchical mobility required.

[0238] The following bullets explain each parameter in detail. 　　- 5G-GUTI: Refer to Step 13 in Fig. 5. 　　- Hierarchical mobility supported: The Hierarchical based mobility supported indicates that the AMF 70 supports a mobility management based on a priority of a cell for satellite access as disclosed by this disclosure. 　　- TAI list: The TAI list composed of list of TAI that structures the Registration Area for the UE 3. In this example, the TAI list has TAI=1. 　　- Hierarchical mobility required: The Hierarchical mobility required indicates that the UE3 is requested to performs the hierarchical mobility procedure as disclosed in this disclosure. 　　- If Hierarchical mobility required is received by the UE 3, the UE 3 may perform the neighbouring cell scanning even the UE 3 has a good signal strength received from the current cell. I.e. even the UE 3 is in a good coverage of the current cell. 　　- One example, the UE 3 performs neighbouring cell scanning only for those of cells that has higher priority than a priority of the current cell (Current priority).

[0239] Steps 4 and 5. At t2 (time 2), the UE 3 is under coverage of cell of RAN 501, RAN 502 and RAN 503. I.e. The UE 3 can see cells with RAN 501, RAN 502 and RAN 503.

[0240] At t2 (time 2), the UE 3 may be at a new location due to movement or / and the same location at t1 (time 1) which is newly covered by more than one satellite after sometime, for example due to satellite obits.

[0241] Step 6. The UE 3 selects a cell corresponding to the highest priority even though a cell with the highest priority is not best suitable cell at t2 (time 2). In this example the UE 3 selects a cell of RAN 503 as the priority in SIB at Step 5 is higher than the priority in SIB at Step 4.

[0242] Step 7. The UE 3 sends Registration Request message to the AMF 70 via the RAN 503 including Hierarchical mobility supported, Current priority, Satellite identifier, list of nonboring satellite. Refer to Step 2 for parameter details.

[0243] Step 8. When the AMF 70 receives the Registration Request message it executes the registration procedure as defined in 3GPP TS 23.502 [4] Section 4.2.2.2. The AMF 70 allocates a registration area set to TAI 1 for the UE 3. The AMF 70 sends Registration Accept message to the UE 3 including 5G-GUTI, TAI list and Hierarchical mobility required. Refer to Step 3 for parameter details.

[0244] With this mobility management mechanism, the UE 3 may stay with cells of the lower Satellite and thus the UE 3 gets better quality of service for connectivity services.

[0245] In one example, the RAN 503 can be a Terrestrial Network (TN).

[0246] In one example, when a the UE 3 is in mix coverage of TN and NTN (e.g. a cell of GEO, or LEO or MEO satellite) then the UE 3 may not treat NTN cell for cell (re)selection until the TN cell signal strength or quality is below some threshold. Alternatively, the UE 3 may disable the NTN RAT capability.

[0247] <First Variant of the Seventh example of the Second Aspect> 　　In another example, a satellite with high altitude may be treated as a high priority depending on the UE 3 mobility and / or the application(s) in the UE 3 in use or to be used. For example, if the UE 3 is a fast-moving UE and / or the UE 3 is in active mode with an active delay tolerant application or the UE 3 itself is in idle mode but the UE 3 is designated for running delay tolerant applications only, then the UE3 may give a higher priority to higher altitude satellites in cell selection / reselection and handover. This way the UE 3 may benefit of reduced cell selections / reselections and reduced handovers if the UE 3 is a fast-moving UE or the UE 3 is running delay tolerant applications.

[0248] <Eighth example of the Second Aspect> 　　The eighth example handles a scenario when a UE 3 is moving from a place where there is a coverage of GEO satellite only to a place of mixed coverage of GEO satellite and LEO satellite or / and MEO satellite. In this case, the UE 3 may select an arbitrary cell o and performs the Registration procedure. Then the AMF 70 provides the UE 3 a TAI list that includes a list of a combination of TAI and priority.

[0249] During the NG Setup procedure, the 501, RAN 502 and RAN 503 indicate their priority of the current TAC to the AMF in a NG SETUP REQUEST message. The AMF also indicates the Support of hierarchical mobility support in NG SETUP RESPONSE message. Refer to Fig. 9 and Fig. 10 in details.

[0250] Note that the Altitude offset in the NTN profile in both Fig. 9 and Fig. 10 may be referred as the priority of TAC.

[0251] The following bullets explain assumptions in Fig. 12. 　　- The priority is in the order of LEO (Priority 1) > MEO (Priority 2) > GEO (Priority 3). 　　- Cells with RAN 501 have a unique TAI assigned. In this example, all Cells with RAN 501 has TAC 1 (TAI 1). 　　- Cells with RAN 502 have a unique TAI assigned. In this example, all Cells with RAN 502 has TAC 2 (TAI 2). 　　- Cells with RAN 503 have a unique TAI assigned. In this example, all Cells with RAN 503 has TAC 3 (TAI 3).

[0252] Fig. 12 illustrates an example of the hierarchical mobility procedure based on TAI with priority.

[0253] The detailed processes of the eighth example of the Second Aspect are described below with reference to Fig. 12.

[0254] Step 0. RAN 501 broadcasts a TAI set to the TAI 1 in the PLMN-IdentityInfoList information element in an existing SIB or a new SIB.

[0255] Step 1. At t1 (time 1), there is coverage of cell corresponding to RAN 501 only. The UE selects a cell of the RAN 501 and initiates registration procedure.

[0256] Step 2. The UE 3 sends Registration Request message to the AMF 70 via the RAN 501 including Hierarchical mobility supported, Current priority, Satellite identifier, list of nonboring satellite.

[0257] Refer to Step 2 in Fig. 11 for parameter details.

[0258] Step 3. When the AMF 70 receives the Registration Request message it executes the registration procedure as defined in 3GPP TS 23.502 [4] Section 4.2.2.2. The AMF 70 allocates a registration area set to TAI 1, TAI 2 and TAI 3 for the UE 3.

[0259] The AMF 70 sends Registration Accept message to the UE 3 including 5G-GUTI, TAI list (TAI 1 with priority 3, TAI 2 with Priority 2, TAI 3 with priority 1), Hierarchical mobility required.

[0260] The following bullets explain each parameter in detail. 　　- 5G-GUTI: Refer to Step 13 in Fig. 5. 　　- Hierarchical mobility supported: Refer to Step 3 in Fig. 11. 　　- TAI list: The TAI list composed of list of TAI that structures the Registration Area for the UE 3. In this example, the TAI list has TAI=1, TAI=2 and TAI=3. Each TAI has an associated priority. In this example, TAI 1 with priority 3, TAI 2 with Priority 2, TAI 3 with priority 1. 　　- The AMF 70 may find relevant TAIs to be set to the TAI list based on the received Satellite identifier and list of nonboring satellite in Step 2 and satellite related data base (ex. Obit data) in the local configuration in the AMF 70. 　　- One example, the priority may be expressed by the Altitude offset as disclosed in Step 1-1 in Fig. 3. One another example, the priority may be expressed as mobility priority, target cell priority, TAI priority, TAC priority, target TAI priority, target TAC priority, cell selection / reselection priority. 　　- Hierarchical mobility required: Refer to Step 3 in Fig. 11. In addition, the UE 3 knows a priority of cells by matching up the TAI broadcasted by cells with the TAI and priority combination in the TAI list that is received in the Registration Accept message.

[0261] Steps 4 and 5. At t2 (time 2), the UE 3 is under coverage of cell of RAN 501, RAN 502 and RAN 503. I.e. The UE 3 can see cells with RAN 501, RAN 502 and RAN 503.

[0262] At t2 (time 2), the UE 3 may be at a new location due to movement or / and the same location at t1 (time 1) which is newly covered by more than one satellite after sometime, for example due to satellite obits.

[0263] Step 6. The UE 3 selects a cell corresponding to the highest priority even though a cell with the highest priority is not best suitable cell at t2 (time 2). In this example the UE 3 selects a cell of RAN 503 as the priority for the TAI=3 in the TAI list is the highest than a priority for other TAIs.

[0264] Step 7. The UE 3 sends Registration Request message to the AMF 70 via the RAN 503 including Hierarchical mobility supported, Current priority, Satellite identifier, list of nonboring satellite. Refer to Step 2 for parameter details.

[0265] Step 8. When the AMF 70 receives the Registration Request message it executes the registration procedure as defined in 3GPP TS 23.502 [4] Section 4.2.2.2. The AMF 70 allocates a registration area set to TAI 1, TAI 2 and TAI 3 for the UE 3.

[0266] The AMF 70 sends Registration Accept message to the UE 3 including 5G-GUTI, TAI list (TAI 1 with priority 3, TAI 2 with Priority 2, TAI 3 with priority 1), Hierarchical mobility required. Refer to Step 3 for parameter details.

[0267] Note that a content of the TAI list varies depending on time and location of the UE 3 and may not be the same as the one in Step 3.

[0268] In one example, the RAN 503 can be a Terrestrial Network (TN). In this case the TAC related to TN can have highest priority among TACs of NTN network.

[0269] With this mobility management mechanism, the UE 3 may stay with cells of the lower Satellite and thus the UE 3 gets better quality of service for connectivity services.

[0270] <Third Aspect> 　　This aspect discloses mechanisms for Session Management with Satellite access.

[0271] <First example of the Third Aspect> 　　The First example of the Third Aspect includes a PDU Session establishment procedure for satellite communication.

[0272] <First scenario in First example of the Third Aspect> 　　The First scenario in First example of the Third Aspect includes an example of the PDU Session establishment procedure for satellite communication with a mechanism for codec adjusting depending on a Radio Access Technology (RAT) type of the satellite communication.

[0273] The UE 3 installs QoS parameters per RAT type of the satellite when the UE 3 creates a PDU Session. The QoS parameters per RAT type used for active mode mobility procedures are disclosed by other disclosures in the Third aspect.

[0274] This scenario is a preparation of the QoS handling per RAT type for the satellite access.

[0275] Fig. 13 illustrates an example of call flow for the PDU Session establishment procedure with QoS parameters per RAT type.

[0276] The detailed processes of the First scenario in First example of the Third Aspect are described below with reference to Fig. 13.

[0277] Step 0. The UE 3 registered with AMF 70 via RAN 501.

[0278] Step 1. Steps 0 to 3 in Fig. 5 take place. The NTN profile and the NTN performance status are installed in the UE 3 by this Step.

[0279] One example, the NTN profile and the NTN performance status are installed in the UE 3 by any of the mechanism as disclosed in Fig. 3.

[0280] Step 2. The UE 3 sends the RRC Message number 3 including Dedicated NAS. The Dedicated NAS includes the UL NAS Transport message. Further the UL NAS Transport message includes PDU Session ID, DNN, S-NSSAI, Requested QoS Type (multi-Satellite), NTN supported, UE NTN Radio capability, GNSS location and NAS.

[0281] Further, NAS includes the PDU Session Establishment Request message including Requested QoS Type (multi-Satellite), NTN supported, UE NTN Radio capability and GNSS location.

[0282] The following bullets explain each parameter in detail. 　　- PDU Session ID: The PDU Session ID is an identifier that corresponds to an Association between the UE 3 and a Data Network 20 that provides a PDU connectivity service. 　　- DNN: The DNN is a Data Network Name that is equivalent to an APN in EPS. The DNN is a reference to a data network. 　　- S-NSSAI: S-NSSAI is a Single NSSAI that indicates a network slice. 　　- Requested QoS Type: The Requested QoS Type indicates that the UE 3 requests to have a QoS information per RAT type in case the RAN 5 (Including the RAN 501 and the RAN 502) are associated with the Satellite access. In this example, the UE 3 sets the Requested QoS Type to multi-Satellite. The multi-Satellite indicates that the UE 3 requests multiple QoS parameters per Satellite access. For example, the Satellite access may be LEO, MEO or GEO. 　　- NTN supported: Refer to Step 2 in Fig. 6. 　　- UE NTN Radio capability: Refer to Step 4 in Fig. 5. 　　- GNSS location: Refer to Step 2 in Fig. 6. 　　- NAS: The NAS contains the NAS message.

[0283] Step 3. The RAN 501 sends the Initial UE message including NAS PDU. The NAS PDU includes the UL NAS Transport message that is received from the UE 3 in Step 2.

[0284] Step 4. Upon reception of the UL NAS Transport message from the UE 3, the AMF 70 performs the SMF selection, if not selected, based on at least one of the received NTN supported, UE NTN Radio capability and GNSS location seeking an SMF that supports the satellite access handling that disclosed by this disclosure.

[0285] Once the SMF 71 is chosen or already associated with the AMF 70, the AMF 70 sends an Nsmf_PDUSession_CreateSMContext Request message to the SMF 71 including at least one of the User ID, PDU Session ID, Requested QoS Type (multi-Satellite), NTN supported, UE NTN Radio capability and GNSS location, and PDU Session Establishment Request message.

[0286] Step 5. Upon reception of the Nsmf_PDUSession_CreateSMContext Request message, the SMF 71 sends an Nsmf_PDUSession_CreateSMContext Response message to the AMF 70.

[0287] The SMF 71 contacts to the UPF 72 to perform the N4 Session Establishment procedure for reserving (setting up) user plane resources in the UPF 72.

[0288] Step 6. The SMF 71 sends an Nudm_SDM_Get message to the UDM 75 including at least one of the User ID, DNN, S-NSSAI, NTN supported, UE NTN Radio capability and GNSS location.

[0289] Step 7. The UDM 75 finds Session Management Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the SMF 71 including the Subscriber data for the UE 3. The Subscriber data may include the List of NTN profile.

[0290] The following bullets explain each parameter in detail. 　　- List of NTN profile: Refer to Step 7 in Fig. 6. 　　- NTN RAT restriction: Refer to Step 0 in Fig. 5. 　　- NTN RAT allowed: Refer to Step 0 in Fig. 5.

[0291] Step 8. If the SMF 71 does not have a PCF association, the SMF 71 establishes the PCF association with the PCF 73. Then the SMF 71 sends an Npcf_SMPolicyControl_Create message to the PCF 73 including at least one of the User ID, DNN, S-NSSAI, Requested QoS Type (multi-Satellite), NTN supported, UE NTN Radio capability and GNSS location.

[0292] Step 9. Upon reception of the Npcf_SMPolicyControl_Create message from the SMF 71, the PCF 73 generates a PCC Rule for the UE 3 and sends an Npcf_SMPolicyControl_Create Response message to the SMF 71 including The PCC rule. In addition to existing parameters in the PCC rule, the PCC rule incudes Authorized QoS rules per RAT type and AMBR per RAT type.

[0293] Refer to Steps 3-1 and 3-2 in Fig. 3 how the PCF 73 obtains the Session Management Subscriber data for the UE 3 from the UDR 7A.

[0294] The following bullets explain each parameter in detail. 　　- Authorized QoS rules per RAT type: The Authorized QoS rules per RAT type indicates a QoS rule per RAT type. 　　- For example, Authorized QoS rules per RAT type may take the following form as an example: 　　- Authorized QoS rules per RAT type 　　　　-- RAT Type GEO 　　　　　　--- GFBR (guaranteed flow bit rate) for uplink: 1Mbps (Mega bit per second) 　　　　　　--- GFBR (guaranteed flow bit rate) for downlink: 1Mbps (Mega bit per second) 　　　　　　--- MFBR (maximum flow bit rate) for uplink: 10Mbps (Mega bit per second) 　　　　　　--- MFBR (maximum flow bit rate) for downlink: 10Mbps (Mega bit per second) 　　　　-- RAT Type MEO 　　　　　　--- GFBR (guaranteed flow bit rate) for uplink: 2Mbps (Mega bit per second) 　　　　　　--- GFBR (guaranteed flow bit rate) for downlink: 2Mbps (Mega bit per second) 　　　　　　--- MFBR (maximum flow bit rate) for uplink: 20Mbps (Mega bit per second) 　　　　　　--- MFBR (maximum flow bit rate) for downlink: 20Mbps (Mega bit per second) 　　　　-- RAT Type LEO 　　　　　　--- GFBR (guaranteed flow bit rate) for uplink: 3Mbps (Mega bit per second) 　　　　　　--- GFBR (guaranteed flow bit rate) for downlink: 3Mbps (Mega bit per second) 　　　　　　--- MFBR (maximum flow bit rate) for uplink: 30Mbps (Mega bit per second) 　　　　　　--- MFBR (maximum flow bit rate) for downlink: 30Mbps (Mega bit per second) 　　- AMBR per RAT type: The AMBR per RAT type indicates an aggregate maximum bit rate per RAT type for this PDU Session. 　　- For example, AMBR per RAT type may take the following form as an example: 　　- AMBR per RAT type 　　　　-- RAT Type GEO 　　　　　　--- Session AMBR for uplink: 10Mbps (Mega bit per second) 　　　　　　--- Session AMBR for downlink: 10Mbps (Mega bit per second) 　　　　-- RAT Type MEO 　　　　　　--- Session AMBR for uplink: 20Mbps (Mega bit per second) 　　　　　　--- Session AMBR for downlink: 20Mbps (Mega bit per second) 　　　　-- RAT Type LEO 　　　　　　--- Session AMBR for uplink: 30Mbps (Mega bit per second) 　　　　　　--- Session AMBR for downlink: 30Mbps (Mega bit per second)

[0295] Upon reception of the Npcf_SMPolicyControl_Create Response message from the PCF 73, the SMF 71 examines the received PCC rule. The SMF 71 may contact to the UPF 72 to perform the N4 Session Modification procedure for updating reserved user plane resources in the UPF 72 if necessary.

[0296] Step 10. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 including PDU Session ID, N2 SM information and N1 SM container.

[0297] The N2 SM information includes PDU Session ID, Authorized QoS rules per RAT type, AMBR per RAT type.

[0298] The N1 SM container includes PDU Session Establishment Accept message that includes Authorized QoS rules per RAT type and AMBR per RAT type.

[0299] Step 11. Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends N2 PDU Session request message to the RAN 501 including N2 SM information and NAS message.

[0300] The N2 SM information includes Authorized QoS rules per RAT type and AMBR per RAT type.

[0301] The NAS message includes PDU Session ID and N1 SM container. Further N1 SM container includes DL NAS Transport message.

[0302] The DL NAS Transport message includes NAS.

[0303] The NAS includes PDU Session Establishment Accept message including Authorized QoS rules per RAT type and AMBR per RAT type.

[0304] The Authorized QoS rules may be coded as a standalone parameter or added into the QoS flow descriptions parameter as defined in 3GPP TS 24.301

[0012] .

[0305] The AMBR per RAT type may be coded as a standalone parameter or added into the Session-AMBR parameter as defined in 3GPP TS 24.301

[0012] .

[0306] In one example, if the AMF 70 has the prioritise RAT list as per one of the above embodiments e.g. in First example of the Second Aspect, the AMF 70 sends this prioritize RAT list to the RAN 501.

[0307] Step 12. The RAN 501 sends the RRC signalling message including DL NAS Transport message.

[0308] The NAS Transport message includes NAS. The NAS includes PDU Session Establishment Accept message. The PDU Session Establishment Accept message includes the Authorized QoS rules per RAT type and AMBR per RAT type.

[0309] In one example, when the RAN 501 receives the prioritise RAT list it stores it. The RAN 501 performs handover to the UE 3 based on the prioritise list. For example, if the prioritise RAT list is LEO>MEO>GEO then the RAN 501 tries to keep the UE on the cell supported by LEO as much as possible. If it is not possible to keep the UE on LEO cells. e.g., LEO cell coverage is diminishing then the RAN 501 tries to keep the UE 3 on a MEO cell.

[0310] Step 13. Upon reception of the PDU Session Establishment Accept message, the UE 3 stores the received data in the PDU Session Establishment Accept message in step 12 into non-volatile memory in the UE 3.

[0311] The received Authorized QoS rules per RAT type and AMBR per RAT type may be used by the UE 3 for codec adjustment in case the PDU Session is handed over to different RAT type.

[0312] Note that mechanisms for codec adjustment during the hand over to different RAT type are disclosed in this disclosure.

[0313] Step 14. After the PDU Session has been established, the AMF may send the Location Reporting control message to RAN 501 to keep track of UE location during the life time of the PDU Session.

[0314] Note that the Location Reporting control based on GNSS location is disclosed in the disclosure to keep track of UE location for satellite access.

[0315] <Second scenario in First example of the Third Aspect> 　　The Second scenario in First example of the Third Aspect includes an example of the PDU Session establishment procedure for satellite communication with redundant PDU session across two orbits during the hand over if the UE 3 hands over between different orbit type of satellite.

[0316] Fig. 14 illustrates an example of call flow for the PDU Session establishment procedure with redundant PDU session across two orbits.

[0317] The detailed processes of the Second scenario in First example of the Third Aspect are described below with reference to Fig. 14.

[0318] Step 0. The PCF 73 configures PDU Session with redundant PDU policy across two orbits based on subscriber data of the UE 3 and location configuration.

[0319] One example, the PCF 73 configures PDU Session with redundant PDU policy across two orbits when the subscriber in the UDM 75 has the Satellite handover type set to Redundant PDU session across two orbits. Refer to Step 0 in Fig. 5 for the Satellite handover type.

[0320] In one example, the PCF 73 obtains the Session Management Subscriber data for the UE 3 from the UDR 7A in the Steps 3-1 and 3-2 in Fig. 3.

[0321] Step 1. Steps 0 to 13 in Fig. 13 take place.

[0322] Step 2. The SMF 71 decides to activate redundant PDU policy across two orbits. 　　One example, this decision is made based on a configuration in Step 0.

[0323] Step 3. The SMF 71 sends an Npcf_SMPolicyControl service to the PCF 73 including redundant PDU policy across two orbits request. The redundant PDU policy across two orbits request indicates that the SMF 71 request to the PCF 73 to perform the redundant PDU policy across two orbits.

[0324] Step 4. The PCF 73 sends an Npcf_SMPolicyControl service response to the SMF 71.

[0325] Step 5. Based on the request from the SMF 71 in Step 3, the PCF 73 sends an Namf_Location_ProvidePositioningInfo for satellite service including SUPI and GNSS location requested.

[0326] The following bullets explain each parameter in detail. 　　- SUPI: The SUPI is Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. 　　- GNSS location requested: The GNSS location requested indicates that location reporting with an expression used by the GNSS is requested. The GNSS location requested has the following information associated. The following information is used by the RAN 501 when the location reporting is needed. 　　　　-- Period: The Period indicates an interval of location reporting. For example, 30 minutes. 　　　　-- Distance: The Distance indicates that the location reporting is needed when the UE 3 moves a designated distance by this parameter from the GNSS location that was reported in the last time. For example, 1 Km.

[0327] Step 6. The AMF 70 starts location monitoring by contacting to the RAN 501. I.e., the AMF 70 sends the Location Reporting control message to RAN 501 to keep track of UE location.

[0328] Note that the Location Reporting control with GNSS location is disclosed by this disclosure.

[0329] Step 7. The AMF 70 sends an Namf_Location_ProvidePositioningInfo response to the PCF 73.

[0330] Step 8. The PCF 73 monitors the UE 3's location and notify to the SMF 71 to activate the redundant PDU session across two orbits with target cell when the PCF 73 observes that UE 3 needs to hand over to a cell with satellite which has different obit type from the one in current cell.

[0331] <First Variant of Second scenario in First example of the Third Aspect> 　　In one example, the redundant PDU session may be established to support greater reliability of a service flow. The redundant PDU session may be established subject to a certain condition, for a certain period, or as a part of conditional handover.

[0332] The detailed process of the First Variant of Second scenario in First example of the Third Aspect is described below with reference to Fig. 15 and Fig.16.

[0333] Note that the Fig. 15 and Fig. 16 illustrates one process. I.e. Step 9 in Fig. 16 is the next step from the Step 8 in Fig. 15.

[0334] Step 0a. UE 3 may support multi-orbit satellite, and conditional redundant PDU session over two (multi-orbit) satellite links. UE 3 may indicate its support for conditional redundant PDU session to the network as a part of registration procedure - e.g., Steps 4 and 5 in Fig. 5 or as a part of PDU session establishment - e.g., Steps 2 to 5 in Fig. 13 of this disclosure.

[0335] Step 0b. Based on, e.g., the UE 3's subscription data, application, type of RAT (i.e., NTN access), PCF 73 may be configured with appropriate session management related policy for establishment of redundant PDUs across two orbits of satellite constellations (e.g., LEO-2 and GEO-1).

[0336] Step 1. PDU Session establishment steps take place according to Fig. 4.3.2.2.1-1 in 3GPP TS 23.502 [4] (Step 1- Step 7a).

[0337] Step 2a. SMF 71 invokes Npcf_SMPolicyControl service to receive policy information for the PDU session.

[0338] Step 2b. PCF 73 updates the SMF 71 with the corresponding policy information about the PDU Session by invoking Npcf_SMPolicyControl_UpdateNotify service operation. This policy information, in addition to the SM Policy Association ID, includes conditions e.g., user subscription, application type, type of RAT (i.e., NTN access), multi-orbit satellite IDs and other conditions for the 2ndPDU session establishment. Optionally, in this step, the ID for the 2ndPDU session and indication that this should be a paired session can be provided to SMF 71. Besides being provided by PCF 73, the entering trigger conditions for establishment of a redundant PDU session may be derived by SMF 71 or by some other network element.

[0339] Step 3. The PDU session establishment follows the procedure outlined in Figure. 4.3.2.2.1-1 in 3GPP TS 23.502 [4] (Step 8- Step 10b).

[0340] Step 4a. SMF 71 invokes Namf_Communication_N1N2MessageTransfer, which contains N2 message (PDU Session ID, N2 SM information (PDU Session ID, CN Tunnel Info,..), as well as N1 SM Container. The N1 SM container, destined for UE 3, contains PDU Session ID as well as trigger conditions and validity rules for establishing the redundant PDU session across the other second orbit. The entering trigger conditions, based on which UE 3 may request a redundant PDU session establishment, may include, e.g.: 　　- UE distance from a reference point above / below the threshold, where the UE location may be determined by the UE or verified by the network as illustrated in the first scenario in the Second example of the Third Aspect 　　- UE location and time 　　- Signal strength (and / or quality) of the serving (NTN - e.g., LEO-2) cell below a threshold and signal strength (and / or quality) of a neighbouring cell (NTN - e.g., GEO-1) above a threshold 　　- Packet error rate above certain threshold, and others.

[0341] The validity rules for the 2ndPDU session establishment may include, e.g.: 　　- minimum time during which the trigger conditions are met 　　- UE 3's battery level above certain threshold, and others.

[0342] Similarly, PCF 73 may provide the leaving conditions for the redundant PDU session, based on which UE 3 will release the 2ndPDU session. The leaving condition may include, e.g.: 　　- distance to lower orbit satellite below the threshold 　　- signal strength (and / or quality) of serving NTN - e.g., LEO-2 cell above a threshold 　　- packet error rate serving NTN - e.g., LEO-2 below a threshold.

[0343] It should be noted that UE 3 may be also configured to release the 1stor 2ndPDU session, according to the trigger conditions and validity rules.

[0344] Step 5. AMF 70 sends N2 PDU Session Request to RAN 501, which contains N2 SM information (e.g., PDU Session ID, QFI(s), QoS Profile(s), CN Tunnel Info, and other parameters as per 3GPP TS 23.502 [4]).

[0345] Step 6. The AMF 70 sends the N1 NAS message containing PDU Session ID and PDU Session Establishment Accept targeted to the UE 3, as well as trigger conditions and validity rules for establishing the redundant PDU session across the other second orbit, as outlined in Step 4a.

[0346] Step 7. RRC messages for radio resources setup for the PDU Session request between RAN 501 and UE 3 are exchanged.

[0347] Step 8. RAN 501 sends N2 PDU session Response to AMF 70.

[0348] Step 9. Steps from 13 as per Figure. 4.3.2.2.1-1 in 3GPP TS 23.502 [4] take place, establishing appropriate DRBs and the first PDU session via LEO-2 with UPF 7201.

[0349] Step 10. UE 3 monitors the (entering) trigger conditions. When the condition(s) are met, the UE initiates the 2nd, redundant PDU session establishment with appropriate DRBs toward RAN 502 and UPF 7202. It should be noted that the second PDU session may also be established towards another SMF and or AMF, not depicted by Fig. 16 for brevity.

[0350] Step 11. Steps according to Figure. 4.3.2.2.1-1, 3GPP TS 23.502 [4] follow to establish 2ndPDU session towards RAN 502 and UPF 7202.

[0351] Step 12. UE 3 monitors the (leaving) trigger conditions, as defined in Step 4b. When the leaving conditions are met, UE 3 initiates PDU session release for the redundant PDU session. UE 3 may also be configured to release the first PDU session, if specified by the leaving conditions.

[0352] In one example, when the RAN 501 triggers the handover procedure to the RAN 502 as soon as DRB is established for the second PDU session when the RAN 501 determines that the UE 3 cannot be served by the RAN 501 and RAN 502 can serve the UE 3. The DRB of the first PDU session is not supported in the RAN 501 e.g., the GBR of the first PDU session is not supported in the RAN 502.

[0353] Alternatively, the redundant (transient) PDU session may be established by means of Dual Connectivity using multi-orbit satellites. In one example, one PDU Session spans from UE 3 via Master RAN 502 (e.g., GEO) where UPF 7202 acts as the PDU Session Anchor, and the other PDU Session spans from UE 3 via the Secondary RAN 501 to UPF 7201 acting as the PDU Session Anchor. In one example, the trigger conditions for Dual Connectivity with multi-orbit satellite may be provided to RAN 502 as a new information element, as a part of N2 message (Step 5 in Fig. 15). The addition of RAN 501 and radio resource setup on RAN 501 for the secondary PDU session is done by means of Xn procedures, as outlined in Section 10.2.2. in 3GPP TS 37.340

[0011] . Given the expected high battery usage, the redundant PDU sessions using Dual Connectivity may be triggered only under special conditions and during limited period.

[0354] In one example, UE 3 and UE 3' are a part of Dual Steer device, supporting conditional transient and redundant PDU session. UE 3' may be configured via e.g., AMF 70 (or another AMF), using N1 message, with a trigger condition(s) to establish a redundant transient PDU session. If the trigger conditions are met, UE 3' establishes a redundant PDU session across e.g., RAN 502 and UPF 7201 or UPF 7202.

[0355] <Second example of the Third Aspect> 　　The Second example of the Third Aspect includes a Location reporting with GNSS location for satellite communication.

[0356] <First scenario in Second example of the Third Aspect> 　　The First scenario in Second example of the Third Aspect includes an example of the Location reporting with GNSS location for satellite communication as an AMF service.

[0357] Note that this disclosure is referred by Steps 5 to 7 in the Fig. 14.

[0358] Fig. 17 illustrates an example of call flow for the Location reporting with GNSS location for satellite communication.

[0359] The detailed processes of the First scenario in Second example of the Third Aspect are described below with reference to Fig. 17.

[0360] Step 0. The UE 3 registered with AMF 70 via RAN 501 and the PDU Session has been created using the PDU Session Establishment procedure as disclosed by Fig. 13.

[0361] Step 1. An NF (I.E. Any NF) sends an Namf_Location_ProvidePositioningInfo for satellite service including SUPI and GNSS location requested.

[0362] Refer to Step 5 in Fig. 14 for parameter details.

[0363] Step 2. Upon reception of the Namf_Location_ProvidePositioningInfo for satellite service, the AMF 70 sends an Namf_Location_ProvidePositioningInfo response to the NF.

[0364] Step 3. The AMF 70 sends a Location reporting control message including Location Reporting Request Type, period and distance.

[0365] The following bullets explain each parameter in detail. 　　- Location Reporting Request Type: The Location Reporting Request Type indicates the type of location request to be handled by the RAN 501. Refer to 3GPP TS 38.413

[0013] Section 9.3.1.65 for details. 　　- In this example, Location Reporting Request Type is set to GNSS location. I.e. the AMF 70 requests the RAN 501 to report the UE 3 location with the location information used by the GNSS. 　　- Period: Refer to Step 5 in Fig. 14. 　　- Distance: Refer to Step 5 in Fig. 14.

[0366] Step 4. The RAN 501 performs the UE location measurement by contacting to the UE 3. 　　For example, Steps 4-1 to 4-3 take place between the RAN 501 and the UE 3.

[0367] Step 4-1. The RAN 501 sends the RRC UE Information Request message to the UE 3 including GNSS location requested. The GNSS location requested indicates that the RAN 501 requests UE 3 for reporting current location information with the location information used by the GNSS.

[0368] One example, the RAN 501 sends this message periodically. For example, every 1 minutes.

[0369] One another example, the RAN 501 sends this information taking the received Period and Distance in Step 3 into account.

[0370] Step 4-2. The AS layer of the UE 3 interrogates to upper layer to obtain GNSS location information using a GNSS client device.

[0371] Step 4-3. After the AS layer of the UE 3 obtains the GNSS location information, the UE 3 sends the UE Information Response message to the RAN 501 including GNSS location. 　　For GNSS location, refer to Step 2 in Fig. 6.

[0372] Step 5. The RAN 501 sends a Location reporting message to the AMF70 including GNSS location.

[0373] One example, the RAN 501 sends this information upon the RAN 501 receives the UE Information Response message from the UE 3 in Step 4-3.

[0374] One another example, the RAN 501 sends this information taking the received Period and Distance in Step 3 into account.

[0375] Step 6. The AMF 70 sends an Namf_Location_Eventnotify to the NF including GNSS location.

[0376] One example, the AMF 70 sends this information upon the AMF 70 receives the Location reporting message from the RAN 501 in Step 5.

[0377] One another example, the AMF 70 sends this information taking the received Period and Distance in Step 1 into account.

[0378] <Third example of the Third Aspect> 　　The Third example of the Third Aspect includes an inter RAT type handover procedure for satellite communication.

[0379] <First scenario in Third example of the Third Aspect> 　　The First scenario in Third example of the Third Aspect includes an example of the inter RAT type handover with QoS adjustment.

[0380] Fig. 18 illustrates an example of call flow for the inter RAT type handover with QoS adjustment.

[0381] The detailed processes of the First scenario in Third example of the Third Aspect are described below with reference to Fig. 18.

[0382] Step 0-1. The UE 3 registered with AMF 70 using the Registration procedure as disclosed in Fig. 6.

[0383] Step 0-2. The PDU Session has been established with RAN 501 using the PDU Session establishment procedure as disclosed in Fig. 13.

[0384] Step 1. The RAN 501 observes that Inter RAT Handover is required with RAN 502.

[0385] For example, the RAN 501 finds that Inter RAT Handover is required with RAN 502 based on the received List of NTN profile, NTN RAT restriction NTN RAT allowed in Step 8 in Fig. 6 and UE GNSS location measured using the RAN monitors UE location procedure as disclosed in Steps 4-1 to 4-3 in Fig. 17.

[0386] For another example, the AMF 70 or the OAM 8 informs the RAN 501 that Inter RAT Handover is required with RAN 502.

[0387] Note that the Inter RAT Handover initiated by the AMF 70 is disclosed in Fig. 19.

[0388] Step 2. The RAN 501 sends an RRC Inter RAT type handover indication message to the UE 3 including Target NTN profile, QoS descriptor in target cell and AMBR in target cell.

[0389] The following bullets explain each parameter in detail. 　　- Target NTN profile: The Target NTN profile indicates the target cell for the handover. Refer to Step 1-1 in Fig. 3 for the NTN profile. 　　- QoS descriptor in target cell: The QoS descriptor in target cell indicates an expected QoS descriptor that the UE 3 may obtained with the target cell. 　　- The QoS descriptor is composed of at least GFBR (guaranteed flow bit rate) for uplink, GFBR (guaranteed flow bit rate) for downlink, GFBR (maximum flow bit rate) for uplink and MFBR (maximum flow bit rate) for downlink per all GBR flows. 　　- AMBR in target cell: The AMBR in target cell indicates an expected AMBR for the PDU Session that the UE 3 may obtained with the target cell. 　　- The AMBR in target cell is composed of at least Session AMBR for uplink and Session AMBR for downlink.

[0390] One example, instead of Step 2, the UE 3 solely observes that Inter RAT Handover is required with RAN 502 based on the received NTN profile, NTN performance status, List of Neighbouring NTN profile and List of Neighbouring NTN performance status in Step 1-1 in Fig. 3 over system information and UE 3's current NGSS location obtained by the NGSS device equipped in the UE 3.

[0391] Steps 3 and 4 are executed only when the QoS descriptor in target cell or / and AMBR in target cell are degraded form the ones with current RAT type. Otherwise, Steps 3 and 4 are skipped.

[0392] Step 3. Once the UE 3 decides to handover to a cell in the RAN 502 and if the QoS descriptor in the target cell or / and AMBR in target cell are degraded for the ones with the current RAT type, an application layer in UE 3 adjusts media codecs being used by contacting with the application service in the AF 201 over the application layer to match with the received QoS descriptor in target cell and AMBR in target cell in Step 2.

[0393] Step 4. Once the UE 3 decides to handover to a cell in the RAN 502 and if the QoS descriptor in target cell or / and AMBR in target cell are degraded for the ones with current RAT type, the UE 3 initiates the PDU Session Modification procedure as descried in 3GPP TS 23.502 [4] Section 4.3.3 with QoS information received in Step 2.

[0394] Step 5. Once the RAN 501 confirms that the PDU Session Modification procedure is completed, the RAN 501 initiates the handover procedure with a cell in the RAN 502 as the target cell.

[0395] Steps 6 and 7 are executed only when the QoS descriptor in target cell or / and AMBR in target cell are upgraded from the ones with current RAT type. Otherwise, Steps 6 and 7 are skipped.

[0396] Step 6. If the QoS descriptor in target cell or / and AMBR in target cell are upgraded for the ones with previous RAT type, the UE 3 initiates the PDU Session Modification procedure as descried in 3GPP TS 23.502 [4] Section 4.3.3 with QoS information received in Step 2.

[0397] Step 7. If the QoS descriptor in target cell or / and AMBR in target cell are upgraded for the ones with previous RAT type, an application layer in UE 3 adjusts media codecs being used by contacting with the application service in the AF 201 over the application layer to match with the updated QoS characteristics in Step 6.

[0398] Step 8. The UE 3 communicates with AF 201 with new QoS characteristics adequate to the RAT type for satellite access with RAN 502.

[0399] <First Variant of First scenario in Third example of the Third Aspect> 　　In one example, when the UE 3 receives the RRC message indicating the inter satellite handover is going to happen then the UE 3 activates a second PDU session with QoS descriptor of the target cell as defined in Fig. 13. The 5GS activates the user plane for the second the PDU session. Once the DRB is established at the source RAN 501 the source RAN 501 triggers handover procedure to the target RAN 502. The RAN 501 can be LEO satellite and RAN 502 can be MEO satellite. This is to handle the case when the QoS of the first PDU session (PDU session established in step 0-2) is not supported in the target RAN 502.

[0400] <Second Variant of First scenario in Third example of the Third Aspect> 　　In one example, when the UE 3 receives the RRC message indicating the inter satellite handover is going to happen then the UE 3 activates a second PDU session with QoS descriptor of the target cell as defined in Fig. 13. The 5GS activates the user plane for the second the PDU session. Once the DRB is established at the source RAN 501 the source RAN 501 triggers handover procedure to the target RAN 502. The RAN 501 can be LEO satellite and RAN 502 can be MEO satellite. This is to handle the case when the QoS of the first PDU session (PDU session established in step 0-2) is not supported in the target RAN 502.

[0401] <Third Variant of First scenario in Third example of the Third Aspect> 　　In one example, when the RAN 501 determines that UE 3 is going from RAN 501 (LEO) to RAN 502 (GEO)coverage and the RAN 502 can't support established DRB, then RAN 501 sends an existing NGAP message or a new NGAP message containing parameters as defined in step 2 of the above embodiment to the AMF 70. The AMF 70 sends an existing NAS message or a new NAS message containing parameters as received from RAN 501 to the UE 3 indicating to UE 3 that the UE 3 is going to handover to a target cell. When the UE receives the NAS message indicating the inter satellite handover is going to happen then the UE 3 activates a second PDU session with QoS descriptor of the target cell as defined in Fig. 13. The 5GS activates the user plane for the second the PDU session. Once the DRB is established at the source RAN 501 the source RAN 501 triggers handover procedure to the target RAN 502. The RAN 501 can be LEO satellite and RAN 502 can be MEO satellite. This is to handle the case when the QoS of the first PDU session (PDU session established in step 0-2) is not supported in the target RAN 502. This is to handle the case when the QoS of the first PDU session (PDU session established in step 0-2) is not supported in the target RAN 502.

[0402] <Second scenario in Third example of the Third Aspect> 　　The Second scenario in Third example of the Third Aspect includes an example of the inter RAT type handover with QoS adjustment finding a target cell by satellite application.

[0403] Fig. 19 illustrates an example of call flow for the inter RAT type handover with QoS adjustment finding a target cell by satellite application.

[0404] The detailed processes of the Second scenario in Third example of the Third Aspect are described below with reference to Fig. 19.

[0405] Step 0-1. The UE 3 registered with AMF 70 using the Registration procedure as disclosed in Fig. 6.

[0406] Step 0-2. The PDU Session has been established with RAN 501 using the PDU Session establishment procedure as disclosed in Fig. 13.

[0407] Step 1. The AMF 70 sends the Location reporting control message to the RAN 501 including Location Reporting Request Type set, period and distance. 　　Refer to Step 3 in Fig. 17 for parameter details.

[0408] Step 2. The RAN 501 performs the UE location measurement by contacting to the UE 3. 　　For example, Steps 4-1 to 4-3 in Fig. 17 take place between the RAN 501 and the UE 3.

[0409] Step 3. The RAN 501 sends a Location reporting message to the AMF 70 including GNSS location.

[0410] Step 4. The AMF 70 sends an Nnef_find satellite service to the NEF 79 including an Allowed NTN profile and GNSS location.

[0411] The following bullets explain each parameter in detail. 　　- Allowed NTN profile: The Allowed NTN profile indicates list of NTN profile that the UE 3 is allowed to use. Refer to Step 1-1 in Fig. 3 for the NTN profile. 　　- One example, the Allowed NTN profile may be Satellite Service provider or / and Satellite Service name. 　　- GNSS location: Refer to Step 2 in Fig. 6.

[0412] Step 5. The NEF 79 sends a Naf_find satellite service to the AF 201 including the Allowed NTN profile and GNSS location.

[0413] Refer to Step 1-1 in Fig. 3 for the NTN profile.

[0414] One example, the Allowed NTN profile may be Satellite Service provider or / and Satellite Service name. 　　Refer to Step 2 in Fig. 6 for the GNSS location.

[0415] Step 6. Upon reception of the Naf_find satellite service from the NEF 79, the AF 502 search a available satellite as a candidate for target cell for the handover based on the received Allowed NTN profile and GNSS location.

[0416] The AF 201 sends a Naf_find satellite response message to the NEF 79 including List of available NTN profile.

[0417] The List of available NTN profile composed of available cells that can be a target cell for the handover.

[0418] One example, The List of available NTN profile composed of a list of the Satellite identifier as defined in Step 1-1 in Fig. 3 or a list of NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5] or a list of NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5] or a list of E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5] or a list of Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5] or any combination of the listed parameters.

[0419] Step 7. The NEF 79 sends the Nnef_find satellite response to the AMF 70 including List of available NTN profile that is received from the AF 205 in Step 6.

[0420] Step 8. Upon reception of the Nnef_find satellite response from the NEF 79, the AMF 70 chooses one cell as a candidate for the target cell for the handover.

[0421] The AMF 70 sends Handover order including Target Satellite identifier.

[0422] The Target Satellite identifier is defined in Step 1-1 in Fig. 3.

[0423] One example, the Target Satellite identifier may be NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5] or NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5] or E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5] or Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5], especially if the target cell is at the ground as TN cell.

[0424] Step 9. Steps 2 to 8 in Fig. 18 take place.

[0425] <Third scenario in Third example of the Third Aspect> 　　The Third scenario in Third example of the Third Aspect includes an example of the inter RAT type handover with Charing data control.

[0426] Fig. 20 illustrates an example of call flow for the inter RAT type handover with Charing data control.

[0427] The detailed processes of the Third scenario in Third example of the Third Aspect are described below with reference to Fig. 20.

[0428] Step 0. Steps 0-1 to 4 in Fig. 18 take place.

[0429] The Xn based inter NG-RAN handover procedure starts.

[0430] Step 1. The Handover preparation and the Handover execution from RAN 501 to RAN 502 take place according to 3GPP TS 23.502 [4] Section 4.9.1.2.2.

[0431] Step 2. The RAN 501 sends an N2 Path Switch Request message to the AMF 70 including Old NTN profile, New NTN profile and RAT Usage data.

[0432] The RAN Usage data includes the list of PDU Session ID and QoS Flow Usage Report Item. Further Usage Report Item include NTN profile, QoS Flow Indicator and QoS Flows Timed Report List.

[0433] The following bullets explain each parameter in detail. 　　- Old NTN profile: The Old NTN profile indicates an Old NTN used until the Xn based inter NG-RAN handover takes place. 　　- One example, the Old NTN profile includes RAT Type, Satellite Service provider, Satellite Service name and Satellite identifier. 　　- New NTN profile: The New NTN profile indicates a New NTN being used after the Xn based inter NG-RAN handover. 　　- One example, the new NTN profile includes RAT Type, Satellite Service provider, Satellite Service name and Satellite identifier. 　　- RAT Usage data: The RAT Usage data indicates a usage data with an access network. The RAN Usage data includes at least the list of PDU Session ID and QoS Flow Usage Report Item. 　　- PDU Session ID: Refer to Step 2 in Fig. 13. 　　- QoS Flow Usage Report Item: The QoS Flow Usage Report Item indicates the Usage data of the PDU Session as identifed by the associated PDU Session ID. The QoS Flow Usage Report Item includes at least list of usage data per QoS Flow includng the QoS Flow Indicator, the NtN profie and QoS Flows Timed Report List. The QoS Flows Timed Report List includes at least Start Timestamp, End Timestamp, Usage Count UL and Usage Count DL.

[0434] Step 3. Upon reception of the N2 Path Switch Request message from the RAN 501, the AMF 70 sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF 71. The Nsmf_PDUSession_UpdateSMContext Request includes at least all data that are received from the RAN 501 in the N2 Path Switch Request message in Step 2.

[0435] Step 4. The SMF 71 stores the received RAT Usage data and reflects it when the SMF 71 generates a Charging data record.

[0436] One example, the SMF 71 sends the generated Charging data record to the OAM 8 or / and the Charging Enablement Function (CEF).

[0437] Step 5. Steps 6 to 9 in 3GPP TS 23.502 [4] Section 4.9.1.2.2 take place.

[0438] The Xn based inter NG-RAN handover procedure ends.

[0439] Step 6. Steps 6 to 8 in Fig. 18 take place.

[0440] <First Variant of the Fourth example of the Second Aspect> 　　If the inter RAT type handover take place within the RAN 501, The RAN 501 sends an N2 message to the AMF 70 including all information that the N2 Path Switch Request message carries to the AMF 70 in Step 2. Then the AMF 70 informs the received information to the SMF 71 to reflect it to the Charging data record.

[0441] One example, the N2 message may be Uplink RAN status transfer, Uplink RAN early status transfer, Retrieve UE information, new N2 message or existing N2 message.

[0442] <Fourth scenario in Third example of the Third Aspect> 　　The Fourth scenario in Third example of the Third Aspect includes an example of the make before break inter RAT type handover with QoS adjustment.

[0443] There are following prerequisites in this scenario: 　　- The UE 3 is a dual steer device and the UE 3 can establish multiple PDU Sessions for the same convertibility with the AF 201. 　　- The UE 3 and UPF 71 have an ability of the traffic steering and traffic switching based on an installed Dual Sterr control policy.

[0444] Fig. 21 illustrates an example of call flow for the make before break inter RAT type handover with QoS adjustment.

[0445] The detailed processes of the Fourth scenario in Third example of the Third Aspect are described below with reference to Fig. 21.

[0446] Step 0-1. The UE 3 registered with AMF 70 using the Registration procedure as disclosed in Fig. 6.

[0447] Step 0-2. The PDU Session has been established with RAN 501 using the PDU Session establishment procedure as disclosed in Fig. 14.

[0448] Step 1. The AMF 70 sends the Namf_Location_Eventnotify to the PCF 73 including GNSS location. Refer to Step 2 in Fig. 6 for the GNSS location.

[0449] Step 2. Upon reception of the Namf_Location_Eventnotify message from the AMF 70, the PCF 73 examines whether inter RAT type handover is necessary.

[0450] If the PCF 73 decides that the inter RAT type handover is necessary with the targe cell. Npcf_SMPolicyControl Notify including Target Satellite identifier.

[0451] The Target Satellite identifier indicates a target cell for the inter RAT type handover.

[0452] One example, the Target Satellite identifier may be NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5] or NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5] or E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5] or Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5], especially if the target cell is at the ground as TN cell.

[0453] Step 3. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer to the AMF 70 including N1 SM container. The N1 SM container includes PDU Session Modification Command. The PDU Session Modification command includes PDU Session ID, cause=Add redundant PDU session with target cell, Target Satellite identifier, QoS descriptor in target cell and AMBR in target cell.

[0454] The following bullets explain each parameter in detail. 　　- PDU Session ID: Refer to Step 2 in Fig. 13. 　　- The Target NTN profile indicates the target cell for the handover. Refer to Step 1-1 in Fig. 3 for the NTN profile. 　　- cause=Add redundant PDU session with target cell: This cause indicates to the UE 3 that new PDU Session as a redundant PDU session for the make before break inter RAT type handover with target cell is required. 　　- QoS descripter in target cell: Refer to Step 2 in Fig. 18. 　　- AMBR in target cell: Refer to Step 2 in Fig. 18.

[0455] Step 4. The AMF 70 sends the DL NAS Transport message to the UE 3 including NAS. The NAS includes a PDU Session Modification Command. The PDU Session Modification Command includes PDU Session ID, cause=Add redundant PDU session with target cell, Target Satellite identifier, QoS descriptor in target cell and AMBR in target cell. Refer to Step 3 for parameter details.

[0456] Step 5. The UE 3 initiates the PDU Session Establishment procedure with RAN 502 as described in 3GPP TS 23.502 [4] Section 4.3.2.

[0457] One example, the PDU Session Establishment request message including the Add redundant PDU session with target cell in order to the SMF 71 to configure the dual steer based PDU Session and corelate with the another PDU Session with the RAN 501.

[0458] Step 6. After successful PDU Session establishment in Step 5, the UE 3 and UPF 71 performs the traffic steering and traffic switching using two PDU Sessions one with RAN 501 and the other one with RAN 502.

[0459] Step 7. The UE 3 adjusts media codecs to match with QoS descriptor in target cell and AMBR in target cell for the cell in RAN 502 over the application layer.

[0460] Step 8. The UE requested PDU Session Release procedure as described in 3GPP TS 23.502 [4] Section 4.3.4 takes place with the PDU Session with the RAN 501.

[0461] After successful RAN 501 performs the UE location measurement by contacting to the UE 3.

[0462] For example, Steps 4-1 to 4-3 in Fig. 17 take place between the RAN 501 and the UE 3.

[0463] Step 3. The RAN 501 sends a Location reporting message to the AMF 70 including GNSS location.

[0464] Step 4. The AMF 70 sends an Nnef_find satellite service to the NEF 79 including NTN profile and GNSS location.

[0465] Refer to Step 1-1 in Fig. 3 for the NTN profile.

[0466] One example, the NTN profile may be Satellite Service provider or / and Satellite Service name.

[0467] Refer to Step 2 in Fig. 6 for the GNSS location.

[0468] Step 5. The NEF 79 sends a Naf_find satellite service to the AF 201 including NTN profile and GNSS location.

[0469] Refer to Step 1-1 in Fig. 3 for the NTN profile.

[0470] One example, the NTN profile may be Satellite Service provider or / and Satellite Service name.

[0471] Refer to Step 2 in Fig. 6 for the GNSS location.

[0472] Step 6. Upon reception of the Naf_find satellite service from the NEF 79, the AF 502 search a available satellite as a candidate for target cell for the handover based on the received NTN profile and GNSS location.

[0473] The AF 201 sends a Naf_find satellite response message to the NEF 79 including List of available NTN profile.

[0474] The List of available NTN profile composed of available cells that can be a target cell for the handover.

[0475] One example, The List of available NTN profile composed of a list of the Satellite identifier as defined in Step 1-1 in Fig. 3 or a list of NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5] or a list of NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5] or a list of E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5] or a list of Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5] or any combination of the listed parameters.

[0476] Step 7. The NEF 79 sends the Nnef_find satellite response to the AMF 70 including List of available NTN profile that is received from the AF 205 in Step 6.

[0477] Step 8. Upon reception of the Nnef_find satellite response from the NEF 79, the AMF 70 chooses one cell as a candidate for the target cell for the handover.

[0478] The AMF 70 sends Handover order including Target Satellite identifier.

[0479] The Target Satellite identifier is defined in Step 1-1 in Fig. 3.

[0480] One example, the Target Satellite identifier may be NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5] or NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [5] or E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5] or Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5].

[0481] Whit this make before break inter RAT type handover with QoS adjustment procedure, the inter RAT type handover without any service disruption is achieved.

[0482] <Fourth example of the Third Aspect> 　　The Fourth example of the Third Aspect includes a paging procedure for satellite communication.

[0483] <First scenario in Fourth example of the Third Aspect> 　　The First scenario in Fourth example of the Third Aspect includes an example of the GNSS location-based paging procedure.

[0484] Fig. 22 illustrates an example of call flow for the GNSS location-based paging procedure.

[0485] The detailed processes of the First scenario in Fourth example of the Third Aspect are described below with reference to Fig. 22.

[0486] Step 0. The UE 3 registered with AMF 70 using the Registration procedure in Fig. 7.

[0487] After successful registration procedure, the AMF 70 holds the GNSS based RA for the UE 3.

[0488] Step 1. Down link data arrives at UPF 72. Then the UPF 72 sends the Data notification message to the SMF 71 including SUPI of the UE 3.

[0489] Step 2. The SMF 71 sends an Namf_Communication_N1N2MessageTransfer to the AMF 70 including SUPI of the UE 3.

[0490] Step 3. As the AMF 70 stores the GNSS based RA for the UE 3 as the registration area, the AMF 70 sends the Nnef_find satellite for page to the NEF 79 including Allowed NTN profile and GNSS based RA.

[0491] The following bullets explain each parameter in detail. 　　- Allowed NTN profile: Refer to Step 4 in Fig. 19. 　　- GNSS based RA: Refer to Step 8 in Fig. 7.

[0492] Step 4. Upon reception of the Nnef_find satellite for page from the AMF 70, the NEF 79 sends a Naf_find satellite for page to the AF 201 including Allowed NTN profile and GNSS based RA.

[0493] Refer to Step 3 for parameter details.

[0494] Step 5. Upon reception of the Naf_find satellite for page from the NEF 79, the NEF 79 searches satellite that may be used for paging to the UE 3 based on the received Allowed NTN profile and GNSS based RA.

[0495] When the AF 201 finds one or some Satellite(s) that may be used for paging to the UE 3, the AF 201 sends the Naf_find satellite for page response message to the NEF 79 including List of available NTN profile.

[0496] Refer to Step 6 in Fig. 19 for List of available NTN profile.

[0497] Step 6. Upon reception of the Naf_find satellite for page response from the AF 205, the NEF 79 sends the Nnef_find satellite for page response to the AMF 70 including List of available NTN profile.

[0498] Step 7. Upon reception of the Nnef_find satellite for page response from the NEF 79, the AMF 70 search possible cells for paging.

[0499] The AMF 70 generates a Satellite identifier list for paging.

[0500] The AMF 70 may also generate TAI list for paging in case that the UE 3 may be reachable with cells in TN.

[0501] One example, the AMF 70 may generate a mixture of Satellite identifier list for paging and TAI list for paging together for possible paging cells.

[0502] Step 8. The AMF 70 sends Paging message to RAN 501 including TAI list for paging, Satellite identifier list for paging and GNSS based RA.

[0503] The following bullets explain each parameter in detail. 　　- TAI list for paging: The TAI list for paging is composed of TAIs that the UE 3 may be located and thus a subject for paging area. 　　- One example, the TAI list for paging is used for paging over cells in TN. 　　- Satellite identifier list for paging: The Satellite identifier list for paging is composed of Satellite identifier(s) that the paging is possible over those satellites. 　　- GNSS based RA: Refer to Step 8 in Fig. 7.

[0504] Step 9. The RAN 501 performs the page based on the received information in Step 8.

[0505] The RAN 501 uses the received GNSS based RA to instruct cells where to page.

[0506] When the UE 3 receives the page, the UE 3 sends the Service request to the AMF 70 via a cell that the UE 3 receives the page.

[0507] <First Variant of the First scenario in Fourth example of the Third Aspect> 　　In Step 8, the AMF 70 stores the TAI list for paging, Satellite identifier list for paging and GNSS based RA together with time of paging occurrence. The AMF 70 may also store how may paging resending occurs in the AMF 70.

[0508] The stored information related to the paging may be reported to other NF in the core network 7 (Example, CHF) in case that the paging is a subject for charging to user of the UE 3 or a subject for settlement between PLMN operator and Satellite service provider.

[0509] In this case, a paging report from the AMF 70 to other NF in the core network 7 (Example, CHF) includes at least, time, RAT type, Satellite Service provider, Satellite Service name, Satellite identifier, successful paging or not (if the service request is received from the UE 3 as the response to the page, it is considered as successful paging), the number of paging repeated, trigger of page (Example, SMS, LCS, Application id, PDU Session ID, DNN, S-NSSAI or SBI signalling).

[0510] <Second scenario in Fourth example of the Third Aspect> 　　The Second scenario in Fourth example of the Third Aspect includes an example of the progressive paging over the satellite.

[0511] In this scenario, it is assumed that a Satellite cannot designate (beam) a zone for downlink data. I.e., service area on earth is only one zone for the satellite.

[0512] With this kind of satellite, the GNSS based RA is not useful for paging as there is only one zone on earth for paging.

[0513] Fig. 23 illustrates an example of call flow for the progressive paging over the satellite.

[0514] The detailed processes of the Second scenario in Fourth example of the Third Aspect are described below with reference to Fig. 23.

[0515] Step 0. It is assumed that a service area of the LEO satellite with RAN 502 is totally overlapped by a service area of the MEO satellite with RAN 501.

[0516] In addition, the LEO satellite and GEO satellite has only one zone on earth as a target zone for sending downlink data over the service link.

[0517] Step 1. Steps 0 to 6 in Fig. 22 take place.

[0518] Step 2. The AMF 70 generates a Satellite identifier list for paging. In this example, cells in RAN 502 and cells in RAN 501 are chosen.

[0519] Step 3. The AMF 70 sends Paging message only to RAN 502 including Satellite identifier list for paging and GNSS based RA.

[0520] Then, the AMF 70 starts the page response timer waiting a Service request message to come from the UE 3 as the page response.

[0521] Step 4. The RAN 502 performs the page based on the received information in Step 3.

[0522] Step 5. When the paging timer, started at Step 3, expires and the UE 3 has not responded to the paging over LEO, The AMF 70 sends Paging message only to RAN 501 including Satellite identifier list for paging and GNSS based RA.

[0523] One example, the AMF 70 sends Paging message to both RAN 501 and RAN 502 including Satellite identifier list for paging and GNSS based RA.

[0524] Step 6. The RAN 501 performs the page based on the received information in Step 5.

[0525] When the UE 3 receives the page, the UE 3 sends the Service request to the AMF 70 via a cell that the UE 3 receives the page.

[0526] With this progressive paging scheme over the satellite, the downlink traffic overload in the service link may be mitigated as paging traffic may be minimized.

[0527] <First Variant of the Second scenario in Fourth example of the Third Aspect> 　　In Step 5, if the AMF 70 sends Paging message to both RAN 501 and RAN 502 and a Service request message form the UE 3 arrives via the RAN 501, The AMF 70 may send a Stop paging message to the RAN 502.

[0528] When the RAN 502 receives the Stop paging message from the AMF 70, the RAN 502 stops performing re-paging and stop the paging process.

[0529] <Second Variant of the Second scenario in Fourth example of the Third Aspect> 　　In Steps 3 and 5, the AMF 70 stores Satellite identifier list for paging and GNSS based RA together with time of paging occurrence. The AMF 70 may also store how may paging resending occurs in the AMF 70.

[0530] The stored information related to the paging may be reported to other NF in the core network 7 (Example, CHF) in case that the paging is a subject for charging to user of the UE 3 or a subject for settlement between PLMN operator and Satellite service provider.

[0531] In this case, a paging report from the AMF 70 to other NF in the core network 7 (Example, CHF) includes at least, time, RAT type, Satellite Service provider, Satellite Service name, Satellite identifier, successful paging or not (if the service request is received from the UE 3 as the response to the page, it is considered as successful paging), the number of paging repeated, trigger of page (Example, SMS, LCS, Application id, PDU Session ID, DNN, S-NSSAI or SBI signalling).

[0532] <System overview> 　　Fig. 24 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.

[0533] The telecommunication system 1 represents a system overview in which an end-to-end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.

[0534] The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0535] The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.

[0536] The (R)AN node 5 may be split into control plane function and user plane function. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane functions are aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called as 'dual connectivity' or 'Multi connectivity'.

[0537] The (R)AN node 5 can also support a communication using the satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access.

[0538] In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0539] The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in logical nodes can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).

[0540] A Network Function can be deployed as distributed, redundant, stateless, and scalable that provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).

[0541] The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0542] As is well known, a UE 3 may enter and leave the areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0543] The core network 7 also includes, amongst others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Data Analytics Function (NWDAF) 74, a Unified Data Management (UDM) 75, a Authentication Server Function (AUSF) 76, a AKMA Anchor Function (AAnF) 77, a Network Repository Function (NRF) 78, a Network Exposure Function (NEF) 79 and a Unified Data Repository (UDR) 7100. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, PCF 73, AAnF 77, NRF 78, NEF 79 and UDR 7100 for the roaming-out UE 3.

[0544] The OAM 8 includes, amongst others, Operational functions, Administrational functions and Maintenance related functions. The OAM 8 has interfaces with RAN 5, logical nodes in the core network 7 in a PLMN. In addition, the OAM 8 has interfaces to the AF 201 and other entities that are located in the data network 20.

[0545] When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, PCF 73, AAnF 77, NRF 78, NEF 79 and UDR 7100 for the roaming-out UE 3.

[0546] The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Neighboring (R)AN node 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "N2" / "N3" interface(s) and / or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In case that the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type. The data network may include an Application Function (AF) 201.

[0547] The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface.

[0548] The User plane of Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection (i.e. PHY sublayer).

[0549] The Control plane of Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.

[0550] For example, the following messages are communicated over the RRC layer to support AS signaling. 　　- RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup Request message. 　　　　-- establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue. 　　- RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup message. 　　　　-- masterCellGroup and radioBearerConfig 　　- RRC setup complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC setup complete message. 　　　　-- guami-Type, iab-NodeIndication, idleMeasAvailable, ue-MeasurementsAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity, s-NSSAI-List , onboardingRequest

[0551] The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and / or the like). The N1 interface is responsible to provide a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface. 　　- registration request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the registration request message. 　　　　-- 5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requested NB-N1 mode DRX parameters. 　　- registration accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the registration accept message. 　　　　-- 5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters and Extended rejected NSSAI. 　　- Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Registration Complete message. 　　　　-- SOR transparent container. 　　- Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Authentication Request message. 　　　　-- ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge) and EAP message. 　　- Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Response message. 　　　　-- Authentication response message identity, Authentication response parameter and EAP message. 　　- Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Result message. 　　　　-- ngKSI, EAP message and ABBA. 　　- Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Failure message. 　　　　-- Authentication failure message identity, 5GMM cause and Authentication failure parameter. 　　- Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Reject message. 　　　　-- EAP message. 　　- Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Request message. 　　　　-- ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container. 　　- Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Accept message. 　　　　-- PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. 　　- Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Reject message. 　　　　-- 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list. 　　- Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Command message. 　　　　-- Configuration update indication,5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI. 　　- Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Complete message. 　　　　-- Configuration update complete message identity.

[0552] <User equipment (UE)> 　　Fig. 25 is a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in the Figure, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signalling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.

[0553] The UE 3 may, for example, support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0554] The UE 3 may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.).

[0555] The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).

[0556] The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).

[0557] The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).

[0558] The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).

[0559] The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like.

[0560] The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)). 　　The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and / or wireless communication technologies.

[0561] Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored / tracked.

[0562] It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0563] It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0564] The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device). For a wearable device, the UE 3 may be a reduced capability device (RedCap).

[0565] The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).

[0566] <(R)AN node> 　　Fig. 26 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0567] The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.

[0568] The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation.

[0569] The (R)AN node 5 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0570] The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.

[0571] <System overview of (R)AN node 5 based on O-RAN architecture> 　　Fig. 27 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.

[0572] The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and / or the like).

[0573] The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and / or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2" / "N3" interface(s) and / or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes via an appropriate interface (such as the so-called "N3" interface(s) and / or the like).

[0574] Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionalities to communicate with a UE 3 (e.g., the Network Relay UE 300) over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.

[0575] <Radio Unit (RU)> 　　Fig. 28 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0576] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3 (e.g., the Network Relay UE 300)), and in particular, relating to MAC layer and RLC layer.

[0577] The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation.

[0578] The RU 60 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0579] As described above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated / combined unit above.

[0580] <Distributed Unit (DU)> 　　Fig. 29 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0581] The DU 61 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0582] As described above, the RU 60 can be integrated / combined with the DU 61 or CU 62 as an integrated / combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated / combined unit above.

[0583] <Centralized Unit (CU)> 　　Fig. 30 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0584] The CU 62 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0585] As described above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated / combined unit above.

[0586] <AMF> 　　Fig. 31 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0587] The AMF 70 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0588] <SMF> 　　Fig. 32 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421) is responsible for handling (generating / sending / receiving) signalling between the SMF 71 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0589] The SMF 71 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0590] <UPF> 　　Fig. 33 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating / sending / receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0591] The UPF 72 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0592] <PCF> 　　Fig. 34 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0593] The PCF 73 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0594] <NWDAF> 　　Fig. 35 is a block diagram illustrating the main components of the NWDAF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70 and the UDM 75) via a network interface 742. A controller 743 controls the operation of the NWDAF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signalling between the NWDAF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0595] The NWDAF 74 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0596] <UDM> 　　Fig. 36 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).

[0597] The UDM 75 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0598] <AUSF> 　　Fig. 37 is a block diagram illustrating the main components of the AUSF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the AUSF 76 in accordance with software stored in a memory 764. Software may be pre-installed in the memory 764 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signalling between the AUSF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).

[0599] The AUSF 76 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0600] <AAnF> 　　Fig. 38 is a block diagram illustrating the main components of the AAnF 77. As shown, the apparatus includes a transceiver circuit 771 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 772. A controller 773 controls the operation of the AAnF 77 in accordance with the software stored in a memory 774. The Software may be pre-installed in the memory 774 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating / sending / receiving) signalling between the AAnF 77 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0601] The AAnF 77 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0602] <NRF> 　　Fig. 39 is a block diagram illustrating the main components of the NRF 78. As shown, the apparatus includes a transceiver circuit 781 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the NRF 78 in accordance with the software stored in a memory 784. The Software may be pre-installed in the memory 784 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating / sending / receiving) signalling between the NRF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0603] The NRF 78 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0604] <NEF> 　　Fig. 40 is a block diagram illustrating the main components of the NEF 79. As shown, the apparatus includes a transceiver circuit 791 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 792. A controller 793 controls the operation of the NEF 79 in accordance with the software stored in a memory 794. The Software may be pre-installed in the memory 794 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7941 and a communications control module 7942 having at least a transceiver control module 79421. The communications control module 7942 (using its transceiver control module 79421) is responsible for handling (generating / sending / receiving) signalling between the NEF 79 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0605] The NEF 79 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0606] <UDR> 　　Fig. 41 is a block diagram illustrating the main components of the UDR 7A. As shown, the apparatus includes a transceiver circuit 7A01 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 7A02. A controller 7A03 controls the operation of the UDR 7A in accordance with the software stored in a memory 7A04. The Software may be pre-installed in the memory 7A04 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7A041 and a communications control module 7A042 having at least a transceiver control module 7A0421. The communications control module 7A042 (using its transceiver control module 7A0421) is responsible for handling (generating / sending / receiving) signalling between the UDR 7A and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3). 　　The UDR 7A may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0607] <OAM> 　　Fig. 42 is a block diagram illustrating the main components of the OAM 8. As shown, the apparatus includes a transceiver circuit 811 which is operable to transmit signals to and to receive signals from other nodes via a network interface 8012. A controller 813 controls the operation of the OAM 8 in accordance with software stored in a memory 814. Software may be pre-installed in the memory 814 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 8141 and a communications control module 8142 having at least a transceiver control module 81421. The communications control module 8142 (using its transceiver control module 81421) is responsible for handling (generating / sending / receiving) signalling between the OAM 8 and other nodes. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0608] The OAM 8 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0609] <AF> 　　Fig. 43 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3 (e.g., the Network Relay UE 300 and the UE 3)) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421) is responsible for handling (generating / sending / receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0610] The AF 201 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0611] The Energy monitor AF 20102 and Energy supply AF 20101 may have same components to the AF 201.

[0612] <Modifications and Alternatives> 　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.

[0613] In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.

[0614] Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions, hardware or software implemented counters, pointers and / or timers; and / or the like.

[0615] In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.

[0616] In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.

[0617] Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0618] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0619] As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.

[0620] It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.

[0621] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0622] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0623] While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).

[0624] <Supplementary notes> 　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes. 　　(Supplementary note 1) 　　A method performed by a user equipment (UE), the method comprising: 　　receiving, from a Radio Access Network (RAN), first message comprising first satellite information and / or second satellite information; 　　sending, to an Access and Mobility Management Function (AMF) via the RAN, a first Non-Access-Stratum (NAS) message; and 　　receiving, from the AMF, a second NAS message. 　　(Supplementary note 2) 　　The method according to supplementary note 1, wherein 　　the sending the first NAS message comprises sending, to the AMF via the RAN, the first NAS message comprising a first capability for an application and a second capability for Non-Terrestrial Networks (NTN), the AMF being selected by the RAN based on the first information and the second information; and 　　the receiving the second NAS message comprises receiving, from the AMF, the second NAS message comprising a prioritized Radio Access Technology (RAT) list. 　　(Supplementary note 3) 　　The method according to supplementary note 1, wherein 　　the sending the first NAS message comprises sending, to the AMF via the RAN, the first NAS message comprising information related to Non-Terrestrial Networks (NTN), information related to an Altitude based mobility, a capability for the NTN, and information related to a Global Navigation Satellite System (GNSS) location; and 　　the receiving the second NAS message comprises receiving, from the AMF, the second NAS message comprising information related to a restriction for the NTN, information related to an allowance for the NTN, and a Tracking Area Identity (TAI) list with an Altitude offset. 　　(Supplementary note 4) 　　The method according to supplementary note 1, wherein 　　the sending the first NAS message comprises sending, to the AMF via the RAN, the first NAS message comprising information related to a Global Navigation Satellite System (GNSS) based mobility and information related to a GNSS location; and 　　the receiving the second NAS message comprises receiving, from the AMF, the second NAS message comprising information related to GNSS based Registration Area (RA). 　　(Supplementary note 5) 　　A user equipment (UE) comprising: 　　one or more memories storing instructions; and 　　　 　　one or more processors configured to process the instructions to control the UE to: 　　receive, from a Radio Access Network (RAN), first message comprising first satellite information and / or second satellite information; 　　send, to an Access and Mobility Management Function (AMF) via the RAN, a first Non-Access-Stratum (NAS) message; and 　　receive, from the AMF, a second NAS message. 　　(Supplementary note 6) 　　The UE according to supplementary note 5, wherein 　　　 　　the one or more processors are configured to process the instructions to control the UE to: 　　send, to the AMF via the RAN, the first NAS message comprising a first capability for an application and a second capability for Non-Terrestrial Networks (NTN), the AMF being selected by the RAN based on the first information and the second information; and 　　receive, from the AMF, the second NAS message comprising a prioritized Radio Access Technology (RAT) list. 　　(Supplementary note 7) 　　The UE according to supplementary note 5, wherein 　　the one or more processors are configured to process the instructions to control the UE to: 　　send, to the AMF via the RAN, the first NAS message comprising information related to Non-Terrestrial Networks (NTN), information related to an Altitude based mobility, a capability for the NTN, and information related to a Global Navigation Satellite System (GNSS) location; and 　　receive, from the AMF, the second NAS message comprising information related to a restriction for the NTN, information related to an allowance for the NTN, and a Tracking Area Identity (TAI) list with an Altitude offset. 　　(Supplementary note 8) 　　The UE according to supplementary note 5, wherein 　　the one or more processors are configured to process the instructions to control the UE to: 　　send, to the AMF via the RAN, the first NAS message comprising information related to a Global Navigation Satellite System (GNSS) based mobility and information related to a GNSS location; and 　　receive, from the AMF, the second NAS message comprising information related to GNSS based Registration Area (RA). 　　(Supplementary note 9) 　　A method performed by a Radio Access Network (RAN), the method comprising: 　　sending, to a user equipment, a first message comprising first satellite information and / or second satellite information; 　　sending, to an Access and Mobility Management Function (AMF), a first Non-Access-Stratum (NAS) message received from the UE; and 　　sending, to the UE, a second NAS message received from the AMF. 　　(Supplementary note 10) 　　A method performed by an Access and Mobility Management Function (AMF), the method comprising: 　　receiving, from a user equipment (UE) via a Radio Access Network (RAN), a first Non-Access-Stratum (NAS) message, the first NAS message being sent by the UE in response to a first message sent by the RAN, the first message comprising first satellite information and / or second satellite information; and 　　sending, to the UE via the RAN, a second NAS message.

[0625] This application is based upon and claims the benefit of priority from Indian Patent Application No. 202411058194, filed on July 31, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0626] 20　　DATA NETWORK 3　　USER EQUIPMENT(UE) 31　　TRANSCEIVER CIRCUIT 32　　ANTENNA 33　　CONTROLLER 34　　USER INTERFACE 35　　USIM 36　　MEMORY 361　　OPERATING SYSTEM 362　　COMMUNICATIONS CONTROL MODULE 3621　　TRANSCEIVER CONTROL MODULE 5　　RADIO ACCESS NETWORK (RAN) 501　　RAN 502　　RAN 503　　RAN 51　　TRANSCEIVER CIRCUIT 52　　ANTENNA 53　　NETWORK INTERFACE 54　　CONTROLLER 55　　MEMORY 551　　OPERATING SYSTEM 552　　COMMUNICATIONS CONTROL MODULE 5521　　TRANSCEIVER CONTROL MODULE 60　　RADIO UNIT (RU) 601　　TRANSCEIVER CIRCUIT 602　　ANTENNA 603　　NETWORK INTERFACE 604　　CONTROLLER 605　　MEMORY 6051　　OPERATING SYSTEM 6052　　COMMUNICATIONS CONTROL MODULE 60521　　TRANSCEIVER CONTROL MODULE 61　　DISTRIBUTED UNIT (DU) 611　　TRANSCEIVER CIRCUIT 612　　NETWORK INTERFACE 613　　CONTROLLER 614　　MEMORY 6141　　OPERATING SYSTEM 6142　　COMMUNICATIONS CONTROL MODULE 61421　　TRANSCEIVER CONTROL MODULE 62　　CENTRALIZED UNIT (CU) 621　　TRANSCEIVER CIRCUIT 622　　NETWORK INTERFACE 623　　CONTROLLER 624　　MEMORY 6241　　OPERATING SYSTEM 6242　　COMMUNICATIONS CONTROL MODULE 62421　　TRANSCEIVER CONTROL MODULE 7　　CORE NETWORK 70　　ACCESS AND MOBILITY MANAGEMENT FUNCTION (AMF) 701　　TRANSCEIVER CIRCUIT 702　　NETWORK INTERFACE 703　　CONTROLLER 704　　MEMORY 7041　　OPERATING SYSTEM 7042　　COMMUNICATIONS CONTROL MODULE 70421　　TRANSCEIVER CONTROL MODULE 71　　SESSION MANAGEMENT FUNCTION (SMF) 711　　TRANSCEIVER CIRCUIT 712　　NETWORK INTERFACE 713　　CONTROLLER 714　　MEMORY 7141　　OPERATING SYSTEM 7142　　COMMUNICATIONS CONTROL MODULE 71421　　TRANSCEIVER CONTROL MODULE 72　　USER PLANE FUNCTION (UPF) 7201　　UPF 7202　　UPF 721　　TRANSCEIVER CIRCUIT 722　　NETWORK INTERFACE 723　　CONTROLLER 724　　MEMORY 7241　　OPERATING SYSTEM 7242　　COMMUNICATIONS CONTROL MODULE 72421　　TRANSCEIVER CONTROL MODULE 73　　POLICY CONTROL FUNCTION (PCF) 731　　TRANSCEIVER CIRCUIT 732　　NETWORK INTERFACE 733　　CONTROLLER 734　　MEMORY 7341　　OPERATING SYSTEM 7342　　COMMUNICATIONS CONTROL MODULE 73421　　TRANSCEIVER CONTROL MODULE 74　　NETWORK DATA ANALYTICS FUNCTION (NWDAF) 741　　TRANSCEIVER CIRCUIT 742　　NETWORK INTERFACE 743　　CONTROLLER 744　　MEMORY 7441　　OPERATING SYSTEM 7442　　COMMUNICATIONS CONTROL MODULE 74421　　TRANSCEIVER CONTROL MODULE 75　　UNIFIED DATA MANAGEMENT (UDM) 751　　TRANSCEIVER CIRCUIT 752　　NETWORK INTERFACE 753　　CONTROLLER 754　　MEMORY 7541　　OPERATING SYSTEM 7542　　COMMUNICATIONS CONTROL MODULE 75421　　TRANSCEIVER CONTROL MODULE 76　　AUTHENTICATION SERVER FUNCTION (AUSF) 761　　TRANSCEIVER CIRCUIT 762　　NETWORK INTERFACE 763　　CONTROLLER 764　　MEMORY 7641　　OPERATING SYSTEM 7642　　COMMUNICATIONS CONTROL MODULE 76421　　TRANSCEIVER CONTROL MODULE 77　　AKMA ANCHOR FUNCTION (AAnF) 771　　TRANSCEIVER CIRCUIT 772　　NETWORK INTERFACE 773　　CONTROLLER 774　　MEMORY 7741　　OPERATING SYSTEM 7742　　COMMUNICATIONS CONTROL MODULE 77421　　TRANSCEIVER CONTROL MODULE 78　　NETWORK REPOSITORY FUNCTION (NRF) 781　　TRANSCEIVER CIRCUIT 782　　NETWORK INTERFACE 783　　CONTROLLER 784　　MEMORY 7841　　OPERATING SYSTEM 7842　　COMMUNICATIONS CONTROL MODULE 78421　　TRANSCEIVER CONTROL MODULE 79　　NETWORK EXPOSURE FUNCTION (NEF) 791　　TRANSCEIVER CIRCUIT 792　　NETWORK INTERFACE 793　　CONTROLLER 794　　MEMORY 7941　　OPERATING SYSTEM 7942　　COMMUNICATIONS CONTROL MODULE 79421　　TRANSCEIVER CONTROL MODULE 7A　　UNIFIED DATA REPOSITORY (UDR) 7A1　　TRANSCEIVER CIRCUIT 7A2　　NETWORK INTERFACE 7A3　　CONTROLLER 7A4　　MEMORY 7A41　　OPERATING SYSTEM 7A42　　COMMUNICATIONS CONTROL MODULE 7A421　　TRANSCEIVER CONTROL MODULE 8　　OPERATIONS, ADMINISTRATION, AND MAINTENANCE (OAM) 811　　TRANSCEIVER CIRCUIT 812　　NETWORK INTERFACE 813　　CONTROLLER 814　　MEMORY 8141　　OPERATING SYSTEM 8142　　COMMUNICATIONS CONTROL MODULE 81421　　TRANSCEIVER CONTROL MODULE 201　　APPLICATION FUNCTION (AF) 2011　　TRANSCEIVER CIRCUIT 2012　　NETWORK INTERFACE 2013　　CONTROLLER 2014　　MEMORY 20141　　OPERATING SYSTEM 20142　　COMMUNICATIONS CONTROL MODULE 201421　　TRANSCEIVER CONTROL MODULE

Claims

1. A method performed by a user equipment (UE), the method comprising: 　　receiving, from a Radio Access Network (RAN), a first message comprising first satellite information and / or second satellite information; 　　sending, to an Access and Mobility Management Function (AMF) via the RAN, a first Non-Access-Stratum (NAS) message; and 　　receiving, from the AMF, a second NAS message.

2. The method according to claim 1, wherein 　　the sending the first NAS message comprises sending, to the AMF via the RAN, the first NAS message comprising a first capability for an application and a second capability for Non-Terrestrial Networks (NTN), the AMF being selected by the RAN based on the first information and the second information; and 　　the receiving the second NAS message comprises receiving, from the AMF, the second NAS message comprising a prioritized Radio Access Technology (RAT) list.

3. The method according to claim 1, wherein 　　the sending the first NAS message comprises sending, to the AMF via the RAN, the first NAS message comprising information related to Non-Terrestrial Networks (NTN), information related to an Altitude based mobility, a capability for the NTN, and information related to a Global Navigation Satellite System (GNSS) location; and 　　the receiving the second NAS message comprises receiving, from the AMF, the second NAS message comprising information related to a restriction for the NTN, information related to an allowance for the NTN, and a Tracking Area Identity (TAI) list with an Altitude offset.

4. The method according to claim 1, wherein 　　the sending the first NAS message comprises sending, to the AMF via the RAN, the first NAS message comprising information related to a Global Navigation Satellite System (GNSS) based mobility and information related to a GNSS location; and 　　the receiving the second NAS message comprises receiving, from the AMF, the second NAS message comprising information related to GNSS based Registration Area (RA).

5. A user equipment (UE) comprising: 　　one or more memories storing instructions; and 　　　 　　one or more processors configured to process the instructions to control the UE to: 　　receive, from a Radio Access Network (RAN), a first message comprising first satellite information and / or second satellite information; 　　send, to an Access and Mobility Management Function (AMF) via the RAN, a first Non-Access-Stratum (NAS) message; and 　　receive, from the AMF, a second NAS message.

6. The UE according to claim 5, wherein 　　　 　　the one or more processors are configured to process the instructions to control the UE to: 　　send, to the AMF via the RAN, the first NAS message comprising a first capability for an application and a second capability for Non-Terrestrial Networks (NTN), the AMF being selected by the RAN based on the first information and the second information; and 　　receive, from the AMF, the second NAS message comprising a prioritized Radio Access Technology (RAT) list.

7. The UE according to claim 5, wherein 　　the one or more processors are configured to process the instructions to control the UE to: 　　send, to the AMF via the RAN, the first NAS message comprising information related to Non-Terrestrial Networks (NTN), information related to an Altitude based mobility, a capability for the NTN, and information related to a Global Navigation Satellite System (GNSS) location; and 　　receive, from the AMF, the second NAS message comprising information related to a restriction for the NTN, information related to an allowance for the NTN, and a Tracking Area Identity (TAI) list with an Altitude offset.

8. The UE according to claim 5, wherein 　　the one or more processors are configured to process the instructions to control the UE to: 　　send, to the AMF via the RAN, the first NAS message comprising information related to a Global Navigation Satellite System (GNSS) based mobility and information related to a GNSS location; and 　　receive, from the AMF, the second NAS message comprising information related to GNSS based Registration Area (RA).

9. A method performed by a Radio Access Network (RAN), the method comprising: 　　sending, to a user equipment, a first message comprising first satellite information and / or second satellite information; 　　sending, to an Access and Mobility Management Function (AMF), a first Non-Access-Stratum (NAS) message received from the UE; and 　　sending, to the UE, a second NAS message received from the AMF.

10. A method performed by an Access and Mobility Management Function (AMF), the method comprising: 　　receiving, from a user equipment (UE) via a Radio Access Network (RAN), a first Non-Access-Stratum (NAS) message, the first NAS message being sent by the UE in response to a first message sent by the RAN, the first message comprising first satellite information and / or second satellite information; and 　　sending, to the UE via the RAN, a second NAS message.

Images