Method for radio terminal, method for base station, method for access and mobility management function, method for second base station and radio terminal

Abstract

An aspect of this disclosure includes a method for a radio terminal comprising　receiving, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information; and receiving, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.

Description

METHOD FOR RADIO TERMINAL, METHOD FOR BASE STATION, METHOD FOR ACCESS AND MOBILITY MANAGEMENT FUNCTION, METHOD FOR SECOND BASE STATION AND RADIO TERMINAL

[0001] The present disclosure relates to a method for method for a radio terminal, a method for a base station, a method for a first base station, a method for a second base station, a method for an access and mobility management function (AMF), a method for a first AMF, a method for a second AMF, a method for a session management function (SMF), a radio terminal, a base station, a first base station, a second base station, an access and mobility management function (AMF), a first AMF, a second AMF, a session management function (SMF), a core network node, and a core network.

[0002] For example, 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. 　　GEO orbits, where the satellite has a field of view (FOV) of about 1 / 3 of the earth's surface area is great for coverage and for flexibly moving bandwidth and capacity from areas of low demand to areas of high demand in real time. 　　LEO orbits with an altitude of a few hundred km are useful for latency sensitive applications and in some cases can provide line-of-sight (LoS) advantages, link budget advantages (this may or may not be the case depending on the satellite size and orbit altitude) and in some cases polar or high latitude coverage depending on the constellation configuration.

[0003] In addition, a communication using the satellites has some unique characteristics on radio penetration. 　　For example, if users on earth cannot see the sky, for example being under the big tree, users may not be able to communicate with the satellite. 　　In another example, downlink data from the satellite may land anywhere in the FOV of the satellite which results in spreading the downlink data unnecessarily too wide on earth.

[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. 　　It is desired that the above-mentioned unique satellite communication characteristics are carefully examined and taken into account for designing the 3GPP system with satellite access.

[0005] 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". V18.6.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) NPL 17:

[0017] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)". V18.3.0 (2024-06) NPL 18:

[0018] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". V18.7.1 (2024-06)

[0006] A technical mechanism is needed to achieve efficient communication through the collaboration of at least one satellite in at least one satellite orbit and ground-based communication terminals and facilities (communication nodes).

[0007] The disclosure has a method for a radio terminal comprising receiving, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information; and receiving, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.

[0008] The disclosure has a method for a radio terminal comprising communicating with an Access and Mobility Management Function (AMF); and receiving, from the AMF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0009] The disclosure has a method for a radio terminal comprising communicating with Policy Control Function (PCF); and receiving, from the PCF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0010] The disclosure has a method for a radio terminal comprising communicating with Access Function (AF) and receiving, from the AF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0011] The disclosure has a method for a radio terminal comprising communicating with a Unified Data Management Function (UDM); and receiving, from the UDM, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0012] The disclosure has a method for a radio terminal comprising receiving, from a base station, satellite related information, sending, to the base station, a Radio Resource Control (RRC) setup request message, receiving, from the base station, a RRC setup message including the satellite related information; and sending, to the base station, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT) , receiving, from an Access and Mobility Management Function (AMF), at least one of information indicating subscribed multi orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use , and information indicating the Tracking Area where the radio terminal is requested to stay; and electing a satellite based on the information indicating subscribed multi orbit satellite access profile.

[0013] The disclosure has a method for a base station comprising sending, to a radio terminal, satellite related information, receiving, from the radio terminal, a Radio Resource Control (RRC) setup request message, sending, to the radio terminal, a RRC setup message including the satellite related information, receiving, from the radio terminal, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT); and sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT.

[0014] The disclosure has a method for an Access and Mobility management Function (AMF) comprising receiving, from a base station, a message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), sending, to a Unified Data Management Function (UDM), a registration request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT, receiving, from the UDM a registration response message, sending, to the UDM, a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT, receiving, from the UDM, a response message including at least one of information related to a first multi-orbit satellite access profile, information indicates that a radio terminal has a valid subscription to redirected page response function, and information indicate that the radio terminal has a valid subscription to the Radio Access Type (RAT) indication in a page function sending, to a Policy Control Function (PCF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, and information indicating support for redirected page response, receiving, from the PCF, a message, receiving, from the PCF, information related to a second multiple-orbit satellite profile, sending, to the radio terminal the information related to the second multiple-orbit satellite profile; and sending, to the radio terminal, at least one of information indicating subscribed multi-orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay.

[0015] The disclosure has a method for a second base station relate to a second satellite comprising receiving, from a radio terminal, a Radio Resource Configuration (RRC) Setup Request message, sending, to the radio terminal ,a Radio Resource Configuration (RRC) Setup message including satellite related information, receiving, from the radio terminal , a Radio Resource Configuration (RRC) message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT);and sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0016] The disclosure has a radio terminal comprising means for receiving, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information; and means for receiving, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.

[0017] Fig. 1 is a diagram illustrating an architecture.Fig. 2 is a diagram illustrating an architecture.Fig. 3 is a diagram illustrating an architecture.Fig. 4 is a diagram illustrating an architecture.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 procedure in the UE in this disclosure.Fig. 8 is an example structure of data in 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 a diagram illustrating an architecture.Fig. 18 is an example signaling diagram of this disclosure.Fig. 19 is an example signaling diagram of this disclosure.Fig. 20 is a diagram illustrating an architecture.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 of satellite coverage.Fig. 24 is an example signaling diagram of this disclosure.Fig. 25 is an example signaling diagram of this disclosure.Fig. 26 is an example of satellite coverage.Fig. 27 is an example signaling diagram of this disclosure.Fig. 28 is an example of satellite coverage.Fig. 29 is a diagram illustrating a system overview.Fig. 30 is a block diagram illustrating a UE.Fig. 31 is a block diagram illustrating an (R)AN node.Fig. 32 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 33 is a block diagram illustrating an RU.Fig. 34 is a block diagram illustrating a DU.Fig. 35 is a block diagram illustrating a CU.Fig. 36 is a block diagram illustrating an AMF.Fig. 37 is a block diagram illustrating an SMF.Fig. 38 is a block diagram illustrating a UPF.Fig. 39 is a block diagram illustrating a PCF.Fig. 40 is a block diagram illustrating an NWDAF.Fig. 41 is a block diagram illustrating a UDM.Fig. 42 is a block diagram illustrating an AUSF.Fig. 43 is a block diagram illustrating an AAnF.Fig. 44 is a block diagram illustrating an NRF.Fig. 45 is a block diagram illustrating an NEF.Fig. 46 is a block diagram illustrating a UDR.Fig. 47 is a block diagram illustrating an OAM.Fig. 48 is a block diagram illustrating an AF.

[0018] <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 HAPS　　High Altitude Platform Station 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 MO　　Mobile Originated 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 Signaling optimization (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 S-CSCF　　Server - Call Session Control Function 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 TAC　　Tracking Area Code 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

[0019] <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].

[0020] <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.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

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

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

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

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

[0031] In this disclosure, regarding listed parameters in the certain message, at least one of the listed parameters may be included in the certain message. For example, "the message including parameter A and parameter B" may mean "the message including at least one of parameter A and parameter B". In addition, for example, "A including (or containing, or similar wording etc.) B and C" may mean "A including at least one of B and C."

[0032] In this disclosure, a RAN, including a RAN 5, a RAN 501 and a RAN 502, may be interpreted as a RAN node or a cell in the RAN node, cells in the RAN node or the RAN node on a satellite.

