[go: up one dir, main page]

WO2025041508A1 - Method of first core network node and first core network node - Google Patents

Method of first core network node and first core network node Download PDF

Info

Publication number
WO2025041508A1
WO2025041508A1 PCT/JP2024/026251 JP2024026251W WO2025041508A1 WO 2025041508 A1 WO2025041508 A1 WO 2025041508A1 JP 2024026251 W JP2024026251 W JP 2024026251W WO 2025041508 A1 WO2025041508 A1 WO 2025041508A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
amf
ran
network
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2024/026251
Other languages
French (fr)
Inventor
Kundan Tiwari
Toshiyuki Tamura
Iskren Ianev
Sadafuku Hayashi
Hisashi Futaki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Publication of WO2025041508A1 publication Critical patent/WO2025041508A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present disclosure relates to a method of a first core network node, and a first core network node etc.
  • NPL 2 there is a potential service requirement related to the 5G system with satellite access taking into account new capabilities such as a Store and Forward Satellite operation for delay-tolerant communication services and a UE-Satellite-UE communication without going through the ground network.
  • NPL 1 3GPP TR 21.905: "Vocabulary for 3GPP Specifications", V17.1.0 (2021-12)
  • NPL 2 3GPP TR 22.865: “Study on satellite access Phase 3", V19.0.0 (2023-06)
  • NPL 3 3GPP TR 38.821: "Solutions for NR to support non-terrestrial networks (NTN) ", V16.2.0 (2023-03)
  • NPL 4 3GPP TS 23.501: "System architecture for the 5G System (5GS)", V18.1.0 (2023-03)
  • NPL 5 3GPP TS 23.502: “Procedures for the 5G System (5GS)", V18.1.1 (2023-04)
  • NPL 6 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2", V18.1.0 (2023-03)
  • NPL 7 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS) Stage 3", V
  • the following service requirement has not been supported by the 5GS yet.
  • satellite access taking into account new capabilities such as a Store and Forward Satellite operation for delay-tolerant communication services and a UE-Satellite-UE communication without going through the ground network.
  • the present disclosure provides a method of a first core network node comprising: sending, to a second core network node, a first message including information related to Feeder link.
  • the present disclosure provides a first core network node comprising: means for sending, to a second core network node, a first message including information related to Feeder link.
  • Fig. 1 is a diagram illustrating a configuration example of a gNB processed payload model of a First Aspect.
  • Fig. 2 is a diagram illustrating a configuration example of a gNB-DU processed payload model of a First Aspect.
  • Fig. 3 is a Signaling diagram of a First example of the First Aspect.
  • Fig. 4 is a Signaling diagram of a Second example of the First Aspect.
  • Fig. 5 is a Signaling diagram of a Third example of the First Aspect.
  • Fig. 6 is a Signaling diagram of a Third example of the First Aspect.
  • Fig. 1 is a diagram illustrating a configuration example of a gNB processed payload model of a First Aspect.
  • Fig. 2 is a diagram illustrating a configuration example of a gNB-DU processed payload model of a First Aspect.
  • Fig. 3 is a Signaling diagram of a First example of the First Aspect.
  • FIG. 7 is a Signaling diagram of a Fourth example of the First Aspect.
  • Fig. 8 is a Signaling diagram of a Fourth example of the First Aspect.
  • Fig. 9 is a Signaling diagram of a Fifth example of the First Aspect.
  • Fig. 10 is a Signaling diagram of a Sixth example of the First Aspect.
  • Fig. 11 is a Signaling diagram of a Seventh example of the First Aspect.
  • Fig. 12 is a Signaling diagram of an Eighth example of the First Aspect.
  • Fig. 13 is a Signaling diagram of a Ninth example of the First Aspect.
  • Fig. 14 is a Signaling diagram of a Tenth example of the First Aspect.
  • Fig. 15 is a diagram illustrating a configuration example of a mini VPLMN in satellite architecture of the Second Aspect.
  • Fig. 16 is a block diagram showing a configuration example of a UDM, AUSF and PCF integrated AMF architecture of a First example of the Second Aspect.
  • Fig. 17 is a Signaling diagram of a First example of the Second Aspect.
  • Fig. 18 is a Signaling diagram of a Second example of the Second Aspect.
  • Fig. 19 is a Signaling diagram of a Third example of the Second Aspect.
  • Fig. 20 is a Signaling diagram of a Fourth example of the Second Aspect.
  • Fig. 21 is a diagram illustrating a configuration example of a system overview.
  • Fig. 16 is a block diagram showing a configuration example of a UDM, AUSF and PCF integrated AMF architecture of a First example of the Second Aspect.
  • Fig. 17 is a Signaling diagram of a First example of the Second Aspect.
  • Fig. 22 is a block diagram illustrating a configuration example of a UE.
  • Fig. 23 is a block diagram illustrating a configuration example of an (R)AN node.
  • Fig. 24 is a diagram illustrating a configuration example of a System overview of (R)AN node based on O-RAN architecture.
  • Fig. 25 is a block diagram illustrating a configuration example of an RU.
  • Fig. 26 is a block diagram illustrating a configuration example of a DU.
  • Fig. 27 is a block diagram illustrating a configuration example of a CU.
  • Fig. 28 is a block diagram illustrating a configuration example of an AMF.
  • Fig. 29 is a block diagram illustrating a configuration example of an SMF.
  • Fig. 29 is a block diagram illustrating a configuration example of an SMF.
  • FIG. 30 is a block diagram illustrating a configuration example of a UPF.
  • Fig. 31 is a block diagram illustrating a configuration example of a PCF.
  • Fig. 32 is a block diagram illustrating a configuration example of an NWDAF.
  • Fig. 33 is a block diagram illustrating a configuration example of a UDM.
  • Fig. 34 is a block diagram illustrating a configuration example of an NRF.
  • Fig. 35 is a block diagram illustrating a configuration example of an NSACF.
  • Fig. 36 is a block diagram illustrating a configuration example of an AUSF.
  • Fig. 37 is a block diagram illustrating a configuration example of an AF.
  • NPL 1 definitions for the purposes of the present document, the terms and definitions given in NPL 1 and the following apply.
  • a term defined in the present document takes precedence over the definition of the same term, if any, in NPL 1.
  • 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.
  • An example object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problem.
  • the above-mentioned service requirement or a service achieved by the above-mentioned service requirement can be expressed as a support of ambient power-enabled Internet of Things, a support of Ambient IoT devices, a support of RFID devices, ambient power-enabled Internet of Things communication, Ambient IoT device communication, Ambient IoT device communication or Ambient IoT communication.
  • UEs need to communicate using satellite access without going to the ground network in order to avoid long delays and limited data rate as well as reducing the consumption of backhaul resources.
  • 5G system there is no mechanism in the current 5G system for supporting the UE-Satellite-UE communication.
  • a method of a first core network node includes sending, to a second core network node, a first message including Feeder link status information.
  • a first core network node includes means for sending, to a second core network node, a first message including Feeder link status information.
  • This aspect includes an architecture and mechanisms to learn the Store and Forward Satellite operation.
  • This aspect discloses mechanisms for the 5G system with satellite-access where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable, e.g., to provide communication service for UE(s) 3 under satellite coverage without a simultaneous active feeder link connection to the ground segment.
  • the RAN 5 complies with the Regenerative payload generic architecture as defined in NPL 3. Further there are two models of the Regenerative payload generic architectures, gNB processed payload model and gNB-DU, gNB-Distributed Unit, processed payload model.
  • Fig. 1 and Fig. 2 illustrate the gNB processed payload model and gNB-DU processed payload model respectively as an example.
  • the gNB 501 is located in the Satellite and the UE(s) 3 communicate with the gNB 501 using the Service link.
  • the NTN, Non-Terrestrial Network, Gateway 502 is located at terrestrial location and communicates with the gNB 501 using the Feeder link.
  • the NTN Gateway 502 communicates with the 5GC, 5G Core Network 7.
  • the RAN 5 includes the gNB 501 and the NTN Gateway 502.
  • the gNB-DU 61 is located in the Satellite and the UE(s) 3 communicate with the gNB-DU 61 using the Service link.
  • the NTN Gateway 502 is located at terrestrial location and communicates with the gNB-DU 61 using the Feeder link.
  • the NTN Gateway 502 communicates with the gNB-CU, gNB-Centralized Unit, 62.
  • the gNB-CU 62 communicates with the 5GC 7.
  • the RAN 5 includes the gNB-DU 61, the NTN Gateway 502 and the gNB-CU 62.
  • First example of the First Aspect Fig. 3 illustrates an example of the RAN initiated Interface Management Procedures for NGAP, Next Generation Application Protocol, interface.
  • the RAN 5 may be referred as the gNB 501.
  • the RAN 5 may be referred as the gNB-DU 61.
  • Step 1 The RAN 5 sends the NG Setup Request message including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • S&F support indicates that the RAN 5 supports Store and Forward, S&F, functionality.
  • the S&F support may indicate the S&F capability of the RAN 5.
  • the S&F capability of the RAN 5 may indicate that the RAN 5 supports the Store and Forward functionality. If the RAN 5 supports S&F functionality, the RAN 5 may perform as follows.
  • the RAN 5 may still communicate with the UE 3 and store the data or an RRC signalling message or a NAS signalling message received from the UE 3 and when the Feeder link becomes available, the RAN 5 forwards the stored data or the RRC signalling message or the NAS signalling message to the network via the Feeder link.
  • the RAN 5 may still communicate with the network via the Feeder link and store the received data for the UE 3 and when the Service link becomes available, the RAN 5 may forward the stored data to the UE 3 via the Service link.
  • the RRC signalling message or the NAS signalling message may be an RRC message or a NAS message encapsulated in the RRC message or the NAS message.
  • the data may be data packets received on an established DRB.
  • the List of Out of Service TAI indicates the list of Tracking Area Identity/Identities, TAI(s), and/or Tracking Area Code(s), TAC(s), of the Tracking Area(s) TA(s), which are not available due to the Feeder link not available or the Service link(s) to that TAI(s) and/or TAC(s) of the TA(s) are not available.
  • the TAC is part of the TAI.
  • the list of TAI(s) and/or TAC(s) which are not available may be expressed as the Out of Service TAI.
  • the Out of Service TAI may be embedded to Supported TAI.
  • the Supported TAI may indicate the Supported TA(s) in the RAN 5.
  • the List of Out of Service TAI may have associated time information.
  • the associated time information may indicate when the TAI(s) in the list are considered as not available and/or when the TAI(s) in the list are considered as available.
  • the List of Out of Service TAI may have Orbit characteristics information.
  • the Orbit characteristics information may indicate a TAI availability that corresponds to an Orbit of connected satellite where the RAN 5 or a part of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
  • the List of Out of Service TAI may indicate the list of TAI(s) supported by the RAN 5 but the service is not available due to the Feeder link or Service link is not available.
  • the Supported TAI list indicates the list of the profile(s) of the Supported TA(s) in the RAN 5. In addition to existing profile(s), the Supported TAI list includes the Feeder link status information and the Service link status information for each TA.
  • Feeder link status information indicates the status of the Feeder link that the TAI is associated with.
  • the Feeder link status information may include at least one of the following parameters: Feeder link identifier (Feeder link ID): The Feeder link identifier, the Feeder link ID, indicates an associated Feeder link with the TAI. There may be one instance or multiple instances.
  • Feeder link status The Feeder link status indicates whether the Feeder link is available or not.
  • Shut down time The Shut down time indicates when the Feeder link will become not available. It can be expressed as an absolute time or a relative time or an associated time.
  • Time to recovery The Time to recovery indicates when the Feeder link will become available. It can be expressed as an absolute time or a relative time or an associated time.
  • Orbit characteristics The Orbit characteristics indicate a Feeder link availability that corresponds to an Orbit of connected satellite where the RAN 5 or a port of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
  • Service link status information indicates the status of the Service link that the TAI is associated with.
  • the Service link status information may include at least one of the following parameters: Service link identifier (Service link ID): The Service link identifier, the Service link ID, indicates an associated Service link with the TAI. There may be one instance or multiple instances.
  • Service link status The Service link status indicates whether the Service link is available or not.
  • Shut down time The Shut down time indicates when the Service link will become not available. It can be expressed as an absolute time or a relative time or an associated time.
  • Time to recovery The Time to recovery indicates when the Service link will become available. It can be expressed as an absolute time or a relative time or an associated time.
  • Orbit characteristics The Orbit characteristics indicate a Service link availability that corresponds to an Orbit of connected satellite where the RAN 5 or a part of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
  • the Store and Forward capacity indicates buffer capacity.
  • the RAN 5 may indicate to the network function, NF, (e.g., AMF 70) the buffer capacity (e.g., in bytes) to store the data when the Feeder link is not available.
  • NF e.g., AMF 70
  • the buffer capacity e.g., in bytes
  • the RAN 5 sends the NG Setup Request message in the following cases: ⁇ The RAN 5 detects that a Feeder link associated with the TAI(s) becomes available or unavailable. ⁇ The RAN 5 changes the TAI(s) being broadcasted in the BCCH (e.g., SIB1) due to the satellite move. ⁇ The RAN 5 detects that a Service link associated with the TAI(s) becomes available or unavailable. ⁇ The NG-RAN TNL Association is updated.
  • Step 2 Upon reception of the NG Setup Request message from the RAN 5 in Step 1, the AMF 70 stores the received information from the RAN 5 and the AMF 70 sends the NG Setup Response message to the RAN 5 including S&F support indication as a parameter.
  • the S&F support indication may indicate that the AMF 70 and/or associated network function(s), NF(s), (e.g., at least one of SMF 71, UPF 72, and UDM 75) support Store and Forward functionality.
  • the AMF 70 and/or associated network function(s) will not transmit data more than the Store and Forward capacity of the RAN 5 when the Service link is not available.
  • the NG Setup Request message may be a RAN Configuration Update message or an existing NGAP message or a new NGAP message.
  • the NG Setup Response message may be a RAN Configuration Update Acknowledge message or an existing NGAP message or a new NGAP message.
  • Second example of the First Aspect Fig. 4 illustrates an example of the AMF initiated Interface Management Procedures for NGAP interface.
  • the RAN 5 may be referred as the gNB 501.
  • the RAN 5 may be referred as the gNB-DU 61.
  • the AMF 70 sends the AMF Configuration Update message to the RAN 5 including S&F support indication as a parameter.
  • the S&F support may indicate that the AMF 70 and/or associated NF(s) (e.g., at least one of SMF 71, UPF 72, and UDM 75) support the Store and Forward functionality.
  • the AMF 70 sends the AMF Configuration Update message in the following cases: ⁇
  • the AMF 70 and/or associated NF(s) e.g., at least one of SMF 71, UPF 72, and UDM 75
  • start supporting or start not supporting the Store and Forward functionality e.g., at least one of SMF 71, UPF 72, and UDM 75
  • start supporting or start not supporting the Store and Forward functionality e.g., at least one of SMF 71, UPF 72, and UDM 75
  • the AMF TNL Association is updated.
  • Step 2 Upon reception of the AMF Configuration Update message from the AMF 70 in Step 1, The RAN 5 stores the received information from the AMF 70 and the RAN 5 sends the AMF Configuration Update Acknowledge message including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • the RAN 5 Upon reception of the AMF Configuration Update message from the AMF 70 in Step 1, The RAN 5 stores the received information from the AMF 70 and the RAN 5 sends the AMF Configuration Update Acknowledge message including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • S&F support List of Out of Service TAI
  • Supported TAI list Supported TAI list
  • S&F capacity S&F capacity
  • Figs. 5 and 6 illustrate examples of the Echo message handling for N3 interface.
  • the RAN 5 may be referred as the gNB 501.
  • the RAN 5 may be referred as the gNB-DU 61.
  • Fig. 5 illustrates the Echo message sent from the RAN 5 as an example.
  • Step 1 The RAN 5 sends the Echo request message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • Step 2 Upon reception of the Echo request message from the RAN 5 in Step 1, the UPF 72 stores the received information from the RAN 5 and the UPF 72 sends the Echo Response message to the RAN 5 including S&F support indication as a parameter.
  • the S&F support indication may indicate that the UPF 72 and/or associated NF(s) (e.g., at least one of AMF 70, SMF 71, and UDM 75) support the Store and Forward functionality.
  • Fig. 6 illustrates the Echo message sent from the UPF 72 as an example.
  • Step 1 The UPF 72 sends the Echo request message to the RAN 5 including S&F support indication as a parameter.
  • the S&F support indication may indicate that the UPF 72 and/or associated NF(s) (e.g., at least one AMF 70, SMF 71, and UDM 75) support the Store and Forward functionality.
  • Step 2 Upon reception of the Echo request message from the UPF 72 in Step 1, the RAN 5 stores the received information from the UPF 72 and the RAN 5 sends the Echo Response message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • the RAN 5 Upon reception of the Echo request message from the UPF 72 in Step 1, the RAN 5 stores the received information from the UPF 72 and the RAN 5 sends the Echo Response message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • the UPF 72 may in advance subscribe with the RAN 5 for notifications (periodic or event based) related to the status of the Service link and/or the Feeder link.
  • the RAN 5 may regularly or based on an event (e.g., Service link status information and/or Feeder link status information change) notify the UPF 72 by sending the Echo request message as in step 1 of Fig. 5 or any other message (e.g., RAN Configuration Update message) with the purpose to notify any changes in the status of the Feeder link and/or the Service link.
  • an event e.g., Service link status information and/or Feeder link status information change
  • any other message e.g., RAN Configuration Update message
  • FIGs. 7 and 8 illustrate examples of the Error Indication message handling for N3 interface.
  • the RAN 5 may be referred as the gNB 501.
  • the RAN 5 may be referred as the gNB-DU 61.
  • Fig. 7 illustrates the Error Indication message sent from the RAN 5 as an example.
  • Step 1 The RAN 5 sends the Error Indication message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
  • Fig. 8 illustrates the Error Indication message sent from the UPF 72 as an example.
  • Step 1 The UPF 72 sends the Error Indication message to the RAN 5 including S&F support indication as a parameter.
  • the S&F support indication may indicate that the UPF 72 and/or associated NF(s) (e.g., at least one of AMF 70, SMF 71, and UDM 75) support the Store and Forward functionality.
  • FIG. 9 illustrates an example of the Registration procedure in a case where the RAN 5 or a part of RAN 5 is located in the satellite.
  • This example applies to both, the gNB processed payload model and the gNB-DU processed payload model.
  • Step 1 The NGAP Setup procedure between the RAN 5 and AMF 70 takes place as disclosed by First example of the First Aspect.
  • Step 2 The RAN 5 broadcasts at least one of the PLMN status information, Service link status information, S&F status information, Processed payload mode and Feeder link status in system information.
  • the RAN 5 may use at least one of SIB1, SIB19 (containing NTN related information) and new SIBx to broadcast.
  • PLMN status information indicates a status of the connectivity to the PLMN.
  • the connectivity depends on the status of the associated Feeder link(s) as the TNL (Transport Network Layer).
  • the PLMN status information may be connected status.
  • the PLMN status information may include at least one of the following parameters: PLMN ID (PLMN identifier): The PLMN ID indicates PLMN identifier. It may comply with MCC and MNC.
  • PLMN status The PLMN status indicates whether the 5GC for the PLMN is reachable or not.
  • Shut down time The Shut down time indicates when a connectivity to the PLMN will become unavailable.
  • the Shut down time can be expressed as an absolute time or a relative time or an associated time.
  • Time to recovery indicates when the connectivity to the PLMN will become available. For example, it depends on the associated Feeder link status.
  • the Time to recovery can be expressed as an absolute time or a relative time or an associated time.
  • Orbit characteristics The Orbit characteristics indicate the connectivity to the PLMN that corresponds to the Orbit of the connected satellite where the RAN 5 or a part of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
  • Service link status information indicates the status of the Service link that the TAI is associated with. Refer to Step 1 of Fig. 3 for parameter details.
  • the S&F status information indicates the status of Store and Forward functionality in the RAN 5.
  • the S&F status information may include at least one of the following parameters: S&F available: The S&F available indicates whether the use of the Store and Forward functionality is available or not.
  • S&F service The S&F service is associated information to the S&F available.
  • the S&F service indicates which service(s) are subject to the Store and Forward functionality being available.
  • the S&F service may be at least one of CIoT C-plane service, CIoT U-plane service, SMS service and Location service.
  • S&F overload The S&F overload indicates that the Store and Forward functionality is overloaded.
  • the UE 3 is requested to refer to an associated S&F backoff parameter in a case where the UE 3 needs to send the uplink data.
  • S&F backoff timer is an associated parameter to the S&F overload.
  • the S&F backoff timer may indicate a wait timer how long the UE 3 needs to deter from sending uplink data.
  • the S&F backoff timer may have a time information when the UE 3 is allowed to send the uplink data. For example, the time information may be broadcasted if the uplink data storage buffer in the RAN 5 is full or close to full but the associated Feeder link is not available but known by the RAN 5 when it will be available.
  • the Processed payload mode indicates the type of the Processed payload mode. For example, it may be Transparent payload, gNB payload, gNB+DU payload, gNB+DU+AMF payload or gNB+DU+AMF+UPF payload.
  • the processed payload mode may be used by the UE 3 to select the preferred satellite cell (i.e., satellite beam) when multiple satellite cells with different Processed payload are available in the UE 3's location.
  • Feeder link status information indicates the status of the Feeder link that the TAI is associated with. Refer to Step 1 of Fig.3 for parameter details.
  • the RAN 5 broadcasts whether the Feeder link is available or not.
  • Step 3 Based on the system information that is received from RAN 5 in Step 2, the UE 3 confirms that a target PLMN is reachable (e.g., the Feeder link is available) and decides to perform the Registration procedure towards the target PLMN.
  • a target PLMN e.g., the Feeder link is available
  • Step 4 The UE 3 sends a Registration Request message to the AMF 70 including at least one of User ID, and S&F support indication.
  • the User ID may be expressed as User Identity
  • the User ID may be a 5G-GUTI, SUCI or SUPI.
  • the S&F support indication indicates that the UE 3 supports the Store and Forward functionality.
  • the S&F support indication may indicate the S&F capability of the UE 3.
  • the S&F capability of the UE 3 may indicate that the UE 3 supports the Store and Forward functionality.
  • the S&F support indication may be expressed differently.
  • the S&F support indication may be expressed as Store and Forward support in the MM context, Delay tolerant IoT support, or UP Delay tolerant IoT support.
  • the UE 3 indicates that it supports S&F feature if the UE 3 supports at least one feature or one procedure defined in this disclosure.
  • the UE 3 also sends the S&F capability in an RRC message during an RRC procedure (e.g., in the RRC SETUP COMPLETE message during RRC connection establishment procedure).
  • the RAN 5 stores this capability and executes one of the procedure defined in this disclosure.
  • Step 5 Upon reception of the Registration Request message in step 4, the AMF 70 sends a Nudm_UECM_Registration message to a UDM 75 including at least one of SUPI and S&F support indication. Refer to Step 4 for parameter details.
  • the UDM 75 stores the S&F support indication from the UE 3. When the S&F capability indicates that the UE 3 supports S&F functions, then the UDM 75 may determine the UE 3 is delay tolerant UE. If the UDM 75 is in congestion, then UDM 75 may delay the processing of the signalling related to the UE 3 and the UDM 75 may prioritize the signalling or handling of other UEs 3 that are non-delay tolerant. The UDM 75 sends the Nudm_UECM_Registration response message to the AMF 70.
  • Step 7 After the completion of the Nudm_UECM_Registration service in steps 4 and 5, the AMF 70 sends a Nudm_SDM_Get Request message to the UDM 75 including at least one of SUPI and S&F support indication. Refer to Step 4 for parameter details.
  • Step 8 The UDM 75 finds the Subscriber data for the UE 3 and sends a Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3.
  • the Subscriber data includes the S&F profiles of the UE 3.
  • the S&F profile includes a subscribed profile when the UE 3 uses the Store and Forward functionality.
  • the S&F profile may be expressed differently. For example, Store and Forward profile, S&F user profile, Delay tolerant IoT profile, UP Delay tolerant IoT profile.
  • the S&F profile may include at least one of the following parameters: S&F allowed: The S&F allowed indicates whether the use of the Store and Forward functionality is allowed or not; S&F data retention period: The S&F data retention period indicates the maximum duration acceptable the UE 3 if the uplink data sent from the UE 3 is retained in the RAN 5.
  • S&F storage quota indicates the maximum data size that the UE 3 is allowed to send as uplink data in a case where the uplink data is to be stored in the RAN 5.
  • S&F priority indicates a relative priority when the UE 3 uses the Store and Forward functionality. For example, sending uplink data to the RAN 5 is allowed even the RAN 5 broadcasts that the Store and Forward functionality is suspended. For example, due to congestion in the RAN 5.
  • the S&F profile may be defined per an S-NSSAI in the subscribed NSSAI.
  • the S&F profile may be defined per a DNN in the subscriber data.
  • the S&F profile may be defined a S-NSSAI and DNN combination.
  • the AMF 70 may invoke service operation other than the Nudm_SDM_GET operation to indicate the S&F capability of the UE 3 to the UDM 75 and fetch the S&F profile from the UDM 75.
  • Step 9 After the AMF 70 obtains the Subscriber data for the UE 3 from the UDM 75 in step 8, the AMF 70 stores the received data, including S&F profile, to the MM context of the UE 3 in the storage of the AMF 70.
  • Step 10 The AMF 70 sends a Registration Accept message to the UE 3 including at least one of 5G-GUTI and S&F profile.
  • S&F profile refer to Step 8 for parameter details.
  • Step 11 Upon reception of the Registration Accept message from the AMF 70, the UE 3 stores the received data into non-volatile memory of the UE 3.
  • Step 12 The UE 3 sends the Registration Complete message to the AMF 70. Whenever the S&F profile is present in the Registration Accept message, the UE sends Registration Complete message.
  • the RAN 5 may broadcast the Time information (e.g., t-Service) on when a cell provided via NTN quasi-Earth fixed system is going to stop serving the area it is currently covering.
  • the Time information may indicate a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900).
  • the exact stop time is between the time indicated by the value of this field minus 1 and the time indicated by the value broadcasted.
  • the Time information is valid regardless of the PLMN in the cell. In other words, this is applicable all the PLMNs in the cell. If RAN 5 broadcasts the Time information and the Shut down time, the UE 3 capable of accessing a cell or RAN 5 supporting the S&F capability may ignore the Time information and may follow the Shut down time.
  • the RAN 5 may broadcast the Shut down time.
  • the Shut down time may indicate a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900).
  • the exact stop time is between the time indicated by the value of this field minus 1 and the time indicated by the value broadcasted.
  • the RAN 5 may broadcast the Time to recovery.
  • the Time to recovery may indicate a time multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900).
  • the exact recovery time is between the time indicated by the value of this field minus 1 and the time indicated by the value broadcasted.
  • the RAN 5 may broadcast one of some of the information of the above-mentioned PLMN status information by reusing the existing PLMN related information.
  • the SIB1 includes the PLMN-IdentityInfoList which further includes the PLMN-IdentityInfo per PLMN.
  • the PLMN-IdentityInfo may include the PLMN status.
  • This example applies to both, the gNB processed payload model and the gNB-DU processed payload model.
  • the PDU Session Establishment procedure is used to install the S&F profile to the SMF 71, UPF 72 and RAN 5 for the PDU Session.
  • the S&F profile may be used in a case where the Stored and Forward functionality is activated after the PDU Session has been established by this procedure.
  • Step 0. The UE 3 is connected to 5GC as both the Service link and the Feeder link are available.
  • Step 1 The UE 3 sends a UL NAS Transport message to the AMF 70 including at least one of PDU Session ID, S-NSSAI, S&F requested and NAS container that includes PDU Session Establishment Request message.
  • ⁇ PDU Session ID is an identifier of the PDU Session being established.
  • ⁇ S-NSSAI is a Single NSSAI that indicates a network slice.
  • ⁇ S&F requested indicates that the Store and Forward functionality is requested for the PDU Session in a case where the Store and Forward functionality is needed. The S&F requested may be included in the PDU Session Establishment Request message.
  • Step 2 Upon reception of the UL NAS Transport message from the UE 3, the AMF 70 performs the SMF selection based on the received S&F requested from the UE 3. The AMF 70 selects the SMF 71 that is capable to handle the Store and Forward functionality.
  • the AMF 70 sends the Nsmf_PDUSession_CreateSMContext Request message to the SMF 71 including at least one of PDU Session ID and S&F requested.
  • the S&F requested may be included in the PDU Session Establishment Request.
  • Step 3 The SMF 71 sends the Nsmf_PDUSession_CreateSMContext Response to the AMF 70.
  • Step 4 In a case where the SMF 71 does not hold the Session Management Subscriber data for the UE 3, The SMF 71 sends the Nudm_SDM_Get message to the UDM 75 including at least one of User ID, DNN, S-NSSAI and S&F requested.
  • the UDM 75 sends the Nudm_SDM_Get Response message to the SMF 71 including Session Management Subscriber data.
  • the Session Management Subscriber data may include S&F profile for the PDU Session being established.
  • Step 6 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 the Npcf_SMPolicyControl_Create message to the PCF 73 including at least one of User ID, S-NSSAI and S&F requested.
  • Step 7 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 the Npcf_SMPolicyControl_Create Response message to the SMF 71 including generated PCC Rule. The SMF 71 derives an ATSSS rule from the received PCC rule.
  • Step 8 The SMF 71 selects the UPF 72 based on the S&F requested in the Nsmf_PDUSession_CreateSMContext Request message in Step 2. Then, the SMF 71 sends the N4 Session Establishment Request message to the UPF 72 including at least one of PDU Session ID, S&F requested, S&F profile and ATSSS rule.
  • Step 9 The UPF 72 stores the received S&F profile. After successful installation of the ATSSS rule in the UPF 72, the UPF 72 sends the N4 Session Establishment Response message to the SMF 71.
  • Step 10 The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 including at least one of PDU Session ID, N2 SM information and N1 SM container.
  • the N2 SM information includes at least one of the PDU Session ID and S&F profile.
  • the N1 SM container includes the PDU Session Establishment Accept message including ATSSS rule.
  • the SMF 71 also sends an existing or a new message including S&F profile to the UPF 72.
  • the UPF 72 determines that the UPF 72 the Feeder link is down then the UPF 72 stores the data for the UE 3 as per the S&F profile.
  • the UPF 72 stores the MT user data and starts the retention timer. If the retention timer expires and the Feeder link is still not connected, then the UPF 72 discards the MT user data and indicate to the SMF 71 by including an information element in the existing message or by sending a new message. The information element indicates the cause of discarding the data.
  • Step 11 Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, The AMF 70 sends the N2 PDU Session Request message including PDU Session ID, S&F profile and N1 SM container that contains the PDU Session Establishment Accept message.
  • the PDU Session Establishment Accept message includes the ATSSS rule.
  • the RAN 5 stores the received S&F profile by associating with the PDU Session.
  • the S&F profile may be used later when the Store and Forward functionality is activated for the PDU Session.
  • the RAN 5 sends DL Information Transfer message.
  • the DL Information Transfer message may include dedicated NAS-Message that may include the PDU Session Establishment Accept message to the UE 3 including the ATSSS rule.
  • the UE 3 installs the received ATSSS rule in the UE 3.
  • Step 13 The RAN 5 sends the N2 PDU Session Response message to the AMF 70.
  • FIG. 11 illustrates an example of the MO-data sending using CIoT Control Plane (C-Plane) procedure.
  • This example applies to both the gNB processed payload model and the gNB-DU processed payload model.
  • Step 1 The UE 3 is registered with the AMF 70 and the PDU Session has been established with the S&F profile.
  • Step 1 The Feeder link that connects to the AMF 70 with the RAN 5 in the satellite is not available or become unavailable.
  • the UE 3 may stay in the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state in the RAN 5 after the Feeder link that connects to the AMF 70 with the RAN 5 in the satellite is not available or become unavailable.
  • the UE 3 may stay in the CM-IDLE state in the RAN 5.
  • the UE 3 may transit from the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state to the CM-IDLE state after the Feeder link that connects to the AMF 70 with the RAN 5 in the satellite is not available or become unavailable.
  • Step 2 The RAN 5 broadcasts at least one of the PLMN status information, Service link status information, S&F status information and Processed payload mode in system information.
  • Step 2 in Fig. 9 for information details in the system information.
  • the PLMN status information of the PLMN where the AMF 70 belongs to is set as not reachable.
  • the UE 3 may stay in the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state.
  • the UE 3 may stay in the CM-IDLE state.
  • the UE 3 may transit from the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state to the CM-IDLE state.
  • Step 3 The RAN 5 sends the NGAP message indicating that the Feeder link is not available or become unavailable.
  • the NGAP message may be the NGAP message that is disclosed in the First example of the First Aspect or any other existing message (e.g., RAN Configuration Update message) or new message on the N2 interface between the AMF 70 and the RAN 5.
  • the NGAP message may include a cause value (e.g., Feeder link not available).
  • all UEs 3 that are connected the RAN 5 may stay in the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state in the AMF 70.
  • the UE 3 may stay in the CM-IDLE state in the AMF 70.
  • the UE 3 may transit from the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state to the CM-IDLE state in the AMF 70.
  • Step 4 UE 3 confirms that the Feeder link is not available or the AMF 70 is not reachable but the Store and Forward functionality is active or available based on system information in Step 2.
  • the UE 3 may decide to send the MO-data to network.
  • the UE 3 may intend to send the MO-data to the AMF 70 via the RAN 5.
  • Step 5 The UE 3 sends the RRC Setup Request message to the RAN 5 including S&F related information.
  • the S&F related information may include at least one of S&F Priority, new Establishment Cause or new Logical Channel ID (LCID).
  • LCID Logical Channel ID
  • ⁇ S&F Priority indicates that the UE 3 has a high priority to send the MO-data even the system information in Step 7 restricts the MO-data handling (i.e., under S&F situation). For example, if the RRC Setup Request message includes the S&F Priority in the S&F related information, the UE 3 sends the MO-data even the system information in Step 7 restricts the MO-data handling.
  • ⁇ New Establishment Cause The new Establishment Cause indicates that the UE 3 has a high priority data to be sent even under S&F situation.
  • the new Establishment Cause may be highPriorityAccessStoreAndForward, mo-SignallingStoreAndForward, or mo-DataStoreAndForward, or storeAndForward-PriorityAccess.
  • ⁇ New LCID A new LCID value is used in the RRC Setup Request message, which indicates that the UE 3 has a high priority data to be sent even under S&F situation.
  • Step 6 Upon the reception of the RRC Setup Request message in Step 5, the RAN 5 sends the RRC Setup message to the UE 3.
  • Step 7 The UE 3 sends the RRC Message number 3 message to the RAN 5.
  • the RRC Message number 3 includes at least one of S&F Priority and Dedicated NAS.
  • the Dedicated NAS includes the Service Request message.
  • the Service Request message includes at least one of the User ID, the S&F Priority and the MO-data.
  • the MO-data may be embedded in the CIoT small data container or CIoT user data container.
  • Step 8 Upon reception of the RRC Message number 3 message from the UE 3, the RAN 5 confirms that the RAN 5 cannot send the Initial UE message to the AMF 70 due to the Feeder link to the AMF 70 is not available.
  • the RAN 5 stores the Dedicated NAS in the RAN 5 and starts the retention timer.
  • the RAN 5 may delete the stored Dedicated NAS message. Upon expiry of the retention timer the RAN 5 may release the RRC connection with the UE 3.
  • the UE 3 also indicates in an RRC message that the UE 3 has more NAS message(s) to send, in this case the RAN 5 will not release the RRC connection immediately and wait for the more RRC message from the UE 3.
  • the UE 3 has transmitted last NAS message it has then it indicates to the RAN 5 in an existing or a new RRC message including an indicator indicating that the UE 3 has no more RRC message(s) to send, in this case the RAN 5 releases the RRC connection.
  • Step 9 The Feeder link that connects the RAN 5 with the AMF 70 is available.
  • Step 10 The RAN 5 sends the NGAP message indicating that the Feeder link is available.
  • the NGAP message may be the NGAP message that is disclosed in the First example of the First Aspect or any other existing message (e.g., RAN Configuration Update message) or new message on the N2 interface between the AMF 70 and the RAN 5.
  • the RAN 5 In a case where the stored message is not transmitted to the AMF 70 (e.g., the retention time expires), the RAN 5 indicates this to the UE 3 by including an indicator in an existing RRC message or by sending a new RRC message. The message also indicates the cause of dropping of stored message, e.g., retention period expires. The RAN 5 also indicates this to the AMF 70 for a UE 3 that the UL NAS messages are dropped due to retention period expires or other related cause value.
  • Step 11 Upon the RAN 5 learning that the Feeder link that connects to the AMF 70 is available, the RAN 5 checks whether there are stored Dedicated NAS(s) message or container that needs to be sent to the AMF 70. If the RAN 5 holds Dedicated NAS(s) message or container that needs to be sent to the AMF 70, the RAN 5 sends the Initial UE message(s) to the AMF 70 for all held Dedicated NAS(s) one by one including S&F Priority and NAS PDU.
  • the NAS PDU includes the Service Request message.
  • the Service Request message includes S&F Priority and the MO-data.
  • the RAN 5 may send the MO-data to the UPF 72 using N3 connection (N3 tunnel).
  • Step 12 The AMF 70 sends the Nsmf_PDUSession_SendMOData message to the SMF 71 including MO-data.
  • Step 13 The SMF 71 forwards the received MO-data to the UPF 72 over User plane.
  • the UPF 72 communicates with the AF 201 or any server in data network for the CIoT communication.
  • the UPF 72 and the AF 201 may perform User data communication.
  • the UPF 72 may send Uplink MO-data to the AF 201, and the AF 201 may send Downlink MT-data to the UPF 72.
  • the UPF 72 may forward the MT-data over User plane if the UPF 72 receive the MT-data from the AF 201 during the CIoT communication in Step 14.
  • Step 16 The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70.
  • the Namf_Communication_N1N2MessageTransfer message my include the MT-data.
  • Step 17 The AMF 70 sends the Service Accept message to the UE 3.
  • the Service Accept message may include the MT-data.
  • the RAN 5 sends the Initial UE message(s) to the AMF 70 for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of uplink packet handling. For example, the RAN 5 sends the Initial UE message(s) to the AMF 70 every 30 seconds.
  • Step 7 if the PDU Session is a Multi Access PDU Session and the UE 3 has another 3GPP access or non-3GPP access that are connected to the UPF 72, the UE 3 sends the MO-data using another access instead of using the RAN 5 at the Satellite or some part of the RAN 5 is at the Satellite.
  • the UE 3 may include a new RRC establishment cause in the RRC Connection Establishment Request message to the RAN 5, e.g., 'S&F data' or any other notation for an RRC establishment cause in order to indicate to the RAN 5 that the UE 3 is aware of the Feeder link's unavailability and the UE 3 uses the 'S&F data' RRC establishment cause to request the RAN 5 to Store the data from the UE 3 and Forward it when the Feeder link becomes available. If the RRC establishment cause is set to 'S&F data' then the RAN 5 will store the NAS container sent in the RRC message.
  • a new RRC establishment cause in the RRC Connection Establishment Request message to the RAN 5 e.g., 'S&F data' or any other notation for an RRC establishment cause in order to indicate to the RAN 5 that the UE 3 is aware of the Feeder link's unavailability and the UE 3 uses the 'S&F data' RRC establishment cause to request the RAN 5
  • Variant 4 of Seventh example of the First Aspect The Store and Forward procedure defined in this disclosure also applies for the case when a DRB is established between the UE 3 and the RAN 5. This is the case the UE 3 and the RAN 5 were in RRC inactive mode and the UE 3 got user data to transmit. In this case the UE 3 will resume the DRB by sending RRC Resume message with establishment cause set to "S&F" and send the user data over the DRB to the RAN 5. The RAN 5 will move the UE 3 to RRC-INACTIVE mode for the DRB only when the S&F feature is supported by the UE 3, the RAN 5 and the 5GC.
  • NAS layer of the UE 3 may inform AS layer (e.g., RRC layer) of the UE 3 that there is the MO-data to be sent even the system information in Step 7 restricts the MO-data handling (i.e., under S&F situation).
  • AS layer e.g., RRC layer
  • the NAS layer of the UE 3 may indicate the S&F Priority to the AS layer of the UE 3.
  • FIG. 12 illustrates an example of the MT-data sending using CIoT Control Plane (C-Plane) procedure.
  • This example applies to both, the gNB processed payload model and the gNB-DU processed payload model.
  • Step 1 Steps 0 to 3 in Fig. 11 take place.
  • Step 2 The RAN 5 sends the Echo request message indicating that the Feeder link is not available or become unavailable.
  • the Echo request message may be the GTP-U message that is disclosed in the Third example of the First Aspect or any other existing message or new message on the RAN 5 to the UPF 72.
  • the Echo request message may include a cause value (e.g., Feeder link not available).
  • Step 3 Downlink packets to the UE 3 arrive at the UPF 72.
  • Downlink packets are sent from the AF 201.
  • Step 4 Upon reception of the Downlink packets in the UPF 72, the UPF 72 confirms that the UPF 72 cannot send the Downlink packets to the RAN 5. For example, due to the Feeder link is not available.
  • the UPF 72 stores the Downlink packets in the UPF 72 and starts the retention timer.
  • the UPF 72 may delete the stored Downlink packets.
  • Step 5 Step 5. Steps 9 to 10 in Fig. 11 take place.
  • Step 6 The RAN 5 sends the Echo request message indicating that the Feeder link is available.
  • the Echo request message may be the GTP-U message that is disclosed in the Third example of the First Aspect or any other existing message or new message on the RAN 5 to the UPF 72.
  • Step 7 Upon the UPF 72 learning that the Feeder link that connects to the RAN 5 is available, the UPF 72 checks where there are stored Downlink packets that needs to be sent to the RAN 5. If the UPF 72 holds Downlink packets that needs to be sent to the RAN 5, the UPF 72 initiates the UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedure as described in the Section 4.24.2 in NPL 5 for all PDU Sessions one by one.
  • the UPF 72 initiates the UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedure for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of downlink packet handling.
  • the AMF 70 informs to the UPF 72 via the SMF 71 that the Feeder link is not available when the AMF 70 receives the NGAP message in Step 3 of Fig. 11.
  • the AMF 70 informs to the UPF 72 via the SMF 71 that the Feeder link is not available when the AMF 70 receives the NGAP message in Step 10 of Fig. 11.
  • Fig. 13 illustrates an example of the MO-data sending using CIoT User Plane (U-Plane) procedure.
  • This example applies to both the gNB processed payload model and the gNB-DU processed payload model.
  • Step 1 Steps 0 to 3 in Fig. 11 take place.
  • Step 2 The UE 3 sends the RRC Resume Request message to the RAN 5 including S&F related information.
  • Step 5 in Fig. 11 For S&F related information, refer to Step 5 in Fig. 11.
  • the new Establishment Cause of Step 5 in Fig. 11 may be reused with a different name (e.g., new Resume Cause), where the contents may be the same as those of the new Establishment Cause.
  • Step 3 Upon the reception of the RRC Resume Request message in Step 2, the RAN 5 sends the RRC Resume message to the UE 3.
  • Step 4 The UE 3 sends the RRC Resume Complete message to the RAN 5 including at least one of S&F Priority and MO-data.
  • the MO-data may be sent from the UE 3 to the RAN 5 with another RRC message or another radio bearer.
  • Step 5 Step 5. Steps 8 to 10 in Fig. 11 take place.
  • Step 6 Upon the RAN 5 learning that the Feeder link that connects to the AMF 70 is available, the RAN 5 checks where there are stored MO-data that needs to be sent to the UPF 72. If the RAN 5 holds MO-data that needs to be sent to the UPF 72, the RAN 5 continues from Step 4B in the UE Triggered Connection Resume in RRC_INACTIVE procedure as described Section 4.8.2.2 in NPL 5 for all PDU Sessions one by one.
  • Step 6 the RAN 5 continues from Step 4B in the UE Triggered Connection Resume in RRC_INACTIVE procedure for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of uplink packet handling.
  • Tenth example of the First Aspect Fig. 14 illustrates an example of the MT-data sending using CIoT User Plane (U-Plane) procedure.
  • This example applies to both the gNB processed payload model and the gNB-DU processed payload model.
  • Step 1 Steps 1 to 6 in Fig. 12 take place.
  • Step 2 Upon the UPF 72 learning that the Feeder link that connects to the RAN 5 is available, the UPF 72 checks whether there are stored Downlink packets that needs to be sent to the RAN 5. If the UPF 72 holds Down link packets that needs to be sent to the RAN 5, the UPF 72 continues from Step 2a in the Network Triggered Service Request procedure as described Section 4.2.3.3 in NPL 5 for all PDU Sessions one by one.
  • Step 2 the UPF 72 continues from Step 2a in the Network Triggered Service Request procedure for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of down link packet handling.
  • This aspect includes an architecture and mechanisms to learn the UE-Satellite-UE communication without going through the ground network.
  • the Second Aspect discloses an example of a mini VPLMN in satellite architecture as illustrated in Fig. 15.
  • the AF 201 for example, at least one of IoT applications, IMS, SMS and location service, is located in the Satellite, the UE-Satellite-UE communication without going through the ground network is possible between those of UEs 3 as far as the Service links are available.
  • the mini VPLMN in satellite architecture is applicable to the gNB processed payload model.
  • the AMF 70, the SMF 71, the UPF 72, the AF 201, the visited PCF, vPCF, 7302, the NRF 76 and possibly other 5GC nodes are deployed in the Satellite together with the gNB 501.
  • the NTN Gateway 502 the home PCF, hPCF, 7301, the UDM 7501, the AUSF 7801 and possibly other 5GC nodes are deployed in the ground network.
  • all 5GC nodes in the Satellite may communicate with 5GC nodes in the terrestrial location using the NTN Gateway 502.
  • all 5GC nodes in the Satellite may communicate with 5GC nodes in the Satellite without using the NTN Gateway 502.
  • First example of the Second Aspect Fig. 16 illustrates an example of an AMF 70 that makes the SBI (Service Based Interface) communication possible within the Satellite.
  • SBI Service Based Interface
  • the Pseud UDM 7502, Pseud AUSF 7802, Pseud hPCF 7303 and possible other 5GC nodes are integrated in the AMF 70 and each node is able to communicate internally.
  • the Pseud UDM 7502 may be a pseud UDM 7502 for the UE 3 in addition to the UDM 7501.
  • the Pseud UDM 7502 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
  • the Pseud UDM 7502 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
  • the Pseud UDM 7502 may hold the subscriber data and authentication vectors for the UE 3.
  • the Pseud AUSF 7802 may be a pseud AUSF 7802 for the UE 3 in addition to the AUSF 7801.
  • the Pseud AUSF 7802 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
  • the Pseud AUSF 7802 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
  • the Pseud AUSF 7802 may hold authentication vectors for the UE 3.
  • the Pseud hPCF 7303 may be a pseud hPCF 7303 for the UE 3 in addition to the home PCF 7301 (Home PCF 7301).
  • the Pseud hPCF 7303 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
  • the Pseud hPCF 7303 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
  • the Pseud hPCF 7303 may hold PCC rule, ADSF rule, ATSSS rule and other policy related rules for the UE 3.
  • Fig. 17 illustrates an example of the NRF update procedure within the Satellite.
  • the NRF 76 is located in the Satellite and provides the node discovery function for those of 5GC nodes that are located within the Satellite.
  • the NRF 76 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
  • the NRF 76 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
  • Step 1 The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
  • Step 2 The UE 3 performs the Registration procedure with the Authentication and Authorization procedure with AUSF 7801 and UDM 7501 in the HPLMN of the UE 3.
  • the Pseud UDM 7502 may stores the subscriber data for the UE 3.
  • the Pseud AUSF 7802 may store Authentication Vectors for the UE 3 for future use.
  • the Authentication Vectors for the UE 3 for future use may be obtained by the Pseud AUSF 7802 using a mechanism that is disclosed by the Fourth example of the Second Aspect and the Fifth example of the Second Aspect.
  • Step 3 the Pseud UDM 7502 sends the Nnrf_NFManagement_NFRegister message to the NRF 76 including at least one of the NF type, PLMN ID and IP address.
  • the NF type is set to the UDM.
  • NF type indicates the Network Function type of the service consumer.
  • PLMN ID indicates the PLMN where the service consumer belongs to. In this example, the PLMN ID may be a Home PLMN of the UE 3.
  • IP address The IP address indicates an IP address of the service consumer.
  • Step 4 Upon reception of the Nnrf_NFManagement_NFRegister message, the NRF 76 register the entry of the service consumer in the record.
  • the NRF 76 sends the Nnrf_NFManagement_NFRegister response message to the Pseud UDM 7502.
  • Step 5 the Pseud AUSF 7802 sends the Nnrf_NFManagement_NFRegister message to the NRF 76 including at least one of the NF type, PLMN ID and IP address.
  • the NF type is set to the AUSF. Refer to Step 3 for parameter details.
  • Step 6 Upon reception of the Nnrf_NFManagement_NFRegister message, the NRF 76 register the entry of the service consumer in the record.
  • the NRF 76 sends the Nnrf_NFManagement_NFRegister response message to the Pseud AUSF 7802.
  • Step 7 The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is not available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite cannot communicate with 5GC nodes in the terrestrial location.
  • Step 8 The AMF 70, SMF 71, vPCF 7302, UPF 72, AF 201 and possibly other 5GC nodes in the Satellite make a query with NRF 76 using the Nnrf_NFDiscovery_Request service for UDM discovery and AUSF discovery and may find Pseud UDM 7502 and Pseud AUSF 7802 in the Satellite.
  • the AMF 70, SMF 71, vPCF 7302, UPF 72, AF 201 and possibly other 5GC nodes make a query with NRF 76 using the Nnrf_NFDiscovery_Request service only when the Feeder link is not available.
  • the AMF 70, SMF 71, vPCF 7302, UPF 72, AF 201 and possibly other 5GC nodes make a query with NRF 76 using the Nnrf_NFDiscovery_Request service when the Feeder link is available.
  • the Registration procedure may be a use case of Step 8.
  • the AMF 70 performs the UDM discovery procedure with the NRF 76 and finds the Pseud UDM 7502. Then, the AMF 70 continues the Registration procedure with the Pseud UDM 7502.
  • the Authentication and Authorization procedure may be a use case of Step 8.
  • the AMF 70 decides to perform the Authentication and Authorization procedure for the UE 3 during the Feeder link that connects to the AUSF 7801 is unavailable, the AMF 70 performs the AUSF discovery procedure with the NRF 76 and finds the Pseud AUSF 7802. Then, the AMF 70 continues the Authentication and Authorization procedure with the Pseud UDM 7502.
  • Variant 3 of First example of the Second Aspect The IMS call control within the Satellite may be a use case of Step 8.
  • the IMS Registration procedure and IMS call are disclosed in this Variant.
  • the IMS Registration procedure If the AF 201 is the IMS (IP Multimedia Subsystem) and the IMS Client in the UE 3 performs the IMS Registration procedure during the Feeder link that connects to the UDM 7501 is unavailable, the IMS node (Example, S-CSCF) performs the UDM discovery procedure with the NRF 76 and finds the Pseud UDM 7502. Then, the IMS node continues the IMS Registration procedure with the Pseud UDM 7502. For example, the IMS node (Example, S-CSCF) performs the IMS level user Authentication (Example, Nhss_ImsUEAuthenticate_Get service) by contacting the Pseud UDM 7502.
  • IMS level user Authentication Example, Nhss_ImsUEAuthenticate_Get service
  • the IMS call The assumption is that the two UE 3s (UE 3a and UE 3b are named for explanatory purpose in this variant) have been performed the IMS Registration procedure as disclosed in this valiant.
  • the UE 3a makes an IMS originating call to the UE 3b.
  • Step 1 The IMS node (S-CSCF) of the UE 3a receives the SIP Invite message and finds the IMS node (I-CSCF or S-CSCF) of the UE 3b.
  • Step 2 The IMS node (I-CSCF or S-CSCF) sends the SIP Invite message to the UE 3b and establishes the IMS connection between UE 3a and UE 3b without going through the ground network.
  • Second example of the Second Aspect Fig. 18 illustrates an example of the Service Availability Notification procedure when the AMF 70 is located in the Satellite.
  • the Service Availability Notification procedure may be used when the AMF 70 is not located in the Satellite.
  • Step 1 The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
  • AMF Service Step 2-A.
  • the UDM 7501 sends any AMF Service invoke message to the AMF 70.
  • Step 3-A Upon reception of the AMF Service invoke message in Step 2-A, the AMF 70 sends the AMF Service response message to the UDM 7501 including the Feeder link status information.
  • the Feeder link status information refer to Step 1 of Fig. 3.
  • Step 4-A Independent from Step 2-A or Step 3-A, the AMF 70 sends the AMF Service Notify message to the UDM 7501 including the Feeder link status information.
  • the Feeder link status information refer to Step 1 of Fig. 3.
  • the UDM 7501 uses the received Feeder link status(s) when the UDM 7501 invokes the AMF service to the AMF 70. For example, the UDM 7501 does not invoke any AMF services provided by the AMF 70 if the Feeder link status indicates as unavailable.
  • the AMF 70 sends the UDM Service invoke message to the UDM 7501 including the Feeder link status information.
  • For the Feeder link status information refer to Step 1 of Fig. 3.
  • Step 3-B Upon reception of the UDM Service invoke message in Step 2-B, the UDM 7501 sends the UDM Service response message to the AMF 70.
  • the UDM 7501 uses the received Feeder link status information when the UDM 7501 invokes the AMF service to the AMF 70. For example, the UDM 7501 does not invoke any AMF services provided by the AMF 70 if the Feeder link status information indicates as unavailable.
  • Variant 1 of Second example of the Second Aspect Steps 2-A to 4-A for the AMF Service may apply to any Services provided by other 5GC nodes.
  • it may be SMF Service, UDM Service PCF Service and other Services.
  • steps 2-A to 4-A for the AMF Service indicates that the UDM 7501 as the Service consumer, any 5GC nodes can be a Service consumer.
  • the UDM 7501 may be replaced with AUSF 7801, hPCF 7301 and any other 5GC nodes.
  • Variant 3 of Second example of the Second Aspect Steps 2-B to 3-B for the UDM Service may apply to any Services provided by other 5GC nodes.
  • it may be SMF Service, AMF Service PCF Service and other Services.
  • the UDM 7501 in Fig. 18 may be replaced with SMF, AMF and PCF respectively.
  • the UDM 7501 may in advance subscribe with the AMF 70 in the satellite for notifications (periodic or event based) related to the status of the Feeder link.
  • the AMF 70 would regularly or based on an event (e.g., Feeder link status information change) notify the UDM 7501 by sending the Namf_Service_Notify as per step 4-A in Fig. 18 or any other message with the purpose to notify any changes in the status of the Feeder link.
  • Third example of the Second Aspect Fig. 19 illustrates an example of the Service Availability Inquiry procedure when the AMF 70 is located in the Satellite.
  • the Service Availability Notification procedure may be used when the AMF 70 is not located in the Satellite.
  • Step 1 The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
  • Step 2 The UDM 7501 sends the Namf_Communication_AMFStatusChangeSubscribe message to the AMF 70 including at least one of GUAMI and Requested reporting period.
  • ⁇ GUAMI The GUAMI indicates the AMF identifier.
  • ⁇ Requested reporting period The Requested reporting period indicates a how often that the AMF 70 reports a status to the UDM 7501. For example, if the reporting period is set as 10 minutes, the AMF 70 reports a status of the AMF 70 to the UDM 7501 every 10 minutes.
  • the Requested reporting period may indicate "one time”. If the "one time” is set to the Requested reporting period, the AMF 70 reports a status of the AMF 70 one time.
  • Step 3 Upon reception of the Namf_Communication_AMFStatusChangeSubscribe in Step 2, the AMF 70 sends the Namf_Communication_AMFStatusChangeNotify message to the UDM 7501 including the Feeder link status information.
  • the Feeder link status information refer to Step 1 of Fig. 3.
  • the UDM 7501 uses the received Feeder link status(s) when the UDM 7501 invokes the AMF service to the AMF 70. For example, the UDM 7501 does not invoke any AMF services provided by the AMF 70 if the Feeder link status indicates as unavailable.
  • the UDM 7501 manages all UE(s) 3 as "Not reachable” if the UEs 3 are associated to the AMF 70 and the Feeder link status indicates that AMF 70 is not available.
  • steps 2 to 3 indicate that the UDM 7501 as the Service consumer, any 5GC nodes can be a Service consumer.
  • the UDM 7501 may be replaced with AUSF 7801, hPCF 7301 and any other 5GC nodes.
  • Second Aspect Fig. 20 illustrates an example of the Authentication procedure with Satellite access when the AMF 70 is located in the Satellite.
  • the Authentication procedure with Satellite access may be used when the AMF 70 is not located in the Satellite.
  • Step 1 The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
  • Step 2 The UE 3 sends a NAS message to the AMF 70 including User ID.
  • the User ID e.g., the User ID may be expressed as User Identity
  • the User ID may be a 5G-GUTI, SUCI or SUPI.
  • the NAS message may be Registration Request message, PDU Session Establishment Request message or Service Request message or any other NAS message.
  • Step 3 Upon reception of the NAS message in Step 2.
  • the AMF 70 may decide to performs the Authentication and Authorization procedure for the UE 3.
  • the AMF 70 sends the Nausf_UEAuthentication_Authenticate Request to the AUSF 7801 including at least one of User ID, SN-name, AMF in Satellite and the number of vectors requested.
  • ⁇ User ID The User ID may be SUCI or SUPI.
  • SN-name The SN-name is the Serving Network name. In this case a PLMN of the AMF 70.
  • AMF in Satellite The AMF in Satellite indicates that the AMF 70 is located in the Satellite. It implicitly indicates that the AMF 70 may be disconnected from the HPLMN or any other PLMN.
  • the number of vectors requested The number of vectors requested indicates that the number of Authentication Vectors, both 5G HE AVs and 5G AVs, being requested by the AMF 70 in addition to the 5G AV for the Authentication and Authorization to be used this Authentication and Authorization procedure. I.e., the AMF 70 requests a list of 5G HE AVs and a list of 5G AVs for future use in a case where the Feeder link becomes unavailable.
  • Step 4 Upon reception of the Nausf_UEAuthentication_Authenticate Request message from the AMF 70 in Step 3, the AUSF 7801 sends the Nudm_UEAuthentication_Get Request message to the UDM 7501 including at least one of User ID, SN-name, AMF in Satellite and the number of vectors requested. Refer to Step 3 for parameter details.
  • Step 5 Upon reception of the Nudm_UEAuthentication_Get Request message from the AUSF 7801, the UDM 7501 decides an Authentication method, either EAP-AKA' or 5G AKA, to be taken and whether the UDM 7501 can accepts providing multiple 5G HE AVs to the AMF 70.
  • the UDM 7501 may takes the received AMF in Satellite and a trust relationship with a VPLMN of the AMF 70 into account for the decision on providing multiple 5G HE AVs.
  • the UDM 7501 sends the Nudm_UEAuthentication_Get Response message to the AUSF 7801 including at least one of User ID, SN-name, AMF in Satellite, the number of vectors requested and List of HE AV.
  • the List of HE AV includes one or multiple HE AVs that can be used for Authentication and Authorization in future. For other parameter details, refer to Step 3.
  • the UDM 7501 includes the List of HE AV only if the UDM 7501 decides to provide multiple 5G HE Avs in Step 5.
  • Step 7 Upon reception of the Nudm_UEAuthentication_Get Response message from the UDM 7501, the AUSF 7801 decides whether the AUSF 7801 can accepts providing multiple 5G AVs to the AMF 70.
  • the AUSF 7801 may takes the received AMF in Satellite and a trust relationship with a VPLMN of the AMF 70 into account for the decision on providing multiple 5G AVs.
  • Step 8 The AUSF 7801 sends the Nausf_UEAuthentication_Authenticate Response message to the AMF 70 including at least one of User ID, List of 5G HE AV and List of 5G AV.
  • the AUSF 7801 includes the List of AV only if the AUSF 7801 decides to provide multiple 5G Avs in Step 7.
  • Step 9 Either the Authentication procedure for EAP-AKA' continues from Step 4 in Section 6.1.3.1 in NPL 8 or the Authentication procedure for 5G-AKA continues from step 6 in Section 6.1.3.2.0 in NPL 8 depending on the Authentication method selection in Step 5.
  • Step 10 After successful Authentication procedure, the AMF 70 sores the received List of 5G AV in Step 8 to the MM context of the UE 3 and shares the received List of 5G HE AV in Step 8 with the Pseud AUSF 7802.
  • the List of 5G HE AV and List of 5G AV are used by the AMF 70 in a case where the Authentication and Authorization procedure is needed but the Feeder link is not available.
  • FIG. 21 schematically illustrates an example of a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.
  • the telecommunication system 1 represents a system overview in which an end-to-end communication is possible.
  • UE 3 or user equipment, 'mobile device' 3
  • 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).
  • RAT 5G radio access technology
  • E-UTRA E-UTRA
  • WLAN wireless local area network
  • the (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU).
  • 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.
  • O-RAN Open RAN
  • 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'.
  • the (R)AN node 5 can also support a communication using the satellite access.
  • the (R)AN node 5 may support a satellite access and a terrestrial access.
  • 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).
  • BBF Broadband Forum
  • IOWN innovative Optical and Wireless Network
  • the core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1.
  • the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions.
  • 5GC 5G Core Network
  • 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).
  • SBA Service Based Architecture
  • 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).
  • ETSI NFV European Telecommunications Standards Institute, Network Functions Virtualization
  • the core network 7 may support the Non-Public Network (NPN).
  • NPN Non-Public Network
  • the NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • 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.
  • 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.
  • 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.
  • 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 Network Repository Function (NRF) 76, a Network Slice Admission Control Function (NSACF) 77 and an Authentication Server Function (AUSF) 78.
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • NWDAF Network Data Analytics Function
  • UDM Unified Data Management
  • NRF Network Repository Function
  • NSACF Network Slice Admission Control Function
  • AUSF Authentication Server Function
  • 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 and NSACF 77 for the roaming-out UE 3.
  • 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.
  • 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.
  • AF Application Function
  • the "Uu” interface may include a Control plane of Uu interface and User plane of Uu interface.
  • 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).
  • 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.
  • RRC Setup Request message This message is sent from the UE 3 to the (R)AN node 5.
  • RRC Setup Request message This message is sent from the UE 3 to the (R)AN node 5.
  • following parameters may be included together in the RRC Setup Request message.
  • the ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue.
  • RRC Setup message This message is sent from the (R)AN node 5 to the UE 3.
  • RRC Setup message This message is sent from the (R)AN node 5 to the UE 3.
  • following parameters may be included together in the RRC Setup message.
  • RRC setup complete message This message is sent from the UE 3 to the (R)AN node 5.
  • RRC setup complete message guami-Type, iab-NodeIndication, idleMeasAvailable, ue-MeasurementsAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity, s-NSSAI-List, onboardingRequest
  • the UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and/or the like).
  • the N1 interface is responsible to provide a communication between the UE 3 and the AMF 70 to support NAS signaling.
  • the N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface.
  • Registration Request message This message is sent from the UE 3 to the AMF 70.
  • 5GS registration type ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requeste
  • Registration Accept message This message is sent from the AMF 70 to the UE 3.
  • 5GS registration result 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSA
  • Registration Complete message This message is sent from the UE 3 to the AMF 70.
  • following parameters may be included together in the Registration Complete message. SOR transparent container.
  • Authentication Request message This message is sent from the AMF 70 to the UE 3.
  • following parameters may be included together in the Authentication Request message.
  • Authentication Response message This message is sent from the UE 3 to the AMF 70.
  • following parameters may be populated together in the Authentication Response message.
  • ⁇ Authentication Result message This message is sent from the AMF 70 to the UE 3.
  • following parameters may be populated together in the Authentication Result message. ngKSI, EAP message and ABBA.
  • Authentication Failure message This message is sent from the UE 3 to the AMF 70.
  • Authentication failure message identity 5GMM cause and Authentication failure parameter.
  • Authentication Reject message This message is sent from the AMF 70 to the UE 3.
  • following parameters may be populated together in the Authentication Reject message. EAP message.
  • ⁇ Service Request message This message is sent from the UE 3 to the AMF 70.
  • Service Request message This message is sent from the UE 3 to the AMF 70.
  • following parameters may be populated together in the Service Request message.
  • Service Accept message This message is sent from the AMF 70 to the UE 3.
  • Service Accept message PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value.
  • Service Reject message This message is sent from the AMF 70 to the UE 3.
  • Service Reject message This message is sent from the AMF 70 to the UE 3.
  • 5GMM cause PDU session status, T3346 value, EAP message, T3448 value and CAG information list.
  • Configuration Update Command message This message is sent from the AMF 70 to the UE 3.
  • Configuration update indication 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI.
  • Configuration Update Complete message This message is sent from the UE 3 to the AMF 70.
  • parameters that are disclosed by Aspects in this disclosure following parameters may be populated together in the Configuration Update Complete message.
  • Configuration update complete message identity In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Complete message. Configuration update complete message identity.
  • UE Fig. 22 is an example of a block diagram illustrating the main components of the UE 3 (mobile device 3).
  • the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32.
  • the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside.
  • the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate.
  • Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • RMD removable data storage device
  • a controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36.
  • the software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621.
  • the communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating/sending/receiving) signalling and uplink/downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70.
  • Such signalling may include, for example, appropriately formatted signalling messages (e.g., a Registration Request message and associated response messages) relating to access and mobility management procedures (for the UE 3).
  • the controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.
  • USIM Universal Subscriber Identity Module
  • the UE 3 may, for example, support the Non-Public Network (NPN),
  • NPN Non-Public Network
  • the NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the UE 3 may, for example, be an item of equipment for production or manufacture and/or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and/or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and/or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and/or related machinery; paper converting machinery; chemical machinery; mining and/or construction machinery and/or related equipment; machinery and/or implements for agriculture, forestry and/or fisheries; safety and/or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and/or application systems for any of the previously mentioned equipment or machinery etc.).
  • equipment or machinery such as: boilers
  • the UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).
  • transport equipment for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.
  • the UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).
  • information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.
  • the UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and/or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).
  • a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.
  • the UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).
  • an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.
  • the UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and/or system, a weapon, an item of cutlery, a hand tool, or the like.
  • the UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).
  • the UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and/or wireless communication technologies.
  • IoT Internet of things
  • IoT devices may be equipped with appropriate electronics, software, sensors, network connectivity, and/or the like, which enable these devices to collect and exchange data with each other and with other communication devices.
  • IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and/or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g., vehicles) or attached to animals or persons to be monitored/tracked.
  • IoT technology can be implemented on any communication devices that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
  • IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.
  • MTC Machine-Type Communication
  • M2M Machine-to-Machine
  • NB-IoT UE Narrow Band-IoT UE
  • the UE 3 may be a smart phone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).
  • a wearable device e.g., smart glasses, a smart watch, a smart ring, or a hearable device.
  • the UE 3 may be a reduced capability device (RedCap).
  • the UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g., Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).
  • V2X Vehicle to Everything
  • FIG. 23 is an example of a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G).
  • the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53.
  • a controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55.
  • Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • the software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.
  • the communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g., directly or indirectly).
  • the signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e., messages by Xn reference point), etc.
  • connection establishment and maintenance e.g., RRC connection establishment and other RRC messages
  • NGAP NG Application Protocol
  • XnAP Xn application protocol
  • Such signalling may also include, for example, broadcast information (e.g., Master Information and System information) in a sending case.
  • the controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
  • the (R)AN node 5 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the gNB 501, the NTN Gateway 502 and the gNB-DU 61 may have same components to the (R)AN node 5.
  • the (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.
  • FIG. 24 schematically illustrates an example of a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.
  • the (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62.
  • each unit may be combined.
  • the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit
  • the DU 61 can be integrated/combined with the CU 62 as another integrated/combined unit.
  • Any functionality in the description for a unit e.g., one of RU 60, DU 61 and CU 62) can be implemented in the integrated/combined unit above.
  • CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP).
  • the CU CP has a control plane functionality in the (R)AN node 5.
  • the CU UP has a user plane functionality in the (R)AN node 5.
  • Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and/or the like).
  • the UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called “Uu” interface and/or the like).
  • Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called “Front haul”, “Open Front haul”, “F1” interface and/or the like).
  • Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called “Mid haul”, “Open Mid haul", “E2" interface and/or the like).
  • Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called “Back haul”, “Open Back haul”, “N2"/ “N3” interface(s) and/or the like).
  • an appropriate interface such as the so-called "Back haul”, “Open Back haul”, “N2"/ “N3” interface(s) and/or the like.
  • a user plane part of the DU 61 can also be connected to the core network nodes via an appropriate interface (such as the so-called “N3" interface(s) and/or the like).
  • each unit provides some of the functionality that is provided by the (R)AN node 5.
  • the RU 60 may provide a functionalities to communicate with a UE 3 (e.g., the Network Relay UE 300) over air interface
  • the DU 61 may provide functionalities to support MAC layer and RLC layer
  • the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.
  • RU Fig. 25 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G).
  • the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603.
  • a controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605.
  • Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • the software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.
  • the communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g., directly or indirectly).
  • the signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3 (e.g., the Network Relay UE 300)), and in particular, relating to MAC layer and RLC layer.
  • the controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
  • the RU 60 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated/combined unit above.
  • FIG. 26 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G).
  • the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612.
  • a controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614.
  • Software may be pre-installed in the memory 614 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • RMD removable data storage device
  • the software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421.
  • the communications control module 6142 (using its transceiver control module 61421) is responsible for handling (generating/sending/receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.
  • the DU 61 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the RU 60 can be integrated/combined with the DU 61 or CU 62 as an integrated/combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated/combined unit above.
  • FIG. 27 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G).
  • the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622.
  • a controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • RMD removable data storage device
  • the software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421.
  • the communications control module 6242 (using its transceiver control module 62421) is responsible for handling (generating/sending/receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.
  • the CU 62 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the CU 62 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated/combined unit above.
  • AMF Fig. 28 is a block diagram illustrating the main components of the AMF 70.
  • the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3 (e.g., the Network Relay UE 300 and the UE 3), the NSSF 76) via a network interface 702.
  • a controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704.
  • Software may be pre-installed in the memory 704 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • the software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421.
  • the communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating/sending/receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g., via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a Registration Request message and associated response messages) relating to access and mobility management procedures (for the UE 3).
  • the AMF 70 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • the AMF 7001, the AMF 7002, the MN AMF 7001 and the SN AMF 7002 may have same components to the AMF 70.
  • SMF Fig. 29 is a block diagram illustrating the main components of the SMF 71.
  • the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712.
  • a controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714.
  • Software may be pre-installed in the memory 714 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421.
  • the communications control module 7142 (using its transceiver control module 71421) is responsible for handling (generating/sending/receiving) signalling between the SMF 71 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
  • the SMF 71 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the SMF 7101 and the SMF 7102 may have same components to the SMF 71.
  • UPF Fig. 30 is a block diagram illustrating the main components of the UPF 72.
  • the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722.
  • a controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724.
  • Software may be pre-installed in the memory 724 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421.
  • the communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating/sending/receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
  • the UPF 72 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • PCF Fig. 31 is a block diagram illustrating the main components of the PCF 73.
  • the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732.
  • a controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734.
  • Software may be pre-installed in the memory 734 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421.
  • the communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating/sending/receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
  • the PCF 73 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the hPCF 7301, the vPCF 7302, the Pseud hPCF 7303 may have same components to the PCF 73.
  • NWDAF Fig. 32 is a block diagram illustrating the main components of the NWDAF 74.
  • the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70 and the UDM 75) via a network interface 742.
  • a controller 743 controls the operation of the NWDAF 74 in accordance with software stored in a memory 744.
  • Software may be pre-installed in the memory 744 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • a removable data storage device e.g., a removable memory device (RMD)
  • the software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421.
  • the communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating/sending/receiving) signalling between the NWDAF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
  • the NWDAF 74 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • UDM Fig. 33 is a block diagram illustrating the main components of the UDM 75.
  • the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752.
  • a controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754.
  • Software may be pre-installed in the memory 754 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • the software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421.
  • the communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating/sending/receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-out).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).
  • the UDM 75 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the UDM 7501 and the Pseud UDM 7502 may have same components to the UDM 75.
  • NRF Fig. 34 is a block diagram illustrating the main components of the NRF 76.
  • the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762.
  • a controller 763 controls the operation of the NRF 76 in accordance with software stored in a memory 764.
  • Software may be pre-installed in the memory 764 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example.
  • the software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421.
  • the communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating/sending/receiving) signalling between the NRF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).
  • the NRF 76 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • NSACF Fig. 35 is a block diagram illustrating the main components of the NSACF 77.
  • the apparatus includes a transceiver circuit 771 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 772.
  • a controller 773 controls the operation of the NSACF 77 in accordance with the software stored in a memory 774.
  • the Software may be pre-installed in the memory 774 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421.
  • the communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating/sending/receiving) signalling between the NSACF 77 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).
  • the NSACF 77 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • AUSF Fig. 36 is a block diagram illustrating the main components of the AUSF 78.
  • the apparatus includes a transceiver circuit 781 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 782.
  • a controller 783 controls the operation of the AUSF 78 in accordance with the software stored in a memory 784.
  • the Software may be pre-installed in the memory 784 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421.
  • the communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating/sending/receiving) signalling between the AUSF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).
  • the AUSF 78 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the AUSF 7801 and the Pseud AUSF 7802 may have same components to the AUSF 78.
  • AF Fig. 37 is a block diagram illustrating the main components of the AF 201.
  • the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3 (e.g., the Network Relay UE 300 and the UE 3)) via a network interface 2012.
  • a controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014.
  • Software may be pre-installed in the memory 2014 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • a removable data storage device e.g., a removable memory device (RMD)
  • the software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421.
  • the communications control module 20142 (using its transceiver control module 201421) is responsible for handling (generating/sending/receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in).
  • signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
  • the AF 201 may support the Non-Public Network (NPN),
  • NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.
  • Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories / caches (program and/or data); processing registers; communication buses (e.g., control, data and/or address buses); direct memory access (DMA) functions, hardware or software implemented counters, pointers and/or timers; and/or the like.
  • processors e.g., one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories / caches (program and/or data); processing registers; communication buses (e.g., control, data and/or address buses); direct memory access (DMA) functions, hardware or software implemented counters, pointers and/or timers; and/or the like.
  • the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities. In the above aspects, a 3GPP radio communications (radio access) technology is used.
  • any other radio communications technology e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.
  • other fix line communications technology e.g., BBF Access, Cable Access, optical access, etc.
  • Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/tablet computers, web browsers, e-book readers and/or the like.
  • Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network.
  • IoT Internet of Things
  • MTC machine-type communication
  • the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
  • the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.
  • each block of the block diagrams can be implemented by computer program instructions.
  • These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • Supplementary notes The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.
  • RAN Radio Access Network
  • S&F Store and Forward
  • S&F related information includes at least one of S&F support, List of Out of Service TAI, Supported TAI list, or S&F capacity.
  • (Supplementary note A3) The method according to supplementary note A1 or A2, wherein the S&F related information of the second core network node is a S&F support indication of the second core network node.
  • (Supplementary note A4) The method according to any one of supplementary notes A1 to A3, wherein the first core network node is an Access and Mobility Management Function (AMF) node or a User Plane Function (UPF) node.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • a method of a User Equipment (UE) comprising: receiving, from a Radio Access Network (RAN) node, a first message including Store and Forward (S&F) related information; and sending a second message including S&F related information of the UE.
  • RAN Radio Access Network
  • a Radio Access Network (RAN) node comprising: means for sending, to a first core network node, a first message including Store and Forward (S&F) related information; and means for receiving, from the first core network node, a second message including S&F related information of a second core network node.
  • the Radio Access Network node according to supplementary note A7 wherein the S&F related information includes at least one of S&F support, List of Out of Service TAI, Supported TAI list, or S&F capacity.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • a User Equipment comprising: means for receiving, from a Radio Access Network (RAN) node, a first message including Store and Forward (S&F) related information; and means for sending a second message including S&F related information of the UE.
  • RAN Radio Access Network
  • S&F Store and Forward
  • UE User Equipment
  • a method of a first core network node comprising: sending, to a second core network node, a first message including Feeder link status information.
  • a first core network node comprising: means for sending, to a second core network node, a first message including Feeder link status information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

