[go: up one dir, main page]

WO2025052803A1 - Procédé d'équipement utilisateur, procédé de nœud de réseau, équipement utilisateur et nœud de réseau - Google Patents

Procédé d'équipement utilisateur, procédé de nœud de réseau, équipement utilisateur et nœud de réseau Download PDF

Info

Publication number
WO2025052803A1
WO2025052803A1 PCT/JP2024/026907 JP2024026907W WO2025052803A1 WO 2025052803 A1 WO2025052803 A1 WO 2025052803A1 JP 2024026907 W JP2024026907 W JP 2024026907W WO 2025052803 A1 WO2025052803 A1 WO 2025052803A1
Authority
WO
WIPO (PCT)
Prior art keywords
femtocell
network
message
csg
network node
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/026907
Other languages
English (en)
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 WO2025052803A1 publication Critical patent/WO2025052803A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • 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/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present disclosure relates to a method of a User Equipment (UE), a method of a network node, a User Equipment (UE), a network node etc.
  • UE User Equipment
  • UE User Equipment
  • High bandwidth and throughput with 5G are required indoors to enable new immersive applications such as AR/VR/MR, etc. While a lot of capacity is required indoor, outdoor to indoor coverage with 5G mid and high-bands is limited.
  • NPL 1 3GPP TR 21.905: "Vocabulary for 3GPP Specifications", V17.1.0 (2021-12)
  • NPL 2 3GPP TS 33.320: "Security of Home Node B (HNB)/Home evolved Node B (HeNB)", V17.0.0 (2022-03)
  • NPL 3 3GPP TS 23.003: "Numbering, addressing and identification”.
  • NPL 4 3GPP TS 23.501: "System architecture for the 5G System (5GS)”.
  • NPL 5 3GPP TS 23.502: “Procedures for the 5G System (5GS)".
  • 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 NPL 8: 3GPP TS 33.501: "Security architecture and procedures for 5G system”.
  • NPL 9 3GPP TS 37.340: “Multi-connectivity Stage 2".
  • NPL 10 3GPP TS 38.413: "NG Application Protocol (NGAP)”.
  • V17.5.0 (2023-06)
  • 5G Femtocell Although there is strong market demand for 5G Femtocell deployments, the current 3GPP standard for 5G system does not support 5G Femtocell access. Lack of 5G Femtocell support may prevent from deploying a cost-effective way to improve 5G indoor coverage.
  • the present disclosure provides a method of a User Equipment (UE) including: performing a registration procedure using a 5G Femtocell.
  • UE User Equipment
  • the present disclosure provides a method of a network node including: performing a registration procedure using a 5G Femtocell.
  • the present disclosure provides a method of a network node including: performing a 5G Femtocell setup procedure.
  • the present disclosure provides a User Equipment (UE) including: means for performing a registration procedure using a 5G Femtocell.
  • UE User Equipment
  • the present disclosure provides a network node including: means for performing a registration procedure using a 5G Femtocell.
  • the present disclosure provides a network node including: means for performing a 5G Femtocell setup procedure.
  • Fig. 1 is a diagram illustrating a configuration example of an Architecture supporting 5G Femtocell of a First example of a First Aspect.
  • Fig. 2 is a diagram illustrating a configuration example of a Protocol stack of a First example of the First Aspect.
  • Fig. 3 is a diagram illustrating a configuration example of a Protocol stack of a First example of the First Aspect.
  • Fig. 4 is a diagram illustrating a configuration example of a Protocol stack of a First example of the First Aspect.
  • Fig. 5 is a diagram illustrating a configuration example of a Protocol stack of a First example of the First Aspect.
  • Fig. 1 is a diagram illustrating a configuration example of an Architecture supporting 5G Femtocell of a First example of a First Aspect.
  • Fig. 2 is a diagram illustrating a configuration example of a Protocol stack of a First example of the First Aspect.
  • Fig. 3 is a diagram illustrating a configuration example of a Protocol
  • FIG. 6 is a Signaling diagram of a Second example of the First Aspect.
  • Fig. 7 is a Signaling diagram of a Third example of the First Aspect.
  • Fig. 8 is a formant of the CSG Identifier of a Third example of the First Aspect.
  • Fig. 9 is an example of a CSG support indication bit of a Fourth example of the First Aspect.
  • Fig. 10 is an example of an access restriction for 5G CAS cell of a Fourth example of the First Aspect.
  • Fig. 11 is a Signaling diagram of a Fifth example of the First Aspect.
  • Fig. 12 is a Signaling diagram of a Sixth example of the First Aspect.
  • Fig. 13 is an Architecture supporting 5G Femtocell of a First example of a Second Aspect.
  • Fig. 13 is an Architecture supporting 5G Femtocell of a First example of a Second Aspect.
  • Fig. 13 is an Architecture supporting 5G Femtocell of a First example
  • Fig. 14 is a Signaling diagram of a Second example of the Second Aspect.
  • Fig. 15 is a Signaling diagram of a Fifth example of the Second Aspect.
  • Fig. 16 is a diagram illustrating a configuration example of an Architecture supporting 5G Femtocell of a First example of a Third Aspect.
  • Fig. 17 is a Signaling diagram of a Second example of the Third Aspect.
  • Fig. 18 is a Signaling diagram of a Fourth example of the Third Aspect.
  • Fig. 19 is a Signaling diagram of a Fifth example of the Third Aspect.
  • Fig. 20 is a diagram illustrating a configuration example of a system overview.
  • Fig. 21 is a block diagram illustrating a configuration example of a UE.
  • Fig. 21 is a block diagram illustrating a configuration example of a UE.
  • FIG. 22 is a block diagram illustrating a configuration example of an (R)AN node.
  • Fig. 23 is a diagram illustrating a configuration example of a System overview of (R)AN node based on O-RAN architecture.
  • Fig. 24 is a block diagram illustrating a configuration example of an RU.
  • Fig. 25 is a block diagram illustrating a configuration example of a DU.
  • Fig. 26 is a block diagram illustrating a configuration example of a CU.
  • Fig. 27 is a block diagram illustrating a configuration example of an AMF.
  • Fig. 28 is a block diagram illustrating a configuration example of an SMF.
  • Fig. 29 is a block diagram illustrating a configuration example of a UPF.
  • FIG. 30 is a block diagram illustrating a configuration example of a PCF.
  • Fig. 31 is a block diagram illustrating a configuration example of an NWDAF.
  • Fig. 32 is a block diagram illustrating a configuration example of a UDM.
  • Fig. 33 is a block diagram illustrating a configuration example of an NSSF.
  • Fig. 34 is a block diagram illustrating a configuration example of an AAA Server.
  • Fig. 35 is a block diagram illustrating a configuration example of an NRF.
  • Fig. 36 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.
  • 5G Femtocell offers a cost-effective way to improve 5G indoor coverage, and offload macro gNB network traffic.
  • 5G Femtocell can use higher frequency bands, allowing premises owners to deploy Femtocell on their own, and leading to efficient and effective usage of higher frequency spectrum.
  • a method of a network node according to example aspect of this disclosure includes performing a 5G Femtocell setup procedure.
  • a User Equipment (UE) includes means for performing a registration procedure using a 5G Femtocell.
  • a network node includes means for performing a registration procedure using a 5G Femtocell.
  • a network node includes performing a 5G Femtocell setup procedure.
  • This aspect discloses an architecture and mechanisms to support the 5G Femtocell 501 in 5GS.
  • This example includes an architecture to support the 5G Femtocell 501 in 5GS.
  • Fig. 1 illustrates an example of an 5GS architecture that supports 5G Femtocells.
  • the 5G Femtocell 501 represents an 5G Femtocell in a private premise, for example, private house, office, school, park, factory, hospital, museum, stadium or etc.
  • the 5G Femtocell 501 is connected to the SecGW 502 that is located at the PLMN.
  • the SecGW 502 in Fig. 1 may be considered as an entity in 5G RAN node 5 of the PLMN or an entity in the Core Network 7 of the PLMN.
  • the connection between the 5G Femtocell 501 and the SecGW 502 are security protected adapting the IPsec technology.
  • the 5G RAN node 5 may include the 5G Femtocell 501.
  • the SecGW 502 may be expressed as SeGW.
  • the 5G Femtocell 501 uses the FR1 (Frequency Range 1, 450MHz - 6000MHz).
  • the SecGW 502 is located at the 5GC (Core network 7) in the PLMN.
  • the SecGW 502 is located at the 5G RAN node 5 in the PLMN.
  • the SecGW 502 may be expressed by different ways, for example, N3IWF, Security gateway for Femtocell access, Security Gateway for Femtocell, etc.
  • the AAA Server 77 is an authentication and authorization server for the 5G Femtocell 501.
  • the AAA Server may be located at a Credentials Holder (CH)'s network.
  • CH Credentials Holder
  • a connection between the 5G Femtocell 501 and the UPF 72 may be directly connected without traversing the SecGW 502. I.e., there is no IPsec tunnel for the connection between the 5G Femtocell 501 and the UPF 72.
  • a connection between the 5G Femtocell 501 and the UPF 72 may always be connected though the SecGW 502. I.e., there is the IPsec tunnel for the connection between the 5G Femtocell 501 and the UPF 72.
  • the user data can be monitored by the PLMN with this connection model.
  • the SMF 71 may be located at the private premise close to the 5G Femtocell 501 if the UPF 72 is located at the private premise.
  • the AF 201 may be located at the private premise close to the 5G Femtocell 501 if the UPF 72 is located at the private premise.
  • this aspect also discloses protocol stacks between the 5G Femtocell 501 and AMF 70 and between the 5G Femtocell 501 and UPF 72.
  • Fig. 2 illustrates an example of a protocol stack between the 5G Femtocell 501 and the AMF 70 for an Internet Protocol IPv4 address with the NAT 503 located between the 5G Femtocell 501 and the AMF 70.
  • the IPsec connection is established between the 5G Femtocell 501 and the AMF 70 in order to secure control signalling in both the STCP layer and the NGAP layer.
  • the STCP connection as well as the NGAP connection are established after the IPsec layer is deployed between the 5G Femtocell 501 and the AMF 70.
  • the NGAP connection is established based on the signalling diagram as disclosed by the Second example of the First Aspect.
  • Fig. 3 illustrates an example of a protocol stack between the 5G Femtocell 501 and the AMF 70 for an Internet Protocol IPv6 address.
  • the IPsec connection is established between the 5G Femtocell 501 and the AMF 70 in order to secure control signalling in both the STCP layer and the NGAP layer.
  • the STCP connection as well as the NGAP connection are established after the IPsec layer is deployed between the 5G Femtocell 501 and the AMF 70.
  • the NGAP connection is established based on the signalling diagram as disclosed by the Second example of the First Aspect.
  • Fig. 4 illustrates an example of a protocol stack between the 5G Femtocell 501 and the UPF 72 for an Internet Protocol IPv4 address with the NAT 503 located between the 5G Femtocell 501 and the UPF 72.
  • the IPsec connection is established between the 5G Femtocell 501 and the UPF 72 in order to secure control signalling in both the UDP layer and the GTP-U layer.
  • Fig. 5 illustrates an example of a protocol stack between the 5G Femtocell 501 and the UPF 72 for an Internet Protocol IPv6 address.
  • the IPsec connection is established between the 5G Femtocell 501 and the UPF 72 in order to secure control signalling in both the UDP layer and the GTP-U layer.
  • This example includes a mechanism of the initialization procedure for the 5G Femtocell 501.
  • the initialization procedure is, for example, booting up procedure, but it can be any other procedure.
  • This aspect may be referred when the 5G Femtocell 501 boots up very first time, when the 5G Femtocell 501 restarts, when the system configuration of the 5G Femtocell 501 is updated.
  • While this example discloses a mechanism to initialize the IP layer for deploying the IPsec tunnel between the 5G Femtocell 501 and SecGW 502, the third example discloses a mechanism to initialize the NGAP layer.
  • Fig. 6 illustrates an example of the initialization procedure for the 5G Femtocell 501.
  • the detailed processes of the Second example of the First Aspect are described below with reference to Fig. 6.
  • Step 1 The 5G Femtocell 501 is ready to start the initialization procedure. For example, the 5G Femtocell 501 boots up very first time, when the 5G Femtocell 501 restarts, when the system configuration of the 5G Femtocell 501 is updated.
  • Step 2 The 5G Femtocell 501 sends the IKE_SA_INIT request message to the SecGW 502.
  • Step 3 Upon reception of the IKE_SA_INIT request message from the 5G Femtocell 501, the SecGW 502 sends the IKE_SA_INIT response message, requesting a certificate from the 5G Femtocell 501.
  • Step 4 Upon reception of the I IKE_SA_INIT response message from the SecGW 502, the 5G Femtocell 501 sends the IKE_AUTH request message including AUTH1 and Idi.
  • the AUTH1 is an authentication parameter of the 5G Femtocell 501.
  • the CSG ID is set to the Idi as the identity of the 5G Femtocell 501.
  • the 5G Femtocell 501 also requests a certificate from the SecGW 502.
  • Step 5 Upon reception of the IKE_AUTH request message from the 5G Femtocell 501, SecGW 502 checks the correctness of the AUTH1 received from the 5G Femtocell 501 and calculates the AUTH parameter as to set to the AUTH2.
  • Step 6 The SecGW 502 sends the IKE_AUTH response message to the 5G Femtocell 501 including with AUTH2 and Idi.
  • the AUTH2 is an authentication parameter of the SecGW 502.
  • the Idi is an identifier of the SecGW 502.
  • Step 7 Upon reception of the IKE_AUTH response message from the SecGW 502, the 5G Femtocell 501 checks the correctness of the AUTH2 received from the SecGW 502.
  • Step 8 The 5G Femtocell 501 sends another IKE_AUTH request message including Idi to perform EAP authentication.
  • the CSG ID is set to the Idi as the identity of the 5G Femtocell 501.
  • Step 9 The SecGW 502 sends the Authentication Request message with an empty EAP AVP to the AAA Server 77, containing the identity received in IKE_AUTH request message received in step 8.
  • Step 10 The EAP-AKA-based authentication procedure continues with Step 10 in section A2 in NPL 2 take place with the following terminology replacements.
  • ⁇ H(e)NB is replaced with the 5G Femtocell 501.
  • ⁇ SeGW is replaced with the SecGW 502.
  • AAA-Server is replaced with the AAA Server 77.
  • ⁇ HSS is replaced with the UDM 75.
  • Step 11 After successful EAP-AKA-based authentication procedure, the 5G Femtocell 501 performs the NG Setup procedure with the AMF 70.
  • Steps 2 to 10 may not take place.
  • Fig. 7 illustrates an example of the setup procedure for the 5G Femtocell 501. The detailed processes of the Third example of the First Aspect are described below with reference to Fig. 7.
  • the 5G Femtocell 501 triggers the NG Setup procedure. For example, in a case where the 5G Femtocell 501 restarts or the configuration of the 5G Femtocell 501 is updated, the 5G Femtocell 501 may trigger the NG Setup procedure.
  • Step 2 The 5G Femtocell 501 sends an NG Setup request message to the AMF 70 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, and List of supported UPF information.
  • the following bullets explain each parameter in detail.
  • the 5G Femtocell supported indicates that the 5G Femtocell related features (for example, CSG handling, etc.) are supported by the 5G Femtocell 501.
  • the 5G Femtocell supported may have a different expression and it has a several value.
  • the 5G Femtocell supported may be called as BS type (Base Station type) and it may have one or more of the following values for example: 5G Femtocell Open 5G Femtocell Private 5G Femtocell NPN 5G Femtocell PNI-NPN 5G Femtocell SNPN 5G Femtocell 5G Femtocell in DU for UPF direct connection Open 5G Femtocell in DU for UPF direct connection Private 5G Femtocell in DU for UPF direct connection NPN 5G Femtocell in DU for UPF direct connection PNI-NPN 5G Femtocell in DU for UPF direct connection SNPN 5G Femtocell in DU for UPF direct connection
  • the CSG ID indicates the CSG (Closed Subscriber Group) identifier.
  • the CSG ID may be the same as the CAG (Closed Access Group) identifier or CAG identity that is used for the Public Network Integrated NPN as defined in NPL 4.
  • CSG Identifier may be used as the same as the CAG identifier in the RRC protocol as well as NAS protocols.
  • the CSG indicator field in the CAG Identifier indicates that this information is used to express the CSG Identifier as a discriminator and the value of the CSG Identifier is in the f (27 bit-length) in the CAG Identifier.
  • the value part of the CSG Identifier can commonly be managed with the Closed Subscriber Group for EPS as defined in section 4.7 in NPL 3.
  • Value "00000" in the CSG indicator field may be a discriminator to indicate that the CAG identifier (32 bit-length) applies to the CSG Identifier and the CSG Identifier field (27 bit-length) is considered as a value of the CSG Identifier.
  • Value "11111" in the CSG indicator field may be a discriminator to indicate that the CAG identifier (32 bit-length) applies to the CSG Identifier and the CSG Identifier field (27 bit-length) is considered as a value of the CSG Identifier.
  • the MSB (Most Significant Bit) of the CAG Identifier may be used to distinguish whether it is a CAG Identifier or a CSG Identifier.
  • the List of supported SMF information indicates a list of SMFs that are integrated with the 5G Femtocell 501 or a list of SMFs that are located close to the 5G Femtocell 501 in the same IP domain.
  • the List of supported SMF information may have one SMF entry or multiple SMF entries. Each entry of the SMF information may have at least the following information: FQDN to the SMF, IP address of the SMF Associated CSG Identifier Supported IP version List of associated DNN List of associated S-NSSAI List of associated NDD and S-NSSAI combination
  • the List of supported UPF information indicates a list of UPFs that are integrated with the 5G Femtocell 501 or a list of UPFs that are located close to the 5G Femtocell 501 in the same IP domain.
  • the List of supported UPF information may have one UPF entry or multiple UPF entries. Each entry of the UPF may have at least the following information: FQDN to the UPF, IP address of the UPF Associated CSG Identifier Supported IP version List of associated DNN List of associated S-NSSAI List of associated NDD and S-NSSAI combination NAT information (the range of IP addresses the NAT uses towards the DN (e.g., public IP addresses))
  • Step 3-a1 Upon reception of the NG Setup request message, the AMF 70 sends an Nnrf_NFManagement_NFRegister message to an NRF 78 including at least one of NF type and SMF information.
  • the NF type indicates the Network Function type and it is set as the SMF.
  • the SMF information is one entity of the List of supported SMF information.
  • the AMF 70 sends the Nudm_UECM_Registration Request message to an NRF 78 multiple times to register the SMFs in the NRF 78.
  • the AMF 70 may include a list of multiple SMF entities in the Nudm_UECM_Registration Request message to the NRF 78 and register them with the NRF 78 in a single interaction with the NRF 78.
  • Step 3-a2 Upon reception of the Nnrf_NFManagement_NFRegister message from the AMF 70, the NRF 78 registers the received SMF information to the record in the NRF 78.
  • the CSG ID may be used by the NRF 78 or other consumer node to restrict the access with this SMF only for those of users who are accessing from the 5G Femtocell 501.
  • the NRF 78 sends the Nnrf_NFManagement_NFRegister response message to the AMF 70.
  • the Nnrf_NFManagement_NFRegister response message may include a cause value indicating that the requested registration is successfully completed or not.
  • Step 3-b1 Upon reception of the NG Setup request message, the AMF 70 sends an Nnrf_NFManagement_NFRegister message to an NRF 78 including at least one of NF type and UPF information.
  • the NF type indicates the Network Function type and it is set as the UPF.
  • the UPF information is one entity of the List of supported SMF information.
  • the AMF 70 sends the Nudm_UECM_Registration Request message to an NRF 78 multiple times to register the UPFs in the NRF 78.
  • the AMF 70 may include a list of multiple UPF entities in the Nudm_UECM_Registration Request message to the NRF 78 and register them with the NRF 78 in a single interaction with the NRF 78.
  • Step 3-b2 Upon reception of the Nnrf_NFManagement_NFRegister message from the AMF 70, the NRF 78 registers the received UPF information to the record in the NRF 78.
  • the CSG ID may be used by the NRF 78 or other consumer node to restrict to access with this UPF only for those of users who are accessing from the 5G Femtocell 501.
  • the NRF 78 sends the Nnrf_NFManagement_NFRegister response message to the AMF 70.
  • the Nnrf_NFManagement_NFRegister response message may include a cause value indicating that the requested registration is successfully completed or not.
  • Step 4 The AMF 70 sends the NG Setup response message to the 5G Femtocell 501 including at least one of 5G Femtocell supported, SMF registered and UPF registered.
  • the 5G Femtocell supported indicates that the 5G Femtocell related features (for example, CSG handling, etc.) are supported by the AMF 70 and associated SMF 71, UPF 72, or other associated 5GC nodes.
  • the SMF registered indicates that the SMF entry, as indicated in the NG Setup request in Step 2, is successfully registered in the NRF 78.
  • the SMF registered may have an associated SMF information in a case where the List of supported SMF information in the NG Setup request in Step 2 has multiple entries. This information may be set based on the received cause in Step 3-a3.
  • the UPF registered indicates that the UPF entry as indicated in the NG Setup request in Step 2 is successfully registered in the NRF 78.
  • the UPF registered may have an associated UPF information in a case where the List of supported UPF information in the NG Setup request in Step 2 has multiple entries. This information may be set based on the received cause in Step 3-b3.
  • the NG Setup request message in Step 2 may be a RAN Configuration Update message or any existing NGAP message or a new NGAP message.
  • the NG Setup response message in Step 4 may be a RAN Configuration Update Acknowledge message or any existing NGAP message or a new NGAP message.
  • Variant 2 of Third example of the First Aspect In a case where the 5G Femtocell 501 receives the AMF Configuration Update message or any other existing or a new NGAP message from the AMF 70, the 5G Femtocell 501 sends the AMF Configuration Update Acknowledge message to the AMF 70 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, and List of supported UPF information. Refer to Step 2 for parameter details.
  • Steps 3-a1 to 3-a3 and/or Steps 3-b1 to 3-b3 take place.
  • the CSG indicator field in the CAG Identifier in the system information (sent over the BCCH) or new indicator in the system information (sent over the BCCH) may indicate whether the 5G Femtocell 501 is an open Femtocell or a closed Femtocell.
  • the closed Femtocell requires a membership to access to the 5G Femtocell 501.
  • the membership to access to the 5G Femtocell 501 may be managed in the UDM 75 as the subscriber data for the UE 3 together with the CSG ID.
  • the AS layer in the UE 3 reports to the upper layer of the UE 3 as the UE 3 is accessing with either as the open Femtocell or as the closed Femtocell.
  • a display of the UE 3 may display an icon that indicate the Femtocell access. The icon that indicates the Femtocell access may be read by the user to distinguish either it is the Femtocell access or not.
  • the icon is useful for users to know a cost of the connectivity services.
  • This example discloses mechanisms for access control to the 5G Femtocell 501 by broadcasting 5G Femtocell related information.
  • the 5G Femtocell 501 for NR The access control to the 5G Femtocell 501 for NR includes one or more of the following technical aspects.
  • a 5G Femtocell 501 broadcasts a CSG support indication bit in an existing MIB or SIB.
  • Fig. 9 illustrates an example of new additional information in the SIB2.
  • the UE 3 When the UE 3, as a 5G UE supporting a CSG features, reads the CSG support indication in a SIB or MIB, it can identify that it is the CSG cell and read the CAG ID (CAG identifier or CAG identity).
  • the UE 3 If the CAG ID is configured in the allowed CSG list in the UE 3, the UE 3 considers the cell as a suitable CSG cell for the UE 3 otherwise the cell is not suitable.
  • the UE 3 If the SIB doesn't broadcast the CSG support indication and broadcasts the CAG ID (CAG identifier or CAG identity), the UE 3 considers the cell as a CAG cell and considers the cell as valid if the CAG ID is configured in the allowed CAG list in the UE 3.
  • CAG ID CAG identifier or CAG identity
  • a 5G Femtocell 501 broadcasts a bit as barred in order to restrict the legacy UE camping on the 5G CSG cell.
  • Fig. 10 illustrates an example of new additional information in the SIB1.
  • the 5G Femtocell 501 for E-UTRA includes one or more of the following technical aspects.
  • a 5G Femtocell 501 broadcasts a 5G CSG support indication bit in an existing SIB 1 which is different than the existing CSG Support indication in SIB 1.
  • a 5G UE supporting a CSG features reads the 5G CSG support indication in a SIB 1, it can determine that the cell support CSG in 5GS and read the CSG ID (CSG identifier or CSG identity).
  • the UE 3 If the CSG ID is configured in the allowed CSG list in the UE 3, the UE 3 considers the cell as a suitable CSG cell for 5GS otherwise the cell is not suitable for the 5GS.
  • the cell can broadcast CSG ID for 5GS which is different from the CSG ID (CSG identifier or CSG identity) for EPS.
  • the UE 3 If the SIB doesn't broadcast the 5G CSG support indication and only broadcasts the CSG support indication, the UE 3 considers the cell supports CSG only in EPS. If the femto cell indicates support of 5GS and does not support CSG in the 5GS then the UE initiates attach procedure or tracking area update procedure if the CSG identity of the femto cell is in the allowed CSG list of the UE.
  • the UE when the UE performs manual CSG identity selection procedure, the UE shall present only those CAG identity to the user which has associated HNB name broadcasted in an existing SIB or a new SIB. the UE will ignore the CAG identities which has no associated HNB name associated with it. This is the case when the CAG identity is used to broadcasts the CSG identity.
  • the 5GS UDM or AMF either triggers network initiated procedure (e.g. UE configuration update procedure) to send the allowed CAG identities which contains CAG identities of only PNI-NPN or send the allowed CAG identities which contains CAG identities of only PNI-NPN in the Registration accept message or any other existing NAS message.
  • network initiated procedure e.g. UE configuration update procedure
  • the CAG identity is used to broadcasts the CSG identity.
  • the UE is configured as CAG only UE and it knows that a CAG identity is associated with femto cell (e.g., the HNB name is associated with the CAG identity) then the UE shall not use the CAG identity to select a cell.
  • FIG. 11 illustrates an example of the Registration procedure with the 5G Femtocell 501.
  • This example includes a method of a User Equipment (UE).
  • the method includes the UE for requesting access 5G Femtocell and a 5GC allows the UE to access 5G Femtocell if the UE has valid subscription for 5G Femtocell access.
  • UE User Equipment
  • Step 1 The UE 3 listens to the broadcast information and decides to perform the Registration procedure with the 5G Femtocell 501.
  • the UE 3 listens to the broadcast information as disclosed in the Fourth example of the First Aspect and decides to perform the Registration procedure with the 5G Femtocell 501.
  • the UE 3 sends the RRC Setup Request message to the 5G Femtocell 501.
  • Step 2 Upon the reception of the RRC Setup Request message in Step 1, the 5G Femtocell 501 sends the RRC Setup message to the UE 3.
  • Step 3 The UE 3 sends the RRC Setup Complete message to the 5G Femtocell 501 including at least one of 5G CSG support indication and Dedicated NAS message.
  • the Dedicated NAS message includes the Registration Request message.
  • the Registration Request message to an AMF 70 includes at least one of User ID and 5G CSG support indication.
  • User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI.
  • the 5G CSG support indication indicates that the UE 3 supports necessary functionalities (e.g., the procedures as defined in the Aspects of this disclosure) to access the 5G Femtocell.
  • Step 4 Upon reception of the RRC Setup Complete message from the UE 3, the 5G Femtocell 501 sends the Initial UE message to the AMF 70 including at least one of 5G CSG support indication, 5G Femtocell supported, 5G CSG ID and NAS PDU.
  • the NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 3.
  • the 5G CSG ID is a 5G CSG ID that the UE 3 is accessing and may be included by the 5G Femtocell 501.
  • Step 5 Upon reception of the Registration Request message in step 5, the AMF 70 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, 5G CSG support indication and 5G CSG ID.
  • the 5G CSG ID in Nudm_UECM_Registration Request message may be included by the AMF 70 from the 5G CSG ID that is received in the Initial UE message in Step 4.
  • the 5G CSG ID in Nudm_UECM_Registration Request message may be included by the AMF 70 from the 5G CSG ID that is received in the NG Setup request message in Step 2 in Fig. 7.
  • Step 6 Upon reception of the Nudm_UECM_Registration Request message in step 5, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 70.
  • Step 7 After the completion of the Nudm_UECM_Registration service in steps 5 and 6, the AMF 70 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI, 5G CSG support indication and 5G CSG ID.
  • the UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3.
  • the Subscriber data may include an Allowed CSG Identifier list or the Operator CSG list.
  • the Allowed CSG Identifier list is a list of CSG IDs that the UE 3 is allowed to access.
  • the Allowed CSG Identifier list may be provided to the AMF 70 in the subscriber data only if the UE 3 subscribes to one or more CSGs (Closed Service Groups).
  • the Allowed CSG Identifier list may be provided to the AMF 70 in the subscriber data if the UDM 75 receives the 5G CSG support indication in the Nudm_UECM_Registration Request message in Step 5 or in the Nudm_SDM_Get Request message in Step 7.
  • the AMF 70 may send the Registration Accept message to the UE 3 as a successful Registration procedure or the Registration Reject message to the UE 3 as an unsuccessful Registration procedure.
  • the successful Registration follows Steps 9-a1 and 9-a2, otherwise, follows Step 9-b1.
  • the AMF 70 sends the Registration Accept message to the UE 3 including at least one of 5G-GUTI and Allowed CSG Identifier list or the Operator CSG list.
  • the AMF 70 accepts the Registration procedure from the UE 3 if the CSG ID for the 5G Femtocell 501 that the UE 3 is currently accessing with is in the Allowed CSG Identifier list or Operator CSG list that is received from the UDM 75.
  • the AMF 70 accepts the Registration procedure from the UE 3 if the UE 3 is accessing with non-Femtocell (for example, usual cells that PLMN operator deployed in their network).
  • non-Femtocell for example, usual cells that PLMN operator deployed in their network.
  • Step 9-a2 Upon reception of the Registration Accept message, the UE 3 stores the received Allowed CSG Identifier list in the Registration Accept message in step 9-a1 into non-volatile memory in the UE 3. The UE 301 sends the Registration Complete message to the AMF 70.
  • the AMF 70 sends the Registration Reject message to the UE 3 including a cause.
  • the AMF 70 may reject the Registration procedure from the UE 3 if the CSG ID for the 5G Femtocell 501 that the UE 3 is currently accessing with is not in the Allowed CSG Identifier list that is received from the UDM 75.
  • the AMF 70 may reject the Registration procedure from the UE 3 if the UE 3 is accessing with the 5G Femtocell 501 but the UE 3 does not indicate the 5G CSG support indication in the Registration Request message.
  • the AMF 70 may include a cause in the Registration Reject with the Cause #6 - Illegal ME or another existing or a new cause value in a case where the UE 3 does not indicate the 5G CSG support indication in the Registration Request message.
  • the AMF 70 may include a new cause in the Registration Reject indicating that the 5G Femtocell 501 that the UE 3 is currently accessing with is not in the Allowed CSG Identifier list.
  • the UE 3 may not attempt another Registration procedure with the 5G Femtocell 501 depending on the received cause value.
  • the S-NSSAI in the subscriber data may have associated CSG Identifiers.
  • each CSG Identifier in the Allowed CSG Identifier list may have associated S-NSSAIs in the Subscribed NSSAI.
  • the UE 3 stores the received Allowed CSG Identifier list in a dedicated memory for the 5G Femtocell access in the UE 3.
  • the UE 3 may have two Allowed CSG Identifier lists, one for the 5G Femtocell access and the other one for the HeNB (Home eNodeB) access in EPS.
  • the CSG Identifier value for the 5G Femtocell access may have a different value from a CSG Identifier value for the HeNB (Home eNodeB) access in EPS.
  • the CAG Identifier that is used for the Public Network Integrated NPN access as defined in NPL 4 may be maintained in the UE 3 even the UE 3 moves to the EPS and an Allowed CSG Identifier list for the HeNB (Home eNodeB) access is stored when the UE 3 accesses with the EPS. I.E., the CAG Identifier for the Public Network Integrated NPN access is not overwritten by the received Allowed CSG Identifier list for the HeNB (Home eNodeB) access.
  • the CSG Identifier for the UE 3 have a common CSG Identifier value for the 5G Femtocell access and the HeNB (Home eNodeB) access in EPS.
  • the 5G Femtocell 501 may use the 5G CSG support indication in order to select an AMF, for example AMF 70, which supports the 5G CSG functionality.
  • Variant 4 of Fifth example of the First Aspect the operator CSG list as defined in Annex C of TS 23.122 is sent using SOR procedure.
  • the UDM in step 3a of C.2 of TS 23.122 gets operator CSG list from the SoR in the Nsoraf_SoR_Get Response message.
  • One receiving the operator CSG list the UDM sends to the operator CSG list in the steering of roaming information UE suing SoR procedure as defined in the Annex C of TS 23.122.
  • an entry in operator CSG list may contain CSG identity or CAG identity + PLMN ID or SNPN ID + HNB name.
  • FIG. 12 illustrates an example of the PDU Session Establishment procedure with both the UPF 72 and the SMF 71 located at close distance to the 5G Femtocell 501.
  • both the UPF 72 and the SMF 71 are located at the same IP domain of the 5G Femtocell 501 and both the UPF 72 and the SMF 71 are reachable from any core network nodes in 5GC (Core network 7) securely using the IPsec tunnel.
  • only the UPF 72 is located at close distance to the 5G Femtocell 501 while the SMF 71 is located at the 5GC (Core network 7) in operator network.
  • the UPF 72 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the 5G Femtocell 501 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect.
  • the UPF 72 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the UPF 72 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the UPF 72 in Fig. 6.
  • the SMF 71 may also be located at close distance to the 5G Femtocell 501.
  • the SMF 71 is located at the same IP domain of the 5G Femtocell 501 and the SMF 71 is reachable from any core network node in 5GC (Core network 7) securely using the IPsec tunnel.
  • the SMF 71 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the 5G Femtocell 501 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect.
  • the SMF 71 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the SMF 71 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the SMF 71 in Fig. 6.
  • Step 1 The UE 3 has been registered to the AMF 70.
  • Step 1 The UE 3 sends a UL NAS Transport message to the AMF 70 including at least one of PDU Session ID, 5G CSG support indication, DNN, S-NSSAI and NAS container.
  • the NAS container includes a PDU Session Establishment Request message, Service Request message or any other NAS message with the purpose of establishing a PDU Session or with the purpose to re-use an already established PDU Session or modify the already established PDU Session.
  • ⁇ PDU Session ID The PDU Session ID is an identifier that corresponds to an Association between the UE 3 and a Data Network 20 that provides a PDU connectivity service.
  • ⁇ 5G CSG support indication Refer to Step 3 in Fig. 11.
  • ⁇ DNN The DNN is a Data Network Name that is equivalent to an APN in EPS.
  • the DNN is a reference to a data network.
  • ⁇ S-NSSAI The S-NSSAI is a Single NSSAI that indicates a network slice.
  • Step 2 Upon reception of the UL NAS Transport message from the UE 3, the AMF 70 performs the SMF selection based on at least one of the received 5G CSG support indication, DNN and S-NSSAI from the UE 3.
  • the AMF 70 sends back to the UE 3 the 5GSM message which was not forwarded to the SMF 71, including a 5GMM cause indicating that the CSG ID is not allowed. Otherwise, the AMF 70 sends the Nnrf_NFDiscovery_Request message to the NRF 78 including at least one of NF type, DNN, S-NSSAI, CSG ID and 5G Femtocell supported.
  • ⁇ NF type indicates the Network Function type that the AMF 70 is selecting. In this case, the NF type is set to the SMF.
  • ⁇ DNN Refer to Step 1.
  • ⁇ S-NSSAI Refer to Step 1.
  • ⁇ CSG ID The CSG ID indicates a 5G CSG ID that the UE 3 is accessing with.
  • the AMF 70 obtains the CSG ID in the Initial UE message from the 5G Femtocell 501 when the 5G Femtocell 501 transfers the UL NAS Transport message in Step 1.
  • ⁇ 5G Femtocell supported Refer to Step 2 in Fig. 7.
  • Step 3 Upon reception of the Nnrf_NFDiscovery_Request message from the AMF 70, the NRF 78 performs the SMF selection based on at least one of the received DNN, S-NSSAI, CSG ID and 5G Femtocell supported indicator from the AMF 70.
  • the NRF 78 refers to the SMF information that is provided by the AMF 70 in Step 3-a1 in Fig. 7 in the SMF selection.
  • the NRF 78 sends the Nnrf_NFDiscovery response message to the AMF 70 including SMF address.
  • the SMF address may be a FQDN of the SMF 71 or the IP address of the SMF 71.
  • Step 4 The AMF 70 sends an Nsmf_PDUSession_CreateSMContext Request message to the SMF 71 based on the SMF address information from the NRF 78 in Step 3 including at least one of PDU Session ID, DNN, S-NSSAI, CSG ID, 5G Femtocell supported and PDU Session Establishment Request message.
  • the DNN, S-NSSAI, CSG ID and 5G Femtocell supported are used when the SMF 71 generates a charging ticket (known as CDR).
  • Step 5 Upon reception of the Nsmf_PDUSession_CreateSMContext Request message from the AMF 70, the SMF 71 sends the Nsmf_PDUSession_CreateSMContext response message to the AMF 70.
  • Step 6 Upon reception of the Nsmf_PDUSession_CreateSMContext Request message from the AMF 70, the SMF 71 performs the UPF selection based on at least one of the received DNN, S-NSSAI, CSG ID and 5G Femtocell supported from the AMF 70. The SMF 71 sends the Nnrf_NFDiscovery_Request message to the NRF 78 including at least one of NF type, DNN, S-NSSAI, CSG ID and 5G Femtocell supported.
  • ⁇ NF type indicates the Network Function type that the SMF 71 is selecting. In this case, the NF type is set to the UPF.
  • ⁇ DNN Refer to Step 1.
  • ⁇ S-NSSAI Refer to Step 1.
  • ⁇ CSG ID Refer to Step 2.
  • ⁇ 5G Femtocell supported Refer to Step 2 in Fig. 7.
  • Step 7 Upon reception of the Nnrf_NFDiscovery_Request message from the SMF 71, the NRF 78 performs the UPF selection based on at least one of the received DNN, S-NSSAI, CSG ID and 5G Femtocell supported from the AMF 70.
  • the NRF 78 refers to the UPF information that is provided by the AMF 70 in Step 3-b1 in Fig. 7 in the UPF selection.
  • the NRF 78 sends the Nnrf_NFDiscovery response message to the SMF 71 including UPF address.
  • the UPF address may be a FQDN of the UPF 72 or the IP address of the UPF 72.
  • Step 8 The SMF 71 sends an N4 Session Establishment Request message to the UPF 72 based on the UPF address information from the NRF 78 in Step 7 including at least one of the PDU Session ID, DNN, S-NSSAI, CSG ID and 5G Femtocell supported.
  • the UPF 72 may reserve resource(s) for the PDU Session.
  • Step 9 After successful resource reservation for the PDU Session, the UPF 72 sends an N4 Session Establishment Response message to the SMF 71 including a UPF close to RAN chosen.
  • UPF close to RAN chosen indicates that the UPF 72 is chosen based on the CSG ID and the UPF 72 is located close to the 5G Femtocell 501.
  • Step 10 The SMF 71 sends an 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 the UPF close to RAN chosen.
  • the N1 SM container includes a PDU Session Establishment Accept message.
  • Step 11 Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends the Downlink NAS Transport message to the 5G Femtocell 501 including the NAS PDU.
  • the NAS PDU includes the PDU Session Establishment Accept message that is transferred by the 5G Femtocell 501 to the UE 3.
  • the UPF close to RAN chosen is transferred by the N2 message to the 5G Femtocell 501 when the AMF 70 sends the Downlink NAS Transport message to the UE 3.
  • the UE 3 communicates with the AF 201 via the UPF 72 that is located close to the 5G Femtocell 501.
  • the AF 201 may be integrated with the 5G Femtocell 501.
  • the AF 201 is located at the same IP domain of the 5G Femtocell 501.
  • the AF 201 may be called as a Service server at the Edge network.
  • the AF 201 may be called as a the MEC Service server.
  • optimized user plane between the UE 3 and AF 201 may be established.
  • the optimized user plane connection may be called as a Traffic offloading, a MEC connection or a MEC service.
  • This aspect discloses an architecture and mechanisms to support the 5G SN Femtocell 501 in 5GS where the 5G SN Femtocell 501 is considered as SN (Secondary Node) in the Multi-connectivity as defined in NPL 9.
  • This example includes an architecture to support the 5G SN Femtocell 501 in 5GS.
  • Fig. 13 illustrates an example of an 5GS architecture that supports 5G Femtocells where the 5G SN Femtocell 501 is considered as SN (Secondary Node) and the 5G MN RAN 503 is considered as MN (Master Node) in the Multi-connectivity as defined in NPL 9.
  • the 5G SN Femtocell 501 uses the FR2 (Frequency Range 2, 24250MHz - 52600MHz) for user data transmission while the 5G MN RAN 503 uses the FR1 (Frequency Range 1, 450MHz - 6000MHz) for both the RRC signalling transmission and user data transmission.
  • FR2 Frequency Range 2, 24250MHz - 52600MHz
  • FR1 Frequency Range 1, 450MHz - 6000MHz
  • the 5G MN RAN 503 may be expressed as the 5G MN RAN node 503 or the 5G MN Femtocell 503.
  • the 5G SN Femtocell 501 may provide one Femto cell.
  • the 5G RAN node 5 may include the 5G SN Femtocell 501 and the 5G MN RAN 503.
  • the 5G SN Femtocell 501 represents an 5G Femtocell in a private premise, for example, private house, office, school, park, factory, hospital, museum, stadium or etc.
  • the 5G SN Femtocell 501 is connected to the SecGW 502 that is located at the PLMN.
  • the connection between the 5G SN Femtocell 501 and the SecGW 502 are security protected adapting the IPsec technology.
  • the IPsec connection between the 5G SN Femtocell 501 and the SecGW 502 may be established by the initialization procedure as disclosed in the Second example of the First Aspect except Step 11 with replacing the 5G Femtocell 501 to the 5G SN Femtocell 501 in Fig. 6.
  • the XN interface is established between the 5G MN RAN 503 and the 5G SN Femtocell 501 after successful IPsec connection established.
  • the IPsec connection between the 5G SN Femtocell 501 and the SecGW 502 in front of the 5G MN RAN 503 may be established by the initialization procedure as disclosed in the Second example of the First Aspect except Step 11 with replacing the 5G Femtocell 501 to the 5G SN Femtocell 501 in Fig. 6.
  • the 5G SN Femtocell 501 and 5G MN RAN 503 may be located at the PLMN or NPN domain.
  • the SecGW 502 may not exist and the 5G SN Femtocell 501 and 5G MN RAN 503 communicate with 5GC nodes within 5GC (Core network 7) in the PLMN or NPN directly.
  • Fig. 14 illustrates an example of the setup procedure for the 5G SN Femtocell 501. The detailed processes of the Second example of the Second Aspect are described below with reference to Fig. 14.
  • the 5G SN Femtocell 501 triggers the XN Setup procedure. For example, in a case where the 5G SN Femtocell 501 restarts or configuration of the 5G SN Femtocell 501 is updated, the 5G SN Femtocell 501 may trigger the XN Setup procedure.
  • the 5G SN Femtocell 501 sends an XN Setup request message to the 5G MN RAN 503 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, and List of supported UPF information.
  • Step 2 in Fig. 7 for parameter details.
  • Step 3-a In a case where the XN Setup request message includes the List of supported SMF information, Steps 2, 3-a1, 3-a2, 3-a3 and 4 in Fig. 7 take place.
  • Step 3-b In a case where the XN Setup request message includes the List of supported UPF information, Steps 2, 3-b1, 3-b2, 3-b3 and 4 in Fig. 7 take place.
  • Step 4 The 5G MN RAN 503 sends the XN Setup response message to the 5G SN Femtocell 501 including at least one of 5G Femtocell supported, SMF registered and UPF registered.
  • the SMF registered indicates that the SMF entry as indicated in the XN Setup request in Step 2 is successfully registered in the NRF 78.
  • the SMF registered may have an associated SMF information in a case where the List of supported SMF information in the XN Setup request in Step 2 has multiple entries. This information may be set based on the received cause in Step 3-a3 in Fig. 7.
  • UPF registered indicates that the UPF entry as indicated in the XN Setup request in Step 2 is successfully registered in the NRF 78.
  • the UPF registered may have an associated UPF information in a case where the List of supported UPF information in the XN Setup request in Step 2 has multiple entries. This information may be set based on the received cause in Step 3-b3 in Fig. 7.
  • the XN Setup request message in Step 2 may be an NG-RAN node Configuration Update message or any other existing message or a new message between the 5G SN Femtocell 501 and the 5G MN RAN 503.
  • the XN Setup response message in Step 4 may be an NG-RAN node Configuration Update Acknowledge message or any other existing message or a new message between the 5G SN Femtocell 501 and the 5G MN RAN 503.
  • Variant 2 of Second example of the Second Aspect In a case where the 5G SN Femtocell 501 receives the XN Setup request message from the 5G MN RAN 503, the 5G Femtocell SN 501 sends the XN Setup response message to the 5G MN RAN 503 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, and List of supported UPF information.
  • the 5G Femtocell 501 receives the XN Setup request message from the 5G MN RAN 503
  • the 5G Femtocell SN 501 sends the XN Setup response message to the 5G MN RAN 503 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, and List of supported UPF information.
  • Step 2 in Fig. 7 for parameter details.
  • Steps 3-a and/or Steps 3-b take place.
  • This example discloses mechanisms for access control to the 5G SN Femtocell 501 and/or 5G MN RAN 503 by broadcasting 5G Femtocell related information.
  • the 5G SN Femtocell 501 may broadcasts 5G Femtocell related information.
  • the 5G SN Femtocell 501 may broadcasts 5G Femtocell related information as disclosed in the Fourth example of the First Aspect with replacing the 5G Femtocell 501 to the 5G SN Femtocell 501.
  • the 5G MN RAN 503 may broadcasts 5G Femtocell related information that support 5G SN Femtocell 501 on behalf of the 5G SN Femtocell 501.
  • the 5G MN RAN 503 may broadcasts 5G Femtocell related information as disclosed in the Fourth example of the First Aspect with replacing the 5G Femtocell 501 to the 5G MN RAN 503.
  • This example discloses an example of the Registration procedure with the 5G SN Femtocell 501.
  • the Registration procedure as disclosed in the Fifth example of the First Aspect may be used with the following replacements: ⁇
  • the 5G Femtocell 501 is replaced with the 5G MN RAN 503.
  • the AMF 70 populates/includes the Allowed CSG Identifier list to the N2 message to the 5G MN RAN 503.
  • the N2 message is not clearly illustrated in Fig. 11.
  • the N2 message is used between the AMF 70 and the 5G MN RAN 503 to convey the Registration accept message to the UE 3 in Step 9-a1.
  • the Allowed CSG Identifier list may be referred by the 5G MN RAN 503 when the 5G MN RAN 503 decides to configure the multi-connectivity as defined in NPL 9.
  • the 5G MN RAN 503 decides to configure the multi-connectivity for the UE 3.
  • the 5G MN RAN 503 decides not to configure the multi-connectivity for the UE 3.
  • the Allowed CSG Identifier list may be defined within the existing NGAP parameter.
  • the Allowed CSG Identifier list may be defined in the Mobility restriction list as defined in NPL 10.
  • the N2 message is the Initial Context setup request message, Downlink NAS Transport message, Reroute NAS Request message, Handover Request message, other existing NGAP message or new NGAP message.
  • FIG. 15 illustrates an example of the PDU Session Establishment procedure with both the UPF 72 and the SMF 71 located at close distance to the 5G SN Femtocell 501.
  • both the UPF 72 and the SMF 71 are located at the same IP domain of the 5G SN Femtocell 501 and both the UPF 72 and the SMF 71 are reachable from any core network nodes in 5GC (Core network 7) securely using the IPsec tunnel.
  • only the UPF 72 is located at close distance to the 5G SN Femtocell 501 while the SMF 71 is located at the 5GC (Core network 7) in operator network.
  • the UPF 72 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the 5G SN Femtocell 501 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with 5G SN Femtocell 501 in Fig. 6.
  • the UPF 72 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the UPF 72 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the UPF 72 in Fig. 6.
  • the SMF 71 may also be located at close to the 5G SN Femtocell 501.
  • the SMF 71 is located at the same IP domain of the 5G SN Femtocell 501 and the SMF 71 is reachable from any core network nodes in 5GC (Core network 7) securely using the IPsec tunnel.
  • the SMF 71 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the 5G SN Femtocell 501 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the 5G SN Femtocell 501 in Fig. 6.
  • the SMF 71 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the SMF 71 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the SMF 71 in Fig. 6.
  • the 5G MN RAN 502 and the 5G SN Femtocell 501 are located at the same IP domain. In another example, the 5G MN RAN 502 and the 5G SN Femtocell 501 are not located at the same IP domain.
  • Step 1 The UE 3 has been registered to the AMF 70.
  • Step 1 The UE 3 sends a UL NAS Transport message to the AMF 70 via the 5G MN RAN 503 including at least one of PDU Session ID, 5G CSG support indication, DNN, S-NSSAI and NAS container.
  • Step 1 in Fig. 12 for parameter details.
  • the AMF 70 sends an Nsmf_PDUSession_CreateSMContext Request message to the SMF 71 based on the SMF address information from the NRF 78 in Step 3 in Fig. 12 including at least one of PDU Session ID, DNN, S-NSSAI, CSG ID, 5G Femtocell supported, Allowed CSG Identifier list and PDU Session Establishment Request message.
  • the Allowed CSG Identifier list is a list of CSG ID that the UE 3 is allowed to access.
  • the AMF 70 may populate/include the Allowed CSG Identifier list if the AMF 70 stores it in the MM context for the UE 3.
  • the AMF 70 may have obtained the Allowed CSG Identifier list for the UE 3 during the Registration procedure as disclosed by the Fifth example of the First Aspect.
  • the DNN, S-NSSAI, CSG ID and 5G Femtocell supported are used when the SMF 71 generates a charging ticket (as known as CDR).
  • Step 5 If the SMF 71 does not have Session Management Subscription data for the UE 3, the SMF 71 may send the Nudm_SDM_Get message to the UDM 75 including at least one of SUPI, DNN, S-NSSAI, CSG ID and 5G Femtocell supported. Refer to Step 1 and Step 2 in Fig. 7 for parameter details.
  • Step 6 Upon reception of the Nudm_SDM_Get message from the SMF 71, the UDM 75 sends the Nudm_SDM_Get response message to the SMF 71 including the Session Management Subscription data.
  • the Session Management Subscription data may include the Allowed CSG Identifier list for the UE 3.
  • Step 7 Steps 5 to 9 in Fig. 12 take place with replacing the 5G Femtocell 501 with the 5G MN RAN 503.
  • Step 8 The SMF 71 sends an Namf_Communication_N1N2MessageTransfer message to the AMF 70 including at least one of PDU Session ID, N2 SM information and N1 SM container.
  • the N1 SM container includes a PDU Session Establishment Accept message.
  • the N2 SM information includes the Allowed CSG Identifier list.
  • Step 9 Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends the Downlink NAS Transport message to the 5G MN RAN 503 including the Allowed CSG Identifier list and the NAS PDU.
  • the NAS PDU includes the PDU Session Establishment Accept message that is transferred by the 5G MN RAN 503 to the UE 3.
  • the Allowed CSG Identifier list that is received by 5G MN RAN 503 in the Downlink NAS Transport message may be considered by the 5G MN RAN 503 when the 5G MN RAN 503 decides to configure the multi-connectivity as defined in NPL 9.
  • the 5G MN RAN 503 decides to configure the multi-connectivity for the UE 3.
  • the 5G MN RAN 503 decides not to configure the multi-connectivity for the UE 3.
  • the Allowed CSG Identifier list may be defined within the existing NGAP parameter.
  • the Allowed CSG Identifier list may be defined in the Mobility restriction list as defined in NPL 10.
  • the UE 3 communicates with the AF 201 via the UPF 72 that may be located close to the 5G MN RAN 503 or the 5G SN Femtocell 501.
  • the AF 201 may be integrated with the 5G MN RAN 503 or the 5G SN Femtocell 501.
  • the AF 201 is located at the same IP domain of the 5G MN RAN 503 or the 5G SN Femtocell 501.
  • the AF 201 may be called as a Service server at the Edge network.
  • the AF 201 may be called as a the MEC Service server.
  • 5G MN RAN 503 may initiate the Secondary Node Addition procedure with the 5G SN Femtocell 501 as described in NPL 9. For example, whether the 5G MN RAN 503 initiate the Secondary Node Addition procedure with the 5G SN Femtocell 501 or not is decided based on the descriptions in Step 9.
  • optimized user plane between the UE 3 and AF 201 may be established.
  • the optimized user plane connection may be called as a Traffic offloading, a MEC connection or a MEC service.
  • This Aspect includes an architecture to support the 5G Femtocell 501 in 5GS where the 5G Femtocell 501 is considered as DU (Distributed Unit) 61.
  • This aspect discloses an architecture and mechanisms to support the 5G DU Femtocell 501 in 5GS where the 5G DU Femtocell 501 is considered as DU (Distributed Unit) 61.
  • Fig. 16 illustrates an example of an 5GS architecture that supports 5G Femtocells where the 5G DU Femtocell 501 is considered as a DU 61 and the 5G CU Femtocell 503 is considered as a CU 62.
  • the 5G CU Femtocell 503 may be expressed as the 5G CU RAN node 503 or the 5G CU RAN 503.
  • the 5G RAN node 5 and/or the 5G Femtocell may include the 5G DU Femtocell 501 and the 5G CU Femtocell 503.
  • 5G DU Femtocell 501 Although there is one 5G DU Femtocell 501 shown in Fig. 16 as the DU 61, there may be more than one 5G DU Femtocells 501 deployed in the Private premise, PLMN or NPN.
  • the UE 3 chooses one 5G DU Femtocell 501 to access to the AF 201 in the external network.
  • the 5G DU Femtocell 501 uses the FR2 (Frequency Range 2, 24250MHz - 52600MHz).
  • the 5G DU Femtocell 501 uses the FR1 (Frequency Range 1, 450MHz - 6000MHz).
  • the 5G DU Femtocell 501 represents an 5G Femtocell in a private premise, for example, private house, office, school, park, factory, hospital, museum, stadium or etc.
  • the 5G DU Femtocell 501 is connected to the SecGW 502 that is located at the PLMN.
  • the connection between the 5G DU Femtocell 501 and the SecGW 502 are security protected adapting the IPsec technology.
  • the IPsec connection between the 5G DU Femtocell 501 and the SecGW 502 may be established by the initialization procedure as disclosed in the Second example of the First Aspect except Step 11 with replacing the 5G Femtocell 501 to the 5G DU Femtocell 501 in Fig. 6.
  • the SecGW 502 may not exist and the 5G DU Femtocell 501 and 5G CU Femtocell 503 communicate with 5GC nodes within 5GC (Core network 7) in the PLMN or NPN directly.
  • Fig. 17 illustrates an example of the setup procedure for the 5G DU Femtocell 501.
  • the detailed processes of the Second example of the Third Aspect are described below with reference to Fig. 17.
  • the 5G DU Femtocell 501 triggers the F1 Setup procedure. For example, in a case where the 5G DU Femtocell 501 restarts or configuration of the 5G DU Femtocell 501 is updated, the 5G DU Femtocell 501 may trigger the F1 Setup procedure.
  • the 5G DU Femtocell 501 sends an F1 Setup request message to the 5G CU Femtocell 503 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, List of supported UPF information and List of associated 5G CU UP information.
  • Step 2 in Fig. 7 for parameter details.
  • the List of associated 5G CU UP information is a set of 5G CU UPs that are associated with the 5G CU Femtocell 503.
  • the 5G CU Femtocell 503 stores the List of associated 5G CU UP information per 5G DU Femtocell 501 basis.
  • a 5G CU UP in the set of 5G CU UPs may be located close to the 5G CU Femtocell 503.
  • a 5G CU UP in the set of 5G CU UPs may be integrated with the 5G CU Femtocell 503.
  • the set of 5G CU UPs may be associated with a UPF 72 or a set of UPFs 72 that are listed in the List of supported UPF information.
  • a 5G CU UP in the set of 5G CU UPs may be located close to a UPF 72 or a set of UPFs that are listed in the List of supported UPF information.
  • a 5G CU UP in the set of 5G CU UPs may be integrated with a UPF 72 or a set of UPFs 72 that are listed in the List of supported UPF information.
  • a 5G CU UP may be chosen by the 5G CU Femtocell 503 when the 5G CU Femtocell 503 establishes user plane resources with a UPF 72 that is listed in the List of supported UPF information in Step 2.
  • the user plane connection between the UE 3 and the AF 201 via the UPF 72 is optimized and may provide low latency communication because of a short path connection.
  • Step 3-a In a case where the F1 Setup request message includes the List of supported SMF information, Steps 2, 3-a1, 3-a2, 3-a3 and 4 in Fig. 7 take place.
  • Step 3-b In a case where the F1 Setup request message includes the List of supported UPF information, Steps 2, 3-b1, 3-b2, 3-b3 and 4 in Fig. 7 take place.
  • Step 4 The 5G CU Femtocell 503 sends the F1 Setup response message to the 5G DU Femtocell 501 including at least one of 5G Femtocell supported, SMF registered and UPF registered.
  • the SMF registered indicates that the SMF entry as indicated in the F1 Setup request in Step 2 is successfully registered in the NRF 78.
  • the SMF registered may have an associated SMF information in a case where the List of supported SMF information in the F1 Setup request in Step 2 has multiple entries. This information may be set based on the received cause in Step 3-a3 in Fig. 7.
  • UPF registered indicates that the UPF entry as indicated in the F1 Setup request in Step 2 is successfully registered in the NRF 78.
  • the UPF registered may have an associated UPF information in a case where the List of supported UPF information in the F1 Setup request in Step 2 has multiple entries. This information may be set based on the received cause in Step 3-b3 in Fig. 7.
  • the F1 Setup request message in Step 2 may be an GNB-DU Configuration Update message or any other existing or a new message between the 5G DU Femtocell 501 and the 5G CU Femtocell 503.
  • the F1 Setup response message in Step 4 may be an GNB-DU Configuration Update Acknowledge message or any other existing or a new message between the 5G DU Femtocell 501 and the 5G CU Femtocell 503.
  • Variant 2 of Second example of the Second Aspect In a case where the 5G DU Femtocell 501 receives the GNB-CU Configuration Update message from the 5G CU Femtocell 503, the 5G Femtocell DU 501 sends the GNB-CU Configuration Update Acknowledge message to the 5G CU Femtocell 503 including at least one of 5G Femtocell supported, CSG ID, List of supported SMF information, and List of supported UPF information.
  • Step 2 in Fig. 7 for parameter details.
  • Steps 3-a and/or Steps 3-b take place.
  • This example discloses mechanisms for access control to the 5G DU Femtocell 501 broadcasting 5G Femtocell related information.
  • the 5G DU 501 may broadcasts 5G Femtocell related information.
  • the 5G DU Femtocell 501 may broadcast 5G Femtocell related information as disclosed in the Fourth example of the First Aspect with replacing the 5G Femtocell 501 to the 5G DU Femtocell 501.
  • This example discloses an example of the Registration procedure with the 5G DU Femtocell 501.
  • This example includes a method of a User Equipment (UE).
  • the method includes the UE for requesting access 5G Femtocell and a 5GC allows the UE to access 5G Femtocell if the UE has valid subscription for 5G Femtocell access.
  • UE User Equipment
  • Step 1 The UE 3 listens to the broadcasting information and decides to perform the Registration procedure with the 5G DU Femtocell 501.
  • the UE 3 listens to the broadcasting information as disclosed in the Third example of the Third Aspect and decides to perform the Registration procedure with the 5G Femtocell DU 501.
  • the UE 3 sends the RRC Setup Request message to the 5G DU Femtocell 501.
  • Step 2 Upon the reception of the RRC Setup Request message in Step 1, the 5G DU Femtocell 501 sends the RRC Setup request message to the UE 3.
  • Step 3 The UE 3 sends the RRC Setup Complete message to the 5G DU Femtocell 501 including at least one of 5G CSG support indication and Dedicated NAS message.
  • Step 3 in the Fifth example of the First Aspect for parameter details.
  • Step 4 Upon reception of the RRC Setup Complete message from the UE 3, the 5G DU Femtocell 501 sends the Initial UE RRC message to the 5G CU Femtocell 503 including at least one of 5G CSG support indication, 5G Femtocell supported, 5G CSG ID and NAS PDU.
  • 5G CSG support indication 5G Femtocell supported
  • 5G CSG ID 5G CSG ID
  • NAS PDU NAS PDU.
  • the 5G CU Femtocell 503 Upon reception of the Initial UE RRC message from the 5G DU Femtocell 501, the 5G CU Femtocell 503 sends the Initial UE message to the AMF 70 including at least one of 5G CSG support indication, 5G Femtocell supported, 5G CSG ID and NAS PDU.
  • the NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 3.
  • the 5G CSG ID is a 5G CSG ID that the UE 3 is accessing and may be included by the 5G DU Femtocell 501.
  • Step 5 Step 5 of Step 5. Steps 4 to 8 in Fig. 11 take place with replacing the 5G Femtocell 501 with the 5G DU Femtocell 501 and the 5G CU Femtocell 503.
  • the AMF 70 may send the Registration Accept message to the UE 3 as a successful Registration procedure or the Registration Reject message to the UE 3 as an unsuccessful Registration procedure.
  • the successful Registration follows Steps 6-a1 to 6-a4, otherwise, follows Step 6-b1.
  • the AMF 70 sends the N2 message to the 5G CU Femtocell 503 including at least one of Allowed CSG Identifier list and NAS PDU.
  • the NAS PDU includes the Registration Accept message. Further the Registration Accept message to the UE 3 including at least one of 5G-GUTI and Allowed CSG Identifier list.
  • the AMF 70 accepts the Registration procedure from the UE 3 if the CSG ID for the 5G DU Femtocell 501 that the UE 3 is currently accessing with is in the Allowed CSG Identifier list that is received from the UDM 75.
  • the AMF 70 accepts the Registration procedure from the UE 3 if the UE 3 is accessing with non-Femtocell (for example, usual cells that PLMN operator deployed in their network).
  • non-Femtocell for example, usual cells that PLMN operator deployed in their network.
  • the N2 message may be DOWNLINK NAS TRANSPORT message, PDU SESSION RESOURCE SETUP REQUEST message, PDU SESSION RESOURCE MODIFY REQUEST message, INITIAL CONTEXT SETUP REQUEST message, UE CONTEXT MODIFICATION REQUEST message, any existing NGAP message or new NGAP message.
  • Step 6-a2 Upon reception of the N2 message from the AMF 70, The 5G CU Femtocell 503 sends the DL RRC MESSAGE TRANSFER message to the 5G DU Femtocell 501 including at least one of Allowed CSG Identifier list and RRC-Container.
  • the RRC-Container includes the Registration Accept message. Further the Registration Accept message to the UE 3 including at least one of 5G-GUTI and Allowed CSG Identifier list.
  • the 5G DU Femtocell 501 stores the received Allowed CSG Identifier list.
  • Step 6-a3 Upon reception of the DL RRC MESSAGE TRANSFER message from the 5G CU Femtocell 503, the 5G DU Femtocell 501 sends the DL information transfer message to the UE 3 including Dedicated NAS message.
  • the Dedicated NAS message includes the Registration Accept message. Further the Registration Accept message to the UE 3 including at least one of 5G-GUTI and Allowed CSG Identifier list.
  • Step 6-a4 Upon reception of the Registration Accept message, the UE 3 stores the received Allowed CSG Identifier list in the Registration Accept message in step 6-a3 into non-volatile memory in the UE 3. The UE 301 sends the Registration Complete message to the AMF 70.
  • FIG. 19 illustrates an example of the PDU Session Establishment procedure with both the UPF 72 and the SMF 71 located at close distance to the 5G DU Femtocell 501.
  • both the UPF 72 and the SMF 71 are located at the same IP domain of the 5G DU Femtocell 501 and both the UPF 72 and the SMF 71 are reachable from any core network nodes in 5GC (Core network 7) securely using the IPsec tunnel.
  • only the UPF 72 is located at close distance to the 5G DU Femtocell 501 while the SMF 71 is located at the 5GC (Core network 7) in operator network.
  • the UPF 72 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the 5G DU Femtocell 501 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the 5G DU Femtocell 501 in Fig. 6.
  • the UPF 72 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the UPF 72 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the UPF 72 in Fig. 6.
  • the SMF 71 may also be located at close to the 5G DU Femtocell 501.
  • the SMF 71 is located at the same IP domain of the 5G DU Femtocell 501 and the SMF 71 is reachable from any core network nodes in 5GC (Core network 7) securely using the IPsec tunnel.
  • the SMF 71 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the 5G DU Femtocell 501 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the 5G DU Femtocell 501 in Fig. 6.
  • the SMF 71 may be securely reachable from the 5GC (Core network 7) using the IPsec tunnel established between the SMF 71 and the SecGW 502 by the procedure as disclosed by the Second example of the First Aspect with replacing the 5G Femtocell 501 with the SMF 71 in Fig. 6.
  • Step 1 Steps 0 to 10 in Fig. 12 take place with replacing the 5G Femtocell 501 with the 5G DU Femtocell 501 and the 5G CU Femtocell 503.
  • Step 2 The AMF 70 sends the PDU SESSION RESOURCE SETUP REQUEST message to the 5G CU Femtocell 503 including at least one of Allowed CSG Identifier list, UPF close to RAN chosen and NAS PDU.
  • the NAS PDU includes the PDU Session Establishment accept message. Further the PDU Session Establishment accept message to the UE 3 including the Allowed CSG Identifier list.
  • Step 3 Upon reception of the PDU SESSION RESOURCE SETUP REQUEST message from the AMF 70, The 5G CU Femtocell 503 selects the 5G CU UP and 5G CU UP resources close to the 5G DU Femtocell 501 if the close to RAN chosen is indicated.
  • the 5G CU Femtocell 503 selects the 5G CU UP and 5G CU UP resources close to the 5G DU Femtocell 501 if the PDU Session Resource Setup Request Transfer in the PDU SESSION RESOURCE SETUP REQUEST message includes the UPF endpoint information that is close to the 5G DU Femtocell 501.
  • Step 4 After successful 5G CU UP selection and 5G CU UP resource reservation, the 5G CU Femtocell 503 sends the DL RRC MESSAGE TRANSFER message to the 5G DU Femtocell 501 including at least one of Allowed CSG Identifier list, UPF close to RAN chosen and RRC-Container.
  • the RRC-Container includes the Session Establishment accept message.
  • Step 5 Upon reception of the DL RRC MESSAGE TRANSFER message from the 5G CU Femtocell 503, the 5G DU Femtocell 501 sends the DL information transfer message to the UE 3 including Dedicated NAS message.
  • the Dedicated NAS message includes the Session Establishment accept message.
  • 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
  • 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 Slice Selection Function (NSSF) 76, an AAA Server 77, a Network Repository Function (NRF) 78.
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • NWDAF Network Data Analytics Function
  • UDM Unified Data Management
  • NSSF Network Slice Selection Function
  • AAA Server 77 an AAA Server 77
  • NRF Network Repository Function
  • 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 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.
  • 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 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.
  • 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 User equipment
  • Fig. 21 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.
  • a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.
  • 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)).
  • 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. 22 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.
  • 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 5G Femtocell 501, SecGW 502, NAT 503, 5G MN RAN 503, and 5G SN Femtocell 501 may have same components to the (R)AN node 5.
  • the (R)AN node 5 may be expressed as a RAN node, 5G RAN node, RAN, (R)AN etc.
  • FIG. 23 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.
  • Radio Unit (RU) Fig. 24 is an example of 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. 25 is an example of 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.
  • the 5G DU Femtocell 501 may have same components to the DU 61.
  • FIG. 26 is an example of 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.
  • the 5G CU Femtocell 503 may have same components to the CU 62.
  • AMF Fig. 27 is an example of 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.
  • RMD removable data storage device
  • 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).
  • SNPN Stand-alone Non-Public Network
  • PNI-NPN Public Network Integrated NPN
  • SMF Fig. 28 is an example of 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
  • UPF Fig. 29 is an example of 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. 30 is an example of 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
  • NWDAF Fig. 31 is an example of 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. 32 is an example of 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
  • NSSF Fig. 33 is an example of a block diagram illustrating the main components of the NSSF 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 NSSF 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 NSSF 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 NSSF 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
  • AAA Server Fig. 34 is an example of a block diagram illustrating the main components of the AAA Server 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 AAA Server 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 AAA Server 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 AAA Server 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
  • NRF Fig. 35 is an example of a block diagram illustrating the main components of the NRF 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 NRF 78 in accordance with the software stored in a memory 784.
  • the Software may be pre-installed in the memory 784 and/or may be downloaded via the telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)), for example.
  • the software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421.
  • the communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating/sending/receiving) signalling between the NRF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3) when the UE 3 is roaming-in.
  • 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 NRF 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
  • AF Fig. 36 is an example of 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.
  • CPUs central processing
  • 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.
  • radio access radio access
  • 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.
  • ⁇ First Supplementary notes> (Supplementary note A1) A method of a User Equipment (UE) comprising: performing a registration procedure using a 5G Femtocell.
  • (Supplementary note A2) A method of a network node comprising: performing a registration procedure using a 5G Femtocell.
  • the core network node is an Access and Mobility Management Function (AMF) node.
  • AMF Access and Mobility Management Function
  • a User Equipment comprising: means for performing a registration procedure using a 5G Femtocell.
  • a network node comprising: means for performing a registration procedure using a 5G Femtocell.
  • the network node according to supplementary note A12, wherein the core network node is an Access and Mobility Management Function (AMF) node.
  • AMF Access and Mobility Management Function
  • DU 5G Distributed Unit
  • CU 5G Centralized Unit
  • (Supplementary note B4) The method according to supplementary note B3, wherein the core network node is a User Plane Function (UPF) node.
  • UPF User Plane Function
  • (Supplementary note B5) The method according to supplementary note B4, wherein the UPF node is located at a private premise network.
  • a User Equipment (UE) comprising: means for performing a PDU Session Establishment procedure related to 5G Femtocell.
  • UE User Equipment
  • a network node comprising: means for performing a PDU Session Establishment procedure related to 5G Femtocell.