[0033] Although this disclosure discloses a mechanism to utilize the multi-orbit satellites for cellular communication in the 5GS, all mechanisms in this disclosure can equally apply to the 6G, EPS and / or any other system as well. In case all mechanisms in this disclosure are to apply to the EPS, the following terminology conversions apply: - gNB ( eNodeB - AMF ( MME - SMF ( SGW or PGW or combined SGW and PGW - UPF ( SGW-U or PGW-U or combined SGW-U and PGW^U - NGAP ( S1AP - XnAP ( X2AP - Any NGAP messages ( Respective S1AP messages - Registration Request message ( Attach Request message or TAU Request message - Any AMF service-related messages (ex. Namf_Communication_NonUeN2InfoNotify) ( GTP-C messages - Any UDM service-related messages (ex. Nudm_SDM_Notification) ( DIAMETER messages - 5G-GUTI ( GUTI - 5G-S-TMSI ( S-TMSI - RRC Setup Request ( RRC Connection Setup Request - RRC Setup ( RRC Connection Setup - RRC Setup Complete ( RRC Connection Setup Complete

[0034] In this disclosure, three architectures for satellite access are assumed. A satellite access as Uu transport, a RAN on the Satellite and a RAN and full 5GC or partial 5GC nodes on Satellite.

[0035] 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.

[0036] Fig. 2 illustrates the architecture for RAN on the Satellite. 　　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). - 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.

[0037] Fig. 3 illustrates the architecture for the RAN and full 5GC or partial 5GC nodes on the Satellite. 　　This architecture has the following characteristics: - RAN 5 is located on the satellite. - A full 5GC nodes or partial 5GC nodes are located on the satellite. In addition, a 5GC node may be split into two parts, one part on the satellite while another part is at the terrestrial network. - RAN 5 on the satellite communicates with the Gateway over the Feeder link. The Feeder link may support N2 and N3 interfaces (reference points). - core network node on the satellite communicates with the Gateway over the Feeder link. In this case, the Feeder link may support SBI (Service Based Interface) between core network nodes. - If a 5GC node may be split into two parts, one part on the satellite while another part is at the terrestrial network, In this case, the Feeder link may support an internal interface within the 5GC node. This internal interface is outside the scope of 3GPP standard. - RAN 5 may communicate with multiple Core Network nodes. - Satellite may have multiple RAN 5s on board. - Satellite may have multiple 5GC nodes on board.

[0038] 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.

[0039] 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 Platform Station (HAPS).

[0040] 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.

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

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

[0043] A method for a radio terminal according to example aspect of this disclosure includes receiving, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information. The method includes receiving, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.

[0044] A method for a radio terminal according to example aspect of this disclosure includes communicating with an Access and Mobility Management Function (AMF). The method includes receiving, from the AMF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0045] A method for a radio terminal according to example aspect of this disclosure includes communicating with Policy Control Function (PCF). The method includes receiving, from the PCF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0046] A method for a radio terminal according to example aspect of this disclosure includes communicating with Access Function (AF). The method includes receiving, from the AF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0047] A method for a radio terminal according to example aspect of this disclosure includes communicating with a Unified Data Management Function (UDM). The method includes receiving, from the UDM, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0048] A method for a radio terminal according to example aspect of this disclosure includes receiving, from a base station, satellite related information. The method includes sending, to the base station, a Radio Resource Control (RRC) setup request message. The method includes receiving, from the base station, a RRC setup message including the satellite related information. The method includes sending, to the base station, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from an Access and Mobility Management Function (AMF), at least one of information indicating subscribed multi orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay. The method includes electing a satellite based on the information indicating subscribed multi orbit satellite access profile.

[0049] A method for a base station according to example aspect of this disclosure includes sending, to a radio terminal, satellite related information. The method includes receiving, from the radio terminal, a Radio Resource Control (RRC) setup request message. The method includes sending, to the radio terminal, a RRC setup message including the satellite related information. The method includes receiving, from the radio terminal, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The method includes sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT.

[0050] A method for an Access and Mobility management Function (AMF) according to example aspect of this disclosure includes receiving, from a base station, a message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes sending, to a Unified Data Management Function (UDM), a registration request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT. The method includes receiving, from the UDM a registration response message. The method includes sending, to the UDM, a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT. The method includes receiving, from the UDM, a response message including at least one of information related to a first multi-orbit satellite access profile, information indicates that a radio terminal has a valid subscription to redirected page response function, and information indicate that the radio terminal has a valid subscription to the Radio Access Type (RAT) indication in a page function. The method includes sending, to a Policy Control Function (PCF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, and information indicating support for redirected page response. The method includes receiving, from the PCF, a message. The method includes receiving, from the PCF, information related to a second multiple-orbit satellite profile. The method includes sending, to the radio terminal the information related to the second multiple-orbit satellite profile. The method includes sending, to the radio terminal, at least one of information indicating subscribed multi-orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay.

[0051] A method for a radio terminal according to example aspect of this disclosure includes registering with an Access and Mobility management Function (AMF. The method includes receiving, from a first base station related to a first satellite, satellite related information. The method includes deciding to establish a Protocol Data Unit (PDU) session. The method includes storing information for prioritization of satellites. The method includes selecting a cell related to a second base station related to a second satellite, based on the information for prioritization of satellites. The method includes sending, to the second base station, a Radio Resource Configuration (RRC) Setup Request message. The method includes receiving, from the second base station, a Radio Resource Configuration (RRC) Setup message. The method includes sending, to the second base station, a Radio Resource Configuration (RRC) message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the second base station, information including at least one of Authorized QoS rules, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay.

[0052] A method for a second base station relate to a second satellite according to example aspect of this disclosure includes receiving, from a radio terminal, a Radio Resource Configuration (RRC) Setup Request message. The method includes sending, to the radio terminal, a Radio Resource Configuration (RRC) Setup message including satellite related information. The method includes receiving, from the radio terminal, a Radio Resource Configuration (RRC) message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The method includes sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0053] A method for an Access and Mobility management Function (AMF) according to example aspect of this disclosure includes receiving, from a base station related to a second satellite, a message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes sending, to a Session Management Function (SMF), at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the SMF, a message.

[0054] A method for a Session Management Function (SMF) according to example aspect of this disclosure includes sending, to a Unified Data Management Function (UDM), information including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the UDM, information including at least one of information related to multi-orbit satellite access profile, Redirected page response subscribed, and RAT Type indication in page subscribed.

[0055] A method for an Access and Mobility management Function (AMF) according to example aspect of this disclosure includes receiving, from a Session Management Function (SMF), information including at least one of information for Authorized QoS rules, information indicating redirect page response function is ready to use , information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay. The method includes sending, to a second base station related to a second satellite, information including at least one of the Authorized QoS rules, the information indicating redirect page response function is ready to use, the information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and the information indicating the Tracking Area where the radio terminal is requested to stay.

[0056] A method for a radio terminal according to example aspect of this disclosure includes selecting a first cell related to a first radio station related to a first satellite. The method includes receiving, from the first radio station, information indicating a type of satellite related to the radio terminal's respond to a page. The method includes selecting a second cell related to a second radio station related to a second satellite, wherein the selecting a second cell is initiated based on the information indicating a type of satellite related to the radio terminal's respond to a page.

[0057] A method for a radio terminal according to example aspect of this disclosure includes establishing a Protocol Data Unit (PDU) session with a second radio station related to a second satellite. The method includes releasing the PDU session. The method includes establishing the PDU session with a first radio station related to a first satellite.

[0058] A method for a base station according to example aspect of this disclosure includes sending, to an Access and Mobility management (AMF), a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, and List of Satellite identifier. The method includes receiving, from the AMF, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0059] A method for an Access and Mobility management (AMF) according to example aspect of this disclosure includes receiving, from a base station, a request message including at least one of information indicating support for communication with multiple-orbit, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, and List of Satellite identifier. The method includes sending, to the base station, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0060] A method for a base station according to example aspect of this disclosure includes sending, to an Access and Mobility management (AMF), a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the AMF, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name and List of Satellite identifier.

[0061] A method for an Access and Mobility management (AMF) according to example aspect of this disclosure includes sending, to a base station, a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the base station, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name and List of Satellite identifier.

[0062] A method for a first base station according to example aspect of this disclosure includes sending, to a second base station, a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the second radio station, a response message corresponds to the request message, wherein the response message includes at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0063] A method for a radio terminal according to example aspect of this disclosure includes communicating with a firs radio station related to a first satellite via a first interface. The method includes communicating with a second radio station relate to a second satellite via a second interface. The method includes switching the first interface to the second interface.

[0064] A method for a radio terminal according to example aspect of this disclosure includes communicating with an Access and Mobility Management Function (AMF. The method includes receiving, from the AMF, at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal support registration management for multiple USIM and information for Subscription Permanent Identifier (SUPI).

[0065] A method for an Access and Mobility Management Function (AMF) according to example aspect of this disclosure includes receiving, from a Unified Data Management Function (UDM), at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal support registration management for multiple USIM, and information for Subscription Permanent Identifier (SUPI) . The method includes sending, to a radio terminal, at least one of the information indicating that the radio terminal supports multiple registration management, the information indicating that the radio terminal support registration management for multiple USIMand the information for Subscription Permanent Identifier (SUPI).

[0066] A method for a radio terminal according to example aspect of this disclosure includes sending, to a base station, a Radio Resource Control (RRC) message including at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal requests to perform multiple registration, information indicating that the radio terminal support registration management for multiple USIM, information indicating that the radio terminal is required to handle multiple registrations, and information for 5G-Globally Unique Temporary Identity (5G-GUTI).

[0067] A method for a base station according to example aspect of this disclosure includes receiving, from a radio terminal, a Radio Resource Control (RRC) message including at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal requests to perform multiple registration, information indicating that the radio terminal support registration management for multiple USIM, information indicating that the radio terminal is required to handle multiple registrations, and information for 5G-Globally Unique Temporary Identity (5G-GUTI) . The method includes sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating that the radio terminal supports multiple registration management, the information indicating that the radio terminal requests to perform multiple registration, the information indicating that the radio terminal support registration management for multiple USIM, the information indicating that the radio terminal is required to handle multiple registrations, and the information for 5G-Globally Unique Temporary Identity (5G-GUTI).

[0068] A method for an Access and Mobility management Function (AMF) according to example aspect of this disclosure includes receiving, from a base station, a request message including at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal requests to perform multiple registration, information indicating that the radio terminal support registration management for multiple USIM, information indicating that the radio terminal is required to handle multiple registrations, and information for 5G-Globally Unique Temporary Identity (5G-GUTI). The method includes sending, to a Unified Data Management Function (UDM), the information indicating that the radio terminal supports multiple registration management, and the information indicating that the radio terminal support registration management for multiple USIM. The method includes sending, to the UDM, a request message. The method includes receiving, from the UDM, a response message including at least one of information indicating that the radio terminal has a valid subscription to multiple registration, information indicating that the radio terminal has a valid subscription to multiple registration with multiple USIM. The method includes sending, to the radio terminal, an accept message including at least one of information indicating that a multiple registration function is activated and information indicating that the multiple registration function with multiple USIM is activated, wherein the multiple registration is related to a radio terminal's ability to manage multiple registration procedure.

[0069] A method for a second base station relate to a second satellite according to example aspect of this disclosure includes receiving, from a radio terminal, a Radio Resource Configuration (RRC) message including at least one of information indicating that the radio terminal requests to perform multiple registration, and information indicating that the radio terminal is required to handle multiple registrations. The method includes sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating that the radio terminal requests to perform multiple registration, and the information indicating that the radio terminal is required to handle multiple registrations.

[0070] A method for an Access and Mobility management Function (AMF) according to example aspect of this disclosure includes receiving, from a base station related to a second satellite, a message including at least one of information indicating that the radio terminal requests to perform multiple registration, and information indicating that the radio terminal is required to handle multiple registrations. The method includes sending, to a Session Management Function (SMF), information requests a Session Management Function (SMF) to send two messages to the AMF and information related to an AMF name. The method includes receiving, from the SMF, a message.

[0071] A method for a Session Management Function (SMF) according to example aspect of this disclosure includes sending, to a Unified Data Management Function (UDM), information including at least one of information indicating that a radio terminal supports multiple registration management, and information indicating that the radio terminal support registration management for multiple USIM. The method includes receiving, from the UDM, information including at least one of information indicating that a radio terminal has a valid subscription to multiple registration, information indicating that the radio terminal has a valid subscription to multiple registration with multiple USIM, wherein the multiple registration is related to a radio terminal's ability to manage multiple registration procedure.

[0072] A method for an Access and Mobility management Function (AMF) according to example aspect of this disclosure includes receiving, from a Session Management Function (SMF), information including at least one of information indicating that a multiple registration function is activated and information indicating that the multiple registration function with multiple USIM is activated. The method includes sending, to a second base station related to a second satellite, information including at least one of the information indicating that a multiple registration function is activated and the information indicating that the multiple registration function with multiple USIM is activated.

[0073] A method for a radio terminal according to example aspect of this disclosure includes communicating with a first base station related to a first satellite and a second base station related to a second satellite. The method includes receiving, from the first base station, a page message with radio terminal identity. The method includes initiating a cell reselection based on the radio terminal identity.

[0074] A method for a second Access and Mobility management Function (AMF) according to example aspect of this disclosure includes detecting that a radio terminal has ability to be registered with multiple AMF(s), wherein the radio terminal is related to the second AMF related to a second satellite. The method includes sending, to a first AMF related to a first satellite, a paging message with information for Subscription Permanent Identifier (SUPI).

[0075] A method for a Session Management Function (SMF) according to example aspect of this disclosure includes detecting that a radio terminal has ability to be registered with multiple Access and Mobility management Function (AMF), wherein the radio terminal has ability to communicate with a first base station related to a first satellite and a second base station related to a second satellite.

[0076] A method for a radio terminal according to example aspect of this disclosure includes establishing a Protocol Data Unit (PDU) session with a second radio station related to a second satellite and a second Access and Mobility management Function (AMF) related to the second satellite. The method includes releasing the PDU session. The method includes establishing the PDU session with a first radio station related to a first satellite and a first AMF related to the first satellite.

[0077] A method for a first base station according to example aspect of this disclosure includes sending, to a first Access and Mobility management (AMF), a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response , information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The method includes receiving, from the first AMF, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes sending, to a second Access and Mobility management (AMF), a request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier . The method includes receiving, from the second AMF, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0078] A method for a first Access and Mobility management (AMF) according to example aspect of this disclosure includes receiving, from a first base station, a request message including at least one of information indicating support for communication with multiple-orbit, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The method includes sending, to the first base station, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from a second base station, a request message including at least one of the information indicating support for communication with multiple-orbit, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The method includes sending, to the second base station, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response , and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0079] A method for a first base station according to example aspect of this disclosure includes receiving, from a first Access and Mobility management (AMF), a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes sending, to the first AMF, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier, . The method includes receiving, from a second Access and Mobility management (AMF), a configuration message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The method includes sending, to the second AMF, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites , the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier.

[0080] A method for a first Access and Mobility management Function (AMF) according to example aspect of this disclosure includes sending, to a first base station, a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the first base station, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The method includes sending, to a second base station, a configuration message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The method includes receiving, from the second base station, a configuration acknowledgement message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier.

[0081] A method for a first base station according to example aspect of this disclosure includes communicating with a first satellite related to a first Access and Mobility management Function (AMF. The method includes sending, to a second base station relate to a second satellite and a second AMF, a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The method includes receiving, from the second radio station, a response message corresponds to the request message, wherein the response message includes at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0082] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information. The at least one means is configured to receive, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.

[0083] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with an Access and Mobility Management Function (AMF. The at least one means configured to receive, from the AMF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0084] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with Policy Control Function (PCF. The at least one means is configured to receive, from the PCF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0085] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with Access Function (AF. The at least one means is configured to receive, from the AF, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0086] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with a Unified Data Management Function (UDM. The at least one means configured to receive, from the UDM, information for provisioning, the information is related to communication with multiple-orbit satellites.

[0087] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a base station, satellite related information, . The at least one means is configured to send, to the base station, a Radio Resource Control (RRC) setup request message. The at least one means is configured to receive, from the base station, a RRC setup message including the satellite related information. The at least one means is configured to send, to the base station, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The at least one means is configured to receive, from an Access and Mobility Management Function (AMF), at least one of information indicating subscribed multi orbit satellite access profile, information indicating redirect page response function is ready to use , information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay. The at least one means is configured to select a satellite based on the information indicating subscribed multi orbit satellite access profile.

[0088] A base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a radio terminal, satellite related information. The at least one means is configured to receive, from the radio terminal, a Radio Resource Control (RRC) setup request message send, to the radio terminal, a RRC setup message including the satellite related information receive, from the radio terminal, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The at least one means is configured to send, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT.

[0089] An Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a base station, a message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT) . The at least one means is configured to send, to a Unified Data Management Function (UDM), a registration request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT. The at least one means is configured to receive from the UDM a registration response message. The at least one means configured to send, to the UDM, a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT receive, from the UDM, a response message including at least one of information related to a first multi-orbit satellite access profile, information indicates that a radio terminal has a valid subscription to redirected page response function, and information indicate that the radio terminal has a valid subscription to the Radio Access Type (RAT) indication in a page function. The at least one means is configured to send, to a Policy Control Function (PCF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, and information indicating support for redirected page response. The at least one means is configured to receive, from the PCF, a message receive, from the PCF, information related to a second multiple-orbit satellite profile send, to the radio terminal the information related to the second multiple-orbit satellite profile send, to the radio terminal, at least one of information indicating subscribed multi-orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay.

[0090] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to register with an Access and Mobility management Function (AMF). The at least one means is configured to receive, from a first base station related to a first satellite, satellite related information. The at least one means is configured to decide to establish a Protocol Data Unit (PDU) session. The at least one means configured to store information for prioritization of satellites. The at least one means is configured to select a cell related to a second base station related to a second satellite, based on the information for prioritization of satellites. The at least one means is configured to send, to the second base station, a Radio Resource Configuration (RRC) Setup Request message. The at least one means is configured to receive, from the second base station, a Radio Resource Configuration (RRC) Setup message. The at least one means is configured to send, to the second base station, a Radio Resource Configuration (RRC) message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the second base station, information including at least one of Authorized QoS rules, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay.

[0091] A second base station relate to a second satellite according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a radio terminal, a Radio Resource Configuration (RRC) Setup Request message). The at least one means is configured to send, to the radio terminal, a Radio Resource Configuration (RRC) Setup message including satellite related information). The at least one means is configured to receive, from the radio terminal , a Radio Resource Configuration (RRC) message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT send, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0092] An Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a base station related to a second satellite, a message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured tosend, to a Session Management Function (SMF), at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the SMF, a message.

[0093] A Session Management Function (SMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a Unified Data Management Function (UDM), information including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the UDM, information including at least one of information related to multi-orbit satellite access profile, Redirected page response subscribed, and RAT Type indication in page subscribed.

[0094] An Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a Session Management Function (SMF), information including at least one of information for Authorized QoS rules, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay ). The at least one means is configured to send, to a second base station related to a second satellite, information including at least one of the Authorized QoS rules, the information indicating redirect page response function is ready to use, the information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and the information indicating the Tracking Area where the radio terminal is requested to stay.

[0095] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to select a first cell related to a first radio station related to a first satellite). The at least one means is configured to receive, from the first radio station, information indicating a type of satellite related to the radio terminal's respond to a page). The at least one means is configured to select a second cell related to a second radio station related to a second satellite, wherein the selecting a second cell is initiated based on the information indicating a type of satellite related to the radio terminal's respond to a page.

[0096] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to establish a Protocol Data Unit (PDU) session with a second radio station related to a second satellite. The at least one means is configured to release the PDU session). The at least one means is configured to establish the PDU session with a first radio station related to a first satellite.

[0097] A base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to an Access and Mobility management (AMF), a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, and List of Satellite identifier. The at least one means is configured to receive, from the AMF, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0098] An Access and Mobility management (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a base station, a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, and List of Satellite identifier. The at least one means is configured to send, to the base station, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0099] A base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to an Access and Mobility management (AMF), a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The at least one means is configured to receive, from the AMF, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name and List of Satellite identifier.

[0100] An Access and Mobility management (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a base station, a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the base station, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name and List of Satellite identifier.

[0101] A first base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a second base station, a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the second radio station, a response message corresponds to the request message, wherein the response message includes at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT) .

[0102] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with a firs radio station related to a first satellite via a first interface. The at least one means is configured to communicate with a second radio station relate to a second satellite via a second interface. The at least one means is configured to switch the first interface to the second interface.

[0103] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with an Access and Mobility Management Function (AMF. The at least one means is configured to receive, from the AMF, at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal support registration management for multiple USIM, and information for Subscription Permanent Identifier (SUPI).

[0104] An Access and Mobility Management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a Unified Data Management Function (UDM), at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal support registration management for multiple USIM, and information for Subscription Permanent Identifier (SUPI). The at least one means is configured to send, to a radio terminal, at least one of the information indicating that the radio terminal supports multiple registration management, the information indicating that the radio terminal support registration management for multiple USIM, and the information for Subscription Permanent Identifier (SUPI).

[0105] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a base station, a Radio Resource Control (RRC) message including at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal requests to perform multiple registration, information indicating that the radio terminal support registration management for multiple USIM, information indicating that the radio terminal is required to handle multiple registrations , and information for 5G-Globally Unique Temporary Identity (5G-GUTI).

[0106] A base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a radio terminal, a Radio Resource Control (RRC) message including at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal requests to perform multiple registration, information indicating that the radio terminal support registration management for multiple USIM, information indicating that the radio terminal is required to handle multiple registrations, and information for 5G-Globally Unique Temporary Identity (5G-GUTI. The at least one means is configured to send, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating that the radio terminal supports multiple registration management, the information indicating that the radio terminal requests to perform multiple registration, the information indicating that the radio terminal support registration management for multiple USIM, the information indicating that the radio terminal is required to handle multiple registrations, and the information for 5G-Globally Unique Temporary Identity (5G-GUTI).

[0107] An Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a base station, a request message including at least one of information indicating that a radio terminal supports multiple registration management, information indicating that the radio terminal requests to perform multiple registration, information indicating that the radio terminal support registration management for multiple USIM, information indicating that the radio terminal is required to handle multiple registrations, and information for 5G-Globally Unique Temporary Identity (5G-GUTI). The at least one means is configured to send, to a Unified Data Management Function (UDM), the information indicating that the radio terminal supports multiple registration management, and the information indicating that the radio terminal support registration management for multiple USIM. The at least one means is configured to send, to the UDM, a request message. The at least one means is configured to receive, from the UDM, a response message including at least one of information indicating that the radio terminal has a valid subscription to multiple registration, information indicating that the radio terminal has a valid subscription to multiple registration with multiple USIM. The at least one means is configured to send, to the radio terminal, an accept message including at least one of information indicating that a multiple registration function is activated, and information indicating that the multiple registration function with multiple USIM is activated, wherein the multiple registration is related to a radio terminal's ability to manage multiple registration procedure.

[0108] A second base station relate to a second satellite according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a radio terminal, a Radio Resource Configuration (RRC) message including at least one of information indicating that the radio terminal requests to perform multiple registration, and information indicating that the radio terminal is required to handle multiple registrations. The at least one means is configured to send, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating that the radio terminal requests to perform multiple registration, and the information indicating that the radio terminal is required to handle multiple registrations.

[0109] An Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a base station related to a second satellite, a message including at least one of information indicating that the radio terminal requests to perform multiple registration, and information indicating that the radio terminal is required to handle multiple registrations, . The at least one means is configured to send, to a Session Management Function (SMF), information request a Session Management Function (SMF) to send two messages to the AMF, and information related to an AMF name. The at least one means is configured to receive, from the SMF, a message.

[0110] A Session Management Function (SMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a Unified Data Management Function (UDM), information including at least one of information indicating that a radio terminal supports multiple registration management, and information indicating that the radio terminal support registration management for multiple USIM. The at least one means is configured to receive, from the UDM, information including at least one of information indicating that a radio terminal has a valid subscription to multiple registration, information indicating that the radio terminal has a valid subscription to multiple registration with multiple USIM, wherein the multiple registration is related to a radio terminal's ability to manage multiple registration procedure.

[0111] An Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a Session Management Function (SMF), information including at least one of information indicating that a multiple registration function is activated, and information indicating that the multiple registration function with multiple USIM is activated. The at least one means is configured to send, to a second base station related to a second satellite, information including at least one of the information indicating that a multiple registration function is activated, and the information indicating that the multiple registration function with multiple USIM is activated.

[0112] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with a first base station related to a first satellite and a second base station related to a second satellite. The at least one means is configured to receive, from the first base station, a page message with radio terminal identity. The at least one means is configured to initiate a cell reselection based on the radio terminal identity.

[0113] A second Access and Mobility management Function (AMF according to example aspect of this disclosure includes at least one means. The at least one means is configured to detect that a radio terminal has ability to be registered with multiple AMF(s), wherein the radio terminal is related to the second AMF related to a second satellite. The at least one means is configured to send, to a first AMF related to a first satellite, a paging message with information for Subscription Permanent Identifier (SUPI).

[0114] A Session Management Function (SMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to detect that a radio terminal has ability to be registered with multiple Access and Mobility management Function (AMF), wherein the radio terminal has ability to communicate with a first base station related to a first satellite and a second base station related to a second satellite.

[0115] A radio terminal according to example aspect of this disclosure includes at least one means. The at least one means is configured to establish a Protocol Data Unit (PDU) session with a second radio station related to a second satellite and a second Access and Mobility management Function (AMF) related to the second satellite. The at least one means is configured to release the PDU session. The at least one means is configured to establish the PDU session with a first radio station related to a first satellite and a first AMF related to the first satellite.

[0116] A first base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a first Access and Mobility management (AMF), a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT) , List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, and List of Satellite identifier. The at least one means is configured to receive, from the first AMF, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to send, to a second Access and Mobility management (AMF), a request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The at least one means is configured to receive, from the second AMF, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0117] A first Access and Mobility management (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a first base station, a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The at least one means is configured to send, to the first base station, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT. The at least one means is configured to receive, from a second base station, a request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response , the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The at least one means is configured to send, to the second base station, a response message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0118] A first base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to receive, from a first Access and Mobility management (AMF), a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to send, to the first AMF, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The at least one means is configured to receive, from a second Access and Mobility management (AMF), a configuration message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to send, to the second AMF, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier.

[0119] A first Access and Mobility management Function (AMF) according to example aspect of this disclosure includes at least one means. The at least one means is configured to send, to a first base station, a configuration message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the first base station, a configuration acknowledgement message including at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier. The at least one means is configured to send, to a second base station, a configuration message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the second base station, a configuration acknowledgement message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT), List of NTN RAT type, List of Satellite Service provider, List of Satellite Service name, List of Satellite identifier.

[0120] A first base station according to example aspect of this disclosure includes at least one means. The at least one means is configured to communicate with a first satellite related to a first Access and Mobility management Function (AMF). The at least one means is configured to send, to a second base station relate to a second satellite and a second AMF, a request message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT). The at least one means is configured to receive, from the second radio station, a response message corresponds to the request message, wherein the response message includes at least one of the of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).

[0121] <First Aspect> 　　This aspect includes mechanisms to 3GPP system for an enhanced mobility management and session management when the UE 3, the RAN 5 and the core network 7 support multi orbit satellite access. For example, if the UE 3 or the RAN 5 support the multi orbit satellite access, the UE 3 or the RAN 5 may have an ability to support the satellites on multiple orbits, to access the satellites on multiple orbits, or communicate with the satellites on multiple orbits.

[0122] This aspect aims to solve the following issues in 3GPP system with multi orbit satellite access. - For example, possible issues related to mechanisms to 3GPP system for an enhanced mobility management and session management when the UE 3, the RAN 5 and the core network 7 support multi orbit satellite access. - For example, if the UE 3 supports multi orbit satellites, the UE 3 may need to tune to multiple satellites and this results in high consumption of UE battery. In order to avoid high consumption of the UE battery, the UE 3 should have a default satellite to tune to when the UE 3 is in CM-IDLE state and CM-CONNECTED with RRC_INACTIVE state.

[0123] For example, since a satellite with Non-Geostationary Satellite Orbit (NGSO) is moving from the UE 3's point of view, the UE 3 always needs to find the best NGSO and switch to the best satellite from time to time. A handshake between UE 3 and RAN 5 when the UE 3 is in CM-IDLE state and CM-CONNECTED with RRC_INACTIVE state may be considered less stable than one with a satellite with Geostationary Satellite Orbit (GSO).

[0124] < First example of the First Aspect> 　　This example includes mechanisms for the UE 3 to move from satellite 1 to satellite 2 when the UE 3 switches to active mode.

[0125] The satellite 101 may be a MEO, GEO or HEO which may have a wide coverage to page the UE 3.

[0126] The satellite 102 may be a MEO, LEO, HAPS or RAN 5 in a terrestrial network (example, regular gNB(s) in the PLMN) for data communication. For example, the satellite 101 (e.g., MEO, GEO or HEO) may be switched to the satellite 102 (e.g., MEO and / or LEO). For example, the satellite 101 (e.g., MEO, GEO or HEO) may be switched to the HAPS. For example, the satellite 101 (e.g., MEO, GEO or HEO) may be switched to the RAN 5.

[0127] Fig. 4 illustrates an example of switching from one satellite to another based on a UE state. Although Fig. 4 applies to an architecture where only RAN nodes are located in the satellite, the satellite switching may apply to any other architectures, example architecture as illustrated in Fig. 1 and Fig. 3. For example, in the following Fig. 4, the satellite related to the RAN 501 (example, the satellite where the RAN 501 is onboarded or cells of RAN 501 are partially onboarded) may be the satellite 101 and the satellite related to the RAN 502 (example, the satellite where the RAN 502 is onboarded or cells of RAN 502 are partially onboarded) may be the satellite 2. For example, in the following Fig. 4, the satellite related to the RAN 501 (example, the satellite where the RAN 501 is onboarded or cells of RAN 501 are partially onboarded) may be the satellite 2 and the satellite related to the RAN 502 (example, the satellite where the RAN 502 is onboarded or cells of RAN 502 are partially onboarded) may be the satellite 101. For example, the satellite 101 may be a MEO, GEO or HEO which may have a wide coverage to page the UE 3. The satellite 102 may be a MEO, LEO, HAPS or RAN 5 in a terrestrial network (example, regular gNBs in the PLMN) for data communication.

[0128] <First scenario in the First example of the First Aspect> 　　The First scenario in the First example of the First Aspect includes a mechanism on system information that the RAN 5 may broadcast in case the RAN 5 supports multi orbit satellite access.

[0129] Fig. 5 illustrates an example of an enhanced system information that is broadcasted by cells that support multi orbit satellite access.

[0130] The detailed processes of this example are described below with reference to Fig. 5.

[0131] Step 1 and Step 2. Cells that are located in satellite that support multi orbit satellite access broadcast the satellite related information includes one or more of the following information. - TAC: Tracking Area Code: The TAC indicates a Tracking Area Code that the cell belongs to. In this example, cells with the RAN 501 have a TAC value TAC=1 and cells with the RAN 502 have a TAC value TAC=2. - NTN configuration: NTN configuration includes parameters needed for the NTN access. The NTN configuration may be a ntn-Config in SIB 19 as defined in 3GPP TS 38.331

[0015] . - NTN RAT type: The NTN Radio Access Technology (RAT) Type indicates a Radio Access Technology (RAT) Type of the cell that is located in satellite. The NTN RAT type may additionally indicate a satellite type (e.g., LEO, MEO, GEO or HEO). The NTN RAT type may be the RAT type as defined in 3GPP TS 29.212 [7] Section 5.3.31. - 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. - The Satellite Service provider may be a PLMN operator or 3rd party service provider. - The Satellite Service provider may have a contract with user of the UE 3 as a subscription to the satellite service not only over the 3GPP system but also direct access to the satellite, for example using the Very Small Aperture Terminal (VSAT) provided by the Satellite Service provider. - The Satellite Service provider may be expressed by a Satellite operator, Satellite Service operator or other name. - 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 Satellite 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 Defence) Catalog Number, NORAD ID, USSPACECOM (United States Space Command) object number or simply catalog number). - Multi orbit satellite access support: The Multi orbit satellite access support indicates a capability to support the mobility management and session management mechanisms that are disclosed by this disclosure. - For example, the Multi orbit satellite access support may indicate to support one or multiple mechanisms as listed below. -- Redirected page response support: The Redirected page response support indicates that the RAN 5 (or the cell of the RAN 5) in the satellite supports a mechanism for paging over one cell and the UE 3 responding over another cell. In other words, the Redirected page response support indicates that a cell providing this capability supports a mechanism that the UE 3 receives a paging in this cell and respond in another cell. -- RAT Type indication in page support: The RAT Type indication in page support indicates that the RAN 5 (or the cell of the RAN 5) supports a mechanism that the cell indicates a RAT Type in the page. In other words, the RAT Type indication in page support indicates that a cell providing this capability supports a mechanism that the RAT Type is provided in the page. 　　In one example, each capability is broadcasted individually or independently. - ntn-Neighbour cell configuration list includes a list of neighbour cells. The ntn-Neighbour cell configuration list may be a ntn-NeighCellConfigLIst in SIB 19 as defined in 3GPP TS 38.331

[0015] . - One or more of the following information is included in the ntn-Neighbour cell configuration list. -- Ephemeris Information: The Ephemeris Information includes a satellite ephemeris of a satellite where the cell is onboard. In one example, the Ephemeris Information may be the EphemerisInfo in SIB 19 as defined in 3GPP TS 38.331

[0015] . -- TAC: TAC information of the neighbour cell. For example, in case the Step 1, TAC information of the neighbour cell (TAC2) may be included. In case the Step 2, TAC information of the neighbour cell (TAC1) may be included. -- NTN RAT type: NTN RAT Type of the neighbour cell. For example, in case the Step 1, NTN RAT type of the neighbour cell served by the RAN 502 may be included. For example, in case the Step 2, NTN RAT type of the neighbour cell served by the RAN 501 may be included. This information may be provided per cell or per frequency. -- Satellite Service operator: Satellite Service operator of the neighbour cell. For example, in case the Step 1, Satellite Service operator of the neighbour cell served by the RAN 502 may be included. For example, in case the Step 2, Satellite Service operator of the neighbour cell served by the RAN 501 may be included. -- Satellite identifier: Satellite identifier of the neighbour cell. For example, in case the Step 1, Satellite identifier of the neighbour cell served by the RAN 502 may be included. For example, in case the Step 2, Satellite identifier of the neighbour cell served by the RAN 501 may be included. -- Multi orbit satellite support: Multi orbit satellite support capability of the neighbour cell. For example, in case the Step 1, Multi orbit satellite support of the neighbour cell served by the RAN 502 may be included. For example, in case the Step 2, Multi orbit satellite support of the neighbour cell served by the RAN 501 may be included.

[0132] The system information may be broadcast over the MIB, SIB 19, existing SIB or new SIB.

[0133] In one example at least one of the parameters being sent to the UE 3 in step 1 or step 2, may be sent to the UE 3 in an existing RRC message e.g., when the UE 3 is going from connected mode to idle mode, the RAN 501 or RAN 502 can send this information to the UE in a RRC Release message.

[0134] < Second scenario in the First example of the First Aspect> 　　The Second scenario in the First example of the First Aspect includes a mechanism for a Subscribed Multi orbit satellite access profile provisioning when the UE 3 accesses with the multi orbit satellite access. The Second scenario in the First example of the First Aspect may include a mechanism for a Subscribed Multi orbit satellite access profile provisioning when the UE 3 supports and / or communicate with the multi orbit satellite access.

[0135] Fig. 6 illustrates an example of the Subscribed Multi orbit satellite access profile provisioning to support multi orbit satellite access.

[0136] The detailed processes of this example are described below with reference to Fig. 6.

[0137] Example 1 　　In this Example, the AMF 70 provides a Subscribed Multi orbit satellite access profile to the UE 3.

[0138] Step 1-1. The AF 201 sends the Naf service notification message to the UDM 75 including a Multi orbit satellite access profile. In case that the AF 201 is located outside of the PLMN domain, the AF 201 sends the Naf service notification message to the UDM 75. For example, in case that the AF 201 is located outside of the PLMN domain, the AF 201 sends the Naf service notification message to the UDM 75 via the NEF 79. The NEF 79 takes the role of exposing NF capabilities and events securely to the AF 201 and also providing means for the AF 201 to securely provide information to 3GPP network, e.g. Expected UE Behaviour, 5G-VN group information, time synchronization service information and PDU Set handling service specific information.

[0139] 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.

[0140] The Multi orbit satellite access 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.

[0141] The Multi orbit satellite access profile includes all satellite information that are available to use by the PLMN operator based on the business agreement.