An aspect of this disclosure includes a method of a method of a first core network node. The method includes sending, to a second core network node, a first message including information related to Feeder link.

Description

METHOD OF FIRST CORE NETWORK NODE AND FIRST CORE NETWORK NODE
　　The present disclosure relates to a method of a first core network node, and a first core network node etc.
　　According to NPL 2, there is a potential service requirement related to the 5G system with satellite access taking into account new capabilities such as a Store and Forward Satellite operation for delay-tolerant communication services and a UE-Satellite-UE communication without going through the ground network.
　　NPL 1: 3GPP TR 21.905: "Vocabulary for 3GPP Specifications", V17.1.0 (2021-12)
　　NPL 2: 3GPP TR 22.865: "Study on satellite access Phase 3", V19.0.0 (2023-06)
　　NPL 3: 3GPP TR 38.821: "Solutions for NR to support non-terrestrial networks (NTN) ", V16.2.0 (2023-03)
　　NPL 4: 3GPP TS 23.501: "System architecture for the 5G System (5GS)", V18.1.0 (2023-03)
　　NPL 5: 3GPP TS 23.502: "Procedures for the 5G System (5GS)", V18.1.1 (2023-04)
　　NPL 6: 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2", V18.1.0 (2023-03)
　　NPL 7: 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS) Stage 3", V18.2.1 (2023-03)
　　NPL 8: 3GPP TS 33.501: "Security architecture and procedures for 5G system", V18.2.0 (2023-06)
　　The following service requirement has not been supported by the 5GS yet. For example, there is no mechanism in the 3GPP specification(s) for achieving the following potential service requirement: satellite access taking into account new capabilities such as a Store and Forward Satellite operation for delay-tolerant communication services and a UE-Satellite-UE communication without going through the ground network.
　　In a first aspect, the present disclosure provides a method of a first core network node comprising:
　　sending, to a second core network node, a first message including information related to Feeder link.
　　In a second aspect, the present disclosure provides a first core network node comprising:
　　means for sending, to a second core network node, a first message including information related to Feeder link.
　　Embodiments of the present disclosure will now be described, by way of example, with reference to the accompanying drawings.
Fig. 1 is a diagram illustrating a configuration example of a gNB processed payload model of a First Aspect. Fig. 2 is a diagram illustrating a configuration example of a gNB-DU processed payload model of a First Aspect. Fig. 3 is a Signaling diagram of a First example of the First Aspect. Fig. 4 is a Signaling diagram of a Second example of the First Aspect. Fig. 5 is a Signaling diagram of a Third example of the First Aspect. Fig. 6 is a Signaling diagram of a Third example of the First Aspect. Fig. 7 is a Signaling diagram of a Fourth example of the First Aspect. Fig. 8 is a Signaling diagram of a Fourth example of the First Aspect. Fig. 9 is a Signaling diagram of a Fifth example of the First Aspect. Fig. 10 is a Signaling diagram of a Sixth example of the First Aspect. Fig. 11 is a Signaling diagram of a Seventh example of the First Aspect. Fig. 12 is a Signaling diagram of an Eighth example of the First Aspect. Fig. 13 is a Signaling diagram of a Ninth example of the First Aspect. Fig. 14 is a Signaling diagram of a Tenth example of the First Aspect. Fig. 15 is a diagram illustrating a configuration example of a mini VPLMN in satellite architecture of the Second Aspect. Fig. 16 is a block diagram showing a configuration example of a UDM, AUSF and PCF integrated AMF architecture of a First example of the Second Aspect. Fig. 17 is a Signaling diagram of a First example of the Second Aspect. Fig. 18 is a Signaling diagram of a Second example of the Second Aspect. Fig. 19 is a Signaling diagram of a Third example of the Second Aspect. Fig. 20 is a Signaling diagram of a Fourth example of the Second Aspect. Fig. 21 is a diagram illustrating a configuration example of a system overview. Fig. 22 is a block diagram illustrating a configuration example of a UE. Fig. 23 is a block diagram illustrating a configuration example of an (R)AN node. Fig. 24 is a diagram illustrating a configuration example of a System overview of (R)AN node based on O-RAN architecture. Fig. 25 is a block diagram illustrating a configuration example of an RU. Fig. 26 is a block diagram illustrating a configuration example of a DU. Fig. 27 is a block diagram illustrating a configuration example of a CU. Fig. 28 is a block diagram illustrating a configuration example of an AMF. Fig. 29 is a block diagram illustrating a configuration example of an SMF. Fig. 30 is a block diagram illustrating a configuration example of a UPF. Fig. 31 is a block diagram illustrating a configuration example of a PCF. Fig. 32 is a block diagram illustrating a configuration example of an NWDAF. Fig. 33 is a block diagram illustrating a configuration example of a UDM. Fig. 34 is a block diagram illustrating a configuration example of an NRF. Fig. 35 is a block diagram illustrating a configuration example of an NSACF. Fig. 36 is a block diagram illustrating a configuration example of an AUSF. Fig. 37 is a block diagram illustrating a configuration example of an AF.
Description of Example Embodiments
　　Abbreviations
　　For the purposes of the present document, the abbreviations given in NPL 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in NPL 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
ABBA　　Anti-Bidding down Between Architectures
AF　　Application Function
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
ARFCN　　Absolute radio-frequency channel number
AS　　Access Stratum
ASN　　Abstract Syntax Notation
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
CHF　　Charging Function
CN PDB　　Core Network Packet Delay Budget
CP　　Control Plane
DAPS　　Dual Active Protocol Stacks
DL　　Downlink
DN　　Data Network
DNAI　　DN Access Identifier
DNN　　Data Network Name
DRX　　Discontinuous Reception
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
G-PDU　　GTP encapsulated user Plane Data Unit
GPS　　Global Positioning System
GPSI　　Generic Public Subscription Identifier
GSO　　Geosynchronous Orbit
GUAMI　　Globally Unique AMF Identifier
GUTI　　Globally Unique Temporary UE Identity
HPLMN　　Home Public Land Mobile Network
HR　　Home Routed (roaming)
HSS　　Home Subscriber Server
IAB　　Integrated access and backhaul
IEC　　International Electrotechnical Commission
IMEI/TAC　　IMEI Type Allocation Code
IMSI　　International Mobile Subscriber Identity
IPsec　　Internet Protocol Security
IPUPS　　Inter PLMN UP Security
I-SMF　　Intermediate SMF
ISO　　International Organization for Standardization
I-UPF　　Intermediate UPF
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
MEO　　Medium Earth Orbit
MFBR　　Maximum Flow Bit Rate
MICO　　Mobile Initiated Connection Only
MINT　　Minimization of service interruption
MITM　　Man In the Middle
MME　　Mobility Management Entity
MN　　Master Node
MNC　　Mobile Network Code
MNO　　Mobile Network Operator
MOCN　　Multiple Operator Core Network
MPS　　Multimedia Priority Service
MPTCP　　Multi-Path TCP Protocol
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 Satellite Orbit
NID　　Network identifier
NMEA　　National Marine Electronics Association
NPN　　Non-Public Network
NR　　New Radio
NRF　　Network Repository Function
NSAC　　Network Slice Admission Control
NSACF　　Network Slice Admission Control Function
NSAG　　Network Slice Access Stratum Group
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 Network
NW-TT　　Network-side TSN translator
NWDAF　　Network Data Analytics Function
PCC　　Policy and Charging Control
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
RACS　　Radio Capabilities Signalling optimisation
(R)AN　　(Radio) Access Network
RAT　　Radio Access Technology
RFID　　Radio Frequency Identification
RG　　Residential Gateway
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
RU　　Radio Unit
RVAS　　Roaming Value Added Service
SA NR　　Standalone New Radio
SBA　　Service Based Architecture
SBI　　Service Based Interface
SCP　　Service Communication Proxy
SD　　Slice Differentiator
SEAF　　Security Anchor Functionality
SENSE　　Signal Level Enhanced Network Selection
SEPP　　Security Edge Protection Proxy
SGW　　Serving Gateway
SIB　　System Information Block
SINR　　Signal to Interference plus Noise Ratio
SLA　　Service Level Agreement
SMF　　Session Management Function
SMS　　Short Message Service
SMSF　　Short Message Service Function
SN　　Sequence Number
SN　　Secondary Node
SN name　　Serving Network name
SNPN　　Stand-alone Non-Public Network
S-NSSAI　　Single Network Slice Selection Assistance Information
SOR　　Steering of Roaming
SSC　　Session and Service Continuity
SSCMSP　　Session and Service Continuity Mode Selection Policy
SST　　Slice/Service Type
SUCI　　Subscription Concealed Identifier
SUPI　　Subscription Permanent Identifier
SV　　Software Version
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
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
　　Definitions
　　For the purposes of the present document, the terms and definitions given in NPL 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in NPL 1.
　　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.
　　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.
　　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.
　　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.
　　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.
　　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.
　　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.
　　Any lists described in following aspects include at least one parameter or multiple parameters.
　　The expression "A and/or B" in this disclosure may mean "at least one of A and B".
　　The definition of parameter(s) in each Aspect may be referred each other.
　　An example object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problem.
　　Although this disclosure discloses a mechanism to establish multiple data plane connections in the 5GS, all mechanisms in this disclosure can equally apply to the EPS and/or any other system as well. In a case where 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 or SMF + PGW-C in the case of interworking with EPS
●　　UPF → SGW-U or PGW-U or combined SGW-U and PGW-U or UPF + PGW-U in the case of interworking with EPS
●　　NGAP → S1AP
●　　XnAP → X2AP
●　　Any NGAP messages → Respective S1AP messages
●　　Any XnAP messages → Respective X2AP messages
●　　Any RRC messages of 5G NR → Respective RRC messages of 4G E-UTRA/LTE or Narrow Band-IoT (NB-IoT)
●　　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
　　In this disclosure, the above-mentioned service requirement or a service achieved by the above-mentioned service requirement can be expressed as a support of ambient power-enabled Internet of Things, a support of Ambient IoT devices, a support of RFID devices, ambient power-enabled Internet of Things communication, Ambient IoT device communication, Ambient IoT device communication or Ambient IoT communication.
　　Each Aspects and elements may relate to one of following descriptions, combination of following descriptions, or all of following descriptions, but the each Aspects and the elements are not limited to following descriptions.
　　Each Aspects and elements may provide solution related to one of following descriptions, combination of following descriptions, or all of following descriptions, but the each Aspects and the elements may provide solution other than the following descriptions.
　　For example, in some scenarios, UEs need to communicate using satellite access without going to the ground network in order to avoid long delays and limited data rate as well as reducing the consumption of backhaul resources.
However, there is no mechanism in the current 5G system for supporting the UE-Satellite-UE communication.
　　A method of a first core network node according to example aspect of this disclosure includes sending, to a second core network node, a first message including Feeder link status information.
　　A first core network node according to example aspect of this disclosure includes means for sending, to a second core network node, a first message including Feeder link status information.
　　First Aspect
　　This aspect includes an architecture and mechanisms to learn the Store and Forward Satellite operation.
　　This aspect discloses mechanisms for the 5G system with satellite-access where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable, e.g., to provide communication service for UE(s) 3 under satellite coverage without a simultaneous active feeder link connection to the ground segment.
　　The aspects assumes that the RAN 5 complies with the Regenerative payload generic architecture as defined in NPL 3. Further there are two models of the Regenerative payload generic architectures, gNB processed payload model and gNB-DU, gNB-Distributed Unit, processed payload model.
　　Fig. 1 and Fig. 2 illustrate the gNB processed payload model and gNB-DU processed payload model respectively as an example.
　　In the gNB processed payload model, the gNB 501 is located in the Satellite and the UE(s) 3 communicate with the gNB 501 using the Service link. The NTN, Non-Terrestrial Network, Gateway 502 is located at terrestrial location and communicates with the gNB 501 using the Feeder link. The NTN Gateway 502 communicates with the 5GC, 5G Core Network 7.
　　The RAN 5 includes the gNB 501 and the NTN Gateway 502.
　　In the gNB-DU processed payload model, the gNB-DU 61 is located in the Satellite and the UE(s) 3 communicate with the gNB-DU 61 using the Service link. The NTN Gateway 502 is located at terrestrial location and communicates with the gNB-DU 61 using the Feeder link. The NTN Gateway 502 communicates with the gNB-CU, gNB-Centralized Unit, 62. The gNB-CU 62 communicates with the 5GC 7.
　　The RAN 5 includes the gNB-DU 61, the NTN Gateway 502 and the gNB-CU 62.
　　First example of the First Aspect
　　Fig. 3 illustrates an example of the RAN initiated Interface Management Procedures for NGAP, Next Generation Application Protocol, interface.
　　For the gNB processed payload model, the RAN 5 may be referred as the gNB 501.
　　For the gNB-DU processed payload model, the RAN 5 may be referred as the gNB-DU 61.
　　The detailed processes of the First example of the First Aspect are described below with reference to Fig. 3.
　　Step 1. The RAN 5 sends the NG Setup Request message including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity.
　　The following bullets explain each parameter in detail.
●　　Store and Forward support (S&F support): The Store and Forward support, S&F support, indicates that the RAN 5 supports Store and Forward, S&F, functionality. The S&F support may indicate the S&F capability of the RAN 5. The S&F capability of the RAN 5 may indicate that the RAN 5 supports the Store and Forward functionality. If the RAN 5 supports S&F functionality, the RAN 5 may perform as follows. For example, when the Feeder link is not available, the RAN 5 may still communicate with the UE 3 and store the data or an RRC signalling message or a NAS signalling message received from the UE 3 and when the Feeder link becomes available, the RAN 5 forwards the stored data or the RRC signalling message or the NAS signalling message to the network via the Feeder link. Also, when the Service link is not available, the RAN 5 may still communicate with the network via the Feeder link and store the received data for the UE 3 and when the Service link becomes available, the RAN 5 may forward the stored data to the UE 3 via the Service link. The RRC signalling message or the NAS signalling message may be an RRC message or a NAS message encapsulated in the RRC message or the NAS message. The data may be data packets received on an established DRB.
●　　List of Out of Service TAI: The List of Out of Service TAI indicates the list of Tracking Area Identity/Identities, TAI(s), and/or Tracking Area Code(s), TAC(s), of the Tracking Area(s) TA(s), which are not available due to the Feeder link not available or the Service link(s) to that TAI(s) and/or TAC(s) of the TA(s) are not available. The TAC is part of the TAI. The list of TAI(s) and/or TAC(s) which are not available may be expressed as the Out of Service TAI. The Out of Service TAI may be embedded to Supported TAI. The Supported TAI may indicate the Supported TA(s) in the RAN 5. The List of Out of Service TAI may have associated time information. The associated time information may indicate when the TAI(s) in the list are considered as not available and/or when the TAI(s) in the list are considered as available. The List of Out of Service TAI may have Orbit characteristics information. The Orbit characteristics information may indicate a TAI availability that corresponds to an Orbit of connected satellite where the RAN 5 or a part of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day. The List of Out of Service TAI may indicate the list of TAI(s) supported by the RAN 5 but the service is not available due to the Feeder link or Service link is not available.
●　　Supported TAI list: The Supported TAI list indicates the list of the profile(s) of the Supported TA(s) in the RAN 5. In addition to existing profile(s), the Supported TAI list includes the Feeder link status information and the Service link status information for each TA.
●　　Feeder link status information: The Feeder link status information indicates the status of the Feeder link that the TAI is associated with. The Feeder link status information may include at least one of the following parameters:
　　　　Feeder link identifier (Feeder link ID): The Feeder link identifier, the Feeder link ID, indicates an associated Feeder link with the TAI. There may be one instance or multiple instances.
　　　　Feeder link status: The Feeder link status indicates whether the Feeder link is available or not.
　　　　Shut down time: The Shut down time indicates when the Feeder link will become not available. It can be expressed as an absolute time or a relative time or an associated time.
　　　　Time to recovery: The Time to recovery indicates when the Feeder link will become available. It can be expressed as an absolute time or a relative time or an associated time.
　　　　Orbit characteristics: The Orbit characteristics indicate a Feeder link availability that corresponds to an Orbit of connected satellite where the RAN 5 or a port of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
●　　Service link status information: The Service link status information indicates the status of the Service link that the TAI is associated with. The Service link status information may include at least one of the following parameters:
　　　　Service link identifier (Service link ID): The Service link identifier, the Service link ID, indicates an associated Service link with the TAI. There may be one instance or multiple instances.
　　　　Service link status: The Service link status indicates whether the Service link is available or not.
　　　　Shut down time: The Shut down time indicates when the Service link will become not available. It can be expressed as an absolute time or a relative time or an associated time.
　　　　Time to recovery: The Time to recovery indicates when the Service link will become available. It can be expressed as an absolute time or a relative time or an associated time.
　　　　Orbit characteristics: The Orbit characteristics indicate a Service link availability that corresponds to an Orbit of connected satellite where the RAN 5 or a part of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
●　　Store and Forward capacity (S&F capacity): The Store and Forward capacity indicates buffer capacity. The RAN 5 may indicate to the network function, NF, (e.g., AMF 70) the buffer capacity (e.g., in bytes) to store the data when the Feeder link is not available.
　　For example, the RAN 5 sends the NG Setup Request message in the following cases:
●　　The RAN 5 detects that a Feeder link associated with the TAI(s) becomes available or unavailable.
●　　The RAN 5 changes the TAI(s) being broadcasted in the BCCH (e.g., SIB1) due to the satellite move.
●　　The RAN 5 detects that a Service link associated with the TAI(s) becomes available or unavailable.
●　　The NG-RAN TNL Association is updated.
　　Step 2. Upon reception of the NG Setup Request message from the RAN 5 in Step 1, the AMF 70 stores the received information from the RAN 5 and the AMF 70 sends the NG Setup Response message to the RAN 5 including S&F support indication as a parameter. The S&F support indication may indicate that the AMF 70 and/or associated network function(s), NF(s), (e.g., at least one of SMF 71, UPF 72, and UDM 75) support Store and Forward functionality. The AMF 70 and/or associated network function(s) will not transmit data more than the Store and Forward capacity of the RAN 5 when the Service link is not available.
　　Variant 1 of First example of the First Aspect
　　In Step 1 in Fig. 3, the NG Setup Request message may be a RAN Configuration Update message or an existing NGAP message or a new NGAP message.
　　In Step 2 in Fig. 3, the NG Setup Response message may be a RAN Configuration Update Acknowledge message or an existing NGAP message or a new NGAP message.
　　Second example of the First Aspect
　　Fig. 4 illustrates an example of the AMF initiated Interface Management Procedures for NGAP interface.
　　For the gNB processed payload model, the RAN 5 may be referred as the gNB 501.
　　For the gNB-DU processed payload model, the RAN 5 may be referred as the gNB-DU 61.
　　The detailed processes of the Second example of the First Aspect are described below with reference to Fig. 4.
　　Step 1. The AMF 70 sends the AMF Configuration Update message to the RAN 5 including S&F support indication as a parameter. The S&F support may indicate that the AMF 70 and/or associated NF(s) (e.g., at least one of SMF 71, UPF 72, and UDM 75) support the Store and Forward functionality.
　　For example, the AMF 70 sends the AMF Configuration Update message in the following cases:
●　　The AMF 70 and/or associated NF(s) (e.g., at least one of SMF 71, UPF 72, and UDM 75) start supporting or start not supporting the Store and Forward functionality.
●　　The AMF TNL Association is updated.
　　Step 2. Upon reception of the AMF Configuration Update message from the AMF 70 in Step 1, The RAN 5 stores the received information from the AMF 70 and the RAN 5 sends the AMF Configuration Update Acknowledge message including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity. Refer to Step 1 in Fig. 3 for parameter details.
　　Third example of the First Aspect
　　Figs. 5 and 6 illustrate examples of the Echo message handling for N3 interface.
　　For the gNB processed payload model, the RAN 5 may be referred as the gNB 501.
　　For the gNB-DU processed payload model, the RAN 5 may be referred as the gNB-DU 61.
　　Fig. 5 illustrates the Echo message sent from the RAN 5 as an example.
　　The detailed processes of the Third example of the First Aspect are described below with reference to Fig. 5.
　　Step 1. The RAN 5 sends the Echo request message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity. Refer to Step 1 in Fig. 3 for parameter details.
　　Step 2. Upon reception of the Echo request message from the RAN 5 in Step 1, the UPF 72 stores the received information from the RAN 5 and the UPF 72 sends the Echo Response message to the RAN 5 including S&F support indication as a parameter. The S&F support indication may indicate that the UPF 72 and/or associated NF(s) (e.g., at least one of AMF 70, SMF 71, and UDM 75) support the Store and Forward functionality.
　　Fig. 6 illustrates the Echo message sent from the UPF 72 as an example.
　　The detailed processes of the Third example of the First Aspect are described below with reference to Fig. 6.
　　Step 1. The UPF 72 sends the Echo request message to the RAN 5 including S&F support indication as a parameter. The S&F support indication may indicate that the UPF 72 and/or associated NF(s) (e.g., at least one AMF 70, SMF 71, and UDM 75) support the Store and Forward functionality.
　　Step 2. Upon reception of the Echo request message from the UPF 72 in Step 1, the RAN 5 stores the received information from the UPF 72 and the RAN 5 sends the Echo Response message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity. Refer to Step 1 in Fig. 3 for parameter details.
　　Variant 1 of Third example of the First Aspect
　　In one example, in Fig. 5 the UPF 72 may in advance subscribe with the RAN 5 for notifications (periodic or event based) related to the status of the Service link and/or the Feeder link. In that case the RAN 5 may regularly or based on an event (e.g., Service link status information and/or Feeder link status information change) notify the UPF 72 by sending the Echo request message as in step 1 of Fig. 5 or any other message (e.g., RAN Configuration Update message) with the purpose to notify any changes in the status of the Feeder link and/or the Service link.
　　Fourth example of the First Aspect
　　Figs. 7 and 8 illustrate examples of the Error Indication message handling for N3 interface.
　　For the gNB processed payload model, the RAN 5 may be referred as the gNB 501.
　　For the gNB-DU processed payload model, the RAN 5 may be referred as the gNB-DU 61.
　　Fig. 7 illustrates the Error Indication message sent from the RAN 5 as an example.
　　The detailed processes of the Fourth example of the First Aspect are described below with reference to Fig. 7.
　　Step 1. The RAN 5 sends the Error Indication message to the UPF 72 including at least one of S&F support, List of Out of Service TAI, Supported TAI list and S&F capacity. Refer to Step 1 in Fig. 3 for parameter details.
　　Fig. 8 illustrates the Error Indication message sent from the UPF 72 as an example.
　　The detailed processes of the Fourth example of the First Aspect are described below with reference to Fig. 8.
　　Step 1. The UPF 72 sends the Error Indication message to the RAN 5 including S&F support indication as a parameter. The S&F support indication mat indicate that the UPF 72 and/or associated NF(s) (e.g., at least one of AMF 70, SMF 71, and UDM 75) support the Store and Forward functionality.
　　Fifth example of the First Aspect
　　Fig. 9 illustrates an example of the Registration procedure in a case where the RAN 5 or a part of RAN 5 is located in the satellite.
　　This example applies to both, the gNB processed payload model and the gNB-DU processed payload model.
　　The detailed processes of the Fifth example of the First Aspect are described below with reference to Fig. 9.
　　Step 1. The NGAP Setup procedure between the RAN 5 and AMF 70 takes place as disclosed by First example of the First Aspect.
　　Step 2. The RAN 5 broadcasts at least one of the PLMN status information, Service link status information, S&F status information, Processed payload mode and Feeder link status in system information. The RAN 5 may use at least one of SIB1, SIB19 (containing NTN related information) and new SIBx to broadcast.
　　The following bullets explain each parameter in detail.
●　　PLMN status information: The PLMN status information indicates a status of the connectivity to the PLMN. The connectivity depends on the status of the associated Feeder link(s) as the TNL (Transport Network Layer). As far as one Feeder link is available to the PLMN, the PLMN status information may be connected status. The PLMN status information may include at least one of the following parameters:
　　　　PLMN ID (PLMN identifier): The PLMN ID indicates PLMN identifier. It may comply with MCC and MNC.
　　　　PLMN status: The PLMN status indicates whether the 5GC for the PLMN is reachable or not.
　　　　Shut down time: The Shut down time indicates when a connectivity to the PLMN will become unavailable. For example, it depends on the associated Feeder link status. The Shut down time can be expressed as an absolute time or a relative time or an associated time.
　　　　Time to recovery: The Time to recovery indicates when the connectivity to the PLMN will become available. For example, it depends on the associated Feeder link status. The Time to recovery can be expressed as an absolute time or a relative time or an associated time.
　　　　Orbit characteristics: The Orbit characteristics indicate the connectivity to the PLMN that corresponds to the Orbit of the connected satellite where the RAN 5 or a part of RAN 5 is located. For example, it can be expressed as 12:00-17:00 available every day.
●　　Service link status information: The Service link status information indicates the status of the Service link that the TAI is associated with. Refer to Step 1 of Fig. 3 for parameter details.
●　　S&F status information: The S&F status information indicates the status of Store and Forward functionality in the RAN 5. The S&F status information may include at least one of the following parameters:
　　　　S&F available: The S&F available indicates whether the use of the Store and Forward functionality is available or not.
　　　　S&F service: The S&F service is associated information to the S&F available. The S&F service indicates which service(s) are subject to the Store and Forward functionality being available. For example, the S&F service may be at least one of CIoT C-plane service, CIoT U-plane service, SMS service and Location service.
　　　　S&F overload: The S&F overload indicates that the Store and Forward functionality is overloaded. The UE 3 is requested to refer to an associated S&F backoff parameter in a case where the UE 3 needs to send the uplink data.
　　　　S&F backoff timer: The S&F backoff timer is an associated parameter to the S&F overload. The S&F backoff timer may indicate a wait timer how long the UE 3 needs to deter from sending uplink data. Alternatively, the S&F backoff timer may have a time information when the UE 3 is allowed to send the uplink data. For example, the time information may be broadcasted if the uplink data storage buffer in the RAN 5 is full or close to full but the associated Feeder link is not available but known by the RAN 5 when it will be available.
●　　Processed payload mode: The Processed payload mode indicates the type of the Processed payload mode. For example, it may be Transparent payload, gNB payload, gNB+DU payload, gNB+DU+AMF payload or gNB+DU+AMF+UPF payload. The processed payload mode may be used by the UE 3 to select the preferred satellite cell (i.e., satellite beam) when multiple satellite cells with different Processed payload are available in the UE 3's location.
●　　Feeder link status information: The Feeder link status information indicates the status of the Feeder link that the TAI is associated with. Refer to Step 1 of Fig.3 for parameter details. The RAN 5 broadcasts whether the Feeder link is available or not.
　　Step 3. Based on the system information that is received from RAN 5 in Step 2, the UE 3 confirms that a target PLMN is reachable (e.g., the Feeder link is available) and decides to perform the Registration procedure towards the target PLMN.
　　Step 4. The UE 3 sends a Registration Request message to the AMF 70 including at least one of User ID, and S&F support indication.
　　The following bullets explain each parameter in detail.
●　　User ID (e.g., the User ID may be expressed as User Identity): The User ID may be a 5G-GUTI, SUCI or SUPI.
●　　Store and Forward support indication (S&F support indication): The S&F support indication indicates that the UE 3 supports the Store and Forward functionality. The S&F support indication may indicate the S&F capability of the UE 3. The S&F capability of the UE 3 may indicate that the UE 3 supports the Store and Forward functionality. The S&F support indication may be expressed differently. For example, the S&F support indication may be expressed as Store and Forward support in the MM context, Delay tolerant IoT support, or UP Delay tolerant IoT support. The UE 3 indicates that it supports S&F feature if the UE 3 supports at least one feature or one procedure defined in this disclosure. In one example the UE 3 also sends the S&F capability in an RRC message during an RRC procedure (e.g., in the RRC SETUP COMPLETE message during RRC connection establishment procedure). The RAN 5 stores this capability and executes one of the procedure defined in this disclosure.
　　Step 5. Upon reception of the Registration Request message in step 4, the AMF 70 sends a Nudm_UECM_Registration message to a UDM 75 including at least one of SUPI and S&F support indication. Refer to Step 4 for parameter details.
　　Sep 6. The UDM 75 stores the S&F support indication from the UE 3. When the S&F capability indicates that the UE 3 supports S&F functions, then the UDM 75 may determine the UE 3 is delay tolerant UE. If the UDM 75 is in congestion, then UDM 75 may delay the processing of the signalling related to the UE 3 and the UDM 75 may prioritize the signalling or handling of other UEs 3 that are non-delay tolerant. The UDM 75 sends the Nudm_UECM_Registration response message to the AMF 70.
　　Step 7. After the completion of the Nudm_UECM_Registration service in steps 4 and 5, the AMF 70 sends a Nudm_SDM_Get Request message to the UDM 75 including at least one of SUPI and S&F support indication. Refer to Step 4 for parameter details.
　　Step 8. The UDM 75 finds the Subscriber data for the UE 3 and sends a Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3. The Subscriber data includes the S&F profiles of the UE 3.
　　The following bullets explain each parameter in detail.
●　　S&F profile: The S&F profile includes a subscribed profile when the UE 3 uses the Store and Forward functionality. The S&F profile may be expressed differently. For example, Store and Forward profile, S&F user profile, Delay tolerant IoT profile, UP Delay tolerant IoT profile. The S&F profile may include at least one of the following parameters:
　　　　S&F allowed: The S&F allowed indicates whether the use of the Store and Forward functionality is allowed or not;
　　　　S&F data retention period: The S&F data retention period indicates the maximum duration acceptable the UE 3 if the uplink data sent from the UE 3 is retained in the RAN 5. For example, due to unavailability of the associated Feeder link;
　　　　S&F storage quota: The S&F storage quota indicates the maximum data size that the UE 3 is allowed to send as uplink data in a case where the uplink data is to be stored in the RAN 5. For example, due to unavailability of the associated Feeder link;
　　　　S&F priority: The S&F priority indicates a relative priority when the UE 3 uses the Store and Forward functionality. For example, sending uplink data to the RAN 5 is allowed even the RAN 5 broadcasts that the Store and Forward functionality is suspended. For example, due to congestion in the RAN 5.
　　In one example, the S&F profile may be defined per an S-NSSAI in the subscribed NSSAI.
　　In another example, the S&F profile may be defined per a DNN in the subscriber data. The S&F profile may be defined a S-NSSAI and DNN combination.
　　In one example, the AMF 70 may invoke service operation other than the Nudm_SDM_GET operation to indicate the S&F capability of the UE 3 to the UDM 75 and fetch the S&F profile from the UDM 75.
　　Step 9. After the AMF 70 obtains the Subscriber data for the UE 3 from the UDM 75 in step 8, the AMF 70 stores the received data, including S&F profile, to the MM context of the UE 3 in the storage of the AMF 70.
　　Step 10. The AMF 70 sends a Registration Accept message to the UE 3 including at least one of 5G-GUTI and S&F profile. For the S&F profile refer to Step 8 for parameter details.
　　Step 11. Upon reception of the Registration Accept message from the AMF 70, the UE 3 stores the received data into non-volatile memory of the UE 3.
　　Step 12. The UE 3 sends the Registration Complete message to the AMF 70. Whenever the S&F profile is present in the Registration Accept message, the UE sends Registration Complete message.
　　After the registration procedure, if there is a change in the S&F profile, the AMF 70 sends the new S&F profile in an existing NAS message during an existing NAS procedure (e.g., in the UE configuration update message during generic UE configuration update procedure).
　　Variant 1 of Fifth example of the First Aspect
　　In one example, the UE 3 has different S&F capability of different access type or RAT type or system type, i.e., the UE has S&F capability for NR, NR(LEO), NR(MEO), NR(GEO) and NR(OTHERSAT), E-UTRAN or EPS or 5GS. Similarly, network has different S&F capability for S&F capability of different access type or RAT type or system type, i.e., the UE has S&F capability for at least one of NR, NR(LEO), NR(MEO), NR(GEO), NR(OTHERSAT), E-UTRAN, EPS and 5GS. The network sends the S&F capability to the UE 3 in an existing NAS message or an existing RRC message. The AMF 70 passes the S&F capability to the RAN 5. The RAN 5 uses the S&F capability to executes S&F operation or procedure for the UE. The S&F operation or procedure may be operation or procedure the RAN 5 performs if the RAN 5 supports S&F functionality.
　　Variant 2 of Fifth example of the First Aspect
　　In one example, the RAN 5 may broadcast the Time information (e.g., t-Service) on when a cell provided via NTN quasi-Earth fixed system is going to stop serving the area it is currently covering. The Time information may indicate a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The exact stop time is between the time indicated by the value of this field minus 1 and the time indicated by the value broadcasted. The Time information is valid regardless of the PLMN in the cell. In other words, this is applicable all the PLMNs in the cell. If RAN 5 broadcasts the Time information and the Shut down time, the UE 3 capable of accessing a cell or RAN 5 supporting the S&F capability may ignore the Time information and may follow the Shut down time.
　　Variant 3 of Fifth example of the First Aspect
　　In one example, the RAN 5 may broadcast the Shut down time. The Shut down time may indicate a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The exact stop time is between the time indicated by the value of this field minus 1 and the time indicated by the value broadcasted. Additionally or alternatively, the RAN 5 may broadcast the Time to recovery. The Time to recovery may indicate a time multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The exact recovery time is between the time indicated by the value of this field minus 1 and the time indicated by the value broadcasted.
　　Variant 4 of Fifth example of the First Aspect
　　In one example, the RAN 5 may broadcast one of some of the information of the above-mentioned PLMN status information by reusing the existing PLMN related information. For example, the SIB1 includes the PLMN-IdentityInfoList which further includes the PLMN-IdentityInfo per PLMN. The PLMN-IdentityInfo may include the PLMN status.
　　Sixth example of the First Aspect
　　Fig. 10 illustrates an example of the PDU Session Establishment procedure in a case where the RAN 5 or a part of RAN 5 is located in the satellite.
　　This example applies to both, the gNB processed payload model and the gNB-DU processed payload model.
　　The PDU Session Establishment procedure is used to install the S&F profile to the SMF 71, UPF 72 and RAN 5 for the PDU Session. The S&F profile may be used in a case where the Stored and Forward functionality is activated after the PDU Session has been established by this procedure.
　　The detailed processes of the Sixth example of the First Aspect are described below with reference to Fig. 10.
　　Step 0. The UE 3 is connected to 5GC as both the Service link and the Feeder link are available.
　　Step 1. The UE 3 sends a UL NAS Transport message to the AMF 70 including at least one of PDU Session ID, S-NSSAI, S&F requested and NAS container that includes PDU Session Establishment Request message.
　　The following bullets explain each parameter in details.
●　　PDU Session ID is an identifier of the PDU Session being established.
●　　S-NSSAI is a Single NSSAI that indicates a network slice.
●　　S&F requested indicates that the Store and Forward functionality is requested for the PDU Session in a case where the Store and Forward functionality is needed. The S&F requested may be included in the PDU Session Establishment Request message.
　　Step 2. Upon reception of the UL NAS Transport message from the UE 3, the AMF 70 performs the SMF selection based on the received S&F requested from the UE 3. The AMF 70 selects the SMF 71 that is capable to handle the Store and Forward functionality.
　　Once the SMF 71 is selected, the AMF 70 sends the Nsmf_PDUSession_CreateSMContext Request message to the SMF 71 including at least one of PDU Session ID and S&F requested. The S&F requested may be included in the PDU Session Establishment Request.
　　Step 3. The SMF 71 sends the Nsmf_PDUSession_CreateSMContext Response to the AMF 70.
　　Step 4. In a case where the SMF 71 does not hold the Session Management Subscriber data for the UE 3, The SMF 71 sends the Nudm_SDM_Get message to the UDM 75 including at least one of User ID, DNN, S-NSSAI and S&F requested.
　　Step 5. The UDM 75 sends the Nudm_SDM_Get Response message to the SMF 71 including Session Management Subscriber data. The Session Management Subscriber data may include S&F profile for the PDU Session being established.
　　Step 6. 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 the Npcf_SMPolicyControl_Create message to the PCF 73 including at least one of User ID, S-NSSAI and S&F requested.
　　Step 7. 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 the Npcf_SMPolicyControl_Create Response message to the SMF 71 including generated PCC Rule. The SMF 71 derives an ATSSS rule from the received PCC rule.
　　Step 8. The SMF 71 selects the UPF 72 based on the S&F requested in the Nsmf_PDUSession_CreateSMContext Request message in Step 2. Then, the SMF 71 sends the N4 Session Establishment Request message to the UPF 72 including at least one of PDU Session ID, S&F requested, S&F profile and ATSSS rule.
　　Step 9. The UPF 72 stores the received S&F profile. After successful installation of the ATSSS rule in the UPF 72, the UPF 72 sends the N4 Session Establishment Response message to the SMF 71.
　　Step 10. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 including at least one of PDU Session ID, N2 SM information and N1 SM container.
　　The N2 SM information includes at least one of the PDU Session ID and S&F profile.
　　The N1 SM container includes the PDU Session Establishment Accept message including ATSSS rule. The SMF 71 also sends an existing or a new message including S&F profile to the UPF 72. When the user data comes to the UPF 72 and the UPF 72 determines that the UPF 72 the Feeder link is down then the UPF 72 stores the data for the UE 3 as per the S&F profile. For example, when the MT user data comes to the UPF 72 for the UE 3 the UPF 72 stores the MT user data and starts the retention timer. If the retention timer expires and the Feeder link is still not connected, then the UPF 72 discards the MT user data and indicate to the SMF 71 by including an information element in the existing message or by sending a new message. The information element indicates the cause of discarding the data.
　　Step 11. Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, The AMF 70 sends the N2 PDU Session Request message including PDU Session ID, S&F profile and N1 SM container that contains the PDU Session Establishment Accept message. The PDU Session Establishment Accept message includes the ATSSS rule.
　　The RAN 5 stores the received S&F profile by associating with the PDU Session. The S&F profile may be used later when the Store and Forward functionality is activated for the PDU Session.
　　Step 12. The RAN 5 sends DL Information Transfer message. The DL Information Transfer message may include dedicated NAS-Message that may include the PDU Session Establishment Accept message to the UE 3 including the ATSSS rule. The UE 3 installs the received ATSSS rule in the UE 3.
　　Step 13. The RAN 5 sends the N2 PDU Session Response message to the AMF 70.
　　Seventh example of the First Aspect
　　Fig. 11 illustrates an example of the MO-data sending using CIoT Control Plane (C-Plane) procedure.
　　This example applies to both the gNB processed payload model and the gNB-DU processed payload model.
　　The detailed processes of the Seventh example of the First Aspect are described below with reference to Fig. 11.
　　Step 0. The UE 3 is registered with the AMF 70 and the PDU Session has been established with the S&F profile.
　　Step 1. The Feeder link that connects to the AMF 70 with the RAN 5 in the satellite is not available or become unavailable.
　　The UE 3 may stay in the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state in the RAN 5 after the Feeder link that connects to the AMF 70 with the RAN 5 in the satellite is not available or become unavailable.
　　The UE 3 may stay in the CM-IDLE state in the RAN 5. One example, the UE 3 may transit from the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state to the CM-IDLE state after the Feeder link that connects to the AMF 70 with the RAN 5 in the satellite is not available or become unavailable.
　　Step 2. The RAN 5 broadcasts at least one of the PLMN status information, Service link status information, S&F status information and Processed payload mode in system information.
　　Refer to Step 2 in Fig. 9 for information details in the system information.
　　As the Feeder link for the AMF 70 is not available, the PLMN status information of the PLMN where the AMF 70 belongs to is set as not reachable.
　　When the UE 3 receives the broadcasting message in Step 2, the UE 3 may stay in the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state.
　　When the UE 3 receives the broadcasting message in Step 2, the UE 3 may stay in the CM-IDLE state. One example, the UE 3 may transit from the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state to the CM-IDLE state.
　　Step 3. The RAN 5 sends the NGAP message indicating that the Feeder link is not available or become unavailable. One example, the NGAP message may be the NGAP message that is disclosed in the First example of the First Aspect or any other existing message (e.g., RAN Configuration Update message) or new message on the N2 interface between the AMF 70 and the RAN 5. One example, the NGAP message may include a cause value (e.g., Feeder link not available).
　　When the AMF 70 receives the NGAP message in Step 3, all UEs 3 that are connected the RAN 5 may stay in the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state in the AMF 70.
　　When the AMF 70 receives the NGAP message in Step 3, the UE 3 may stay in the CM-IDLE state in the AMF 70. One example, the UE 3 may transit from the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state to the CM-IDLE state in the AMF 70.
　　Step 4. UE 3 confirms that the Feeder link is not available or the AMF 70 is not reachable but the Store and Forward functionality is active or available based on system information in Step 2. The UE 3 may decide to send the MO-data to network. The UE 3 may intend to send the MO-data to the AMF 70 via the RAN 5.
　　Step 5. The UE 3 sends the RRC Setup Request message to the RAN 5 including S&F related information. The S&F related information may include at least one of S&F Priority, new Establishment Cause or new Logical Channel ID (LCID).
　　The following bullets explain each parameter in details.
●　　S&F Priority: The S&F Priority indicates that the UE 3 has a high priority to send the MO-data even the system information in Step 7 restricts the MO-data handling (i.e., under S&F situation). For example, if the RRC Setup Request message includes the S&F Priority in the S&F related information, the UE 3 sends the MO-data even the system information in Step 7 restricts the MO-data handling.
●　　New Establishment Cause: The new Establishment Cause indicates that the UE 3 has a high priority data to be sent even under S&F situation. The new Establishment Cause may be highPriorityAccessStoreAndForward, mo-SignallingStoreAndForward, or mo-DataStoreAndForward, or storeAndForward-PriorityAccess.
●　　New LCID: A new LCID value is used in the RRC Setup Request message, which indicates that the UE 3 has a high priority data to be sent even under S&F situation.
　　Step 6. Upon the reception of the RRC Setup Request message in Step 5, the RAN 5 sends the RRC Setup message to the UE 3.
　　Step 7. The UE 3 sends the RRC Message number 3 message to the RAN 5. The RRC Message number 3 includes at least one of S&F Priority and Dedicated NAS. The Dedicated NAS includes the Service Request message.
　　The Service Request message includes at least one of the User ID, the S&F Priority and the MO-data. The MO-data may be embedded in the CIoT small data container or CIoT user data container.
　　Step 8. Upon reception of the RRC Message number 3 message from the UE 3, the RAN 5 confirms that the RAN 5 cannot send the Initial UE message to the AMF 70 due to the Feeder link to the AMF 70 is not available.
　　In this case, the RAN 5 stores the Dedicated NAS in the RAN 5 and starts the retention timer.
　　In a case where the retention timer expires before the stored Dedicated NAS is sent to the AMF 70, the RAN 5 may delete the stored Dedicated NAS message. Upon expiry of the retention timer the RAN 5 may release the RRC connection with the UE 3. In one example, The UE 3 also indicates in an RRC message that the UE 3 has more NAS message(s) to send, in this case the RAN 5 will not release the RRC connection immediately and wait for the more RRC message from the UE 3. When the UE 3 has transmitted last NAS message it has then it indicates to the RAN 5 in an existing or a new RRC message including an indicator indicating that the UE 3 has no more RRC message(s) to send, in this case the RAN 5 releases the RRC connection.
　　Step 9. The Feeder link that connects the RAN 5 with the AMF 70 is available.
　　Step 10. The RAN 5 sends the NGAP message indicating that the Feeder link is available. One example, the NGAP message may be the NGAP message that is disclosed in the First example of the First Aspect or any other existing message (e.g., RAN Configuration Update message) or new message on the N2 interface between the AMF 70 and the RAN 5.
　　In a case where the stored message is not transmitted to the AMF 70 (e.g., the retention time expires), the RAN 5 indicates this to the UE 3 by including an indicator in an existing RRC message or by sending a new RRC message. The message also indicates the cause of dropping of stored message, e.g., retention period expires. The RAN 5 also indicates this to the AMF 70 for a UE 3 that the UL NAS messages are dropped due to retention period expires or other related cause value.
　　Step 11. Upon the RAN 5 learning that the Feeder link that connects to the AMF 70 is available, the RAN 5 checks whether there are stored Dedicated NAS(s) message or container that needs to be sent to the AMF 70. If the RAN 5 holds Dedicated NAS(s) message or container that needs to be sent to the AMF 70, the RAN 5 sends the Initial UE message(s) to the AMF 70 for all held Dedicated NAS(s) one by one including S&F Priority and NAS PDU. The NAS PDU includes the Service Request message.
　　The Service Request message includes S&F Priority and the MO-data.
　　In the case where the UE 3 is managed as the CM-CONEECTED state or the CM-CONNECTED with RRC_INACTIVE state in the RAN 5, the RAN 5 may send the MO-data to the UPF 72 using N3 connection (N3 tunnel).
　　Step 12. The AMF 70 sends the Nsmf_PDUSession_SendMOData message to the SMF 71 including MO-data.
　　Step 13. The SMF 71 forwards the received MO-data to the UPF 72 over User plane.
　　Step 14. The UPF 72 communicates with the AF 201 or any server in data network for the CIoT communication. The UPF 72 and the AF 201 may perform User data communication. For example, the UPF 72 may send Uplink MO-data to the AF 201, and the AF 201 may send Downlink MT-data to the UPF 72.
　　Step 15. The UPF 72 may forward the MT-data over User plane if the UPF 72 receive the MT-data from the AF 201 during the CIoT communication in Step 14.
　　Step 16. The SMF 71 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70. The Namf_Communication_N1N2MessageTransfer message my include the MT-data.
　　Step 17. The AMF 70 sends the Service Accept message to the UE 3. The Service Accept message may include the MT-data.
　　Variant 1 of Seventh example of the First Aspect
　　In Step 11, the RAN 5 sends the Initial UE message(s) to the AMF 70 for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of uplink packet handling. For example, the RAN 5 sends the Initial UE message(s) to the AMF 70 every 30 seconds.
　　Variant 2 of Seventh example of the First Aspect
　　In Step 7, if the PDU Session is a Multi Access PDU Session and the UE 3 has another 3GPP access or non-3GPP access that are connected to the UPF 72, the UE 3 sends the MO-data using another access instead of using the RAN 5 at the Satellite or some part of the RAN 5 is at the Satellite.
　　Variant 3 of Seventh example of the First Aspect
　　In one example, at step 5 of Fig. 11 the UE 3 may include a new RRC establishment cause in the RRC Connection Establishment Request message to the RAN 5, e.g., 'S&F data' or any other notation for an RRC establishment cause in order to indicate to the RAN 5 that the UE 3 is aware of the Feeder link's unavailability and the UE 3 uses the 'S&F data' RRC establishment cause to request the RAN 5 to Store the data from the UE 3 and Forward it when the Feeder link becomes available. If the RRC establishment cause is set to 'S&F data' then the RAN 5 will store the NAS container sent in the RRC message.
　　Variant 4 of Seventh example of the First Aspect
　　The Store and Forward procedure defined in this disclosure also applies for the case when a DRB is established between the UE 3 and the RAN 5. This is the case the UE 3 and the RAN 5 were in RRC inactive mode and the UE 3 got user data to transmit. In this case the UE 3 will resume the DRB by sending RRC Resume message with establishment cause set to "S&F" and send the user data over the DRB to the RAN 5. The RAN 5 will move the UE 3 to RRC-INACTIVE mode for the DRB only when the S&F feature is supported by the UE 3, the RAN 5 and the 5GC.
　　Variant 5 of Seventh example of the First Aspect
　　In one example, at Step 4 of Fig. 11, NAS layer of the UE 3 may inform AS layer (e.g., RRC layer) of the UE 3 that there is the MO-data to be sent even the system information in Step 7 restricts the MO-data handling (i.e., under S&F situation). The NAS layer of the UE 3 may indicate the S&F Priority to the AS layer of the UE 3.
　　Eighth example of the First Aspect
　　Fig. 12 illustrates an example of the MT-data sending using CIoT Control Plane (C-Plane) procedure.
　　This example applies to both, the gNB processed payload model and the gNB-DU processed payload model.
　　The detailed processes of the Eighth example of the First Aspect are described below with reference to Fig. 12.
　　Step 1. Steps 0 to 3 in Fig. 11 take place.
　　Step 2. The RAN 5 sends the Echo request message indicating that the Feeder link is not available or become unavailable. One example, the Echo request message may be the GTP-U message that is disclosed in the Third example of the First Aspect or any other existing message or new message on the RAN 5 to the UPF 72. One example, the Echo request message may include a cause value (e.g., Feeder link not available).
　　Step 3. Downlink packets to the UE 3 arrive at the UPF 72. In one example, Downlink packets are sent from the AF 201.
　　Step 4. Upon reception of the Downlink packets in the UPF 72, the UPF 72 confirms that the UPF 72 cannot send the Downlink packets to the RAN 5. For example, due to the Feeder link is not available.
　　In this case, the UPF 72 stores the Downlink packets in the UPF 72 and starts the retention timer.
　　In a case where the retention timer expires before the stored Dedicated NAS is sent to the RAN 5, the UPF 72 may delete the stored Downlink packets.
　　Step 5. Steps 9 to 10 in Fig. 11 take place.
　　Step 6. The RAN 5 sends the Echo request message indicating that the Feeder link is available. One example, the Echo request message may be the GTP-U message that is disclosed in the Third example of the First Aspect or any other existing message or new message on the RAN 5 to the UPF 72.
　　Step 7. Upon the UPF 72 learning that the Feeder link that connects to the RAN 5 is available, the UPF 72 checks where there are stored Downlink packets that needs to be sent to the RAN 5. If the UPF 72 holds Downlink packets that needs to be sent to the RAN 5, the UPF 72 initiates the UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedure as described in the Section 4.24.2 in NPL 5 for all PDU Sessions one by one.
　　Variant 1 of Eighth example of the First Aspect
　　In Step 7, the UPF 72 initiates the UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedure for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of downlink packet handling.
　　Variant 2 of Eighth example of the First Aspect
　　Instead of Step 2, the AMF 70 informs to the UPF 72 via the SMF 71 that the Feeder link is not available when the AMF 70 receives the NGAP message in Step 3 of Fig. 11.
　　Variant 3 of Eighth example of the First Aspect
　　Instead of Step 6, the AMF 70 informs to the UPF 72 via the SMF 71 that the Feeder link is not available when the AMF 70 receives the NGAP message in Step 10 of Fig. 11.
　　Variant 4 of Eighth example of the First Aspect
In Step 4, if the PDU Session is a Multi Access PDU Session and the UPF 72 has another 3GPP access or non-3GPP access that are connected to the UE 3, the UPF 72 sends the MO-data using another access instead of using the RAN 5 at the Satellite or some part of the RAN 5 is at the Satellite.
　　Ninth example of the First Aspect
Fig. 13 illustrates an example of the MO-data sending using CIoT User Plane (U-Plane) procedure.
　　This example applies to both the gNB processed payload model and the gNB-DU processed payload model.
　　The detailed processes of the Ninth example of the First Aspect are described below with reference to Fig. 13.
　　Step 1. Steps 0 to 3 in Fig. 11 take place.
　　Step 2. The UE 3 sends the RRC Resume Request message to the RAN 5 including S&F related information.
　　For S&F related information, refer to Step 5 in Fig. 11. The new Establishment Cause of Step 5 in Fig. 11 may be reused with a different name (e.g., new Resume Cause), where the contents may be the same as those of the new Establishment Cause.
　　Step 3. Upon the reception of the RRC Resume Request message in Step 2, the RAN 5 sends the RRC Resume message to the UE 3.
　　Step 4. The UE 3 sends the RRC Resume Complete message to the RAN 5 including at least one of S&F Priority and MO-data. The MO-data may be sent from the UE 3 to the RAN 5 with another RRC message or another radio bearer.
　　Step 5. Steps 8 to 10 in Fig. 11 take place.
　　Step 6. Upon the RAN 5 learning that the Feeder link that connects to the AMF 70 is available, the RAN 5 checks where there are stored MO-data that needs to be sent to the UPF 72. If the RAN 5 holds MO-data that needs to be sent to the UPF 72, the RAN 5 continues from Step 4B in the UE Triggered Connection Resume in RRC_INACTIVE procedure as described Section 4.8.2.2 in NPL 5 for all PDU Sessions one by one.
　　Variant 1 of Ninth example of the First Aspect
　　In Step 6, the RAN 5 continues from Step 4B in the UE Triggered Connection Resume in RRC_INACTIVE procedure for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of uplink packet handling.
　　Tenth example of the First Aspect
　　Fig. 14 illustrates an example of the MT-data sending using CIoT User Plane (U-Plane) procedure.
　　This example applies to both the gNB processed payload model and the gNB-DU processed payload model.
　　The detailed processes of the Tenth example of the First Aspect are described below with reference to Fig. 14.
　　Step 1. Steps 1 to 6 in Fig. 12 take place.
　　Step 2. Upon the UPF 72 learning that the Feeder link that connects to the RAN 5 is available, the UPF 72 checks whether there are stored Downlink packets that needs to be sent to the RAN 5. If the UPF 72 holds Down link packets that needs to be sent to the RAN 5, the UPF 72 continues from Step 2a in the Network Triggered Service Request procedure as described Section 4.2.3.3 in NPL 5 for all PDU Sessions one by one.
　　Variant 1 of Tenth example of the First Aspect
　　In Step 2, the UPF 72 continues from Step 2a in the Network Triggered Service Request procedure for one PDU Session and another gradually with enough pace in order to avoid possible congestions due to huge number of down link packet handling.
　　Second Aspect
　　This aspect includes an architecture and mechanisms to learn the UE-Satellite-UE communication without going through the ground network.
　　The Second Aspect discloses an example of a mini VPLMN in satellite architecture as illustrated in Fig. 15. As the AF 201, for example, at least one of IoT applications, IMS, SMS and location service, is located in the Satellite, the UE-Satellite-UE communication without going through the ground network is possible between those of UEs 3 as far as the Service links are available.
　　The mini VPLMN in satellite architecture is applicable to the gNB processed payload model.
　　The AMF 70, the SMF 71, the UPF 72, the AF 201, the visited PCF, vPCF, 7302, the NRF 76 and possibly other 5GC nodes are deployed in the Satellite together with the gNB 501.
　　The NTN Gateway 502, the home PCF, hPCF, 7301, the UDM 7501, the AUSF 7801 and possibly other 5GC nodes are deployed in the ground network.
　　When the Feeder link is available, all 5GC nodes in the Satellite may communicate with 5GC nodes in the terrestrial location using the NTN Gateway 502.
　　When the Feeder link is not available, all 5GC nodes in the Satellite may communicate with 5GC nodes in the Satellite without using the NTN Gateway 502.
　　First example of the Second Aspect
　　Fig. 16 illustrates an example of an AMF 70 that makes the SBI (Service Based Interface) communication possible within the Satellite.
　　The Pseud UDM 7502, Pseud AUSF 7802, Pseud hPCF 7303 and possible other 5GC nodes are integrated in the AMF 70 and each node is able to communicate internally.
　　The Pseud UDM 7502 may be a pseud UDM 7502 for the UE 3 in addition to the UDM 7501.
　　For example, the Pseud UDM 7502 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
　　For example, the Pseud UDM 7502 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
　　The Pseud UDM 7502 may hold the subscriber data and authentication vectors for the UE 3.
　　The Pseud AUSF 7802 may be a pseud AUSF 7802 for the UE 3 in addition to the AUSF 7801.
　　For example, the Pseud AUSF 7802 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
　　For example, the Pseud AUSF 7802 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
　　The Pseud AUSF 7802 may hold authentication vectors for the UE 3.
　　The Pseud hPCF 7303 may be a pseud hPCF 7303 for the UE 3 in addition to the home PCF 7301 (Home PCF 7301).
　　For example, the Pseud hPCF 7303 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
　　For example, the Pseud hPCF 7303 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
　　The Pseud hPCF 7303 may hold PCC rule, ADSF rule, ATSSS rule and other policy related rules for the UE 3.
　　Fig. 17 illustrates an example of the NRF update procedure within the Satellite.
The NRF 76 is located in the Satellite and provides the node discovery function for those of 5GC nodes that are located within the Satellite.
　　For example, the NRF 76 may be contacted by 5GC nodes in the Satellite if the Feeder link is not available.
　　For example, the NRF 76 may be contacted by 5GC nodes in the Satellite if the Feeder link is available.
　　The detailed processes of the First example of the Second Aspect are described below with reference to Fig. 17.
　　Step 1. The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
　　Step 2. The UE 3 performs the Registration procedure with the Authentication and Authorization procedure with AUSF 7801 and UDM 7501 in the HPLMN of the UE 3.
　　After the successful Registration procedure, the Pseud UDM 7502 may stores the subscriber data for the UE 3.
　　After the successful Authentication and Authorization procedure, the Pseud AUSF 7802 may store Authentication Vectors for the UE 3 for future use. The Authentication Vectors for the UE 3 for future use may be obtained by the Pseud AUSF 7802 using a mechanism that is disclosed by the Fourth example of the Second Aspect and the Fifth example of the Second Aspect.
　　Step 3. Once the Registration procedure is successfully completed, the Pseud UDM 7502 sends the Nnrf_NFManagement_NFRegister message to the NRF 76 including at least one of the NF type, PLMN ID and IP address. The NF type is set to the UDM.
　　The following bullets explain each parameter in details.
●　　NF type: The NF type indicates the Network Function type of the service consumer.
●　　PLMN ID: The PLMN ID indicates the PLMN where the service consumer belongs to. In this example, the PLMN ID may be a Home PLMN of the UE 3.
●　　IP address: The IP address indicates an IP address of the service consumer.
　　Step 4. Upon reception of the Nnrf_NFManagement_NFRegister message, the NRF 76 register the entry of the service consumer in the record.
　　The NRF 76 sends the Nnrf_NFManagement_NFRegister response message to the Pseud UDM 7502.
　　Step 5. Once the Authentication and Authorization procedure is successfully completed, the Pseud AUSF 7802 sends the Nnrf_NFManagement_NFRegister message to the NRF 76 including at least one of the NF type, PLMN ID and IP address. The NF type is set to the AUSF. Refer to Step 3 for parameter details.
　　Step 6. Upon reception of the Nnrf_NFManagement_NFRegister message, the NRF 76 register the entry of the service consumer in the record.
　　The NRF 76 sends the Nnrf_NFManagement_NFRegister response message to the Pseud AUSF 7802.
　　Step 7. The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is not available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite cannot communicate with 5GC nodes in the terrestrial location.
　　Step 8. The AMF 70, SMF 71, vPCF 7302, UPF 72, AF 201 and possibly other 5GC nodes in the Satellite make a query with NRF 76 using the Nnrf_NFDiscovery_Request service for UDM discovery and AUSF discovery and may find Pseud UDM 7502 and Pseud AUSF 7802 in the Satellite.
　　One example, the AMF 70, SMF 71, vPCF 7302, UPF 72, AF 201 and possibly other 5GC nodes make a query with NRF 76 using the Nnrf_NFDiscovery_Request service only when the Feeder link is not available.
　　One another example, the AMF 70, SMF 71, vPCF 7302, UPF 72, AF 201 and possibly other 5GC nodes make a query with NRF 76 using the Nnrf_NFDiscovery_Request service when the Feeder link is available.
　　Variant 1 of First example of the Second Aspect
　　The Registration procedure may be a use case of Step 8.
　　When the UE 3 initiates the Registration procedure during the Feeder link that connects to the UDM 7501 is unavailable, the AMF 70 performs the UDM discovery procedure with the NRF 76 and finds the Pseud UDM 7502. Then, the AMF 70 continues the Registration procedure with the Pseud UDM 7502.
　　Variant 2 of First example of the Second Aspect
　　The Authentication and Authorization procedure may be a use case of Step 8.
When the AMF 70 decides to perform the Authentication and Authorization procedure for the UE 3 during the Feeder link that connects to the AUSF 7801 is unavailable, the AMF 70 performs the AUSF discovery procedure with the NRF 76 and finds the Pseud AUSF 7802. Then, the AMF 70 continues the Authentication and Authorization procedure with the Pseud UDM 7502.
　　Variant 3 of First example of the Second Aspect
　　The IMS call control within the Satellite may be a use case of Step 8.
　　The IMS Registration procedure and IMS call are disclosed in this Variant.
　　The IMS Registration procedure:
　　If the AF 201 is the IMS (IP Multimedia Subsystem) and the IMS Client in the UE 3 performs the IMS Registration procedure during the Feeder link that connects to the UDM 7501 is unavailable, the IMS node (Example, S-CSCF) performs the UDM discovery procedure with the NRF 76 and finds the Pseud UDM 7502. Then, the IMS node continues the IMS Registration procedure with the Pseud UDM 7502. For example, the IMS node (Example, S-CSCF) performs the IMS level user Authentication (Example, Nhss_ImsUEAuthenticate_Get service) by contacting the Pseud UDM 7502.
　　The IMS call:
　　The assumption is that the two UE 3s (UE 3a and UE 3b are named for explanatory purpose in this variant) have been performed the IMS Registration procedure as disclosed in this valiant.
　　Then, the UE 3a makes an IMS originating call to the UE 3b.
　　In this case, the following steps are taken:
　　Step 1: The IMS node (S-CSCF) of the UE 3a receives the SIP Invite message and finds the IMS node (I-CSCF or S-CSCF) of the UE 3b.
　　Step 2: The IMS node (I-CSCF or S-CSCF) sends the SIP Invite message to the UE 3b and establishes the IMS connection between UE 3a and UE 3b without going through the ground network.
　　Second example of the Second Aspect
　　Fig. 18 illustrates an example of the Service Availability Notification procedure when the AMF 70 is located in the Satellite.
　　The Service Availability Notification procedure may be used when the AMF 70 is not located in the Satellite.
　　The detailed processes of the Second example of the Second Aspect are described below with reference to Fig. 18.
　　Step 1. The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
　　AMF Service:
　　Step 2-A. The UDM 7501 sends any AMF Service invoke message to the AMF 70.
　　Step 3-A. Upon reception of the AMF Service invoke message in Step 2-A, the AMF 70 sends the AMF Service response message to the UDM 7501 including the Feeder link status information. For the Feeder link status information, refer to Step 1 of Fig. 3.
　　Step 4-A. Independent from Step 2-A or Step 3-A, the AMF 70 sends the AMF Service Notify message to the UDM 7501 including the Feeder link status information. For the Feeder link status information, refer to Step 1 of Fig. 3.
　　One example, the UDM 7501 uses the received Feeder link status(s) when the UDM 7501 invokes the AMF service to the AMF 70. For example, the UDM 7501 does not invoke any AMF services provided by the AMF 70 if the Feeder link status indicates as unavailable.
　　UDM Service:
　　Step 2-B. The AMF 70 sends the UDM Service invoke message to the UDM 7501 including the Feeder link status information. For the Feeder link status information, refer to Step 1 of Fig. 3.
　　Step 3-B. Upon reception of the UDM Service invoke message in Step 2-B, the UDM 7501 sends the UDM Service response message to the AMF 70.
　　One example, the UDM 7501 uses the received Feeder link status information when the UDM 7501 invokes the AMF service to the AMF 70. For example, the UDM 7501 does not invoke any AMF services provided by the AMF 70 if the Feeder link status information indicates as unavailable.
　　Variant 1 of Second example of the Second Aspect
　　Steps 2-A to 4-A for the AMF Service may apply to any Services provided by other 5GC nodes.
　　For example, it may be SMF Service, UDM Service PCF Service and other Services.
　　Variant 2 of Second example of the Second Aspect
　　Although steps 2-A to 4-A for the AMF Service indicates that the UDM 7501 as the Service consumer, any 5GC nodes can be a Service consumer.
　　For example, the UDM 7501 may be replaced with AUSF 7801, hPCF 7301 and any other 5GC nodes.
　　Variant 3 of Second example of the Second Aspect
　　Steps 2-B to 3-B for the UDM Service may apply to any Services provided by other 5GC nodes.
　　For example, it may be SMF Service, AMF Service PCF Service and other Services. In this case, the UDM 7501 in Fig. 18 may be replaced with SMF, AMF and PCF respectively.
　　Variant 4 of Second example of the Second Aspect
　　In one example, in Fig. 18 the UDM 7501 may in advance subscribe with the AMF 70 in the satellite for notifications (periodic or event based) related to the status of the Feeder link. In that case the AMF 70 would regularly or based on an event (e.g., Feeder link status information change) notify the UDM 7501 by sending the Namf_Service_Notify as per step 4-A in Fig. 18 or any other message with the purpose to notify any changes in the status of the Feeder link.
　　Third example of the Second Aspect
　　Fig. 19 illustrates an example of the Service Availability Inquiry procedure when the AMF 70 is located in the Satellite.
　　The Service Availability Notification procedure may be used when the AMF 70 is not located in the Satellite.
　　The detailed processes of the Third example of the Second Aspect are described below with reference to Fig. 19.
　　Step 1. The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
　　Step 2. The UDM 7501 sends the Namf_Communication_AMFStatusChangeSubscribe message to the AMF 70 including at least one of GUAMI and Requested reporting period.
　　The following bullets explain each parameter in details.
●　　GUAMI: The GUAMI indicates the AMF identifier.
●　　Requested reporting period: The Requested reporting period indicates a how often that the AMF 70 reports a status to the UDM 7501. For example, if the reporting period is set as 10 minutes, the AMF 70 reports a status of the AMF 70 to the UDM 7501 every 10 minutes.
　　One example, the Requested reporting period may indicate "one time". If the "one time" is set to the Requested reporting period, the AMF 70 reports a status of the AMF 70 one time.
　　Step 3. Upon reception of the Namf_Communication_AMFStatusChangeSubscribe in Step 2, the AMF 70 sends the Namf_Communication_AMFStatusChangeNotify message to the UDM 7501 including the Feeder link status information. For the Feeder link status information, refer to Step 1 of Fig. 3.
　　In one example, the UDM 7501 uses the received Feeder link status(s) when the UDM 7501 invokes the AMF service to the AMF 70. For example, the UDM 7501 does not invoke any AMF services provided by the AMF 70 if the Feeder link status indicates as unavailable.
　　In another example, the UDM 7501 manages all UE(s) 3 as "Not reachable" if the UEs 3 are associated to the AMF 70 and the Feeder link status indicates that AMF 70 is not available.
　　Variant 2 of Third example of the Second Aspect
　　Although steps 2 to 3 indicate that the UDM 7501 as the Service consumer, any 5GC nodes can be a Service consumer.
　　For example, the UDM 7501 may be replaced with AUSF 7801, hPCF 7301 and any other 5GC nodes.
　　Fourth example of the Second Aspect
　　Fig. 20 illustrates an example of the Authentication procedure with Satellite access when the AMF 70 is located in the Satellite.
　　The Authentication procedure with Satellite access may be used when the AMF 70 is not located in the Satellite.
　　The detailed processes of the Fourth example of the Second Aspect are described below with reference to Fig. 20.
　　Step 1. The Feeder link that provides the connectivity to 5GC nodes in a terrestrial location is available. I.e., the gNB 501 and 5GC nodes that are located in the Satellite can communicate with 5GC nodes in the terrestrial location.
　　Step 2. The UE 3 sends a NAS message to the AMF 70 including User ID. The User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI.
　　For example, the NAS message may be Registration Request message, PDU Session Establishment Request message or Service Request message or any other NAS message.
　　Step 3. Upon reception of the NAS message in Step 2. The AMF 70 may decide to performs the Authentication and Authorization procedure for the UE 3.
　　The AMF 70 sends the Nausf_UEAuthentication_Authenticate Request to the AUSF 7801 including at least one of User ID, SN-name, AMF in Satellite and the number of vectors requested.
　　The following bullets explain each parameter in details.
●　　User ID: The User ID may be SUCI or SUPI.
●　　SN-name: The SN-name is the Serving Network name. In this case a PLMN of the AMF 70.
●　　AMF in Satellite: The AMF in Satellite indicates that the AMF 70 is located in the Satellite. It implicitly indicates that the AMF 70 may be disconnected from the HPLMN or any other PLMN.
●　　The number of vectors requested: The number of vectors requested indicates that the number of Authentication Vectors, both 5G HE AVs and 5G AVs, being requested by the AMF 70 in addition to the 5G AV for the Authentication and Authorization to be used this Authentication and Authorization procedure. I.e., the AMF 70 requests a list of 5G HE AVs and a list of 5G AVs for future use in a case where the Feeder link becomes unavailable.
　　Step 4. Upon reception of the Nausf_UEAuthentication_Authenticate Request message from the AMF 70 in Step 3, the AUSF 7801 sends the Nudm_UEAuthentication_Get Request message to the UDM 7501 including at least one of User ID, SN-name, AMF in Satellite and the number of vectors requested. Refer to Step 3 for parameter details.
　　Step 5. Upon reception of the Nudm_UEAuthentication_Get Request message from the AUSF 7801, the UDM 7501 decides an Authentication method, either EAP-AKA' or 5G AKA, to be taken and whether the UDM 7501 can accepts providing multiple 5G HE AVs to the AMF 70. The UDM 7501 may takes the received AMF in Satellite and a trust relationship with a VPLMN of the AMF 70 into account for the decision on providing multiple 5G HE AVs.
　　Step 6. The UDM 7501 sends the Nudm_UEAuthentication_Get Response message to the AUSF 7801 including at least one of User ID, SN-name, AMF in Satellite, the number of vectors requested and List of HE AV. The List of HE AV includes one or multiple HE AVs that can be used for Authentication and Authorization in future. For other parameter details, refer to Step 3.
　　The UDM 7501 includes the List of HE AV only if the UDM 7501 decides to provide multiple 5G HE Avs in Step 5.
　　Step 7. Upon reception of the Nudm_UEAuthentication_Get Response message from the UDM 7501, the AUSF 7801 decides whether the AUSF 7801 can accepts providing multiple 5G AVs to the AMF 70. The AUSF 7801 may takes the received AMF in Satellite and a trust relationship with a VPLMN of the AMF 70 into account for the decision on providing multiple 5G AVs.
　　Step 8. The AUSF 7801 sends the Nausf_UEAuthentication_Authenticate Response message to the AMF 70 including at least one of User ID, List of 5G HE AV and List of 5G AV.
　　The AUSF 7801 includes the List of AV only if the AUSF 7801 decides to provide multiple 5G Avs in Step 7.
　　Step 9. Either the Authentication procedure for EAP-AKA' continues from Step 4 in Section 6.1.3.1 in NPL 8 or the Authentication procedure for 5G-AKA continues from step 6 in Section 6.1.3.2.0 in NPL 8 depending on the Authentication method selection in Step 5.
　　Step 10. After successful Authentication procedure, the AMF 70 sores the received List of 5G AV in Step 8 to the MM context of the UE 3 and shares the received List of 5G HE AV in Step 8 with the Pseud AUSF 7802.
　　One example, the List of 5G HE AV and List of 5G AV are used by the AMF 70 in a case where the Authentication and Authorization procedure is needed but the Feeder link is not available.
　　System overview
　　Fig. 21 schematically illustrates an example of a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.
　　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.
　　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).
　　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.
　　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'.
　　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.
　　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).
　　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).
　　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).
　　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).
　　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.
　　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 Network Repository Function (NRF) 76, a Network Slice Admission Control Function (NSACF) 77 and an Authentication Server Function (AUSF) 78. 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 and NSACF 77 for the roaming-out UE 3.
　　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 a case where 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.
　　The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface.
　　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).
　　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.
　　For example, the following messages are communicated over the RRC layer to support AS signaling.
●　　RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup Request message.
　　　　establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue.
●　　RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup message.
　　　　masterCellGroup and radioBearerConfig
●　　RRC setup complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC setup complete message.
　　　　guami-Type, iab-NodeIndication, idleMeasAvailable, ue-MeasurementsAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity, s-NSSAI-List, onboardingRequest
The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and/or the like). The N1 interface is responsible to provide a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface.
●　　Registration Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Registration Request message.
　　　　5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requested NB-N1 mode DRX parameters.
●　　Registration Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Registration Accept message.
　　　　5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters and Extended rejected NSSAI.
●　　Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Registration Complete message.
　　　　SOR transparent container.
●　　Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Authentication Request message.
　　　　ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge) and EAP message.
●　　Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Response message.
　　　　Authentication response message identity, Authentication response parameter and EAP message.
●　　Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Result message.
　　　　ngKSI, EAP message and ABBA.
●　　Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Failure message.
　　　　Authentication failure message identity, 5GMM cause and Authentication failure parameter.
●　　Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Reject message.
　　　　EAP message.
●　　Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Request message.
　　　　ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.
●　　Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Accept message.
　　　　PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value.
●　　Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Reject message.
　　　　5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.
●　　Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Command message.
　　　　Configuration update indication,5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI.
●　　Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Complete message.
　　　　Configuration update complete message identity.
　　User equipment (UE)
　　Fig. 22 is an example of a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in Fig. 22, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating/sending/receiving) signalling and uplink/downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. Such signalling may include, for example, appropriately formatted signalling messages (e.g., a Registration Request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.
　　The UE 3 may, for example, support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　The UE 3 may, for example, be an item of equipment for production or manufacture and/or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and/or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and/or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and/or related machinery; paper converting machinery; chemical machinery; mining and/or construction machinery and/or related equipment; machinery and/or implements for agriculture, forestry and/or fisheries; safety and/or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and/or application systems for any of the previously mentioned equipment or machinery etc.).
　　The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).
　　The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).
　　The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and/or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).
　　The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).
　　The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and/or system, a weapon, an item of cutlery, a hand tool, or the like.
The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).
　　The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and/or wireless communication technologies.
　　Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and/or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and/or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g., vehicles) or attached to animals or persons to be monitored/tracked.
　　It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
　　It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.
　　The UE 3 may be a smart phone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device). For a wearable device, the UE 3 may be a reduced capability device (RedCap).
　　The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g., Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).
　　(R)AN node
　　Fig. 23 is an example of a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.
　　The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g., directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e., messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g., Master Information and System information) in a sending case.
　　The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
　　The (R)AN node 5 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　The gNB 501, the NTN Gateway 502 and the gNB-DU 61 may have same components to the (R)AN node 5. The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.
　　System overview of (R)AN node 5 based on O-RAN architecture
　　Fig. 24 schematically illustrates an example of a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.
　　The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit, the DU 61 can be integrated/combined with the CU 62 as another integrated/combined unit. Any functionality in the description for a unit (e.g., one of RU 60, DU 61 and CU 62) can be implemented in the integrated/combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and/or the like).
　　The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and/or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and/or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and/or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2"/ "N3" interface(s) and/or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes via an appropriate interface (such as the so-called "N3" interface(s) and/or the like).
　　Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionalities to communicate with a UE 3 (e.g., the Network Relay UE 300) over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.
　　Radio Unit (RU)
　　Fig. 25 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.
　　The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g., directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3 (e.g., the Network Relay UE 300)), and in particular, relating to MAC layer and RLC layer.
　　The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
　　The RU 60 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As described above, the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated/combined unit above.
　　Distributed Unit (DU)
　　Fig. 26 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421) is responsible for handling (generating/sending/receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.
　　The DU 61 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As described above, the RU 60 can be integrated/combined with the DU 61 or CU 62 as an integrated/combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated/combined unit above.
　　Centralized Unit (CU)
　　Fig. 27 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421) is responsible for handling (generating/sending/receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.
　　The CU 62 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　As described above, the CU 62 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated/combined unit above.
　　AMF
　　Fig. 28 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3 (e.g., the Network Relay UE 300 and the UE 3), the NSSF 76) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating/sending/receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g., via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a Registration Request message and associated response messages) relating to access and mobility management procedures (for the UE 3).
　　The AMF 70 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AMF 7001, the AMF 7002, the MN AMF 7001 and the SN AMF 7002 may have same components to the AMF 70.
　　SMF
　　Fig. 29 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421) is responsible for handling (generating/sending/receiving) signalling between the SMF 71 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
　　The SMF 71 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The SMF 7101 and the SMF 7102 may have same components to the SMF 71.
　　UPF
　　Fig. 30 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating/sending/receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
　　The UPF 72 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　PCF
　　Fig. 31 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating/sending/receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
　　The PCF 73 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　The hPCF 7301, the vPCF 7302, the Pseud hPCF 7303 may have same components to the PCF 73.
　　NWDAF
　　Fig. 32 is a block diagram illustrating the main components of the NWDAF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70 and the UDM 75) via a network interface 742. A controller 743 controls the operation of the NWDAF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating/sending/receiving) signalling between the NWDAF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
　　The NWDAF 74 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　UDM
　　Fig. 33 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating/sending/receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 (e.g., the Network Relay UE 300 and the UE 3) when the UE 3 is roaming-out). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).
　　The UDM 75 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　The UDM 7501 and the Pseud UDM 7502 may have same components to the UDM 75.
　　NRF
　　Fig. 34 is a block diagram illustrating the main components of the NRF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NRF 76 in accordance with software stored in a memory 764. Software may be pre-installed in the memory 764 and/or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating/sending/receiving) signalling between the NRF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).
　　The NRF 76 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　NSACF
　　Fig. 35 is a block diagram illustrating the main components of the NSACF 77. As shown, the apparatus includes a transceiver circuit 771 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 772. A controller 773 controls the operation of the NSACF 77 in accordance with the software stored in a memory 774. The Software may be pre-installed in the memory 774 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating/sending/receiving) signalling between the NSACF 77 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).
　　The NSACF 77 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　AUSF
　　Fig. 36 is a block diagram illustrating the main components of the AUSF 78. As shown, the apparatus includes a transceiver circuit 781 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the AUSF 78 in accordance with the software stored in a memory 784. The Software may be pre-installed in the memory 784 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating/sending/receiving) signalling between the AUSF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).
　　The AUSF 78 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　The AUSF 7801 and the Pseud AUSF 7802 may have same components to the AUSF 78.
　　AF
　　Fig. 37 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3 (e.g., the Network Relay UE 300 and the UE 3)) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421) is responsible for handling (generating/sending/receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g., a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).
　　The AF 201 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
　　Modifications and Alternatives
　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.
　　In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.
　　Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories / caches (program and/or data); processing registers; communication buses (e.g., control, data and/or address buses); direct memory access (DMA) functions, hardware or software implemented counters, pointers and/or timers; and/or the like.
　　In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.
In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g., BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.
　　Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/tablet computers, web browsers, e-book readers and/or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
　　Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.
　　As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.
　　It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.
　　The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
　　The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
　　While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).
　　This application is based upon and claims the benefit of priority from Indian Patent Application No. 202311055549, filed on August 18, 2023, the disclosure of which is incorporated herein in its entirety by reference.
　　Supplementary notes
　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.
　　<First Supplementary notes>
　　　　(Supplementary note A1)
　　A method of a Radio Access Network (RAN) node comprising:
　　sending, to a first core network node, a first message including Store and Forward (S&F) related information; and
　　receiving, from the first core network node, a second message including S&F related information of a second core network node.
　　　　(Supplementary note A2)
　　The method according to supplementary note A1, wherein the S&F related information includes at least one of S&F support, List of Out of Service TAI, Supported TAI list, or S&F capacity.
　　　　(Supplementary note A3)
　　The method according to supplementary note A1 or A2, wherein the S&F related information of the second core network node is a S&F support indication of the second core network node.
　　　　(Supplementary note A4)
　　The method according to any one of supplementary notes A1 to A3, wherein the first core network node is an Access and Mobility Management Function (AMF) node or a User Plane Function (UPF) node.
　　　　(Supplementary note A5)
　　The method according to any one of supplementary notes A1 to A4, wherein the first core network node and the second core network node is the same core network node.
　　　　(Supplementary note A6)
　　A method of a User Equipment (UE) comprising:
　　receiving, from a Radio Access Network (RAN) node, a first message including Store and Forward (S&F) related information; and
　　sending a second message including S&F related information of the UE.
　　　　(Supplementary note A7)
　　A Radio Access Network (RAN) node comprising:
　　means for sending, to a first core network node, a first message including Store and Forward (S&F) related information; and
　　means for receiving, from the first core network node, a second message including S&F related information of a second core network node.
　　　　(Supplementary note A8)
　　The Radio Access Network node according to supplementary note A7, wherein the S&F related information includes at least one of S&F support, List of Out of Service TAI, Supported TAI list, or S&F capacity.
　　　　(Supplementary note A9)
　　The Radio Access Network node according to supplementary note A7 or A8, wherein the S&F related information of the second core network node is a S&F support indication of the second core network node.
　　　　(Supplementary note A10)
　　The Radio Access Network node according to any one of supplementary notes A7 to A9, wherein the first core network node is an Access and Mobility Management Function (AMF) node or a User Plane Function (UPF) node.
　　　　(Supplementary note A11)
　　The Radio Access Network node according to any one of supplementary notes A7 to A10, wherein the first core network node and the second core network node is the same core network node.
　　　　(Supplementary note A12)
　　A User Equipment (UE) comprising:
　　means for receiving, from a Radio Access Network (RAN) node, a first message including Store and Forward (S&F) related information; and
　　means for sending a second message including S&F related information of the UE.
　　<Second Supplementary notes>
　　　　(Supplementary note B1)
　　A method of a first core network node comprising:
　　sending, to a second core network node, a first message including Feeder link status information.
　　　　(Supplementary note B2)
　　A first core network node comprising:
　　means for sending, to a second core network node, a first message including Feeder link status information.
1　　TELECOMMUNICATION SYSTEM
3　　USER EQUIPMENT (UE)
5　　(R)AN NODE
501　　gNB
502　　NTN GATEWAY
60　　RADIO UNIT (RU)
61　　DISTRIBUTED UNIT (DU)
62　　CENTRALIZED UNIT (CU)
7　　CORE NETWORK
70　　ACCESS AND MOBILITY MANAGEMENT FUNCTION (AMF)
71　　SESSION MANAGEMENT FUNCTION (SMF)
72　　USER PLANE FUNCTION (UPF)
73, 7301, 7302, 7303　　POLICY CONTROL FUNCTION (PCF)
74　　NETWORK DATA ANALYTICS FUNCTION (NWDAF)
75, 7501, 7502　　UNIFIED DATA MANAGEMENT (UDM)
76　　NETWORK REPOSITORY FUNCTION (NRF)
77　　NETWORK SLICE ADMISSION CONTROL FUNCTION (NSACF)
78, 7801, 7802　　AUTHENTICATION SERVER FUNCTION (AUSF)
20　　DATA NETWORK
201　　APPLICATION FUNCTION (AF)
31, 51, 601, 611, 621, 701, 711, 721, 731, 741, 751, 761, 771, 781, 2011　　TRANSCEIVER CIRCUIT
32, 52, 602　　ANTENNA
53, 603, 612, 622, 702, 712, 722, 732, 742, 752, 762, 772, 782, 2012　　NETWORK INTERFACE
33, 54, 604, 613, 623, 703, 713, 723, 733, 743, 753, 763, 773, 2013　　CONTROLLER
34　　USER INTERFACE
35　　UNIVERSAL SUBSCRIBER IDENTITY MODULE (USIM)
36, 55, 605, 614, 624, 704, 714, 724, 734, 744, 754, 764, 774, 784, 2014　　MEMORY
361, 551, 6051, 6141, 6241, 7041, 7141, 7241, 7341, 7441, 7541, 7641, 7741, 7841, 20141　　OPERATING SYSTEM
362, 552, 6052, 6142, 6242, 7042, 7142, 7242, 7342, 7442, 7542, 7642, 7742, 7842, 20142　　COMMUNICATIONS CONTROL MODULE
3621, 5521, 60521, 61421, 62421, 70421, 71421, 72421, 73421, 74421, 75421, 76421, 77421, 78421, 201421　　TRANSCEIVER CONTROL MODULE