Landscapes

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

Abstract

Un aspect de la présente divulgation concerne un procédé d'un équipement utilisateur (UE). Le procédé comprend la réalisation d'une procédure d'enregistrement à l'aide d'une femtocellule 5G. Un autre aspect de la présente divulgation comprend un procédé d'un nœud de réseau. Le procédé comprend la réalisation d'une procédure d'enregistrement à l'aide d'une femtocellule 5G.
PCT/JP2024/026907 2023-09-08 2024-07-29 Procédé d'équipement utilisateur, procédé de nœud de réseau, équipement utilisateur et nœud de réseau Pending WO2025052803A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202311060522 2023-09-08
IN202311060522 2023-09-08

Publications (1)

Publication Number Publication Date
WO2025052803A1 true WO2025052803A1 (fr) 2025-03-13

Family

ID=94923466

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/026907 Pending WO2025052803A1 (fr) 2023-09-08 2024-07-29 Procédé d'équipement utilisateur, procédé de nœud de réseau, équipement utilisateur et nœud de réseau

Country Status (1)

Country Link
WO (1) WO2025052803A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013001054A1 (fr) * 2011-06-30 2013-01-03 Nokia Siemens Networks Oy Transfert intercellulaire entre différents groupes fermés d'abonnés
US20200163140A1 (en) * 2017-08-08 2020-05-21 Mitsubishi Electric Corporation Communication system, communication terminal device, and base station device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013001054A1 (fr) * 2011-06-30 2013-01-03 Nokia Siemens Networks Oy Transfert intercellulaire entre différents groupes fermés d'abonnés
US20200163140A1 (en) * 2017-08-08 2020-05-21 Mitsubishi Electric Corporation Communication system, communication terminal device, and base station device