[0142] The UDM 75 or UDR 7A maintains the received Multi orbit satellite access profile as a subscription data. The UDR 7A takes the role of storage and providing subscription data to the UDM 75 and storage and providing policy data to the PCF 73 and similar storage functions to other NFs. 　　The Multi orbit satellite access profile may include the following information: - Satellite Service provider: Refer to Step 1 and Step 2 in Fig. 5. - Satellite Service name: Refer to Step 1 and Step 2 in Fig. 5. - Satellite identifier: Refer to Step 1 and Step 2 in Fig. 5. - Prioritized NTN RAT Type list: The Prioritized NTN RAT Type list indicates the NTN RAT Type priority for the UE 3. - The Prioritized NTN RAT Type list includes one or multiple NTN RAT Type in priority order. Refer to Step 1 and Step 2 in Fig. 5 for the NTN RAT Type. - The Prioritized NTN RAT Type list may be an NTN RAT Type 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. - In addition, each entry of the NTN RAT Type in the list may have an associate information with regard to a satellite, for example Satellite Service provider, Satellite Service name and / or Satellite identifier. - Prioritized NTN RAT Type list per a UE state: The Prioritized NTN RAT Type list indicates the NTN RAT Type priority for the UE 3 based on UE state. - In addition, each entry of the NTN RAT Type in the list may have an associated information with regard to a satellite, for example Satellite Service provider, Satellite Service name and / or Satellite identifier. - This data is referred by the UE 3 when the UE 3 is in a state out of states listed below and stays tuned to the best prioritised NTN RAT Type accordingly. - There may be at least the following UE states: - Registration state: The Registration state is referred as a UE state before the initial registration. For example, powered-on in a very first time. - Idle mode state: The Idle mode state is referred to a UE 3 where the UE 3 is in a CM-IDLE sate and a CM-CONNECTED sate with RRC-INACTIVE. - Connected mode state: The Connected mode state is referred to UE 3 where the UE 3 is in a CM-CONNECTED state. - Connected mode state with sensitive data communication: The Connected mode state with sensitive data communication is referred to the UE 3 in a CM-CONNECTED state with the sensitive data communication. Whether PDU Session for data communication is sensitive or not is defined by the AF 201 or the UDM 75 or HPLMN configuration or VPLMN configuration. - Multi Radio Dual Connectivity (MR-DC) access preference: This parameter includes the preferred satellite access type for Master Node (MN) (or Maste Cell Group (MCG)) and the Secondary Node (SN) (or Secondary Cell Group (SCG)). For example, in some scenario the preferred satellite access type for master node (or MCG) can be GEO satellite where as for the secondary nodes (or SCG) the preferred satellite access type is LEO satellite. The MR-DC includes Dual Connectivity between E-UTRA and NR nodes, or between two NR nodes. - The Multi Radio Dual Connectivity (MR-DC) access preference may have the following sub category to each preferred satellite access types one for Master Node and the other one for secondary Node. Note that the following sub-category may be applied per DRB, QoS flow or PDU session. - Both Uplink data and Downlink data. - Uplink data only. In this case, the satellite access with either the MN or the SN has radio resource only for uplink data. For example, this sub-category may be used when the LEO satellite is designated for uplink data only so that the UE 3 can avoid high battery consumption due to uplink data transmission rather than transmitting it to the GEO satellite. - Downlink data only. In this case, the satellite access with either the MN or the SN has radio resource only for downlink data. - Allowed area list for NTN RAT access: The Allowed area list for NTN RAT access includes a list of area where the NTN RAT access is allowed. For example, each entry of area may be express by nation name with the mcc form as administered by the ITU. For another example, each entry of area may be express by a shape as defined in the 3GPP TS 23.032 [6]. - The Allowed area list for NTN RAT access may be defied 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 Allowed area list for NTN RAT access may be defied per NTN RAT Type basis. - Not allowed area list for NTN RAT access: The Not allowed area list for NTN RAT access includes a list of area where the NTN RAT access is not allowed. For example, each entry of area may be express by nation name with the mcc form as administered by the ITU. For another example, each entry of area may be express by a shape as defined in the 3GPP TS 23.032 [6]. - The Not allowed area list for NTN RAT access may be defied 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 Not allowed area list for NTN RAT access may be defied per NTN RAT Type basis. - In one example the Prioritized NTN RAT Type list or The Prioritized NTN RAT Type list in connected state also includes TN (Terrestrial RAT).

[0143] Step 1-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 a Subscribed Multi orbit satellite access profile. The Subscribed Multi orbit satellite access profile may be included in Subscriber data information. The Subscribed Multi orbit satellite access profile may be the same as the Multi orbit satellite access profile that is received from the AF 201 at Step 1-1 or a compiled profile using the received Multi orbit satellite access profile in Step 1-1 or using multiple Multi orbit satellite access profiles in case where the UDM 75 receives multiple Multi orbit satellite access profiles from multiple AF 201s at Step 1-1.

[0144] In one example, the Subscribed Multi orbit satellite access profile for UE 3 may also be provided by the UDM 75 to the AMF 70 within the existing Nudm_SD_Get service operation or within the existing Nudm_SDM_Notify service operation.

[0145] The AMF 70 stores the received Subscribed Multi orbit satellite access profile in the MM context of the UE 3.

[0146] The AMF 70 may subscribe for the UDM service provided by the UDM 75 beforehand.

[0147] Step 1-3. Upon reception of the Nudm service notification message from the UDM 75, the AMF 70 sends a NAS message to the UE 3 via the RAN 501 including the Subscribed Multi orbit satellite access profile. The Subscribed Multi orbit satellite access 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.

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

[0012] Section 8 for details.

[0149] Upon the UE 3 receiving the NAS message including the Subscribed Multi orbit satellite access profile, the UE 3 stores the received Subscribed Multi orbit satellite access profile in a non-volatile memory in the UE 3 or USIM and uses it for choosing a cell for a satellite access.

[0150] In one example the Multi orbit satellite access profile is applicable at least in the selected PLMN or serving PLMN or registered PLMN where the UE 3 has received the Multi orbit satellite access profile or equivalent PLMN or EHPLMN of the serving PLMN or registered PLMN.

[0151] In one example, the Multi orbit satellite access profile is sent by the HPLMN and is applicable to all the PLMN to which the UE3 may register.

[0152] In one example, the HPLMN the Multi orbit satellite access profile and PLMN list where the Multi orbit satellite access profile is applicable.

[0153] In one example Multi Radio Dual Connectivity (MR-DC) access preference is sent independently from Multi-orbit satellite access preference profile.

[0154] In one example, the UE 3 stores the Prioritized NTN RAT Type list and Prioritized NTN RAT Type list per a UE state to the Elementary Files for satellite priority EFSATRATPRIORITY and EFSATRATPRIORITYUESTATE in the USIM respectively.

[0155] In one example, the UE 3 refers the EFSATRATPRIORITYUESTATE and may take the following procedure. 　　The detailed processes of this example are described below with reference to Fig. 7.

[0156] Step 1. The UE 3 is powered on. 　　The UE 3 reads the EFSATRATPRIORITYUESTATEfor the Registration sate. 　　Then, the UE 3 selects a suitable cell for the highest priority NTN RAT Type for the registration. (Ex. GEO RAT Type)

[0157] Step 2. The UE 3 performs a registration procedure with the selected cell.

[0158] Step 3. The UE goes to idle mode after successful registration procedure in Step 2 and selects a cell of highest priority NTN RAT Type (Ex. LEO RAT Type) for idle mode state and camps on it.

[0159] If the UE 3 cannot see any cells that belong to the selected NTN RAT Type, then the UE 3 reads the EFSATRATPRIORITYUESTATEfor the Idle mote sate to find next higher priority NTN RAT Type. The UE 3 stays in a cell with the best higher priority of an NTN RAT Type.

[0160] Step 4. If the UE 3 receives page on the cell. The UE 3 selects a cell of highest priority NTN RAT Type for connected mode state. (Ex. LEO RAT Type)

[0161] Then, the UE 3 performs the service request procedure on the selected cell.

[0162] If the UE 3 cannot see any cells that belong to the selected NTN RAT Type when the UE 3 is in Connected mode, then the UE 3 reads the EFSATRATPRIORITYUESTATEfor the connected mote sate to find next higher priority NTN RAT Type. Then the UE 3 may perform handover to a cell with the best higher priority of NTN RAT Type. 　　In one example, in the connected mode the UE 3 sends the information read from EFSATRATPRIORITYUESTATEto RAN 501 in an existing RRC message or in a new RRC message or to the AMF 70 in an existing NAS message or a new NAS message, the AMF 70 sends the information received from the UE 3 to the RAN 501 in an existing NGAP message or a new NGAP message. The RAN 501 takes the information into account to handover the UE 3 to an NTN cell belonging to the most preferred RAT if available. For example, the UE is on the NTN cell of GEO Satellite and the information indicates that the most preferred RAT is LEO, then RAN 501 executes a procedure defined in 3GPP TS 38.331

[0015] to handover the UE to the NTN cell belonging to the LEO satellite.

[0163] Example 2 　　In this Example, the PCF 73 provides the Subscribed Multi orbit satellite access profile to the UE 3 within the URSP Rule.

[0164] Step 2-1. The same as Step 1-1. Refer to Step 1-1. 　　In addition, the UDM 75 may provide the Subscribed Multi orbit satellite access profile relevant to UE 3. The UDM 75 sends the Subscribed Multi orbit satellite access profile to the UDR 7A in order to update a subscription profile in the UDR 7A.

[0165] Step 2-2. The UDM 75 sends the Nudm service notification message to the PCF 73 including the Subscribed Multi orbit satellite access profile for the UE 3.

[0166] The PCF 73 may subscribe for the UDM service provided by the UDM 75 beforehand.

[0167] In one example, the UDR 7A sends the Nudr service notification message to the PCF 73 including the Subscribed Multi orbit satellite access profile for the UE 3. The Subscribed Multi orbit satellite access profile for UE 3 may also be provided by the UDR 7A to the PCF 73 within the existing Nudr_DM_Query service operation or within the existing Nudr_DM_Notify service operation.

[0168] The PCF 73 subscribes to the UDR service provided by the UDR 7A beforehand.

[0169] 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 Subscribed Multi orbit satellite access profile.

[0170] 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 the URSP rule for the UE 3 includes only NTN RAT type data applicable to the Satellite Service provider A.

[0171] Step 2-3. The PCF 73 sends the NAS message, via the AMF 70, including the URSP rule that includes the Subscribed Multi orbit satellite access profile.

[0172] The NAS message may be the Manage UE policy command message, DL NAS transport message, UE Configuration update command message, other existing NAS messages or a new NAS message.

[0173] Upon the UE 3 receiving the NAS message including the Subscribed Multi orbit satellite access profile, the UE 3 stores the Subscribed Multi orbit satellite access profile in a non-volatile memory in the UE 3 or USIM and the UE 3 uses the Subscribed Multi orbit satellite access profile for discovering a satellite based on the Subscribed Multi orbit satellite access profile. The UE 3 sends the acknowledgement or response NAS message after the NAS message including the Subscribed Multi orbit satellite access profile. For example, if the UE 3 receives Registration accept message containing the Subscribed Multi orbit satellite access profile, then the UE 3 sends Registration complete message to the AMF 70 letting the AMF 70 know that the UE 3 has received the NAS message carrying the Subscribed Multi orbit satellite access profile.

[0174] In one example, the URSP may structure as illustrated in Fig. 8.

[0175] In Fig. 8, The Subscribed Multi orbit satellite access profile may be listed under the Route Selection Descriptor in the URSP Rule for the UE 3.

[0176] In one example, NTN RAT Type in the Prioritized NTN RAT Type list is listed in order of decreasing priority, with the first NTN RAT Type being the highest priority. It is also acceptable if the priority is specified in some other way.

[0177] Example 3 　　In this Example, the AF 201 provides satellite information to the UE 3 based on the UE 3 location. 　　In one example, the AF 201 is an application server that may be managed by a Satellite Service provider.

[0178] Step 3. The AF 201 provides the Multi orbit satellite access profile over the application layer to the UE 3.

[0179] In one example, if the AF 201 obtains an exact geographical location of the UE 3 over the application layer, the AF 201 provides a Multi orbit satellite access profile that are only relevant to the UE 3 location. In one example, if the AF 201 obtains a geographical location of the UE 3 over the application layer, the AF 201 provides a Multi orbit satellite access profile that are only relevant to the UE 3 location.

[0180] Upon the UE 3 receiving the Multi orbit satellite access profile, the UE 3 stores the Multi orbit satellite access profile in a non-volatile memory in the UE 3 or in the USIM and uses the Multi orbit satellite access profile for discovering a satellite.

[0181] In one example, the EFSATRATPRIORITYUESTATE is storedin is provisioned in the ME memory and updated using Open Mobile Alliance Device Management (OMA DM) as defined in 3GPP TS 24.368

[0017] .

[0182] Example 4 　　In Step 4, the UDM 75 or the SoR AF 201 sends multi-orbit satellite access profile information using the Steering of roaming over the control plane in a PLMN as defined in Annex C of 3GPP TS 23.122

[0018] . 　　In one example, following are the changes, with the Gray-coloured highlighted, required in the C.2 Stage-2 flow for steering of UE in VPLMN during registration to send the multi-orbit satellite access profile.

[0183] For example, although the following Step 3c) is described as "3c)　　The SOR-AF to the HPLMN UDM: Nsoraf_SoR_Get response (the list of preferred PLMN / access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet, or neither of them);" it is possible to make changes like "3c)　　The SOR-AF to the HPLMN UDM: Nsoraf_SoR_Get response (the list of preferred PLMN / access technology combinations, the SOR-CMCI, or multi-orbit satellite access profile if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet, or neither of them);".

[0184] For example, although the following Step 3c) is described as "3c)….If the SOR-AF includes the list of preferred PLMN / access technology combinations, and the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store SOR-CMCI in ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor "Store the SOR-CMCI in ME" indicator.", it is possible to make changes like "3c)…If the SOR-AF includes the list of preferred PLMN / access technology combinations or multi-orbit satellite access profile, and the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store SOR-CMCI in ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor "Store the SOR-CMCI in ME" indicator."

[0185] For example, the following step 3c) is described as follows, but it is possible to modify it adding a sentence like "The secured packet may include multi-orbit satellite access profile".

[0186] Each step can be executed based on these modifications.

[0187] == Copy from the Annex C of 3GPP TS 23.122

[0018] and updates start. == 3b)　　The HPLMN UDM to the SOR-AF: Nsoraf_SoR_Get request (VPLMN ID, SUPI of the UE, access type (see 3GPP TS 29.571)). The VPLMN ID and the access type parameters, indicating where the UE is registering, are stored in the HPLMN UDM; NOTE 5:　　Information about UE supporting SOR-SENSE can be available directly in SOR-AF (or in OAM which configures the secure packet in UDM / UDR). 3c)　　The SOR-AF to the HPLMN UDM: Nsoraf_SoR_Get response (the list of preferred PLMN / access technology combinations, the SOR-CMCI, or multi-orbit satellite access profile if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet, or neither of them); 　　Based on the information received in step 3b and any operator specific criteria, the SOR-AF may either: -　　include the list of preferred PLMN / access technology combinations, the SOR-CMCI, if any, and optionally the "Store SOR-CMCI in ME" indicator, if any; -　　provide the secured packet in the Nsoraf_SoR_Get response; or -　　provide the Nsoraf_SoR_Get response with neither of the information above. 　　If the SOR-AF includes the list of preferred PLMN / access technology combinations or multi-orbit satellite access profile, and the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store SOR-CMCI in ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor "Store the SOR-CMCI in ME" indicator. NOTE 6:　　In this version of the specification, when the access type where the UE is registering indicates 3GPP access, then the UE is registering over the NG-RAN access technology. NOTE 7:　　Based on operator deployment and policy, if the UDM receives the list of preferred PLMN / access technology combinations, and the SOR-CMCI, if any, in the Nsoraf_SoR_Get response from the SOR-AF, and the UDM supports communication with SP-AF, it can send this list, and the SOR-CMCI, if any, to SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544

[0071] . NOTE 8:　　The SOR-AF can include a different list of preferred PLMN / access technology combinations, different SOR-CMCI, if any, and different "Store SOR-CMCI in ME" indicator, if any, or a different secured packet for each Nsoraf_SoR_Get request even if the same VPLMN ID, the SUPI of the UE, and the access type are provided to the SOR-AF. NOTE 9:　　The SOR-AF can subscribe to the HPLMN UDM to be notified about the changes of the roaming status of the UE identified by SUPI. NOTE 10:　　The SOR-AF can determine that the ME supports the SOR-CMCI if the Nsoraf_SoR_Info service operation has returned the "ME support of SOR-CMCI" indicator. NOTE 11:　　Secured packet provided by the SOR-AF can include SOR-CMCI only if the SOR-AF has determined that the ME supports the SOR-CMCI and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then SOR-CMCI, if any, cannot be included in the secured packet. NOTE 12:　　Secured packets do not include the "Store SOR-CMCI in ME" indicator. The secured packet may include multi-orbit satellite access profile. 3d)　　The HPLMN UDM forms the steering of roaming information as specified in 3GPP TS 33.501

[0066] from: -　　the list of preferred PLMN / access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet obtained in step 3a; or 　　the list of preferred PLMN / access technology combinations and the SOR-CMCI, if any, and "Store the SOR-CMCI in ME" indicator, if any, or the secured packet, obtained in step 3c. 　　If: -　　neither the list of preferred PLMN / access technology combinations nor the secured packet was obtained in steps 3a or 3c; or -　　the SOR-AF has not sent to the HPLMN UDM an Nsoraf_SoR_Get response (step 3c) within an operator defined time after the HPLMN UDM sending to the SOR-AF an Nsoraf_SoR_Get request (step 3b); NOTE 13:　　Stage 3 to define the timer needed for the SOR-AF to respond to the HPLMN UDM. The max time needs to be defined considering that this procedure is part of the registration procedure. 　　and the UE is performing initial registration in a VPLMN and the user subscription information indicates to send the steering of roaming information due to initial registration in a VPLMN, then the HPLMN UDM forms the steering of roaming information as specified in 3GPP TS 33.501

[0066] from the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN / access technology combinations is provided'; 　　If the "Store SOR-CMCI in ME" indicator was not obtained in step 3a or 3c and the "ME support of SOR-CMCI" indicator is stored for the UE in the HPLMN UDM, the HPLMN UDM forms the steering of roaming information with the "Store SOR-CMCI in ME" indicator set to "Do not store SOR-CMCI in ME"; 　　== Copy from the Annex C of 3GPP TS 23.122

[0018] and updates end. ==

[0188] <Third scenario in the First example of the First Aspect> 　　The Third scenario in the First example of the First Aspect includes a mechanism for a registration procedure with multi orbit satellite.

[0189] Fig. 9 illustrates an example of a call flow for the Registration procedure accessing with multi orbit satellites.

[0190] The detailed processes of this scenario are described below with reference to Fig. 9.

[0191] Step 0. The UDM 75 holds the subscriber data related to Multi orbit satellite access. Refer to Step 1-2 in Fig. 6 for details of subscriber data.

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

[0193] Step 2. The UE 3 sends the RRC Setup request message to the RAN 5.

[0194] Step 3. The RAN 5 sends the RRC Setup message to the UE 3 including the satellite related information. The satellite related information may be the same as one broadcasted in Steps 1 and 2 in Fig. 5.

[0195] Step 4. The UE 3 sends the RRC Setup Complete message to the RAN 5 including Multi orbit satellite access support, Redirected page response support and 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, Multi orbit satellite access support, Redirected page response support, RAT type indication page support and Neighboring cell information.