Claims (7)

  1. 　　A method of a first core network node comprising:
    　　sending, to a second core network node, a first message including information related to Feeder link.
  2. 　　A first core network node comprising:
    　　means for sending, to a second core network node, a first message including information related to Feeder link.
  3. 　　The first core network node according to claim 2, wherein the information includes Feeder link identifier, the Feeder link ID indicating an associated Feeder link with tracking Area Identity.
  4. 　　The first core network node according to claim 2, wherein the information includes Feeder link status, the Feeder link status indicating whether the Feeder link is available or not.
  5. 　　The first core network node according to claim 2, wherein the information includes shut down time, the shut down time indicating when the Feeder link will become not available.
  6. 　　The first core network node according to claim 2, wherein the information includes time to recovery, the time to recovery indicating when the Feeder link will become available.
  7. 　　The first core network node according to claim 2, wherein the information includes orbit characteristics, the orbit characteristics indicating a Feeder link availability that corresponds to an Orbit of connected satellite where a Radio Access Network (RAN) or a port of the RAN is located.
PCT/JP2024/026251 2023-08-18 2024-07-23 Method of first core network node and first core network node Pending WO2025041508A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202311055549 2023-08-18
IN202311055549 2023-08-18

Publications (1)

Publication Number Publication Date
WO2025041508A1 true WO2025041508A1 (en) 2025-02-27