Similar Documents

Publication Publication Date Title
WO2023286779A1 (fr) Procédé exécuté par un terminal radio, et terminal radio
WO2023080057A1 (fr) Procédé pour appareil à fonction de gestion d'accès et de mobilité (amf), procédé pour nœud de réseau d'accès radio de prochaine génération (ng-ran), procédé pour équipement utilisateur (ue), procédé pour nœud maître (mn), appareil amf, nœud ng-ran, ue et mn
WO2023145526A1 (fr) Procédé d'équipement utilisateur (eu), procédé d'appareil de communication, eu et appareil de communication
WO2023182199A1 (fr) Procédé d'équipement utilisateur (eu), procédé d'appareil de communication et appareil de communication
WO2024162185A1 (fr) Fonction de gestion d'accès et de mobilité, amf, réseau d'accès radio partagé, ran et procédé
WO2024150678A1 (fr) Terminal radio, nœud de réseau central, gestion de données unifiée (udm), serveur d'abonné domestique (hss), équipement utilisateur (ue) et procédé
WO2024053551A1 (fr) Procédé d'équipement utilisateur (ue), procédé d'accès et fonction de gestion de mobilité (amf), procédé de gestion unifiée de données (udm), ue, amf et udm
WO2025052803A1 (fr) Procédé d'équipement utilisateur, procédé de nœud de réseau, équipement utilisateur et nœud de réseau
WO2025052804A1 (fr) Procédé d'équipement utilisateur, procédé de nœud de réseau, équipement utilisateur et nœud de réseau
WO2025041507A1 (fr) Procédé de nœud de réseau d'accès radio, procédé d'équipement utilisateur, nœud de réseau d'accès radio, et équipement utilisateur
WO2025041508A1 (fr) Procédé relatif à un premier nœud de réseau central et premier nœud de réseau central
WO2025033139A1 (fr) Procédé de premier appareil de communication, procédé d'appareil de communication, premier appareil de communication et appareil de communication
WO2025069797A1 (fr) Procédé d'équipement utilisateur (ue), procédé de fonction de gestion d'accès et de mobilité (amf), ue et amf
WO2025069793A1 (fr) Procédé d'équipement utilisateur (ue), procédé de fonction de gestion d'accès et de mobilité (amf), ue et amf
WO2025211350A1 (fr) Procédé mis en œuvre par un équipement utilisateur (ue), procédé mis en œuvre par un premier dispositif de réseau central (cn), équipement utilisateur (ue) et premier dispositif de réseau central (cn)
WO2025211360A1 (fr) Procédé mis en œuvre par un équipement utilisateur (ue), procédé mis en œuvre par un premier dispositif de réseau central (cn), un équipement utilisateur (ue) et un premier dispositif de réseau central (cn)
WO2025211365A1 (fr) Procédé mis en œuvre par un équipement utilisateur, procédé mis en œuvre par un premier dispositif de réseau central, équipement utilisateur et premier dispositif de réseau central
WO2024185489A1 (fr) Équipement utilisateur, première fonction de gestion d'accès et de mobilité, gestion de données unifiée et procédé associé
WO2024053389A1 (fr) Équipement utilisateur (ue), procédé d'ue et fonction de gestion d'accès et de mobilité (amf)
WO2025018238A1 (fr) Procédé de premier appareil de communication, procédé d'équipement utilisateur (ue), premier appareil de communication et ue
WO2025089126A1 (fr) Procédé d'appareil de communication, amf, ran, gnb cu-cp, gnb du, gnb cu-cp, gnb cu-up, udm, pcf, ue, et appareil de communication, amf, ran, gnb cu-cp, gnb du, gnb cu-cp, gnb cu-up, udm, pcf et ue
WO2024150683A1 (fr) Station radio, nœud de réseau central, terminal radio et procédés
WO2024225050A1 (fr) Procédé d'équipement utilisateur (ue) distant, procédé de premier appareil de communication, ue distant et premier appareil de communication
WO2025089109A1 (fr) Procédé d'équipement utilisateur (ue), procédé d'appareil de communication, ue et appareil de communication
WO2025088989A1 (fr) Procédé d'un appareil de communication, procédé d'un autre appareil de communication, appareil de communication et autre appareil de communication

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: 24862459

Country of ref document: EP

Kind code of ref document: A1