[0196] 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. - Multi orbit satellite access support: The Multi orbit satellite access support indicates that the UE 3 supports one or multiple new mechanisms in the mobility management and session management that are disclosed by this disclosure. - Redirected page response support: The Redirected page response support indicates that the UE 3 supports a mechanism paged over one cell and responding to another cell is supported. - For example, the UE 3 paged by a cell on the GEO satellite and responding to a cell on the LEO satellite. - RAT Type indication in page support: The RAT Type indication in page support indicates that UE 3 supports to receive the page with a RAT Type. The RAT Type in Page is interpreted by the UE 3 as the RAT Type that the UE 3 uses for activating PDU session. - Neighbouring cell information: This information consists of information (CGI ID, RAT Type (e.g., TN or NTN, Satellite ID of the serving satellite) related to the neighbouring cells detected by the UE. In one example this information is same as or a part of the information broadcasted in SIB in Fig. 5.

[0197] Step 5. Upon reception of the RRC Setup Complete 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. The Registration Request message may include the UE ID, Muli orbit satellite access support information, Redirected page response support information, RAT type indication in page support information.

[0198] 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, Multi orbit satellite access support, RAT Type indication in page support, Neighbouring cell information and Redirected page response support. 　　The following bullets explain each parameter in detail. - SUPI: Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. - Multi orbit satellite access support: Refer to Step 4. - Redirected page response support: Refer to Step 4. - RAT Type indication in page support: Refer to Step 4. - Neighbouring cell information.

[0199] 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.

[0200] 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, Multi orbit satellite access support, RAT Type indication in page support and Redirected page response support. Refer to Step 6 and Step 4 for parameter details.

[0201] Step 9. 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 Subscribed Multi orbit satellite access profile, Redirected page response subscribed, and RAT Type indication in page subscribed. The value of the following parameters may depend on the neighbouring cell list and serving cell list. For example, if the neighbouring cell lists indicates there is GEO and LEO cells then UDM 75 includes in Multi orbit satellite access profile parameters related to GEO and LEO e.g., the idle mode priority list would be LEO > GEO.

[0202] The following bullets explain each parameter in detail. - Subscribed Multi orbit satellite access profile; Refer to the Step 1-2 in Fig. 6. - Redirected page response subscribed: The Redirected page response subscribed indicates that the UE 3 has a valid subscription to the Redirected page response function. - RAT Type indication in page subscribed: The RAT Type indication in page subscribed indicates that the UE 3 has a valid subscription to the RAT Type indication in page function.

[0203] Step 10. The AMF 70 sends the Npcf_policy_association Request message to the PCF 73 including at least one of the SUPI, Multi orbit satellite access support and Redirected page response support. Refer to Step 6 and step 4 for the parameter details.

[0204] Step 11. Upon reception of the Npcf_policy_association Request message from the AMF 70, the PCF 73 sends the Npcf_policy_association Response message to the AMF 70.

[0205] Step 12. Upon reception of the Npcf_policy_association Request message from the AMF 70, the PCF 73 generates the URSP rule with Subscribed Multi orbit satellite access profile. 　　For Subscribed Multi orbit satellite access profile, refer to Step 2-2 in Fig. 6 for parameter details. 　　Refer also Fig. 8 for the URSP rule structure as an example.

[0206] Step 13. The PCF 73 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 including SUPI and URSP rule. The URSP rule includes the Subscribed Multi orbit satellite access profile. The URSP rule may be embedded in the UE Policy container parameter. The PCF 73 may also apply rules to set the Multi orbit satellite as defined in step 9.

[0207] Step 14. Upon reception of the Namf_Communication_N1N2MessageTransfer message from the PCF 73, the AMF sends the UE Configuration Update message to the UE 3 including the URSP rule. The URSP rule includes the Subscribed Multi orbit satellite access profile. The URSP rule may be embedded in the UE Policy container parameter.

[0208] Upon reception of the UE Configuration Update message from the AMF 70, the UE 3 stores the received URSP rule in a non-volatile memory in the UE 3 or USIM.

[0209] Step 15. Upon reception of the Nudm_SDM_Get Response message from the UDM 75 in Step 9, the AMF 70 sends the Registration Accept message to the UE 3 including 5G-GUTI, TAI list, Subscribed Multi orbit satellite access profile, Redirected page response activated, RAT Type indication in page activated and TAI to stay.

[0210] 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 a registration area that the AMF 70 has assigned to the UE 3. For example, the TAI list is used by the AMF 70 for page the UE 3. - In one example, the TAIs in the TAI list is composed of cells that are located in the same NTN RAT type. - One another example, the TAIs in the TAI list is composed of cells that are located in multipe NTN RAT types. - Subscribed Multi orbit satellite access profile: Refer to Step 2-2 in Fig. 6. - Redirected page response activated: The Redirected page response activated indicates that the Redirected page response function is activated and ready to use. - I.e. Redirected page response function is supported by RAN 5 and core network nodes in the core network 7 and the UE 3 has valid subscription to use Redirected page response function. I.e. AMF 70 has received the Redirected page response subscribed from the UDM 75 - RAT Type indication in page activated: The RAT Type indication in page activated indicates that the RAT Type indication in page function is activated and ready to use. - I.e., RAT Type indication in page function is supported by RAN 5 and core network nodes in the core network 7 and the UE 3 has valid subscription to use RAT Type indication in page function. I.e. AMF 70 has received the RAT Type indication in page from the UDM 75. - TAI to stay: The TAI to stay indicates that one TAI or list of TAIs within the TAI list that the AMF 70 requests the UE 3 to stay when the UE 3 is in a CM-IDLE sate and a CM-CONNECTED sate with RRC-INACTIVE. - In one example, in case where the TAI list composes of TAIs that span to multi orbit satellite, the AMF may populate only TAIs that are located in the GEO satellite. With this configuration, the AMF 70 may page the UE 3 only targeting the TAIs that are located in the GEO satellite.

[0211] Upon reception of the Registration accept message from the AMF 70, the UE 3 stores the received information in a non-volatile memory in the UE 3 or USIM.

[0212] Step 16. The UE 3 sends the Registration Complete message to the AMF 70.

[0213] Step 17. After successful registration procedure, the UE 3 uses the received Subscribed Multi orbit satellite access profile for selecting a satellite.

[0214] <First Variant of the Third scenario in the First example of the First Aspect> 　　Steps 12 to 14 may take place after the successful registration procedure.

[0215] <Second Variant of the Third scenario in the First example of the First Aspect> 　　In one example, the Subscribed Multi orbit satellite access profile in the URSP rule that is received in the UE Configuration Update message from the AMF 70 in Step 14 conflicts with the Subscribed Multi orbit satellite access profile that is received in the Registration Accept message from the AMF 70 in Step 15, the UE 3 only refers to the Subscribed Multi orbit satellite access profile in the URSP rule that is received in the UE Configuration Update message from the AMF 70 in Step 14.

[0216] One another example, the Subscribed Multi orbit satellite access profile in the URSP rule that is received in the UE Configuration Update message from the AMF 70 in Step 14 conflicts with the Subscribed Multi orbit satellite access profile that is received in the Registration Accept message from the AMF 70 in Step 15, the UE 3 only refers to the Subscribed Multi orbit satellite access profile that is received in the Registration Accept message from the AMF 70 in Step 15.

[0217] <Third Variant of the Third scenario in the First example of the First Aspect> 　　If the UE 3 receives the TAI to stay in the Registration Accept message in Step 15 and this information conflicts with the Prioritized NTN RAT Type list or / and Prioritized NTN RAT Type list per a UE state in the Subscribed Multi orbit satellite access profile, a RAT Type in the TAI to say takes precedent over the priority related information in the Subscribed Multi orbit satellite access profile.

[0218] <Fourth Variant of the Third scenario in the First example of the First Aspect> 　　In the Step 5, if the RAT Type being used by the UE 3 is contradict with the Prioritized NTN RAT Type list or / and Prioritized NTN RAT Type list per a UE state for Idle mode state in the MM context for the UE 3 in the AMF 70, the AMF 70 may send the Registration Reject message to the UE 3 including Cause, Reregistration required and Target RAT Types.

[0219] The following bullets explain each parameter in detail. - Cause: The Cause may indicate that the Registration request is rejected due to use of inappropriate RAT Type. When the UE 3 receives this Cause, the UE 3 performs the cell re-selection procedure to move to a cell with an appropriate RAT Type and initiate the Registration procedure. - Reregistration required: The Reregistration required indicates the UE 3 that the UE 3 needs to performs the Registration procedure. - In one example, the AMF 70 includes this information in case that there is no cell within the Registration Area (RA) that is appropriate to use for the UE 3. - Target RAT Types: The Target RAT Types indicates candidate RAT Types that the UE 3 may stay in the idle mode state.

[0220] <Fifth Variant of the Third scenario in the First example of the First Aspect> 　　In any time after the UE 3 has registered to the AMF 70, the AMF sends the De-registration request message to the UE 3 including Cause, Reregistration required and Target RAT Types.

[0221] The following bullets explain each parameter in detail. - Cause: The Cause may indicate that the UE 3 stays in a cell with an unappropriated RAT Type. When the UE 3 receives this Cause, the UE 3 performs the cell re-selection procedure to move to a cell with an appropriate RAT Type and initiate the Registration procedure. - Reregistration required: The Reregistration required indicates the UE 3 that the UE 3 needs to perform the Registration procedure. - In one example, the AMF 70 includes this information in case that there is no cell within the Registration Area (RA) that is appropriate to use for the UE 3. - Target RAT Types: The Target RAT Types indicates candidate RAT Types that the UE 3 may stay in the idle mode state.

[0222] <Fourth scenario in the First example of the First Aspect> 　　The Fourth scenario in the First example of the First Aspect includes a mechanism for a Mobile Originated (MO) Session Activation accessing procedure with multi orbit satellite.

[0223] Fig. 10 and Fig. 11 illustrate an example of a call flow for the Mobile Originated (MO) Session Activation procedure accessing with multi orbit satellites.

[0224] Note: Due to space limitation, the Mobile Originated (MO) Session Activation accessing procedure with multi orbit satellite is illustrated in two figures, Fig. 10 and Fig. 11. I.e. Step 9 in Fig. 11 is a next step to take place after Step 8 in Fig. 10.

[0225] The detailed processes of this scenario are described below with reference to both Fig. 10 and Fig. 11.

[0226] Step 0-1. The UE 3 has registered with the AMF 70 with Subscribed Multi orbit satellite access profile set to as follows: - Prioritized NTN RAT Type list per a UE state for Idle mode state: GEO>LEO. For example, GEO takes priority over LEO. - Prioritized NTN RAT Type list per a UE state for connected mode state: LEO>GEO. For example, LEO takes priority over GEO. - The priority can be set arbitrarily, not limited to the above examples.

[0227] Step 0-2. Steps 1 to 3 in Fig. 5 take place. 　　Based on the Prioritized NTN RAT Type list per a UE state for Idle mode state in a non-volatile memory in the UE 3, the UE 3 stays in a cell with the RAN 501 in the GEO satellite.

[0228] Step 1. The UE 3 buffers an uplink data and decides to establish PDU Session. For example, an Application in the UE 3 requests to send a data to an NAS layer of the UE 3.

[0229] Step 2. The UE 3 performs a Cell reselection to a cell with LEO (RAN 502) based on the Prioritized NTN RAT Type list per a UE state for connected mode state in a non-volatile memory in the UE 3. For example, the UE 3 performs a Cell reselection to a cell with LEO in the RAN 502 or relate to the RAN 502 based on the Prioritized NTN RAT Type list per a UE state for connected mode state in a non-volatile memory in the UE 3. 　　For example, the UE 3 obtains and stores the Prioritized NTN RAT Type list per a UE state for connected mode state in a non-volatile memory in the UE 3 based on the Step 1-3 or Step 2-3 in Fig. 6.

[0230] Step 3. The UE 3 sends the RRC Setup request message to the RAN 502.

[0231] Step 4. The RAN 502 sends the RRC Setup message to the UE 3 including the satellite related information. The satellite related information may be the same as one broadcasted in Steps 1 and 2 in Fig. 5.

[0232] Step 5. The UE 3 sends the RRC Setup Complete message, to the RAN 502 including Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support and Dedicated NAS. The Dedicated NAS includes the UL NAS Transport message. The UL NAS Transport message includes PDU Session ID, DNN, S-NSSAI, Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support and NAS. Further, the NAS includes the PDU Session Establishment Request message. The PDU Session Establishment Request message includes at least one of User ID, Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support.

[0233] The following bullets explain each parameter in detail. - User ID: Refer to Step 4 in Fig. 9. - 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. - Multi orbit satellite access support: Refer to Step 4 in Fig. 9. - Redirected page response support: Refer to Step 4 in Fig. 9. - RAT Type indication in page support: Refer to Step 4 in Fig. 9.

[0234] Step 6. The RAN 502 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 5.

[0235] Step 7. 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 Multi orbit satellite access support, Redirected page response support and RAT Type indication in page support, the AMF 70 selects an SMF that supports the multi orbit satellite access mechanisms that are disclosed by this disclosure. 　　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, Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support and PDU Session Establishment Request message.

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

[0237] Step 9. The SMF 71 sends an Nudm_SDM_Get message to the UDM 75 including at least one of the User ID, DNN, S-NSSAI, Multi orbit satellite access support, Redirected page response support and RAT Type indication in page support.

[0238] Step 10. 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 includes the following parameters. - Subscribed Multi orbit satellite access profile: Refer to Step 9 in Fig. 9. - In one example, the Subscribed Multi orbit satellite access profile may be dedicated data for the DNN, S-NSSAI or DNN / S-NSSAI combination. - Redirected page response subscribed: Refer to Step 9 in Fig. 9. - In one example, the Redirected page response subscribed may be dedicated data for the DNN, S-NSSAI or DNN / S-NSSAI combination. - RAT Type indication in page subscribed: Refer to Step 9 in Fig. 9. - In one example, the RAT Type indication in page subscribed may be dedicated data for the DNN, S-NSSAI or DNN / S-NSSAI combination.

[0239] Step 11. 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, Multi orbit satellite access support, Redirected page response support and RAT Type indication in page support.

[0240] Step 12. 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.

[0241] Upon reception of the Npcf_SMPolicyControl_Create Response message from the PCF 73, the SMF 71 examines the received PCC rule.

[0242] Step 13. The SMF 71 sends the N4 Session Establishment request message to the UPF 72 to assign user plane resources in the UPF 72 that is used for the PDU Session being created.

[0243] Step 14. After successful user plane resource assignment in the UPF 72, the UPF 72 sends the N4 Session Establishment response message to the SMF 71.

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

[0245] The N2 SM information includes PDU Session ID, Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated and TAI to stay.

[0246] The N1 SM container includes PDU Session Establishment Accept message that includes Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated and TAI to stay.

[0247] The following bullets explain each parameter in detail. - PDU Session ID: Refer to Step 5. - Authorized QoS rules: 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.501

[0012] . - Redirected page response activated: Refer to Step 15 in Fig. 9. - In one example, the Redirected page response activated may be dedicated data for the DNN, S-NSSAI or DNN / S-NSSAI combination. - RAT Type indication in page activated: Refer to Step 15 in Fig. 9. - In one example, the RAT Type indication in page activated may be dedicated data for the DNN, S-NSSAI or DNN / S-NSSAI combination. - TAI to stay: Refer to Step 15 in Fig. 9. - In one example, the TAI to stay may be dedicated data for the DNN, S-NSSAI or DNN / S-NSSAI combination.

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

[0249] The N2 SM information includes Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated, TAI to stay and N1 SM container. Further N1 SM container includes DL NAS Transport message.

[0250] The DL NAS Transport message includes NAS.

[0251] The NAS includes PDU Session Establishment Accept message including Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated and TAI to stay.

[0252] For example, upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends N2 PDU Session request message to the RAN 502 including N2 SM information and NAS message. The N2 SM information includes Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated, TAI to stay. The NAS message includes PDU session ID, N1 SM container. The N1 SM containers include DL NAS Transport message. The DL NAS Transport message include NAS. The NAS includes PDU Session Establishment Accept. The PDU Session Establishment Accept includes Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated and TAI to stay.

[0253] Upon reception of the N2 PDU Session request message from the AMF 70, the RAN 502 stores the received data.

[0254] Step 17. The RAN 502 sends the RRC signalling message including DL NAS Transport message. 　　The DL NAS Transport message includes NAS. The NAS includes PDU Session Establishment Accept message. The PDU Session Establishment Accept message includes Authorized QoS rules, Redirected page response activated, RAT Type indication in page activated and TAI to stay.

[0255] Step 18. After successful PDU Session establishment procedure, User plane is established between the UE 3 and the UPF 71 via the RAN 502 and the UE 3 communicates with the AF 201. For example, the PDU Session establishment procedure may be executed through above steps from Step 3 to Step 17. The User plane is established between the UE 3 and the UPF 72 via the RAN 502 and the UE 3 communicates with the AF 201.

[0256] <First Variant of the Fourth scenario in the First example of the First Aspect> 　　The call flow for the Mobile Originated (MO) Session Activation procedure accessing with multi orbit satellites illustrated in both Fig. 10 and Fig. 11 are fairly referred to the UE triggered Service request procedure with the following replacements: - In Steps 5, 6 and 7, the PDU Sessin Establishment Request messages are replaced with the Service Request messages. - In Steps 15, 16 and 17, the PDU Sessin Establishment Accept messages are replaced with the Service Accept messages. - In Step11, the Npcf_SMPolicyControl_Create message is replaced with the Npcf_SMPolicyControl_Modify message. - In Step12, the Npcf_SMPolicyControl_Create response message is replaced with the Npcf_SMPolicyControl_Modify response message.

[0257] <Second Variant of the Fourth scenario in the First example of the First Aspect> 　　In Step 7, if the RAT Type being used by the UE 3 may contradict with the Prioritized NTN RAT Type list or / and Prioritized NTN RAT Type list that corresponds to the DNN, S-NSSAI or DNN / S-NSSAI combination or / and Prioritized NTN RAT Type list per a UE state for Connected mode state in the MM context in the AMF 70, the AMF 70 may send the DL NAS message to the UE 3 including Cause, Reregistration required and Target RAT Types.

[0258] The following bullets explain each parameter in detail. - Cause: The Cause may indicate that the PDU Session establishment request is rejected due to use of inappropriate RAT Type. When the UE 3 receives this Cause, the UE 3 performs the cell re-selection procedure to move to a cell with an appropriate RAT Type and initiate the PDU Session Establishment procedure. - Reregistration required: The Reregistration required indicates the UE 3 that the UE 3 needs to performs the Registration procedure if the UE 3 wishes to establish the PDU Session. - In one example, the AMF 70 includes this information in case that there is no cell within the Registration Area (RA) that is appropriate to be used by the PDU Session. - Target RAT Types: The Target RAT Types indicates candidate RAT Types that the UE 3 may use for the PDU Session.

[0259] <Third Variant of the Fourth scenario in the First example of the First Aspect> 　　In one example, at step 1 of Fig. 10 the UE 3 may analyze the buffered data to be exchanged with the network. If the buffered data to be exchanged with the network is a small data, e.g. the RRC establishment cause to be used is to indicate a small data transmission via control plane or via EDT (Early Data Transmission) configuration where no user plane establishment is needed, the UE 3 instead triggering a cell re-selection to a cell from LEO satellite, the UE 3 may stay on the same cell from the GEO satellite and the UE 3 may initiate RRC connection with RAN 501 from the GEO satellite. Then the UE would continue with the small data exchange with the network via control plane signaling or EDT with no user plane establishment as per TS23.502 and at the end of the data exchange the UE would fall back in idle mode on the same cell of the RAN 501 of the GEO satellite.

[0260] <Fourth Variant of the Fourth scenario in the First example of the First Aspect> 　　In another example, at step 1 of Fig. 10 the UE 3 may analyze the buffered data to be exchanged with the network. If the buffered MO data to be exchanged with the network is delay tolerant, one of the options for data exchange with the network, which may be UE configured or user preferred, could be the GEO option, i.e., the data to be exchanged via GEO satellite. For example, one reason for user preference for the data to be exchanged via the GEO satellite could be a cheaper data charging rate via GEO satellite. In another example, the reason for the UE configuration the data to be exchanged via GEO satellite could be the UE's URSP configuration by the network. The UE URSP rules may contain satellite preference rules which may define which applications in the UE what satellites, GEO or LEO, to use for data exchange. In this case if the user preference or the URSP rules require the UE to use LEO satellite for the data exchange, the UE 3 may stay on the same cell from the GEO satellite and the UE 3 may initiate RRC connection with RAN 501 from the GEO satellite. Then the UE would continue with the PDU Session establishment as per Fig. 10 and Fig. 11 with the only difference that the RRC connection and the PDU Session are established with / via RAN 501 and the data is exchanged over the GEO satellite.

[0261] <Fifth Variant of the Fourth scenario in the First example of the First Aspect> 　　In another example, at step 1 of Fig. 10 the UE 3, after a decision to exchange the buffered data via the LEO satellite, based on the user preference or URSP configuration or based on the data size and type, the UE 3 may still not re-select to a cell from LEO satellite as in step 2 of Fig. 10. Instead, the UE 3 may continue with the RRC connection establishment with the RAN 501 of GEO satellite and the PDU Session establishment via the RAN 501 of the GEO satellite as per steps 3 to 17 of Fig. 10 and Fig. 11. Then after the PDU session via the GEO satellite is established at step 17 of Fig. 11, the AMF 70 may decide to trigger Handover from GEO to LEO satellite, e.g. from RAN 501 to RAN 502. The decision in the AMF 70 to trigger such handover from GEO to LEO satellite may be for example: - The size of the data to be exchange between the UE 3 and the network - If the size of the data to be exchange between the UE 3 and the network is large, the AMF 70 may decide for the data to be exchanged via LEO satellite so that the UE battery is saved. This is one reason for the AMF 70 to trigger Handover from GEO to LEO satellite. - The type of the data to be exchange between the UE 3 and the network - If the type of the data to be exchange between the UE 3 and the network is of delay sensitive type, the AMF 70 may decide for the data to be exchanged via LEO satellite so that the quality of the service is maintained. This is another reason for the AMF 70 to trigger Handover from GEO to LEO satellite. - UE service subscription details - based on the UE service subscription which the AMF 70 retrieves from the UDM 75 or UDR 7A at the UE 3 registration with the network and the AMF 70 stores this information in the UE 3 context within the AMF 70, the AMF 70 may decide for the data to be exchanged via LEO satellite as per the UE 3 service subscription. This is another reason for the AMF 70 to trigger Handover from GEO to LEO satellite.

[0262] <Sixth Variant of the Fourth scenario in the First example of the First Aspect> 　　In one example when the UE 3 and network support Multi-Satellite MR-DC, the UE 3 sends Multi-Satellite MR-DC capability to the AMF 70 during the registration procedure in an existing NAS message or in a new NAS message. The AMF 70 sends the Multi-Satellite MR-DC capability to the UDM 75 during the registration procedure in an existing or in a new message between the AMF 70 and the UDM 75. The UDM takes the Multi-Satellite MR-DC capability into account to send the Multi-Satellite MR DC access preference to the AMF 70 in an existing or in a new message between the UDM 75 and AMF 70. The AMF 70 sends the Multi-Satellite MR DC access preference to the UE 3 in an existing NAS message or in the new NAS message. The AMF 70 also sends Multi-Satellite MR DC access preference to RAN 501 in an existing NGAP message or a new NGAP message. RAN 501 will take Multi-Satellite MR DC access preference into account while selecting the secondary node for the MR Dual connectivity. For example, according to the Multi-Satellite MR DC access preference if the primary cell preference is GEO stationary cell and the secondary node preference is LEO satellite then RAN 501 selects LEO satellite cell as the secondary cell. The RAN 501 also configures only satellite cell as primary cells to the UE 3 to report in the measurement report. The RAN 501 always performs Handover to the GEO stationary satellite.

[0263] In one example, the SMF 71 can get or fetch Multi-Satellite MR DC access preference information during the PDU session establishment procedure from the UDM 75 using the existing message or a new message between the SMF 71 and the UDM 75. The SMF 71 sends Multi-Satellite MR DC access preference to the AMF 70 in step 15 and the AMF 70 sends Multi-Satellite MR DC access preference to the RAN 501. The RAN 501 handling of Multi-Satellite MR DC access preference is defined as above.

[0264] <Seventh Variant of the Fourth scenario in the First example of the First Aspect> 　　In one example, step 1 and step 2 of Fig. 10 may be exchanged. For example, the UE AS layer may perform cell reselection to a cell associated with the prioritized RAT type (e.g., NTN access over LEO) upon receiving the Satellite related information at step 0-2. Then, upon receiving an uplink data from the UE NAS layer, the UE AS layer initiates the RRC connection establishment (e.g., RRC setup procedure).

[0265] The Fifth scenario in the First example of the First Aspect includes a mechanism for a Mobile Terminated (MT) Session Activation procedure with multi orbit satellite.

[0266] Fig. 12 illustrates an example of a call flow for the Mobile Terminated (MT) Session Activation procedure accessing via multi orbit satellites.

[0267] The detailed processes of this scenario are described below with reference to Fig. 12.

[0268] Step 0-1. The UE 3 has registered with AMF 70 with Subscribed Multi orbit satellite access profile set to as follows: - Prioritized NTN RAT Type list per a UE state for Idle mode state: GEO>LEO. For example, GEO takes priority over LEO. - Prioritized NTN RAT Type list per a UE state for connected mode state: LEO>GEO. For example, LEO takes priority over GEO. - The priority can be set arbitrarily, not limited to the above examples.

[0269] Step 0-2. The UE 3 establishes a PDU Session and becomes idle mode state. For example, due to user data inactivity.

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

[0271] Based on the Prioritized NTN RAT Type list per a UE state for Idle mode state in a non-volatile memory in the UE 3, the UE 3 stays in a cell with RAN 501 in the GEO satellite.

[0272] Step 1. Downlink data arrives to the UPF 72.

[0273] Step 2. The UPF 72 sends the Data Notification to the SMF 71.

[0274] Step 3. Upon reception of the Data Notification message from the UPF 72, the SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 including SUPI and PDU Session ID. The SMF 71 may download the UE subscription parameters from the UDM 75 using existing service operation between the SMF 71 and the UDM 75. The SMF 71 based on the subscription parameters may send the target RAT for the UE to the AMF 70. For example, if the MT data is related to S-NSSAI corresponding to a machine type communication including an mIoT (massive Internet of Things) and mIoT services are provided by the LEO satellite then SMF can send the target RAT as LEO. In another example, if the MT data is related to S-NSSAI corresponding to an eMBB (enhanced Mobile Broadband) services the target RAT can be GEO. The AMF 70 will send this target to the RAN 501 as defined in the step 4 below.

[0275] Step 4, Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends the Paging message to RAN 501 including UE Paging Identity and Target RAT Types set to LEO.

[0276] The following bullets explain each parameter in detail. - UE Paging Identity: The UE Paging Identity identifies the UE 3 in NGAP interface. It may be a 5G-S-TMSI. - Target RAT Types: The Target RAT Types indicates that the AMF 70 requests the UE 3 to reply page using a cell belonging to a RAT Type indicated in this parameter. The Target RAT Types has one or multiple RAT Types. In case multiple RAT Types are included, the UE 3 can choose one RAT Type out of received multiple RAT Types.

[0277] In one example, the AMF 70 sends the Paging message only to RAN 5s within the RA (Registration Area) that has a cell with the highest RAT Type in the Prioritized NTN RAT Type list or / and the highest RAT Type in the Prioritized NTN RAT Type list per a UE state for Idle mode state in the MM context in the AMF 70. 　　If there is no page response from the UE 3, the AMF 70 adds more RAN 5s within the RA that has a cell with the highest and following higher RAT Types in the Prioritized NTN RAT Type list or / and the highest RAT Type and following higher RAT Types in the Prioritized NTN RAT Type list per a UE state for Idle mode state in the MM context in the AMF 70.

[0278] If there is no page response from the UE 3, the AMF 70, the AMF sends all RAN 5 that covers the RA.

[0279] This paging mechanism may be called as a progressive paging based on the prioritized RAT Type. With this mechanism, the paging process becomes less impact to the 5GS since significant of page traffic could be reduced.

[0280] Step 5. The RAN 501 performs Page. Page signal includes UE Identity and Target RAT Types.

[0281] The following bullets explain each parameter in detail. - UE Identity: A UE Identity that the UE 3 scans whether there is a page for the UE 3. - Target RAT Types: Refer to Step 4.

[0282] Step 6. Once the UE 3 receives the page for the UE 3, the UE 3 may perform the Cell reselection to a cell with LEO based on the received Target RAT Types in Step 5.

[0283] Step 7. Steps 3 to 18 in Fig. 10 and 11 take place.

[0284] <First Variant of the Fifth scenario in the First example of the First Aspect> 　　If the Target RAT Types received in Step 5 conflicts with a prioritized RAT Type in the Prioritized NTN RAT Type list or / and a Prioritized NTN RAT Type list per a UE state for Idle mode state, the Target RAT Types received in Step 5 takes precedence over the priority related information in the Subscribed Multi orbit satellite access profile.

[0285] <Second Variant of the Fifth scenario in the First example of the First Aspect> 　　In one example, at step 3 of Fig. 12 the AMF 70 may analyze the MT data and the UE 3 service subscription details retrieved from the UDM 75 at registration with the network: - If the UE 3 is paged for small data which can be exchanged via control plane signaling or EDT, the AMF 70 pages the UE 3 over GEO satellite and the AMF 70 does not include the 'Target RAT Type = LEO' parameter in the Paging message to RAN 501. In this case the UE 3 is paged over RAN 501 of the GEO satellite as per the Paging procedure in 3GPP TS 38.413

[0013] . The UE 3 responds to the paging via RAN 501 of the GEO satellite and the MT data is exchange between the UE 3 and the network over GEO satellite. - If the UE 3 is paged for delay tolerant data, the AMF 70 may check the UE 3 service subscription details which were retrieved from the UDM 75 and stored in the UE 3 context within the AMF 70 during the UE 3 registration with the network for any instruction on how to exchange delay tolerant data. If the UE 3 subscription requires the delay tolerant data to be exchanged via GEO satellite, the AMF 70 does not include the 'Target RAT Type =LEO' parameter in the Paging message to RAN 501. In this case the UE is paged over RAN 501 of the GEO satellite as per the Paging procedure in 3GPP TS 38.413

[0013] . The UE 3 responds to the paging via RAN 501 of the GEO satellite and the MT data is exchange between the UE 3 and the network over the GEO satellite. - If the UE 3 has registered via both satellite accesses, via GEO and via LEO, the AMF 70 may page the UE 3 via the LEO satellite. In this case the AMF 70 sends the Paging message in step 4 of Fig. 12 to RAN 502 instead to RAN 501 and the AMF 70 does not include the 'Target RAT Type = LEO' parameter. In this case the UE is paged over RAN 502 of the LEO satellite as per the Paging procedure in 3GPP TS 38.413

[0013] . The UE 3 responds to the paging via RAN 502 of the LEO satellite and the MT data is exchange between the UE 3 and the network over the LEO satellite.

[0286] <Sixth scenario in the First example of the First Aspect> 　　The Sixth scenario in the First example of the First Aspect includes a mechanism for a Session Release procedure with multi orbit satellite.

[0287] Fig. 13 illustrates an example of a call flow for the Session Release procedure accessing with multi orbit satellites.

[0288] The detailed processes of this scenario are described below with reference to Fig. 13.

[0289] Step 0-1. The UE 3 has registered with AMF 70 with Subscribed Multi orbit satellite access profile set to as follows: - Prioritized NTN RAT Type list per a UE state for Idle mode state: GEO>LEO. For example, GEO takes priority over LEO. - Prioritized NTN RAT Type list per a UE state for connected mode state: LEO>GEO. For example, LEO takes priority over GEO. - The priority can be set arbitrarily, not limited to the above examples.

[0290] Step 0-2. The UE 3 establishes a PDU Session with the RAN 502 on the LEO satellite based on the prioritized RAT Type in the Prioritized NTN RAT Type list or / and the Prioritized NTN RAT Type list per a UE state for Connected mode state.

[0291] Step 1. The PDU Session Release takes place according to the session 4.3.4.2 in 3GPP TS 23.502 [4].

[0292] Step 2. Once the UE 3 becomes the Idle mode state, the UE 3 performs the Cell reselection procedure to move to a cell with the RAT Type GEO based on the prioritized RAT Type in the Prioritized NTN RAT Type list or / and the Prioritized NTN RAT Type list per a UE state for Idle mode state.

[0293] For example, the UE 3 may activate the released PDU session by the procedure as disclosed in the First Variant of the Fourth scenario in the First example of the First Aspect.

[0294] <Seventh scenario in the First example of the First Aspect> 　　The Seventh scenario in the First example of the First Aspect includes a mechanism for the capability negotiation between the RAN 5 and the AMF 70 for the support of multi orbit satellite access (RAN 5 initiated)

[0295] Fig. 14 illustrates an example of a call flow for the capability negotiation between the RAN 5 and the AMF 70 accessing with multi orbit satellites.

[0296] The detailed processes of this scenario are described below with reference to Fig. 14.

[0297] Step 1. The RAN 5 sends the NG Setup Request message to the AMF 70 including Supported TA List, Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support, list of NTN RAT type, list of Satellite Service provider, list of Satellite Service name and list of Satellite identifier.

[0298] The following bullets explain each parameter in detail. - Supported TA List: The Supported TA List indicates supported TAIs by the RAN 5. - Multi orbit satellite access support: The Multi orbit satellite access support indicates that the RAN 5 supports one or multiple new mechanisms in the mobility management and session management that are disclosed by this disclosure. - Redirected page response support: The Redirected page response support indicates that the RAN 5 supports a mechanism paged over one cell and responding to another cell is supported. - RAT Type indication in page support: The RAT Type indication in page support indicates that RAN 5 supports the RAT Type indication in page function. - List of NTN RAT type: The list of NTN Radio Access Technology (RAT) Type indicates a list of Radio Access Technology (RAT) Type(s) supported by the RAN 5. An NTN RAT in the list of NTN RAT type may be the RAT type as defined in 3GPP TS 29.212 [7] Section 5.3.31. - List of Satellite Service provider: The list of Satellite Service provider indicates a list of the Service provider(s) supported by the RAN 5. The Satellite Service provider in the List of 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. - The Satellite Service provider may be a PLMN operator or 3rd party service provider. - The Satellite Service provider may have a contract with user of the UE 3 as a subscription to the satellite service not only using over the 3GPP system but also direct access to the satellite, for example using the Very Small Aperture Terminal (VSAT) provided by the Satellite Service provider. - The Satellite Service provider may be expressed by a Satellite operator, Satellite Service operator or other name. - List of Satellite Service name: The list of Satellite Service name indicates a list of Service name of the satellite access provided by the Service provider and supported them by the RAN 5. For example, a Satellite Service name in the list of Satellite Service name may be expressed by a normalized numeric number for the Service name or Service name with the FQDN format. - List of Satellite identifier: The List of Satellite identifier indicates a list of the satellite identifier supported by the RAN 5. The Satellite identifier in the List of Satellite identifier may be defined by the Satellite 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 Defence) Catalog Number, NORAD ID, USSPACECOM (United States Space Command) object number or simply catalog number)