Family

ID=94731680

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/026251 Pending WO2025041508A1 (en) 2023-08-18 2024-07-23 Method of first core network node and first core network node

Country Status (1)

Country Link
WO (1) WO2025041508A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3958479A1 (en) * 2019-04-18 2022-02-23 Datang Mobile Communications Equipment Co., Ltd. Method and apparatus for determining satellite communication system parameter, terminal, and service device
WO2022215122A1 (en) * 2021-04-05 2022-10-13 株式会社Ｎｔｔドコモ Terminal and base station

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3958479A1 (en) * 2019-04-18 2022-02-23 Datang Mobile Communications Equipment Co., Ltd. Method and apparatus for determining satellite communication system parameter, terminal, and service device
WO2022215122A1 (en) * 2021-04-05 2022-10-13 株式会社Ｎｔｔドコモ Terminal and base station

Similar Documents

Publication Publication Date Title
JP7694804B2 (en) Method of gNB-CU-CP device, method of AMF device, method of SMF device, gNB-CU-CP device, AMF device, SMF device, and UPF device
WO2022270258A1 (en) Method of access and mobility management function (amf) apparatus, method of user equipment (ue), method of network slice admission control function (nsacf) apparatus, method of radio access network (ran) node, method of policy control function (pcf) apparatus, amf apparatus, ue, nsacf apparatus, ran node and pcf apparatus
WO2023080032A1 (en) Method of application function (af) apparatus, method of network exposure function (nef) apparatus, method of unified data management (udm) apparatus, method of access and mobility management function (amf) apparatus, method of user equipment (ue), method of policy control function (pcf) apparatus, method of radio access network (ran) node, af apparatus, nef apparatus, udm apparatus, amf apparatus, ue, pcf apparatus and ran node
US20240260112A1 (en) Method performed by radio terminal and radio terminal
WO2023032528A1 (en) METHOD OF gNB-DU APPARATUS, METHOD OF gNB-CU-UP APPARATUS, METHOD OF AMF APPARATUS, METHOD OF FIRST gNB-CU-CP APPARATUS, gNB-DU APPARATUS, gNB-CU-UP APPARATUS, AMF APPARATUS AND FIRST gNB-CU-CP APPARATUS
WO2023145526A1 (en) Method of user equipment (ue), method of communication apparatus, ue and communication apparatus
US20250184261A1 (en) Method for policy control function (pcf) and pcf
WO2023002991A1 (en) Access and mobility management function (amf) device, user equipment (ue), method of amf device and method of ue
WO2024162185A1 (en) Access and mobility management function, amf, shared radio access network, ran, and method
WO2024150678A1 (en) Radio terminal, core network node, unified data management (udm), home subscriber server(hss),user equipment (ue), and method
WO2025041508A1 (en) Method of first core network node and first core network node
WO2025041507A1 (en) Method of radio access network node, method of user equipment, radio access network node, and user equipment
WO2025069793A1 (en) Method of user equipment (ue), method of access and mobility management function (amf), ue, and amf
WO2025069797A1 (en) Method of user equipment (ue), method of access and mobility management function (amf), ue, and amf
WO2025052804A1 (en) Method of user equipment, method of network node, user equipment, and network node
WO2025052803A1 (en) Method of user equipment, method of network node, user equipment, and network node
WO2025211350A1 (en) Method performed by user equipment (ue), method performed by first core network (cn) device, user equipment (ue), and first core network (cn) device
WO2025033139A1 (en) Method of first communication apparatus, method of communication apparatus, first communication apparatus and communication apparatus
WO2025211365A1 (en) Method performed by user equipment, method performed by first core network device, user equipment, and first core network device
WO2025211360A1 (en) Method performed by user equipment (ue), method performed by first core network (cn) device, user equipment (ue), and first core network (cn) device
WO2024185489A1 (en) User equipment, first access and mobility management function, unified data management, and method thereof
WO2025018243A1 (en) Radio terminal, first core network node, second core network node, third core network node, fourth core network node, method for a radio terminal, method for a first core network node, method for a second core network node, method for a third core network node, and method for a fourth core network node
WO2024225050A1 (en) Method of remote user equipment (ue), method of first communication apparatus, remote ue and first communication apparatus
WO2025018245A1 (en) Radio terminal, master first core network node, secondary first core network node, second core network node, fourth core network node, method for radio terminal, method for master first core network node, method for secondary first core network node, method for second core network node, and method for fourth core network node
WO2025018277A1 (en) Method of user equipment (ue) and ue

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24856202

Country of ref document: EP

Kind code of ref document: A1