[0299] 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 and session management with RAN 5 for the multi orbit satellite access.

[0300] The AMF 70 sends the NG Setup Response message to the RAN 5 including Multi orbit satellite access support, Redirected page response support and RAT Type indication in page support.

[0301] The following bullets explain each parameter in detail. - Multi orbit satellite access support: The Multi orbit satellite access support indicates that the AMF 70 and associated core network nodes support one or multiple new mechanisms in the mobility management and session management that are disclosed by this disclosure. - Redirected page response support: The Redirected page response support indicates that AMF 70 and associated core network nodes support a mechanism paged over one cell and responding to another cell is supported. - RAT Type indication in page support: The RAT Type indication in page support indicates that AMF 70 and associated core network nodes support the RAT Type indication in page function.

[0302] 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 and session management with the AMF 70 for the multi orbit satellite access.

[0303] <Eighth scenario in the First example of the First Aspect> 　　The Eighth scenario in the First example of the First Aspect includes a mechanism for the capability negotiation between the RAN 5 and the AMF 70 for the support of multi orbit satellite access. (AMF 70 initiated)

[0304] Fig. 15 illustrates an example of a call flow for the capability negotiation between the RAN 5 and the AMF 70 accessing with multi orbit satellites.

[0305] The detailed processes of this scenario are described below with reference to Fig. 15.

[0306] Step 1. The AMF 70 sends the AMF Configuration Update message to the RAN 5 including Multi orbit satellite access support, Redirected page response support and RAT Type indication in page support.

[0307] Refer to Step 2 in Fig. 14 for parameter details.

[0308] Step 2. Upon reception of the AMF Configuration Update message from the AMF 70 in Step 1, the RAN 5 saves the received information and uses them for the mobility management and session management with RAN 5 for the multi orbit satellite access.

[0309] The RAN 5 sends the AMF Configuration Update Acknowledge message to the AMF 70 including Supported TA List, Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support, list of Satellite Service provider, list of Satellite Service name and list of Satellite identifier.

[0310] Refer to Step 1 in Fig. 14 for parameter details.

[0311] 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 multi orbit satellite access.

[0312] <Ninth scenario in the First example of the First Aspect> 　　The Ninth scenario in the First example of the First Aspect includes a mechanism for the capability negotiation between the RAN 5s for the support of multi orbit satellite access.

[0313] Fig. 16 illustrates an example of a call flow for the capability negotiation between the RAN 5s accessing with multi orbit satellites. For example, the Fig. 16 illustrates an example of a call flow for the capability negotiation between the RAN 501 and the RAN 502.

[0314] The detailed processes of this scenario are described below with reference to Fig. 16.

[0315] Step 1. The RAN 501 sends the XN Setup Request message to the RAN 502 including Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support, list of Satellite Service provider, list of Satellite Service name and list of Satellite identifier.

[0316] The following bullets explain each parameter in detail. - Multi orbit satellite access support: The Multi orbit satellite access support indicates that the RAN 501 supports one or multiple new mechanisms in the mobility management and session management that are disclosed by this disclosure. - Redirected page response support: The Redirected page response support indicates that the RAN 501 supports a mechanism paged over one cell and responding to another cell is supported. - RAT Type indication in page support: The RAT Type indication in page support indicates that RAN 501 supports the RAT Type indication in page function. - List of NTN RAT type: The list of NTN Radio Access Technology (RAT) Type indicates a list of Radio Access Technology (RAT) Type(s) supported by the RAN 501. An NTN RAT in the list of NTN RAT type may be the RAT type as defined in 3GPP TS 29.212 [7] Section 5.3.31. - List of Satellite Service provider: The list of Satellite Service provider indicates a list of the Service provider(s) supported by the RAN 501. The Satellite Service provider in the List of 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. - The Satellite Service provider may be a PLMN operator or 3rd party service provider. - The Satellite Service provider may have a contract with user of the UE 3 as a subscription to the satellite service not only using over the 3GPP system but also direct access to the satellite, for example using the Very Small Aperture Terminal (VSAT) provided by the Satellite Service provider. - The Satellite Service provider may be expressed by a Satellite operator, Satellite Service operator or other name. - List of Satellite Service name: The list of Satellite Service name indicates a list of Service name of the satellite access provided by the Service provider and supported them by the RAN 501. For example, a Satellite Service name in the list of Satellite Service name may be expressed by a normalized numeric number for the Service name or Service name with the FQDN format. - List of Satellite identifier: The List of Satellite identifier indicates a list of the satellite identifier supported by the RAN 501. The Satellite identifier in the List of Satellite identifier may be defined by the Satellite 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). 　　Step 2. Upon reception of the XN Setup Request message from the RAN 501 in Step 1, the RAN 502 saves the received information and uses them for the mobility management and session management with RAN 5 for the multi orbit satellite access. 　　The RAN 502 sends the XN Setup Response message to the RAN 501 including Multi orbit satellite access support, Redirected page response support, RAT Type indication in page support, list of Satellite Service provider, list of Satellite Service name and list of Satellite identifier. 　　The following bullets explain each parameter in detail. - Multi orbit satellite access support: The Multi orbit satellite access support indicates that the RAN 502 supports one or multiple new mechanisms in the mobility management and session management that are disclosed by this disclosure. - Redirected page response support: The Redirected page response support indicates that the RAN 502 supports a mechanism paged over one cell and responding to another cell is supported. - RAT Type indication in page support: The RAT Type indication in page support indicates that RAN 502 supports the RAT Type indication in page function. - List of NTN RAT type: The list of NTN Radio Access Technology (RAT) Type indicates a list of Radio Access Technology (RAT) Type(s) supported by the RAN 502. An NTN RAT in the list of NTN RAT type may be the RAT type as defined in 3GPP TS 29.212 [7] Section 5.3.31. - List of Satellite Service provider: The list of Satellite Service provider indicates a list of the Service provider(s) supported by the RAN 502. The Satellite Service provider in the List of 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. - The Satellite Service provider may be a PLMN operator or 3rd party service provider. - The Satellite Service provider may have a contract with user of the UE 3 as a subscription to the satellite service not only using over the 3GPP system but also direct access to the satellite, for example using the Very Small Aperture Terminal (VSAT) provided by the Satellite Service provider. - The Satellite Service provider may be expressed by a Satellite operator, Satellite Service operator or other name. - List of Satellite Service name: The list of Satellite Service name indicates a list of Service name of the satellite access provided by the Service provider and supported them by the RAN 502. For example, a Satellite Service name in the list of Satellite Service name may be expressed by a normalized numeric number for the Service name or Service name with the FQDN format. - List of Satellite identifier: The List of Satellite identifier indicates a list of the satellite identifier supported by the RAN 502. The Satellite identifier in the List of Satellite identifier may be defined by the Satellite 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).

[0317] Upon reception of the XN Setup Response message from the RAN 502 in Step 2, the RAN 501 saves the received information and uses them for the mobility management with the RAN 501 for the multi orbit satellite access.

[0318] <First Variant of the Ninth scenario in the First example of the First Aspect> 　　The List of Satellite Service provider, List of Satellite Service name and List of Satellite identifier are referred by the source RAN 5 (RAN 501 or RAN 502) to find a target cell for handover.

[0319] <Second example of the First Aspect> 　　This example includes mechanisms for the UE 3 to move a satellite 1 to a satellite 2 when the UE 3 becomes active mode with a deployment example where AMF 70 is located at the satellite together with RAN 5.

[0320] The satellite 1 may be a MEO, GEO or HEO which may have a wide coverage to page UE 3.

[0321] The satellite 2 may be a MEO, LEO, HAPS or RAN 5 in a terrestrial network (example, regular gNBs in the PLMN) for data communication.

[0322] In this example, it is assumed that the RAN 501 and AMF 7001 are located in a satellite, while the RAN 502 and AMF 7002 are located in another satellite. In addition, the RAN 501, RAN 502, AMF 7001 and AMF 7002 are able to communicate with other core network nodes in the Core Network 7.

[0323] In addition, there are two architecture assumption related to this example, a case where the UE 3 has one USIM and a case where the UE 3 has two USIMs.

[0324] If the UE 3 has one USIMs, the UE 3 may have two AMFs associated. I.e., the UE 3 may have two 5G-GUTIs.

[0325] If the UE 3 has two USIMs, each USIM may have an association with one AMF and performs the registration management procedures independently from the one with another USIM. I.e., there are two registration management procedures take place in parallel and each USIM has each 5G-GUTI assigned.

[0326] In one example, the AMF 7001 and the AMF 7001 may communicate each other using the N14 reference point via Inter Satellite Link (ISL) or via a Gateway node located at the ground of earth.

[0327] In another example, the AMF 7001 and the AMF 7001 may not be able to communicate each other.

[0328] Fig. 17 illustrates an example of switching one satellite to another based on a UE state. 　　This example may also apply to any other deployment examples. For example, one AMF in a satellite while another AMF is at a ground of earth.

[0329] <First scenario in the Second example of the First Aspect> 　　The First scenario in the Second example of the First Aspect includes a mechanism on system information that the RAN 5 may broadcast in case the RAN 5 supports multi orbit satellite access.

[0330] This scenario applies to the architecture as illustrated in Fig. 17.

[0331] I.E., There are two AMF 70s (e.g., AMF 7001and AMF 7002) to support data communication for the UE 3.

[0332] The disclosure that disclosed in the First scenario in the First example of the First Aspect apply as the mechanism on system information.

[0333] <Second scenario in the Second example of the First Aspect> 　　The Second scenario in the Second example of the First Aspect includes a mechanism for a Subscribed Multi orbit satellite access profile provisioning when the UE 3 accesses with the multi orbit satellite access.

[0334] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s (e.g., AMF 7001and AMF 7002) to support data communication for the UE 3.

[0335] The disclosure that disclosed in the Second scenario in the First example of the First Aspect apply as the mechanism for the Subscribed Multi orbit satellite access profile provisioning with the following additions and modifications:

[0336] Step 1-2 　　Additionally, the UDM 75 holds the following data as a subscriber data and provides them to the AMF 70. - Dual Registration: The Dual Registration indicates that the UE 3 is allowed to configure the dual registration. The dual registration implies that the UE 3 is able to perform two independent registration management. - Dual Registration with two USIM: The Dual Registration with two USIM indicates that the UE 3 is allowed to configure the dual registration using two USIMs. The dual registration using two USIMs implies that the UE 3 is able to perform two independent registration management one with a USIM and another one with another USIM. - Linked SUPI: The Linked SUPI indicates an associated SUPI in case that the UE 3 has the subscription Dual Registration with two USIM. A subscriber data in each SUPI has a paired SUPI.

[0337] For example, the UDM 75 sends, to the AMF 70, at least one of the Dual Registration information, Dual Registration with two USIM information and Linked SUPI information.

[0338] Step 1-3 　　The parameters listed in Step 1-2 in this scenario are transferred from the AMF 70 to the UE 3.

[0339] <Third scenario in the Second example of the First Aspect> 　　The Third scenario in the Second example of the First Aspect includes a mechanism for a registration procedure with multi orbit satellite.

[0340] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s (e.g., AMF 7001 and AMF 7002) to support data communication for the UE 3.

[0341] The disclosure that disclosed in the Third scenario in the First example of the First Aspect apply as the mechanism for the registration procedure with the following additions and modifications:

[0342] Fig. 9 　　The AMF 70 is replaced with AMF 7001.

[0343] All Steps related to Fig. 9 and / or the third scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001.

[0344] Steps 4 and 5 related to Fig. 9 and / or the third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Registration request message in Steps 4 and 5 related to Fig. 9, the Registration request message includes at least one of the following parameters: - Dual Registration support: The Dual Registration support indicates that the UE 3 has a capability to support the dual registration. In one example, the Dual Registration support may be expressed in the UE 5GMM Core Network Capability. - Dual Registration requested: The Dual Registration requested indicates that the UE 3 requests to perform the dual registration. - Dual Registration with two USIM support: The Dual Registration with two USIM support indicates that the UE 3 has a capability to support the dual registration using two USIMs. In one example, the Dual Registration with two USIM support may be expressed in the UE 5GMM Core Network Capability. - Dual Registration with two USIM requested: The Dual Registration with two USIM requested indicates that the UE 3 requests to perform the dual registration. - Linked 5G-GUTI: The Linked 5G-GUTI indicates a 5G-GUTI that has been associated. This parameter is set by the UE 3 in case that the Dual Registration or the Dual Registration with two USIM has been activated and the UE 3 has already in RM-Registered state.

[0345] Step 5 relate to Fig. 9 and / or the third scenario in the First example of the First Aspect 　　The following texts are added to the Step 5 related to Fig. 9 and / or the third scenario in the First example of the First Aspect.

[0346] If the AMF 7001 receives the Linked 5G-GUTI in the Registration request message, the AMF 7001 sends an N14 message to an AMF 7002 including the 5G-GUTI of the AMF 7001. The AMF 7002 may be routed based on the Linked 5G-GUTI. Then, the AMF 7001 receives an N14 response message from the AMF 7002. With this process, the AMF 7001 and AMF 7002 hold two 5G-GUTIs, one for own 5G-GUTI and another 5G-GUTI for the associated AMF.

[0347] Steps 6 and 8 relate to Fig. 9 and / or the third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nudm service messages in Steps 6 and 8, the Nudm service messages include the following parameters. - Dual Registration support: Refer to Step 4. - Dual Registration with two USIM support: Refer to Step 4.

[0348] Step 9 relate to Fig. 9 and / or the third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nudm service response messages in Step 9, the Nudm service response message includes the following parameters. - Dual Registration subscribed: The Dual Registration subscribed indicates that the UE 3 has a valid subscription to the Dual Registration function. - Dual Registration with two USIM subscribed: The Dual Registration with two USIM subscribed indicates that the UE 3 has a valid subscription to the Dual Registration with two USIM function.

[0349] Step 15 relate to Fig. 9 and / or the third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Registration Accept message in Step 15, the Registration Accept message includes the following parameters. - Dual Registration activated: The Dual Registration activated indicates that the Dual Registration function has been activated. - Dual Registration with two USIM activated: The Dual Registration with two USIM activated indicates that the Dual Registration with two USIM function has been activated.

[0350] <Fourth scenario in the Second example of the First Aspect> 　　The Fourth scenario in the Second example of the First Aspect includes a mechanism for a Mobile Originated (MO) Session Activation procedure with multi orbit satellite.

[0351] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s (e.g., AMF 7001 and AMF 7002) to support data communication for the UE 3.

[0352] The disclosure that disclosed in the Fourth scenario in the First example of the First Aspect apply as the mechanism for the Mobile Originated (MO) Session Activation procedure with the following additions and modifications:

[0353] Fig. 10 for the Fourth scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001.

[0354] All Steps related to the Fourth scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001.

[0355] Steps 5 and 6 related to Fig. 10 and / or the Fourth scenario in the First example of the First Aspect 　　In addition to the parameters included in the UL NAS Transport message and PDU Session Establishment Request messages in Step 5 and 6 respectively, the UL NAS Transport message and PDU Session Establishment Request message include the following parameters: - Dual Registration requested: The Dual Registration requested indicates that the UE 3 requests to perform the dual registration. - Dual Registration with two USIM requested: The Dual Registration with two USIM requested indicates that the UE 3 requests to perform the dual registration.

[0356] Steps 7 related to Fig. 10 and / or the Fourth scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nsmf_PDUSession_CreateSMContext Request message in Step 7, the Nsmf_PDUSession_CreateSMContext Request message include the following parameters: - Page bicast requested: The Page bicast requested indicates that the SMF 71 is requested to sends two Namf_Communication_N1N2MessageTransfer messages to the AMF 7001 and an AMF as indicated in the companion parameter Associated AMF name in this message. Typically, this parameter is set in case where the AMF 7001 does not have an N14 reference point to an associated AMF due to no ISL. - Associated AMF name: The Associated AMF name indicates an associated AMF when the UE 3 configures the two AMFs based on either Dual Registration function or Dual Registration with two USIM function. The Associated AMF name may be expressed by an IPv4 address, IPv6 address or Fully Qualified Domain Name (FQDN). The AMF 7001 generates the Associated AMF name based on the Linked 5G-GUTI. - If the SMF 71 receives the Associated AMF name, the SMF 71 recognizes that the SMF 71 may receive the Nsmf_PDUSession_UpdateSMContext Request message from the associated AMF. For example, in case that the UE 3 cannot see any cells on the LEO satellite but sees a cell on the GEO satellite and the UE 3 has registered with the associated AMF that is located in the GEO satellite, the UE 3 may send the Service Request message with a cell on the GEO satellite.

[0357] Steps 9 related to Fig. 11 and / or the Fourth scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nudm service message in Step 9, the Nudm service message includes the following parameters. - Dual Registration support: The Dual Registration support indicates that the UE 3 has a capability to support the dual registration. - Dual Registration with two USIM support: The Dual Registration with two USIM support indicates that the UE 3 has a capability to support the dual registration using two USIMs.

[0358] Step 10 related to Fig. 11 and / or the Fourth scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nudm service response message in Step 10, the Nudm service response message includes the following parameters. - Dual Registration subscribed: The Dual Registration subscribed indicates that the UE 3 has a valid subscription to the Dual Registration function for DNN, S-NSSAI or a combination of DNN and S-NSSAI. - Dual Registration with two USIM subscribed: The Dual Registration with two USIM subscribed indicates that the UE 3 has a valid subscription to the Dual Registration with two USIM function for DNN, S-NSSAI or a combination of DNN and S-NSSAI.

[0359] Steps 15 to 17 related to Fig. 11 and / or the Fourth scenario in the First example of the First Aspect 　　In addition to the parameters included in the PDU Session Establishment Accept message in Steps 15 and 17, the PDU Session Establishment Accept message includes the following parameters. - Dual Registration activated: The Dual Registration activated indicates that the Dual Registration function has been activated for the PDU Session. - Dual Registration with two USIM activated: The Dual Registration with two USIM activated indicates that the Dual Registration with two USIM function has been activated for the PDU Session.

[0360] New paragraph added to the bottom of the Fourth scenario in the First example of the First Aspect 　　With the successful PDU Session Establishment procedure with either Dual Registration function or Dual Registration with two USIM function, the UE 3 can establish PDU Session with the best satellite for data communication, that may be in accordance with the Prioritized NTN RAT Type or / and the Prioritized NTN RAT Type list per a UE state for the Connected mode state, while the UE 3 maintains an association with another satellite that is the best for the UE 3 in the Idle mode state, that may be in accordance with the Prioritized NTN RAT Type or / and the Prioritized NTN RAT Type list per a UE state for the Idle mode state.

[0361] <Fifth scenario in the Second example of the First Aspect> 　　The Fifth scenario in the Second example of the First Aspect includes a mechanism for a Mobile Terminated (MT) Session Activation procedure with the N14 reference with multi orbit satellite.

[0362] This scenario applies to the architecture as illustrated in Fig. 17.

[0363] I.E., There are two AMF 70s (e.g., AMF 7001 and AMF 7002) to support data communication for the UE 3.

[0364] Fig. 18 illustrates an example of a call flow for the Mobile Terminated (MT) Session Activation procedure accessing with the N14 reference with multi orbit satellites.

[0365] The detailed processes of this scenario are described below with reference to Fig. 18.

[0366] Step 0-1. The UE 3 has registered with AMF 7001, with 5G-GUTI 1 assigned, with Subscribed Multi orbit satellite access profile set to as follows: - Prioritized NTN RAT Type list per a UE state for Idle mode state: GEO>LEO. For example, GEO takes priority over LEO. - Prioritized NTN RAT Type list per a UE state for connected mode state: LEO>GEO. For example, LEO takes priority over GEO. - The priority can be set arbitrarily, not limited to the above examples.

[0367] In addition, the UE 3 has registered with AMF 7002, with 5G-GUTI 2 assigned, with Subscribed Multi orbit satellite access profile set to as follows: - Prioritized NTN RAT Type list per a UE state for Idle mode state: GEO>LEO. For example, GEO takes priority over LEO. - Prioritized NTN RAT Type list per a UE state for connected mode state: LEO>GEO. For example, LEO takes priority over GEO. - The priority can be set arbitrarily, not limited to the above examples.

[0368] In one example, the AMF 7001 is located in the GEO satellite while the AMF 7002 is located in the LEO satellite.

[0369] In one example the UE 3 is provisioned with an information either in a USIM, in a memory object using OMA DM method to registers via GEO cells and LEO cell or MEO cell to a PLMN or to two different PLMNs simultaneously when the UE sees one GEO cell and one LEO cell or one MEO cell. The UE reads this information element and register to a PLMN via GEO cell or LEO or MEO cell or two different PLMNs via GEO cell and LEO or MEO cell independently. The UE 3 and the AMF 7001 maintains two independents 5GMM contexts one for each registration procedure.

[0370] In one example the UE 3 supporting dual registration includes dual registration capability of the UE 3 to the AMF 7001. The AMF 7001 stores this capability and also forwards it to the UDM 75 in an existing message between the UE 3 and the AMF 7001.

[0371] In one example, when the UE 3 is registering to the PLMN via the RAN 502, the UE sends the 5G-GUTI 1 in the registration request message to the AMF 7002. When the AMF 7002 receives the 5G-GUTI 1 then the AMF 7002 concludes that the UE is already registered to the AMF 7001 identified by the GUAMI of the 5G-GUTI 1.

[0372] Step 0-2. The UE 3 establishes a PDU Session with the AMF 7002 and becomes idle mode state due to user data inactivity.

[0373] Step 0-3. The UE 3 (with 5G-GUTI 1) stays with a cell in GEO satellite where the AMF 7001 is located.

[0374] Step 0-4. The UE 3 (with 5G-GUTI 2) stays with a cell in LEO satellite where the AMF 7002 is located.

[0375] Step 1. Downlink data arrives to the UPF 72.

[0376] Step 2. The UPF 72 sends the Data Notification to the SMF 71.

[0377] Step 3. Upon reception of the Data Notification message from the UThe UPF 72, the SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 7002 including SUPI and PDU Session ID.

[0378] Step 4, Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 7002 checks the MM context for the UE 3 and finds out that the UE 3 is Dual registered with AMF 7001. The AMF 7002 may determine the UE is dual registered when the AMF 7002 has 5G-GUTI 1 as received in Step 0-1. 　　With this situation, the AMF 7002 decides to perform a multiple paging one over the AMF 7002 and the other one over the AMF 7001.

[0379] Step 5. The AMF 7002 sends the Paging message to the RAN 502 including UE Paging Identity. 　　The following bullets explain each parameter in detail. - UE Paging Identity: Refer to Step 4 in Fig. 12. In this step, the UE Paging Identity is set as the 5G-S-TMSI 2 generated from the 5G-GUTI 2.

[0380] Step 6. The RAN 502 performs Page. Page signal includes UE Identity. 　　The following bullets explain each parameter in detail. - UE Identity: Refer to Step 5 in Fig. 12.

[0381] Step 7. Based on the decision in Step 4, The AMF 7002 sends the N14 Paging message to AMF 7001 including SUPI. For SUPI, refer to Step 6 in Fig. 9 in details. 　　In one example, the AMF 7002 based on the stored 5G-GUTI 1 determines AMF 7001 based on the GUAMI 1 of 5G-GUTI 1. The AMF 7002 also includes 5G-GUTI 1.

[0382] Step 8. Upon reception of the N14 Paging message from the AMF 7002, the AMF 7001 sends the Paging message to the RAN 501 including at least one of UE Paging Identity and 5G-GUTI 1. 　　The following bullets explain each parameter in detail. - UE Paging Identity: Refer to Step 4 in Fig. 12. In this step, the UE Paging Identity is set as the 5G-S-TMSI 1 generated from the 5G-GUTI 1 that is assigned to the SUPI in the AMF 7001.

[0383] Step 9. The RAN 501 performs Page. Page signal includes UE Identity. 　　The following bullets explain each parameter in detail. - UE Identity: Refer to Step 5 in Fig. 12.

[0384] Step 10. Once the UE 3 receives the page for the UE 3, the UE 3 may perform the Cell reselection to a cell with either LEO or GEO. It is based on the radio condition and based on the Prioritized NTN RAT Type or / and Prioritized NTN RAT Type list per a UE state for Connected mode state.

[0385] Step 11. Steps 3 to 18 in Fig. 10 and 11 take place.

[0386] <First Variant of the Fifth scenario in the Second example of the First Aspect> 　　Steps 5 to 6 and Steps 7 to 9 are executed in parallel. 　　In one example, Steps 7 to 9 are executed when the AMF 7002 does not receive the Service Request message form the UE 3 within the pre-defined value for a timer in the AMF 7002.

[0387] <Second Variant of the Fifth scenario in the Second example of the First Aspect> 　　If the AMF 7002 receives the Service Request message form the UE 3 after Steps 6, the AMF 7002 may send a Paging stop message to the AMF 7001 including SUPI. Once the AMF 7001 receives the Paging stop message from the AMF 7002, the AMF 7001 stops the paging process to the UE 3.

[0388] <Third Variant of the Fifth scenario in the Second example of the First Aspect> 　　In Step 0-1, when the UE 3 is registering via the RAN 501 to a PLMN, the AMF 7001 for the UE 3 supporting dual registration procedure sends the GUAMI to which the UE 3 is registering to the UDM 75 in an existing message or a new message between the AMF 7001 and the UDM 75. Similarly, when the UE 3 is registering via the RAN 502 the AMF 7002 sends this information to the UDM 75 using an existing message between the AMF 7002 and the UDM 75. The UDM 75 stores two AMF IDs for a UE3 registered via two satellite access simultaneously. In Step 4 the AMF 7002 queries the UDM 75 whether the UE 3 is registered to the PLMN via another access using an existing message or a new message. The UDM 75 sends a response message containing the GUAMI 1. The AMF 702 sends N14 paging message to the AMF 7001 determined by the GUAMI1.

[0389] <Sixth scenario in the Second example of the First Aspect> 　　The Sixth scenario in the Second example of the First Aspect includes a mechanism for a Mobile Terminated (MT) Session Activation procedure without the N14 reference with multi orbit satellite.

[0390] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s (e.g., AMF 7001 and AMF 7002) to support data communication for the UE 3.

[0391] Fig. 19 illustrates an example of a call flow for the Mobile Terminated (MT) Session Activation procedure accessing without the N14 reference with multi orbit satellites.

[0392] The detailed processes of this scenario are described below with reference to Fig. 19.

[0393] Step 1. Steps 0-1 to 2 in Fig. 18 take place.

[0394] Step 2. Upon reception of the Data Notification from the UPF72, the SMF 71 checks the Session Management related subscriber for the UE 3 and finds out that the UE 3 is Dual registered with AMF 7001. In one example, the SMF 71 finds it out by checking whether the SMF 71 has received the Page bicast requested or / and Associated AMF name. 　　With this situation, the SMF 71 decides to perform a multiple paging, one over the AMF 7002 and the other one over the AMF 7001.

[0395] Step 3. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 7002 including SUPI and PDU Session ID.

[0396] Step 4. Steps 5 and 6 in Fig. 18 take place.

[0397] Step 5. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 7001 including SUPI and PDU Session ID.

[0398] Step 6. Steps 8 and 9 in Fig. 18 take place.

[0399] Step 7. Steps 10 and 11 in Fig. 18 take place.

[0400] <First Variant of the Sixth scenario in the Second example of the First Aspect> 　　Steps 3 to 4 and Steps 5 to 6 are executed in parallel.

[0401] In one example, Steps 5 to 6 are executed when the SMF 71 does not receive the Nsmf_PDUSession_UpdateSMContext Request message form the AMF 7002, as the page response, within the pre-defined value for a timer in the SMF 71.

[0402] One another example, the SMF execute Steps 5 to 6. Then, steps 3 to 4 are executed when the SMF 71 does not receive the Nsmf_PDUSession_UpdateSMContext Request message form the AMF 7001, as the page response, within the pre-defined value for a timer in the SMF 71.

[0403] <Second Variant of the Sixth scenario in the Second example of the First Aspect> 　　In one example, in Step 2 when the SMF 71 receives the data notification message, the SMF 71 queries to the UDM 75 using an existing message whether the UE 3 is dual registered using an existing message between the SMF 71 and the UDM 75. In response of the received message from the SMF 71, the UDM 75 sends a response message containing the GUAMI 1 and indication the UE 3 is dual registered to the AMF 7001 identified by GUAMI 1. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 7001 and the AMF 7002 including SUPI and PDU Session ID. The AMF 7001 and 7002 follows Steps 8-9.

[0404] <Seventh scenario in the Second example of the First Aspect> 　　The Seventh scenario in the Second example of the First Aspect includes a Session Release procedure with multi orbit satellite.

[0405] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s to support data communication for the UE 3.

[0406] The disclosure that disclosed in the Sixth scenario in the First example of the First Aspect apply as the mechanism the Session Release procedure with multi orbit satellite without any modifications.

[0407] <Eighth scenario in the Second example of the First Aspect> 　　The Eighth scenario in the Second example of the First Aspect includes a mechanism for capability negotiation between the RAN 5 and the AMF 70 for the support of multi orbit satellite access (RAN 501 initiated).

[0408] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s to support data communication for the UE 3.

[0409] The disclosure that disclosed in the Seventh scenario in the First example of the First Aspect apply as the mechanism for capability negotiation between the RAN 501 and the AMF 7001 and between the RAN 502 and the AMF 7002 for the support of multi orbit satellite access (RAN 5 initiated) with the following additions and modifications:

[0410] Fig. 14 related to the Seventh scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001.　The AMF 70 may be replaced with AMF 7002.

[0411] The RAN 5 is replaced with RAN 501. The RAN 5 may be replaced with RAN 502.

[0412] All Steps related to Fig. 14 and / or the Seventh scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001. The AMF 70 may be replaced with AMF 7002. 　　The RAN 5 is replaced with RAN 501. The RAN 5 may be replaced with RAN 502.

[0413] New paragraph added to the bottom of the Seventh scenario in the First example of the First Aspect 　　The NG Setup procedure in Fig. 14 is equally applicable to the N2 reference point between the RAN 502 and the AMF 7002.

[0414] <Ninth scenario in the Second example of the First Aspect> 　　The Ninth scenario in the Second example of the First Aspect includes a mechanism for capability negotiation between the RAN 5 and the AMF 70 for the support of multi orbit satellite access (AMF 7001 initiated).

[0415] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s to support data communication for the UE 3.

[0416] The disclosure that disclosed in the Eighth scenario in the First example of the First Aspect apply as the mechanism for capability negotiation between the RAN 501 and the AMF 7001 and between the RAN 502 and the AMF 7002 for the support of multi orbit satellite access (AMF 7001 initiated) with the following additions and modifications:

[0417] Fig. 15 related to the Eighth scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001.The AMF 70 is replaced with AMF 7002. 　　The RAN 5 is replaced with RAN 501. The RAN 5 is replaced with RAN 502.

[0418] All Steps related to Fig. 15 and / or the Eighth scenario in the First example of the First Aspect 　　The AMF 70 is replaced with AMF 7001. The AMF 70 is replaced with AMF 7002. 　　The RAN 5 is replaced with RAN 501. The RAN 5 is replaced with RAN 502.

[0419] New paragraph added to the bottom of the Eighth scenario in the First example of the First Aspect 　　The AMF Configuration Update procedure in Fig. 15 is equally applicable to the N2 reference 　　point between the RAN 502 and the AMF 7002.

[0420] <Tenth scenario in the Second example of the First Aspect> 　　The Tenth scenario in the Second example of the First Aspect includes a mechanism for capability negotiation between the RAN 5s for the support of multi orbit satellite access.

[0421] This scenario applies to the architecture as illustrated in Fig. 17. 　　I.E., There are two AMF 70s to support data communication for the UE 3.

[0422] The disclosure that disclosed in the Ninth scenario in the First example of the First Aspect apply as the mechanism for capability negotiation between the RAN 501 and the RAN 502 for the support of multi orbit satellite access without any modifications.

[0423] <Second Aspect> 　　This aspect discloses mechanisms for a data communication with a resilient notification with the satellite access. In this this patent specifications, the term resilient notification, in a flexible manner, generally denotes the act of providing notifications, and its name may vary. The term resilient notification broadly refers to devising notification method to ensure that notifications reach users or other nodes under various circumstances. For example, a resilient notification may be a support or recovery system for communication between communication systems (or between communication nodes) for notification failures. For example, the communication systems or the communication nodes may be a radio terminal, a base station, a core network node or any other devices involved in communication.

[0424] This aspect aims to solve the following issue with 3GPP system with satellite access. - For example, possible issues related to mechanisms for a data communication with a resilient notification with the satellite access. - The satellite communication typically uses the high frequency band. For example, the SHF frequency band (3GHz to 30GHz). Due to a characteristic of the radio penetration in high frequency band, a communication between the satellite and the UE may be disrupted easily. For example, if a user of the UE is under the big tree during the hiking, downlink data from the satellite may not reach to the UE as the big tree is an obstacle to block receiving the downlink data. - For another example, if a user of the UE is under the big tree during the hiking, uplink data from the UE may not reach to the satellite as the big tree is an obstacle to block sending the uplink data. - With this point of view, the user may miss an important notification easily with satellite access rather than the one over the cellular access with the terrestrial network. - With this consideration, a resilient notification mechanism with the satellite access is desired to make the satellite communication more reliable.

[0425] This aspect discloses mechanisms to make the resilient notification possible for the satellite communication when the downlink signal is missed for the UE 3 while the UE 3 is out of coverage of satellite coverage.

[0426] For example, the satellite may a HEO, GEO, MEO, LEO, HAPS or RAN 5 on grand for data communication. However, the satellite is not limited to the HEO, GEO, MEO, LEO, HAPS or RAN 5. For example, the satellites may be satellites that have different orbits.

[0427] Fig. 20 illustrates an example of a service disruption for satellite communication.

[0428] If there is a downlink signal, example page, from the satellite to the UE 3 in a period T1 to T1+t, the UE 3 misses to receive the downlink signal. The UE 3 should be notified the missing as soon as the UE 3 becomes reachable from the satellite. For example, the UE 3 may fail to receive the downlink signal due to communication interruptions or disruption caused by obstacle against satellite communication or some other reasons.

[0429] <First example of the Second Aspect> 　　The First example of the Second Aspect includes a network centric mechanism for the resilient notification in case that the user missed a page with satellite access.

[0430] <First scenario in the First example of the Second Aspect> 　　The First scenario in the First example of the Second Aspect includes a mechanism on system information that the RAN 5 may broadcast in case the RAN 5 supports the resilient notification.

[0431] This scenario applies to the architecture as illustrated in Fig. 20.

[0432] The disclosures that disclosed in the First scenario in the First example of the First Aspect apply as the mechanism on system information with the following additions and modifications: The RAN 501 may broadcast in case the RAN 501 supports the resilient notification. The RAN 502 may broadcast in case the RAN 502 supports the resilient notification.

[0433] Steps 1 and 2 related to Fig. 5 and / or the First scenario in the First example of the First Aspect 　　In addition to the parameters included in the System information in Steps 1 and 2, the System information includes the following parameters: - Resilient notification: The Resilient notification indicates that the RAN 5 supports the Resilient notification function as disclosed in this disclosure. The RAN 5 may be the RAN 501 and / or the RAN 502. - If the UE 3 has activated the Resilient notification service, the UE 3 reads this parameter and the UE 3 confirms that the Resilient notification is activated. - In one example, the RRC layer in the UE 3 notifies a status of the Resilient notification to upper layer. - In another example, If both AS layer and the NAS layer of the UE 3 holds statuses the Resilient notification in the system information and the Resilient notification activated in the NAS layer, the upper layer of the UE 3 may display an icon indicating to user that the Resilient notification is activated.

[0434] <Second scenario in the First example of the Second Aspect> 　　The Second scenario in the First example of the Second Aspect includes the mechanism for the resilient notification profile provisioning with the resilient notification function.

[0435] This scenario applies to the architecture as illustrated in Fig. 20.

[0436] The disclosures that disclosed in the Second scenario in the First example of the First Aspect apply as the mechanism for the resilient notification profile provisioning with the following additions and modifications:

[0437] Step 1-2 related to Fig. 6 and / or the Second scenario in the First example of the First Aspect 　　Additionally, the UDM 75 holds the following data as a subscriber data and provides them to the AMF 70. - Resilient notification subscribed: The Resilient notification subscribed indicates that the UE 3 has a valid subscription to the Resilient notification function. - Resilient notification parameters: The Resilient notification parameters indicate a page resending related parameters in case that the UE 3 does not response to the page. The Resilient notification parameters may include the following parameters: -- Page resending window: The Page resending window indicates a maximum time window for page resending. For example, if the Page resending window is set to 2 minutes, the page resending continues for maximum 2 minutes when if the UE 3 does not reply to the page. -- Page resending frequency: The Page resending frequency indicates how often the AMF 70 initiates the paging procedure. For example, if the Page resending frequency is set to 20 seconds, the AMF 70 initiates the paging procedure every 20 seconds if the UE 3 does not reply to the page.

[0438] <Third scenario in First example of the Second Aspect> 　　The Third scenario in First example of the Second Aspect includes a mechanism for a registration procedure with the resilient notification function.

[0439] This scenario applies to the architecture as illustrated in Fig. 20.

[0440] The disclosures that disclosed in the Third scenario in the First example of the First Aspect apply as the mechanism on system information with the following additions and modifications:

[0441] Steps 4 and 5 related to Figure8 and / or the Third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Registration request message in Steps 4 and 5, the Registration request message includes the following parameters: - Resilient notification support: The Resilient notification support indicates that the UE 3 has a capability to support the Resilient notification support. In one example, the Resilient notification support may be expressed in the UE 5GMM Core Network Capability. - Resilient notification requested: The Resilient notification requested indicates that the UE 3 requests to activate the Resilient notification.

[0442] Steps 6 and 8 related to Fig. 9 and / or the Third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nudm service messages in Steps 6 and 8 (For example, Nudm_UECM_Registraion Request message and Nudm_SDM_Get Request message), the Nudm service messages include the following parameters. - Resilient notification support: Refer to Step 4.

[0443] Step 9 related to Figure8 and / or the Third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Nudm service response messages in Step 9, the Nudm service response message includes the following parameters. - Resilient notification subscribed: The Resilient notification subscribed indicates that the UE 3 has a valid subscription to the Resilient notification function. - Resilient notification parameters: Refer to Steps 1-2 in Fig. 6.

[0444] Step 15 related to Figure8 and / or the Third scenario in the First example of the First Aspect 　　In addition to the parameters included in the Registration Accept message in Step 15, the Registration Accept message includes the following parameters. - Resilient notification activated: The Resilient notification activated indicates that the Resilient notification function has been activated. - Resilient notification parameters: Refer to Steps 1-2 in Fig. 6.

[0445] <Fourth scenario in the First example of the Second Aspect> 　　The Fourth scenario in the First example of the Second Aspect includes a mechanism for a Mobile Terminated (MT) Session Activation procedure with the resilient notification function.

[0446] This scenario applies to the architecture as illustrated in Fig. 20.

[0447] Fig. 21 illustrates an example of a call flow for the Mobile Terminated (MT) Session Activation procedure with the network centric resilient notification function.

[0448] The detailed processes of this scenario are described below with reference to Fig. 21.

[0449] Step 0-1. The UE 3 has registered with AMF 70 and the resilient notification is activated. The AMF 70 assigns 5G-GUTI 1 to the UE 3.

[0450] Step 0-2. The UE 3 establishes a PDU Session with the SMF 71 and UPF 73. Then the UE 3 becomes to an idle mode state. For example, due to user data inactivity.

[0451] Step 1. Downlink data arrives from the AF 201 to the UPF 72.

[0452] Step 2. The UPF 72 sends the Data Notification to the SMF 71.

[0453] Step 3. Upon reception of the Data Notification message from the UPF 72, the SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 including SUPI, PDU Session ID, DNN, S-NSSAI. 　　The following bullets explain each parameter in detail. - SUPI: The SUPI is Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. - 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.

[0454] Step 4, Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 stores the received DNN and S-NSSAI and sends the Paging message to the RAN 5 including UE Paging Identity. 　　The following bullets explain each parameter in detail. - UE Paging Identity: Refer to Step 4 in Fig. 12. In this scenario, the 5G-S-TMSI is constructed based on the 5G-GUTI 1.

[0455] Step 5. The RAN 5 performs the Page. The Page signal includes UE Identity. 　　The following bullets explain each parameter in detail. - UE Identity: A UE Identity that the UE 3 scans whether there is a page for the UE 3.

[0456] Step 6. The UE 3 misses the Page. For example, the UE 3 is located behind the big tree or some obstacle and the UE 3 cannot receive the system information that a cell with the RAN 5 broadcasts. For example, the UE 3 may not be able to receive information from the RAN 5 due to some reasons.

[0457] Steps 7 and 8. The AMF 70 checks a status of Resilient notification activated in the MM context for the UE 3 and confirms that the UE 3 has Resilient notification function is activated.

[0458] With this confirmation, the AMF 70 repeats sending the Paging message to the RAN 5, as the same way with the Step 4, according to the Resilient notification parameters in the MM context of the UE 3. I.e. The AMF 70 sends the same Paging message in Step 4 again.

[0459] Step 9. The UE 3 sends a NAS message to the AMF 70. For example, the NAS message may be a UL NAS transport message including the Service request message as the response to the page in Step 8. For another example, the NAS message may be a Registration Request message.

[0460] Step 10. Upon reception of the NAS message, the AMF 70 checks whether the Resilient notification is activated or not. If the Resilient notification is activated, the AMF 70 collects session related data (Example, DNN, S-NSSAI) that the Mobile Terminated (MT) Session Activation(s) failed due to no page response from the UE 3.

[0461] The AMF sends another NAS message to the UE 3 including Resilient notification data. For example, another NAS message may be a DL NAS transport message including the Service accept message. For another example, another NAS message may be a Registration Accept message.

[0462] The following bullets explain each parameter in detail. - Resilient notification data: The Resilient notification data includes the data related to the page that the UE 3 missed in the past. The Resilient notification data may be composed of multiple Resilient notification data when the UE 3 missed pages multiple times. Each Resilient notification data may include the following parameters: -- Time: Time indicates when the UE 3 missed the page. -- DNN: The DNN contains a DNN of a PDU Session that a page is trigged. -- S-NSSAI: The S-NSSAI contains an S-NSSAI of a PDU Session that a page is trigged.

[0463] Step 11. The UE 3 takes an action based on the received Resilient notification data. 　　For example, if the received Resilient notification data includes a DNN for the IMS service, the UE 3 sends the Service Request message to the SMF 71 and activate the PDU Session. Then, the IMS application in the UE 3 sends a sip:REGISTER (Session Initiation Protocol: REGISTER) method to the S-CSCF (Server - Call Session Control Function) of the UE 3 so that the S-CSCF recognizes that the UE 3 is reachable and provides a SIP:MESSAGE (Session Initiation protocol: MESSAGE) method to the IMS application in the UE 3 informing a missed calling party number.

[0464] Then, the user of the UE 3 recognizes a call missed and makes a call by referring to the received calling party number.

[0465] <First Variant of the Fourth scenario in the First example of the Second Aspect> 　　The disclosure in this scenario is equally applicable to the network where a RAN 5 is located in the Terrestrial Network.

[0466] <Second Variant of the Fourth scenario in the First example of the Second Aspect> 　　In one example, the UDM 75 per S-NSSAI or per DNN or per S-NSSAI+DNN basis stores whether resilient notification procedure is applicable or not.

[0467] In Step 3, when the AMF 70 determines that the S-NSSAI or the DNN or S-NSSAI + DNN are subscribed for the resilient notification then the AMF 70 and the UE 3 executes Steps 4-11.

[0468] <Third Variant of the Fourth scenario in the First example of the Second Aspect> 　　In one example, when the UE 3 is registered over two accesses (3GPP accesses or 3GPP access and non-3GPP access) (the UE is dual registered to a PLMN or different PLMN same as in Fig. 18), if the UE 3 is not reachable over the first access then the UE 3 send an information element indicating to the AMF 70 via the second access using an existing NAS message or a new NAS message that the UE 3 is not reachable through the first access then the AMF 70 sends the information element to the UDM 75 using an existing message between the AMF 70 and the UDM 75. The UDM 75 stores the status of the UE 3 not reachable via the first access. When an NF e.g. (SMF 71 or AMF 70) gets a user data (Example, data related to IMS call.) or signalling data to send then NF sends an existing message or a new message to query the UE reachability. When the UDM 75 receives the message, the UDM 75 sends a response message (e.g., existing message or a new message between the NF and the UDM 75) a first information element indicating that the UE 3 is not reachable through the first access and a second information element indicating that the UE 3 is reachable through the second access and the AMF ID GUAMI). The NF sends a robust notification information element indicating that there is data pending for the UE 3 over the first access in an existing message between the NF and the AMF 70 corresponding to the GUAMI where the UE 3 is registered over the second access. The robust notification information element may consist of S-NSSAI or S-NSSAI and DNN or DNN related to the PDU session of the user data. The robust notification information element may also include caller id of the calling party in case of MT IMS call. When the AMF 70 receives the message including the robust notification information element then the AMF 70 sends the robust notification information element in a new NAS message or an existing NAS message to the UE 3 over the first access. When the UE receives the NAS message then the UE 3 informs this to the user. When the UE 3 finds coverage of the first access then the UE 3 sends an information element in an existing NAS message or in a new NAS message over first access or the second access to the first AMF or the second AMF respectively. When the first AMF or the second AMF receives the NAS message the first AMF or the second AMF sends this information element to the UDM 75 using an existing message or a new message between the AMF and the UDM 75. Upon receiving the message, the UDM 75 marks that the UE is reachable through the first access. Upon query from a NF using an existing message or a new message between the UDM 75 and the NF the UDM 75 responds that the UE 3 is reachable through the first access.

[0469] <Second example of the Second Aspect> 　　The Second example of the Second Aspect includes a terminal centric mechanism for the resilient notification in case that the user missed a page with satellite access.

[0470] <First scenario in the Second example of the Second Aspect> 　　The First scenario in the Second example of the Second Aspect includes a mechanism on system information that the RAN 5 may broadcast in case the RAN 5 supports the resilient notification.

[0471] This scenario applies to the architecture as illustrated in Fig. 20.

[0472] The disclosures that disclosed in the First scenario in the First example of the Second Aspect apply as the mechanism on system information for this example.

[0473] <Second scenario in the Second example of the Second Aspect> 　　The Second scenario in the Second example of the Second Aspect includes the mechanism for the resilient notification profile provisioning with the resilient notification function.

[0474] This scenario applies to the architecture as illustrated in Fig. 20.

[0475] The disclosures that disclosed in the Second scenario in the First example of the Second Aspect apply as the mechanism of the resilient notification profile provisioning for this example.

[0476] <Third scenario in Second example of the Second Aspect> 　　The Third scenario in Second example of the Second Aspect includes a mechanism for a registration procedure with the resilient notification function.

[0477] This scenario applies to the architecture as illustrated in Fig. 20.

[0478] The disclosures that disclosed in the Third scenario in the First example of the Second Aspect apply as the mechanism for the registration procedure for this example.

[0479] <Fourth scenario in the Second example of the Second Aspect> 　　The Fourth scenario in the Second example of the Second Aspect includes a mechanism for a Mobile Terminated (MT) Session Activation procedure with the resilient notification function.

[0480] This scenario applies to the architecture as illustrated in Fig. 20.

[0481] Fig. 22 illustrates an example of a call flow for the Mobile Terminated (MT) Session Activation procedure with the terminal centric resilient notification function.

[0482] The detailed processes of this scenario are described below with reference to Fig. 22.

[0483] Step 1. Steps 0-1 to 4 in Fig. 21 take place. In one example t is sent during the registration procedure to the UE 3 in an existing NAS message or in a new NAS message. the parameter t can be stored in the UDM 75 per UE basis (in this case the UDM 75 provides the t to the AMF 70 in an existing message or a new message between the AMF 70 and the UDM 75) or in the AMF 70 per UE basis or for all UE. In one example parameter t will be broadcasted in an existing SIB or in a new SIB.

[0484] Step 2. The UE 3 moves into an out of coverage area. For example, the UE 3 is located behind the big tree and the UE 3 cannot receives the system information that a cell with the RAN 5 broadcasts. 　　When the UE 3 loses the coverage in Step 2, the UE 3 starts an internal timer.

[0485] Step 3. The RAN 5 performs Page. Page signal includes UE Identity. 　　Refer to Step 8 in Fig. 21 for parameter details. 　　The UE 3 misses the Page as the UE 3 is not reachable from the RAN 5.

[0486] Step 4 The UE 3 tunes to a cell with RAN 5. I.e., the UE 3 gets out from an out of coverage area. For example, the UE 3 has traversed the big tree and the UE 3 can listen to the system information that a cell with the RAN 5 broadcasts.

[0487] At Step 4 the UE 3 compares the t and t_UE. 　　The t_UE is a pre-defined time period in the UE 3 since the UE 3 loses a signal from a cell with the RAN 5 at T1. A value of t_UE is referred by the UE 3 whether the UE 3 needs to send the Registration Request message to the AMF 70 to see if there is a page to the UE 3 during the UE 3 is out of coverage between T1 and T1+t_UE. 　　The t is an elapsed time since the UE 3 lost a signal from a cell with the RAN 5 at T1. 　　Since t is greater than t_UE at Step 4, the UE 3 decides to send the Registration Request message to the AMF 70. I.e., the UE stays out of coverage longer than the pre-defined period in the UE 3. 　　For example, if the t_UE is set to 10 seconds, the UE 3 does not expect a page to come to the UE3 while the UE 3 is out of coverage for 10 seconds.

[0488] Step 5. Based on the decision made in Steps 4, the UE 3 sends the Registration Request message to the AMF 70 including User ID, Resilient notification support and Resilient notification requested.

[0489] If the Resilient notification is activated to the UE 3, the AMF 70 accepts the Registration Request message from the UE 3 even the AMF 70 receives it too often than the periodic registration update timer (T3512) that the AMF 70 informed to the UE 3 as the T3512 value parameter in the Registration Accept message. 　　The following bullets explain each parameter in detail. - User ID: Refer to Step 4 in Fig. 9. - Resilient notification support: The Resilient notification support indicates that the UE 3 has a capability to support the Resilient notification support. In one example, the Resilient notification support may be expressed in the UE 5GMM Core Network Capability. - Resilient notification requested: The Resilient notification requested indicates that the UE 3 requests to activate the Resilient notification.

[0490] Step 6. The Registration procedure continues from Step 2 to 19c in section 4.2.2.2.2 in 3GPP TS 23.502 [4].

[0491] Step 7. The AMF 70 checks whether the Resilient notification is activated or not. If the Resilient notification is activated, the AMF 70 collects session related data (Example, DNN, S-NSSAI) that the Mobile Terminated (MT) Session Activation(s) failed due to no page response from the UE 3 between T1 and T1+t.

[0492] The AMF 70 sends the Registration Accept message to the UE 3 including 5G-GUTI and Resilient notification data.

[0493] The following bullets explain each parameter in detail. - 5G-GUTI: Refer to Step 15 in Fig. 9. - Resilient notification data: Refer to Step 10 in Fig. 21.

[0494] Step 8. Step 11 in Fig. 21 takes place.

[0495] <First Variant of the Fourth scenario in the Second example of the Second Aspect> 　　The disclosure in this scenario is equally applicable to the network where a RAN 5 is located in the Terrestrial Network.

[0496] <Third Aspect> 　　This aspect discloses mechanisms for a data communication with a downlink data landing to specific area from the satellite.

[0497] This aspect aims to solve the following issue with 3GPP system with satellite access. - For example, downlink data from the satellite may be landed anywhere in the FOV of satellite and this may result spreading downlink data unnecessarily too wide on earth. This can be an issue to users. For example, some users may want to avoid transmitting downlink data to areas that belong to adversarial nations or have geopolitical instability.

[0498] For example, a user requires for transmitting downlink data only to south part of Tamil Nadu state in India as illustrates in Fig. 23.

[0499] This aspect discloses mechanisms to make the targeting area for downlink data transmitting from the satellite possible. For example, this aspect may disclose mechanisms to make the targeting area for the UE 3 to receive downlink data transmitting from the satellite to UE 3 possible.

[0500] In this aspect, for example, the satellite may a HEO, GEO, MEO, LEO, HAPS or RAN 5 on grand for data communication. For example, the satellite is not limited to the HEO, GEO, MEO, LEO, HAPS or RAN 5.

[0501] <First example of the Third Aspect> 　　The First example of the First Aspect includes a mechanism for targeting an area for downlink data transmitting from the satellite.

[0502] <First scenario in the First example of the Third Aspect> 　　The First scenario in the First example of the Third Aspect includes a mechanism on system information that the RAN 5 may broadcast in case the RAN 5 (or a cell of the RAN 5) supports targeting an area for downlink data transmitting.

[0503] The disclosures that disclosed in the First scenario in the First example of the First Aspect may apply as the mechanism on system information with the following additions and modifications:

[0504] Steps 1 and 2 　　In addition to the parameters included in the System information in Steps 1 and 2 in figure 5, the System information may include at least one of the following parameters: - Targeting area for downlink data: The Targeting area for downlink data may indicate that the RAN 5 (or a cell of the RAN 5) supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. For example, Information on the Targeting area for downlink data may indicate that the RAN 5 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. - Targeting area for downlink data may have the following associated parameters; -- PLMN: The PLMN indicates an associated PLMN with the Targeting area for downlink data. The PLMN may be a PLMN based on the 5G Multi-Operator Core Network (5G MOCN) or a participating operator's PLMN based on the Indirect Network Sharing as defined in section 5.18.1 in 3GPP TS 23.501 [3]. -- Service time period: The Service time period indicates a time period where the Targeting area for downlink data is applicable. For example, the Service time period may be expressed by staring time in UTC and ending time in UTC. - Accuracy on Targeting area for downlink data: The Accuracy on Targeting area for downlink data may indicate an accuracy on Targeting area for downlink data that cells in the RAN 5 supports. - For example, the Accuracy can be expressed by Units for each of these are 1000Km, 100Km, 10Km and 1Km and other. The Accuracy can also be expressed by for example "Very Wide Area", "Medium Area", "Small Area", "Very Small Area" where these areas are configured by OAM (Operation And Management). 　　The Accuracy of Targeting area for downlink data may be described "the Range of Targeting area for downlink data". - Targeting area for page: The Targeting area for page may indicate that the RAN 5 supports a Paging mechanism for targeting an area for Page. For example, the information on Targeting area for page may indicate whether or not the RAN 5 supports a Paging mechanism for targeting an area for Page in this patent specification. - Targeting area for page may have the following associated parameters; -- PLMN: The PLMN indicates an associated PLMN with the Targeting area for page. The PLMN may be a PLMN based on the 5G Multi-Operator Core Network (5G MOCN) or a participating operator's PLMN based on the Indirect Network Sharing as defined in section 5.18.1 in 3GPP TS 23.501 [3]. -- Service time period: The Service time period indicates a time period where the Targeting area for page is applicable. For example, the Service time period may be expressed by staring time in UTC and ending time in UTC. - Accuracy on Targeting area for page: The Accuracy on Targeting area for page may indicate an accuracy on Targeting area for page that cells in the RAN 5 supports. - For example, the Accuracy can be expressed by Units for each of these are 1000Km, 100Km, 10Km and 1Km and other. The accuracy can also be expressed by for example "Very Wide Area", "Medium Area", "Small Area", "Very Small Area" where these areas are configured by OAM (Operation And Management). 　　The Accuracy on Targeting area for page may be described "the Range of Targeting area for page" in this disclosure.

[0505] <Second scenario in the First example of the Third Aspect> 　　The Second scenario in the First example of the Third Aspect includes the mechanism for targeting an area for downlink data transmitting from the satellite.

[0506] The disclosures that were disclosed in the Second scenario in the First example of the First Aspect may apply as the mechanism for the Subscribed data provisioning with the following additions and modifications:

[0507] Step 1-2 　　Additionally, the UDM 75 may hold at least one of the following data as a subscriber data and provide them to the AMF 70 in Step 1-2 or Step 2-2 in Fig. 6. - Targeting an area for downlink data subscribed: The Targeting an area for downlink data subscribed may indicate that the UE 3 has a valid subscription to the Targeting an area for downlink data transmitting function. For example, the Targeting an area for downlink data subscribed may indicate that the UE 3 is subscribed to the Targeting an area for downlink data transmitting function or service. - In one example, the Targeting an area for downlink data subscribed may apply to both the Targeting an area for downlink data function and the Targeting an area for page function. - Accuracy on Targeting area: The Accuracy on Targeting area may indicate the required accuracy on Targeting area for downlink data transmission. The Accuracy on Targeting area may be defined per DNN, per S-NSSAI or per combination of DNN and S-NSSAI which may be per PDU Session. - In one example, the Accuracy on Targeting area may apply to both the Targeting an area for downlink data function and the Targeting an area for page function.

[0508] <Third scenario in First example of the Third Aspect> 　　The Third scenario in First example of the Second Aspect includes a mechanism for a registration procedure for targeting an area for downlink data transmitting function.

[0509] The disclosures that are disclosed in the Third scenario in the First example of the First Aspect may apply as the mechanism for a registration procedure for targeting an area for downlink data transmitting function with the following additions and modifications:

[0510] Steps 4 and 5 　　In addition to the parameters included in the Registration request message in Steps 4 and 5 in figure 8, the Registration request message may include at least one of the following parameters: - Targeting an area for downlink data support: The Targeting an area for downlink data support may indicate that the UE 3 has a capability to support the Targeting an area for downlink data transmitting. In one example, the Targeting an area for downlink data support may be expressed in the UE 5GMM Core Network Capability. - In one example, the Targeting an area for downlink data support may apply to both the Targeting an area for downlink data function and the Targeting an area for page function. - Targeting an area for downlink data requested: The Targeting an area for downlink data requested may indicate that the UE 3 requests to activate the Targeting an area for downlink data transmitting function. - In one example, the Targeting an area for downlink data requested may apply to both the Targeting an area for downlink data function and the Targeting an area for page function.

[0511] Steps 6 and 8 　　In addition to the parameters included in the Nudm service messages in Steps 6 and 8 in figure 8, the Nudm service messages may include the following parameters. - Targeting an area for downlink data support: Refer to Step 4 above in the third scenario in first example of the third aspect.

[0512] Step 9 　　In addition to the parameters included in the Nudm service response messages in Step 9 in figure 8, the Nudm service response message may include at least one of the following parameters. - Targeting an area for downlink data subscribed: The Targeting an area for downlink data subscribed may indicate that the UE 3 has a valid subscription to the Targeting an area for downlink data transmitting function. - In one example, the Targeting an area for downlink data subscribed may apply to both the Targeting an area for downlink data function and the Targeting an area for page function. - Accuracy on Targeting area subscribed: The Accuracy on Targeting area subscribed may indicate that a subscribed accuracy on Targeting area for downlink data transmission. The Accuracy on Targeting area may be defined per DNN, per S-NSSAI or per combination of DNN and S-NSSAI which may be per PDU Session. - In one example, the Accuracy on Targeting area subscribed may apply to both the Targeting an area for downlink data function and the Targeting an area for page function.

[0513] Step 15 　　In addition to the parameters included in the Registration Accept message in Step 15 in figure 8, the Registration Accept message may include at least one of the following parameters. - Targeting an area for downlink data activated: The Targeting an area for downlink data activated may indicate that the Targeting an area for the downlink data transmitting function has been activated. - In one example, the Targeting an area for downlink data activated may apply to both the Targeting an area for downlink data function and the Targeting an area for page function. - Accuracy on Targeting area subscribed: Refer to Step 9 above in the third scenario in first example of the third aspect.

[0514] <Fourth scenario in First example of the Third Aspect> 　　The Fourth scenario in First example of the Third Aspect includes a mechanism for a capability negotiation between the RAN 5 and the AMF 70 for the support of targeting an area for downlink data transmitting function.

[0515] The disclosures that are disclosed in the Seventh scenario in the First example of the First Aspect may apply as the mechanism for the capability negotiation between the RAN 5 and the AMF 70 with the following additions and modifications:

[0516] Steps 1 　　In addition to the parameters included in the NG Setup Request message in Step 1 in figure 13, the NG Setup Request message may include at least one of the following parameters: - Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect.

[0517] The Targeting area for downlink data may indicate that the RAN 5 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. For example, the Targeting area for downlink data may indicate whether or not the RAN 5 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. - Accuracy on Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Accuracy on Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect.

[0518] <Fifth scenario in First example of the Third Aspect> 　　The Fifth scenario in First example of the Third Aspect includes a mechanism for a capability negotiation between the RAN 5 and the AMF 70 for the support of the targeting an area for downlink data transmitting function. (AMF 70 initiated)

[0519] The disclosures that are disclosed in the Eighth scenario in the First example of the First Aspect may apply as the mechanism for the capability negotiation between the RAN 5 and the AMF 70 with the following additions and modifications:

[0520] Steps 1 　　In addition to the parameters included in the AMF Configuration Update Acknowledge message in Step 1in figure 14, the AMF Configuration Update Acknowledge message may include at least one of the following parameters: - Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. 　　The Targeting area for downlink data may indicate that the RAN 5 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. For example, the Targeting area for downlink data may indicate whether or not the RAN 5 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. - Accuracy on Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Accuracy on Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect.

[0521] <Sixth scenario in First example of the Third Aspect> 　　The Sixth scenario in First example of the Third Aspect includes a mechanism for a capability negotiation between the RAN 5s (RAN 501 and RAN 502) for the support of the targeting an area for downlink data transmitting function.

[0522] The disclosures that are disclosed in the Ninth scenario in the First example of the First Aspect apply as the mechanism for the capability negotiation between the RAN 5s with the following additions and modifications:

[0523] Step 1 　　In addition to the parameters included in the XN Setup Request message in Step 1 in figure 15, the XN Setup Request message may include at least one of the following parameters: - Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect.

[0524] For example, The Targeting area for downlink data may indicate that the RAN 501 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. For example, the Targeting area for downlink data may indicate whether or not the RAN 501 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. - Accuracy on Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Accuracy on Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect.

[0525] Step 2 　　In addition to the parameters included in the XN Setup Response message in Step 2 in figure 15, the XN Setup Response message may include at least one of the following parameters: - Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. 　　For example, The Targeting area for downlink data may indicate that the RAN 502 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. For example, the Targeting area for downlink data may indicate whether or not the RAN 502 supports a Data Radio Bearer (DRB) or QoS Flow or PDU Session targeting an area for downlink data transmission. - Accuracy on Targeting area for downlink data: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect. - Accuracy on Targeting area for page: Refer to Steps 1 and 2 in the First scenario in the First example of the Third Aspect.

[0526] <Seventh scenario in the First example of the Third Aspect> 　　The Seventh scenario in the First example of the Third Aspect includes a mechanism for a Mobile Originated (MO) Session Activation procedure with targeting an area for downlink data transmitting function.

[0527] Fig. 24 and Fig. 25 illustrate an example of a call flow for the Mobile Originated (MO) Session Activation procedure with targeting an area for downlink data transmitting function.

[0528] Note: Due to space limitation, the Mobile Originated (MO) Session Activation accessing procedure with the targeting an area for downlink data transmitting function is illustrated in two figures, Fig. 24 and Fig. 25. i.e., Step 11 in Fig. 25 is a next step to take after Step 10 in Fig. 24. Fig. 24 and Fig. 25 should originally be drawn as a single figure, but for drawing convenience, they have been separated into two figures.

[0529] The detailed processes of this scenario are described below with reference to both Fig. 24 and Fig. 25.

[0530] Step 0-1. Steps 1 to 3 in Fig. 5 take place. 　　Based on the received Targeting area for page, Accuracy on Targeting area for page, Targeting area for downlink data and Accuracy on Targeting area for downlink data over the system information, the UE 3 recognizes that the Targeting an area for downlink data transmitting function may be activated with a cell with the RAN 5.

[0531] Refer to Step 1 in the First scenario in First example of the Third Aspect for parameter details.

[0532] Step 0-2. The NG Setup procedure with targeting an area for downlink data transmitting function or / and the AMF Configuration Update procedure with targeting an area for downlink data transmitting function may be performed.

[0533] With this capability negotiation between the RAN 5 and the AMF 70, the AMF 70 recognizes that the Targeting an area for downlink data transmitting function may be activated with the RAN 5.

[0534] Step 0-3. The UE 3 registers with AMF 70 (5G-GUTI 1 assigned) and targeting an area for downlink data transmitting function is activated.

[0535] Step 1. The UE 3 sends the RRC Setup request message to the RAN 5.

[0536] Step 2. The RAN 5 sends the RRC Setup message to the UE 3 which may include Targeting area for page, Accuracy on Targeting area for page, Targeting area for downlink data and Accuracy on Targeting area for downlink data. For example, the RAN 5 may send the RRC Setup message to the UE 3 which may include at least one of Targeting area for page, Accuracy on Targeting area for page, Targeting area for downlink data and Accuracy on Targeting area for downlink data.

[0537] Refer to Step 1 in the Sixth scenario in First example of the Third Aspect for parameter details.

[0538] Step 3. The UE 3 sends the RRC Setup Complete message to the RAN 5 which may include Targeting an area for downlink data requested, GNSS location and Dedicated NAS. The Dedicated NAS may include the UL NAS Transport message. The UL NAS Transport message may include PDU Session ID, DNN, S-NSSAI, Targeting an area for downlink data requested, GNSS location and NAS. Further, the NAS may include the PDU Session Establishment Request message. The PDU Session Establishment Request message may include at least one of User ID, Targeting an area for downlink data requested and GNSS location.

[0539] The following bullets explain each parameter in detail. - User ID: Refer to Step 4 in Fig. 9. - PDU Session ID: Refer to Step 5 in Fig. 11. - 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. - Targeting an area for downlink data requested: Refer to Step 1 in the Sixth scenario in First example of the Third Aspect. - 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.

[0540] Step 4. The RAN 5 sends the Initial UE message which may include NAS PDU. The NAS PDU may include the UL NAS Transport message that is received from the UE 3 in Step 3.

[0541] Step 5. 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 Session ID, DNN, S-NSSAI, Targeting an area for downlink data requested and GNSS location, the AMF 70 selects an SMF that supports the targeting an area for downlink data transmitting function that is disclosed by this disclosure.

[0542] 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, Targeting an area for downlink data requested, GNSS location and PDU Session Establishment Request message.

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

[0544] Step 7. The SMF 71 sends an Nudm_SDM_Get message to the UDM 75 including at least one of the User ID, DNN, S-NSSAI and Targeting an area for downlink data support.

[0545] Step 8. 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 includes the following parameters. - Targeting an area for downlink data subscribed: Refer to Step 9 in Third scenario in First example of the Third Aspect. - In one example, the Targeting an area for downlink data subscribed is applicable only to the DNN, S-NSSAI or combination of DNN and S-NSSAI that are indicated in Step 7. - Accuracy on Targeting area subscribed: Refer to Step 9 in Third scenario in First example of the Third Aspect. - In one example, the Accuracy on Targeting area subscribed is applicable only to the DNN, S-NSSAI or combination of DNN and S-NSSAI that are indicated in Step 7.

[0546] Step 9. 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, Targeting an area for downlink data support.

[0547] Step 10. 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.

[0548] Upon reception of the Npcf_SMPolicyControl_Create Response message from the PCF 73, the SMF 71 examines the received PCC rule.

[0549] Step 11. The SMF 71 sends the N4 Session Establishment request message to the UPF 72 to assign user plane resources in the UPF 72 that is used for the PDU Session being created.

[0550] Step 12. After successful user plane resource assignment in the UPF 72, the UPF 72 sends the N4 Session Establishment response message to the SMF 71.

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

[0552] The N2 SM information includes PDU Session ID, Authorized QoS rules, Targeting an area for downlink data activated and Accuracy on Targeting area for downlink data requested.

[0553] The N1 SM container includes PDU Session Establishment Accept message that includes Authorized QoS rules, Targeting an area for downlink data activated and Accuracy on Targeting area for downlink data requested.

[0554] The following bullets explain each parameter in detail. - PDU Session ID: Refer to Step 5 in Fig. 11. - Authorized QoS rules: 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.501

[0012] . - Targeting an area for downlink data activated: The Targeting an area for downlink data activated indicates that the SMF 71 is ready to activate the Targeting an area for downlink data transmitting. - Accuracy on Targeting area for downlink data requested: The Accuracy on Targeting area for downlink data requested indicates a requested accuracy on Targeting area for downlink data. An accuracy data may be decided based on the Accuracy on Targeting area subscribed in the UDM 75. The Accuracy on Targeting area for downlink data requested may be dedicated accuracy for the DNN, S-NSSAI or combination of DNN and S-NSSAI.

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

[0556] The N2 SM information includes Authorized QoS rules, Targeting an area for downlink data activated, Accuracy on Targeting area for downlink data requested, Shape for downlink data and N1 SM container. Further N1 SM container includes DL NAS Transport message.

[0557] The DL NAS Transport message may include NAS.

[0558] The NAS may include PDU Session Establishment Accept message including Authorized QoS rules, Targeting an area for downlink data activated and Accuracy on Targeting area for downlink data requested.

[0559] The following bullets explain each parameter in detail. - Authorized QoS rules: 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.501

[0012] . - Targeting an area for downlink data activated: The Targeting an area for downlink data activated indicates that the Targeting an area for downlink data transmitting is activated for the PDU Session. For example, the AMF 70 may set this parameter if the SMF 71 is ready to activate the Targeting an area for downlink data transmitting function. For example, the AMF 70 may set this parameter only if the SMF 71 is ready to activate the Targeting an area for downlink data transmitting function. - Accuracy on Targeting area for downlink data requested: The Accuracy on Targeting area for downlink data requested indicates a requested accuracy on Targeting area for downlink data. An accuracy data may be decided based on the Accuracy on Targeting area subscribed in the UDM 75 and supported accuracy by cells with the RAN 5. - The Accuracy on Targeting area for downlink data requested may be dedicated accuracy for the DNN, S-NSSAI or combination of DNN and S-NSSAI which may be per PDU Session. - Shape for downlink data: The Shape for downlink data indicates an area that the downlink data can land. - The Shape for downlink data may be expressed by a list of TAC, a list of cell identities, a shape with Polygon. - In addition, the Shape for downlink data may be expressed by a combination of the expressions as listed in the following bullets. - The following bullets explain how the Shape for downlink data may be expressed. -- List of TAC: The list of TAC is composed of one or multiple Tracking Area Codes, TAC supported by the RAN 5. The list of TAC may be the same as Registration Area (RA) for the UE 3. -- List of cell identities: The list of cell identities is composed of one or multiple cell identities. The cell identity may be a NR Cell Identity (NCI) or E-UTRAN Cell Identity (ECI) as defined in 3GPP TS 23.003 [5]. -- Shape with Polygon: The Shape is expressed by the polygon according to the 3GPP TS 23.032 [6]. -- See the Fig. 26 illustrates an example of geographical location expressed by the polygon.

[0560] Step 15. Upon reception of the N2 PDU Session request message from the AMF 70, RAN 5 stores the received data.

[0561] The RAN 5 confirms that the current cell with current beam pattern is compliant with the Shape for downlink data for downlink data landing. If not, the RAN 5 may perform the beam forming to make it compliant with the Shape for downlink data.

[0562] In one example, the RAN 5 may perform the cell re-selection procedure to make it compliant with the Shape for downlink data.

[0563] In one example, the RAN 5 may perform beam forming based on the Shape for downlink data.

[0564] Step 16. The RAN 5 sends, to the UE 3, the RRC signalling message including DL NAS Transport message. 　　The NAS Transport message includes NAS. The NAS includes PDU Session Establishment Accept message. The PDU Session Establishment Accept message includes Targeting an area for downlink data activated and Accuracy on Targeting area for downlink data requested.

[0565] Step 17. After successful the PDU Session establishment procedure, User plane has been established between UE 3 and UPF 71 via the RAN 502 and UE 3 communicates with AF 201 with the down link packet landing limited to a geographical area as described by the Shape for downlink data.

[0566] <First Variant of the Seventh scenario in the First example of the Third Aspect> 　　The call flow for the Mobile Originated (MO) Session Activation procedure accessing with with the Targeting an area for downlink data transmitting function illustrated in both Fig. 24 and Fig. 25 are fairly referred to the UE triggered Service request procedure with the following replacements: - In Steps 3, 4 and 5, the PDU Session Establishment Request messages are replaced with the Service Request messages. - In Steps 13, 14 and 16, the PDU Sessin Establishment Accept messages are replaced with the Service Accept messages. - In Step9, the Npcf_SMPolicyControl_Create message is replaced with the Npcf_SMPolicyControl_Modify message. - In Step10, the Npcf_SMPolicyControl_Create response message is replaced with the Npcf_SMPolicyControl_Modify response message.

[0567] <Second Variant of the Seventh scenario in the First example of the Third Aspect> 　　The disclosure in this scenario is equally applicable to the network where a RAN 5 is located in the Terrestrial Network.

[0568] <Eighth scenario in the First example of the Third Aspect> 　　The Eighth scenario in the First example of the Third Aspect includes a mechanism for a Mobile Terminated (MT) Session Activation procedure for the UE 3 is in Idle mode state with the Targeting an area for page function.

[0569] Fig. 27 illustrates an example of a call flow for the Mobile Terminated (MT) Session Activation procedure for the UE 3 is in Idle mode state with the Targeting an area for page function.

[0570] The detailed processes of this scenario are described below with reference to Fig. 27.

[0571] Step 0-1. The PDU session is established for the UE 3 based on the PDU Session establishment procedure as disclosure in Seventh scenario in the First example of the Third Aspect.

[0572] Step 0-2. The UE 3 becomes idle mode state. For example, due to user data inactivity.

[0573] Step 1. Downlink data arrives to the UPF 72.

[0574] Step 2. The UPF 72 sends the Data Notification to the SMF 71.

[0575] Step 3. Upon reception of the Data Notification message from the UPF 72, the SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 which may include SUPI, PDU Session ID, Targeting an area for page activated and Accuracy on Targeting area for page requested. For example, the Namf_Communication_N1N2MessageTransfer message may include at least one of SUPI, PDU Session ID, Targeting an area for page activated and Accuracy on Targeting area for page requested. 　　The following bullets explain each parameter in detail. - SUPI: Refer to Step 6 in Fig. 9. - PDU Session ID: Refer to Step 5 in Fig. 11. - Targeting an area for page activated: The Targeting an area for page activated indicates that the SMF 71 is ready to activate the Targeting an area for page function. - Accuracy on Targeting area for page requested: The Accuracy on Targeting area for page requested indicates a requested accuracy on Targeting area for page. An accuracy data may be decided (or determined or considered) based on the Accuracy on Targeting area subscribed in the UDM 75. The Accuracy on Targeting area for downlink data requested may be dedicated accuracy for the DNN, S-NSSAI or combination of DNN and S-NSSAI.

[0576] Step 4, Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends the Paging message to RAN 5 which may include UE Paging Identity, Targeting an area for page activated, Accuracy on Targeting area for page requested and Shape for page. For example, the Paging message may include at least one of UE Paging Identity, Targeting an area for page activated, Accuracy on Targeting area for page requested and Shape for page.

[0577] The AMF 70 may decide (or determine or consider) the Shape for page based on the last known UE location. For example, the AMF 70 may decide (determine or consider) the Shape for page based on a last known User Location Information received from the RAN 5 in NGAP interface or a last known GNSS location received from the UE 3 in NAS message.

[0578] The following bullets explain each parameter in detail. - UE Paging Identity: Refer to Step 4 in Fig. 12. - Targeting an area for page activated: The Targeting an area for page activated indicates that the Targeting an area for page is activated for the PDU Session. The AMF 70 may set this parameter if the SMF 71 is ready to activate the Targeting an area for page function. For example, the AMF 70 may set this parameter only if the SMF 71 is ready to activate the Targeting an area for page function. - Accuracy on Targeting area for page requested: The Accuracy on Targeting area for page requested indicates a requested accuracy on Targeting area for page. An accuracy data may be decided (or determined or considered) based on the Accuracy on Targeting area subscribed in the UDM 75 and supported accuracy by cells with the RAN 5. - The Accuracy on Targeting area for page requested may be dedicated (or determined or considered) accuracy for the DNN, S-NSSAI or combination of DNN and S-NSSAI. - Shape for page: The Shape for page indicates an area that the page can land. - The Sape for page may be expressed by a list of TAC, a list of cell identities, a shape with Polygon. Refer to Step 14 in Fig. 25 for each expression.

[0579] Steps 5 and 6. Based on Shape for page, RAN 5 performs the page with cells that belongs to the RAN 5. The RAN 5 confirms (or determines or considers) that an area to page is compliant with the Shape for page. In order to do so, the RAN 5 may perform the beam forming to make it compliant with the Shape for page. For example, RAN 5 may perform the beam forming based on the information on the Shape for downlink data. For example, RAN 5 may perform a paging with a UE in a cell belonging to the RAN 5.

[0580] Step 7. User plane is established between UE and UPF and UE communicates with AF 201 based on the Service Request procedure as disclosed by the First Variant of the Seventh scenario in the First example of the Third Aspect.

[0581] <First Variant of the Eighth scenario in the First example of the Third Aspect> 　　In Steps 5 and 6 in figure 26, in order to compliant to the Shape with Polygon, cells with the RAN 5 in the satellite may performs the multiple pages with high beam forming with changing beaming size and paging area. 　　In one example, the multiple pages with high beam forming with changing beaming size and paging area is illustrated in Fig. 28.

[0582] The detailed processes of the multiple pages with high beam forming with changing beaming size and paging area are described below with reference to Fig. 28.

[0583] The prerequisite for this variant is follows: - A cell in the satellite is able to cover entire shape expressed by Polygon or circle with a circular shape. However, page lands outside of the area with this circular shape. - The cell in the satellite is able to perform the beamforming with the Accuracy of 100Km radius. 　　Step 1. The RAN 5 receives the Paging message from AMF 70 including UE Paging Identity, Targeting an area for page activated, Accuracy on Targeting area for page requested and Shape for page. The Shape with Polygon is used for Shape for page as illustrated in points A to G in Fig. 28, but the Shape for page is not limited to the polygon. For example, the Shape with circle may be used for Shape for page. 　　The RAN 5 instructs (or performs) to a cell to perform the multiple pages with high beam forming with changing beaming size and paging area.

[0584] Step 2. In the first Paging Occasion for the UE3, the cell performs the beamforming to an area close to the point A, B and E and control an RF power to reach 500 Km radius and perform the page.

[0585] Step 3. In the second Paging Occasion for the UE3, the cell performs the beamforming to an area close to the point E, F and G and control the RF power to reach 200 Km radius and perform the page.

[0586] Step 4. In the third Paging Occasion for the UE3, the cell performs the beamforming to an area close to the point B, C and D and control the RF power to reach 100 Km radius and perform the page.

[0587] The UE 3 may be paged by any of Step 2, Step 3 and Step 4 with complying to the Shape for page. 　　With the multiple pages with high beam forming with changing beaming size and paging area, the page targeting to the Shape with Polygon may be achieved.

[0588] For another example, the Steps 2 to 4 take place in every paging DRX cycle.

[0589] <Second Variant of the Eighth scenario in the First example of the Third Aspect> 　　The disclosure in this scenario is equally applicable to the network where a RAN 5 is located in the Terrestrial Network.

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

[0591] 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.

[0592] 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).

[0593] 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.

[0594] 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'.

[0595] 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.

[0596] 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).

[0597] 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).

[0598] 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).

[0599] 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).

[0600] 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.

[0601] 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) 7A. 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 7A for the roaming-out UE 3.

[0602] 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.

[0603] 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 7A for the roaming-out UE 3.

[0604] 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.

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

[0606] 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).

[0607] 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.

[0608] 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)A...

Claims

A method for a radio terminal comprising:　　receiving, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information; and　　receiving, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.　　A method for a radio terminal comprising:　　communicating with an Access and Mobility Management Function (AMF); and　　receiving, from the AMF, information for provisioning, the information is related to communication with multiple-orbit satellites.　　A method for a radio terminal comprising:　　communicating with Policy Control Function (PCF); and　　receiving, from the PCF, information for provisioning, the information is related to communication with multiple-orbit satellites.　　A method for a radio terminal comprising:　　communicating with Access Function (AF); and　　receiving, from the AF, information for provisioning, the information is related to communication with multiple-orbit satellites.　　A method for a radio terminal comprising:　　communicating with a Unified Data Management Function (UDM); and　　receiving, from the UDM, information for provisioning, the information is related to communication with multiple-orbit satellites.　　A method for a radio terminal comprising:　　receiving, from a base station, satellite related information,　　sending, to the base station, a Radio Resource Control (RRC) setup request message,　　receiving, from the base station, a RRC setup message including the satellite related information; and　　sending, to the base station, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT) ,　　receiving, from an Access and Mobility Management Function (AMF), at least one of information indicating subscribed multi orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use , and information indicating the Tracking Area where the radio terminal is requested to stay; and　　electing a satellite based on the information indicating subscribed multi orbit satellite access profile.　　A method for a base station comprising:　　sending, to a radio terminal, satellite related information,　　receiving, from the radio terminal, a Radio Resource Control (RRC) setup request message,　　sending, to the radio terminal, a RRC setup message including the satellite related information,　　receiving, from the radio terminal, a RRC message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT); and　　sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT.　　A method for an Access and Mobility management Function (AMF) comprising:　　receiving, from a base station, a message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response, information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT),　　sending, to a Unified Data Management Function (UDM), a registration request message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT,　　receiving, from the UDM a registration response message,　　sending, to the UDM, a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, the information indicating that the radio terminal supports to receive a page with the RAT,　　receiving, from the UDM, a response message including at least one of information related to a first multi-orbit satellite access profile, information indicates that a radio terminal has a valid subscription to redirected page response function, and information indicate that the radio terminal has a valid subscription to the Radio Access Type (RAT) indication in a page function　　sending, to a Policy Control Function (PCF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, and information indicating support for redirected page response,　　receiving, from the PCF, a message,　　receiving, from the PCF, information related to a second multiple-orbit satellite profile,　　sending, to the radio terminal the information related to the second multiple-orbit satellite profile; and　　sending, to the radio terminal, at least one of information indicating subscribed multi-orbit satellite access profile, information indicating redirect page response function is ready to use, information indicating Radio Access Type (RAT type) indication in a page function is ready to use, and information indicating the Tracking Area where the radio terminal is requested to stay.　　A method for a second base station relate to a second satellite comprising:　　receiving, from a radio terminal, a Radio Resource Configuration (RRC) Setup Request message,　　sending, to the radio terminal ,a Radio Resource Configuration (RRC) Setup message including satellite related information,　　receiving, from the radio terminal , a Radio Resource Configuration (RRC) message including at least one of information indicating support for communication with multiple-orbit satellites, information indicating support for redirected page response and information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT);and　　sending, to an Access and Mobility management Function (AMF), a message including at least one of the information indicating support for communication with multiple-orbit satellites, the information indicating support for redirected page response, and the information indicating that the radio terminal supports to receive a page with a Radio Access Type (RAT).　　A radio terminal comprising:　　means for receiving, from a first radio station related to a first satellite, at least one of Non-Terrestrial Network Radio Access Type (NTN RAT type) information, Satellite Service provider information, Satellite Service name information, Satellite identifier, information indicating support for communication with multiple-orbit satellites, first Tracking Area Code (TAC) information, Satellite Service operator information; and　　means for receiving, from a second radio station related to a second satellite, at least one of the Non-Terrestrial Network Radio Access Type (NTN RAT type) information, the Satellite Service provider information, the Satellite Service name information, the Satellite identifier, the information indicating support for communication with multiple-orbit satellites, second Tracking Area Code (TAC) information.

Images