Access and Mobility Management Function (AMF) method, User Equipment (UE) method, AMF, UE, and program

Abstract

One aspect of the present disclosure includes a method in an Access and Mobility Management Function (AMF) of a network for providing access to localized services, the method including registering a plurality of User Equipment (UE) devices for the localized services and controlling deregistration of a portion of the plurality of UE devices when the localized services are terminated.

Description

[Technical Field]

[0001] The present disclosure relates to a method performed by a communication device, a method performed by User Equipment (UE), a communication device, and a UE. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) Service and System Aspects Working Group 2 (SA2) is working on further enhancements to the 5G System (5GS) to support Non-Public Networks (NPNs). Specifically, the SA2 NPN study item aims to address the SA1 requirements specified in TS 22.261 (Non-Patent Document 4) related to support for Providing Access to Localized Services (PALS). One of the requirements is to provide support for returning to the home network, and one of the aspects considered in this requirement is as follows (Non-Patent Document 8): To study ways to mitigate the overload of the user plane and control plane caused by a large number of UEs returning from temporary local access of the hosting network to their home network in a very short period of time. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications” V17.1.0(2021-12) [Non-patent document 2] 3GPP TS 23.501: "System architecture for the 5G System(5GS); Stage 2" V17.4.0(2022-03) [Non-Patent Document 3] 3GPP TS 23.502: "Procedures for the 5G System(5GS); Stage 2" V17.4.0(2022-03) [Non-Patent Document 4] 3GPP TS 22.261: "Service requirements for the 5G System; Stage 1" V18.5.0(2021-12) [Non-Patent Document 5] 3GPP TR 22.844: "Study on 5G Network Providing Access to Localized Services; Stage 1" V18.2.0(2021-12) [Non-Patent Document 6] 3GPP TR 23.700-07: "Study on enhanced support of Non-Public Networks(NPN)" V17.0.0(2021-03) [Non-Patent Document 7] 3GPP TS 23.122: "Non-Access-Stratum(NAS) functions related to Mobile Station(MS) in idle mode" V17.6.0(2022-03) [Non-Patent Document 8] 3GPP TR 23.700-08: "Study on enhanced support of Non-Public Networks(NPN); Phase 2" V0.3.0(2022-05) [Non-Patent Document 9] 5G-ACIA White Paper: "5G Non-Public Networks for Industrial Scenarios" [Summary of the Invention] [Problem to be solved by the invention]

[0004] According to the current specification TS 23.501 (Non-Patent Document 2), there are two techniques for controlling overload in the home network: i) access control and regulation, and ii) control plane load control, congestion and overload control. However, these techniques can lead to overload when a large number of UEs simultaneously try to re-register with their home network after accessing localized services from a temporary hosting network, increasing the waiting time of the UEs because they are assigned random back-off timer values ​​to wait before making another attempt due to the overload. [Means for solving the problem]

[0005] In a first exemplary aspect, a method of an Access and Mobility Management Function (AMF) of a network providing access to localized services includes: performing registration of multiple User Equipment (UE) for localization services; Controlling deregistration of some of the UEs when localization services are terminated Includes.

[0006] In a second exemplary aspect, a method for a User Equipment (UE) includes: registering with an Access and Mobility Management Function (AMF) of a network that provides access to localized services to a plurality of UEs, including the UE; When the localization service ends, you will be required to unsubscribe from AMF. Including, The deregistration is performed on a subset of the UEs.

[0007] In a third exemplary aspect, an Access and Mobility Management Function (AMF) of a network providing access to localized services comprises: means for registering a plurality of User Equipment (UE) devices for localization services; A means for controlling the deregistration of some of the UEs when the localization service is terminated. Includes:

[0008] In a fourth exemplary aspect, a User Equipment (UE) means for registering with an Access and Mobility Management Function (AMF) of a network that provides access to localization services to a plurality of UEs, including the UE; A way to unsubscribe from AMF when localization services end. Including, The deregistration is performed on a subset of the UEs. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to provide a method for reducing overload in a home network. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a signaling diagram of a first embodiment. [Figure 2] FIG. 10 is a signaling diagram of variant 4 of the first embodiment. [Figure 3] FIG. 2 is a signaling diagram of a second embodiment. [Figure 4] FIG. 10 is a signaling diagram of variant 3 of the second embodiment. [Figure 5] FIG. 10 is a signaling diagram of a third embodiment. [Figure 6] FIG. 10 is a signaling diagram of variant 1 of the third embodiment. [Figure 7] FIG. 10 is a signaling diagram of a fourth embodiment. [Figure 8] FIG. 10 is a signaling diagram of variant 1 of the fourth embodiment. [Figure 9] FIG. 1 is a diagram illustrating an example of a system overview. [Figure 10] FIG. 1 is a block diagram illustrating a UE. [Figure 11] FIG. 1 is a block diagram illustrating an (R)AN node. [Figure 12] FIG. 1 illustrates a system overview of an (R)AN node based on an O-RAN architecture. [Figure 13] FIG. 1 is a block diagram illustrating an RU. [Figure 14] FIG. 2 is a block diagram illustrating a DU. [Figure 15] FIG. 2 is a block diagram illustrating a CU. [Figure 16] FIG. 1 is a block diagram illustrating an AMF. [Figure 17] FIG. 1 is a block diagram illustrating an SMF. [Figure 18] FIG. 1 is a block diagram illustrating a UPF. [Figure 19] FIG. 1 is a block diagram illustrating a PCF. [Figure 20] FIG. 1 is a block diagram illustrating an NEF. [Figure 21] FIG. 1 is a block diagram illustrating a UDM. [Figure 22] FIG. 1 is a block diagram illustrating an NWDAF. DETAILED DESCRIPTION OF THE INVENTION

[0011] (abbreviation) For the purposes of this document, TR 21.905 (Non-Patent Document 1) and the abbreviations given below apply. Abbreviations defined in this document take precedence over the definition of the same abbreviation in TR 21.905 (Non-Patent Document 1), if any. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier ABBA Anti-Bidding-down Between Architectures AF Application Function AMF Access and Mobility Management Function API Application Programming Interface AS Access Stratum ATSSS Access Traffic Steering,Switching,Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BBF Broadband Forum BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane CU Centralized Unit DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator DU Distributed Unit ePDG evolved Packet Data Gateway EAP Extensible Authentication Protocol EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HR Home Routed(ローミング) IAB Integrated access and backhaul IMEI International Mobile Equipment Identity IMEI / TAC IMEI Type Allocation Code IMS IP Multimedia Subsystem IOWN Innovative Optical and Wireless Network IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out(ローミング) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function LTE Long Term Evolution MAC Medium Access Control MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MNC Mobile Network Code MO Mobile Originated MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol MT Mobile Terminated MT Mobile Termination N3IWF Non-3GPP InterWorking Function N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access Stratum NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol ngKSI Next Generation Key Set Identifier NID Network identifier NPN Non-Public Network NR New Radio NRF Network Repository Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NW-TT Network-side TSN translator NWDAF Network Data Analytics Function O-RAN Open RAN Alliance O-DU O-RAN Distributed Unit O-CU O-RAN Centralized Unit O-RU O-RAN Radio Unit PCF Policy Control Function PDB Packet Delay Budget PDCP Packet Data Convergence Protocol PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience QoS Quality of Service RACS Radio Capabilities Signalling optimisation (R)AN(Radio)Access Network RG Residential Gateway RU Radio Unit RIM Remote Interference Management RLC Radio Link Control RQA Reflective QoS Attribute RQI Reflective QoS Indication RRC Radio Resource Control RSN Redundancy Sequence Number SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SDAP Service Data Adaptation Protocol SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy SMF Session Management Function SMS Short Message Service SMSF Short Message Service Function SN Sequence Number SN名 Serving Network Name SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SOR Steering Of Roaming SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TAI Tracking Area Identity TCP Transmission Control Protocol TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier UP User Plane UPF User Plane Function URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy UU Interface between User Equipment and Radio Access Network VID VLAN Identifier VLAN Virtual Local Area Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function WLAN Wireless Local Area Network WUS Wake Up Signal

[0012] (definition) For the purposes of this document, 3GPP TR 21.905 (Non-Patent Document 1) and the terms and definitions given below apply. Terms defined in this document take precedence over the definition of the same term in 3GPP TR 21.905 (Non-Patent Document 1), if any. Home Network: The network that owns the UE's current subscription / entitlement. The home network can be either a PLMN or an NPN. Home network service: A service provided to a UE based on a subscription agreement with a home network operator. Hosting Network: A network that provides access to local / localized services. Local service, localized service: A service that is localized (i.e., provided in a specific / limited area) and / or may be time-restricted. This service may be realized via an application (e.g., live or on-demand audio / video streams, electronic games, IMS, etc.) or a connection (e.g., UE-to-UE, UE-to-data network). Localization Service Provider: An application provider or network operator that localizes services and makes them available to end users through a hosting network. Non-Public Network (NPN): A network for non-public use. Public Network Integrated NPN: A non-public network deployed with PLMN support. Return to Home Network: The UE leaves the hosting network (e.g., when local / localized services are discontinued) and resumes using the home network registration / entitlement. This may include network selection (e.g., selecting HPLMN or VPLMN) and deactivating / activating the SNPN access mode. Stand-alone Non-Public Network (SNPN): A non-public network that does not rely on network functions provided by a PLMN.

[0013] (First aspect (Solution 1)) Referring to FIG. 1, this solution solves or at least alleviates the problem of overload in the home network by adaptively deregistering the UE from the hosting network based on input from the home network.

[0014] One of the first aspects is a method for a first node of access and mobility management in a first network, where the first network may be a local network, a SNPN, or a hosting network such as a PNI-NPN.

[0015] In a first step of this aspect, a first access and mobility management node receives a value from a second access and mobility management node included in a second network. The value indicates a number of first UEs allowed to register in the second network per unit time. The number of first UEs may be a maximum allowed number of return UEs from the first network to the second network per unit time. The second network may be a home network such as a PLMN or NPN.

[0016] In a second step of this aspect, the first node transmits a first message to at least one second UE among the third UEs registered in the first network to deregister from the first network. The first message may be a deregistration request message or a UE configuration update command instructing the second UE to deregister from the first network. The number of the third UEs is equal to or less than the number of the first UEs.

[0017] One of the first aspects may include: the first node sends, to the second node, a registration request for a maximum allowed number of re-tuning UEs to the second node; the first node sends, to the second node, a de-registration for a maximum allowed number of re-tuning UEs to the second node after all UEs have returned to the second network. This aspect will be described in detail later. There are two types of NPNs: standalone NPNs (SNPNs) and public network integrated NPNs (PNI-NPNs). Either type of NPN can be used as a hosting network for accessing localized services. The home network can be a PLMN or an SNPN. In this case, the hosting network AMF registers with the home network AMF to obtain notification of the maximum allowed number of returning UE(s) from the hosting network to the home network per unit time. The maximum allowed number of returning UE(s) from the hosting network to the home network per unit time may be the number of UE(s), the number of UE(s) returning from the hosting network to the home network per unit time, where the number of UE(s) is allowed by the home network, such as the home network AMF. Based on the usage registration request, the home network AMF determines a value, which may be a hosting-network- and / or localization-service-specific maximum allowed number of returning UE(s) to the home network per unit time. Then, based on the usage registration request, the home network AMF notifies (or sends, or transmits) to the hosting network AMF the hosting-network- and / or localization-service-specific maximum allowed returning UE(s) to the home network per unit time. After the localization service is terminated, the hosting network AMF selects (one or more) UE(s) such that the number of selected UEs is less than or equal to the maximum allowed returning UE number. Then, the hosting network AMF deregisters the selected UE(s) simultaneously or during the unit time.The deregistered UE(s) then select a home network. The deregistered UE(s) then initiate a registration procedure to connect to the home network. The registration procedure may include the deregistered UE(s) sending a registration request message to the home network AMF. If there is a change in the maximum allowed number of returning UE(s) to the home network per unit time from the hosting network, the home network AMF notifies the hosting network AMF of the new value in a new notification. This process of adaptively deregistering UEs from the hosting network based on input from the home network continues until all UEs registered with the localization service are deregistered from the hosting network.

[0018] Figure 1 will now be described in more detail, purely by way of example, and shows the adaptive deregistration procedure.

[0019] 1. An agreement exists between the hosting network and the home network, and based on the agreement, the identity, location, and / or localization service information of the home network and the hosting network are pre-configured for communication purposes.

[0020] 2a. The UE initiates registration with the hosting network to access localization services. The UE sends a registration request message to the hosting network AMF. The registration request message may include the identity of the UE's home network.

[0021] 2b. An authentication procedure is performed and the UE is allowed to access the localization service.

[0022] Note: The UE's home network credentials for authenticating and authorizing access to localization services can be used to identify the UE's home network. If other credentials are used to access localization services, the UE can share the UE's home network ID with the hosting network when initiating the registration procedure to access localization services.

[0023] 2c. The hosting network AMF accepts the UE's registration. The hosting network AMF sends a registration acceptance message to the UE.

[0024] 3a. AF provides localized service information. If the AF is under the control of a third-party service provider, including other network operators and localized service providers, the AF provides localized service information through the NEF.

[0025] 3b. When the UDM receives the localized service information, the UDM forwards the localized service information by including the number of UEs registered for the localized service.

[0026] 3c. The hosting network AMF registers to a configuration service for adaptively deregistering the hosting network UE. The registration request includes the hosting network ID, localization service information, and / or the number of UEs registered for the localization service.

[0027] 3d. Upon receiving a usage registration request from the hosting network AMF, the home network AMF determines the maximum allowable number of hosting network and / or localized service-specific return UEs to the home network per unit time, which is used for simultaneous / or unit time deregistration in the hosting network.

[0028] The home network AMF may determine the maximum number of UEs that the home network AMF can process at one time based on the processing capacity of the home network AMF.

[0029] Based on the number of UEs registered for a localization service in the hosting network, the localization service termination time, and / or the number of UEs that can attempt registration from the home network and other hosting networks, the home network AMF determines the maximum allowable number of hosting network and / or localization service-specific return UEs to the home network per unit time. The home network AMF ensures that the total number of UEs attempting registration at one time from the home network and the hosting network does not exceed the maximum number of UEs. The total number of UEs attempting registration at that time is a number that the home network AMF can handle based on its processing capacity to avoid congestion and overload.

[0030] 3e. The home network AMF notifies the hosting network of the maximum allowed number of returning UEs to the home network per unit time. The notification includes the hosting network ID, the maximum allowed number of returning UEs for deregistration per unit time, the valid time for complying with this instruction, and / or the localized service information the UE is accessing. The valid time for complying with this instruction is the number of time units during which the notified value of the maximum allowed number of returning UEs is applicable to deregistration of the UE in the hosting network within a unit time. For example, if the valid time for complying with this instruction is 2, the notified value of the maximum allowed number of returning UEs is valid as the maximum allowed number of returning UEs per unit time within 2 time units.

[0031] If there is a change in the maximum allowed number of returning UEs from the hosting network to the home network per unit time due to an increase or decrease in the number of UEs that can attempt registration from the home network and other hosting networks, the home network AMF notifies the hosting network AMF of the new value (updated maximum allowed returning UEs) in a new notification. In this case, the hosting network AMF discards the old notification according to the instructions in the new notification, i.e., the new notification always has a higher priority than the old notification.

[0032] 4. The temporary localization service is terminated or discontinued in the hosting network.

[0033] 5a. The hosting network AMF selects the number of returning UEs from the list of UEs registered for localization services. The selection is for adaptive UE simultaneous or sub-unit deregistration based on a notification from the home network AMF, and ensures that the number of returning UEs from the hosting network does not exceed the maximum number of UEs that the home network AMF can handle. Alternatively, the selected number of returning UEs is less than or equal to the notified value of the maximum allowed number of returning UEs.

[0034] Note: The advertised value of the maximum allowed number of returning UEs to the home network is valid until the validity time expires.

[0035] 5b. The hosting network AMF initiates simultaneous or sub-unit time deregistration of UEs for a selected number of returning UEs to the home network.

[0036] Note: Some UEs may initiate a deregistration procedure before the localization service is terminated. The hosting network AMF can also process UE-initiated deregistration requests. To allow the hosting network AMF to select that number of returning UEs to the home network, the UE's service termination time can be set slightly more than the actual localization service termination time.

[0037] 5c. The UE deregisters from the hosting network, and the AMF accepts the deregistration. This step may be that the UE sends a deregistration acceptance message to the hosting network AMF.

[0038] Note: After deregistration, the UE puts the hosting network NPN into the temporary barred list and starts the automatic PLMN / SNPN network selection mode.

[0039] 6. The deregistered UE leaves the hosting network and initiates (re)registration to the home network.

[0040] 7. When all UEs registered for the localization service are deregistered from the hosting network, the hosting network AMF deregisters from the configuration service. The request for deregistration from the configuration service for the temporary localization service includes the hosting network ID and localization service information.

[0041] According to this aspect, since the hosting network is provided with an upper limit per unit time (the maximum allowable number of UEs returning from the hosting network to the home network), the number of deregistered UEs that (re)register with the home network can be limited so as not to exceed the upper limit per unit time, thereby reducing the load on the home network.

[0042] (Modification 1 of the first aspect) In step 3a, the AMF may have subscribed to the UDM service after successful registration procedures in steps 2a, 2b, and 2c to receive localized service information from the UDM.

[0043] In this case, the AMF sends the UDM a Nudm_EventExposure_Subscribe message with the application ID that the AMF wants to be notified about. When the UDM receives the Nudm_EventExposure_Subscribe message from the AMF, the UDM sends an Nnef_EventExposure_Subscribe message with the received application ID from the AMF to either the NEF or the AF. With this subscription to the NEF or AF, the NEF or AF notifies the UDM of the localization service information by sending an Nnef_EventExposure_Notify message in step 3a. When the UDM receives the Nnef_EventExposure_Notify message with the localization service information from the NEF or AF, the UDM sends a Nudm_EventExposure_Notify message with the localization service information to the AMF in step 3b.

[0044] (Modification 2 of the first aspect) In step 3a, the AMF may have subscribed to the NEF or AF service after successful registration procedures in steps 2a, 2b and 2c in order to receive localized service information directly from the NEF or AF without involving the UDM.

[0045] In this case, the AMF sends the NEF or AF an Nnef_EventExposure_Subscribe message with the application ID that the AMF wants to be notified about. With this subscription to the NEF or AF, the NEF or AF notifies the AMF of the localized service information by sending an Nnef_EventExposure_Notify message directly to the AMF.

[0046] (Modification 3 of the first aspect) In step 4, the AMF recognizes that the localization service has been discontinued by explicit signaling for the AF.

[0047] When the AMF registers for a UDM service as described in Variant 1 of the first aspect, the AMF receives a Nudm_EventExposure_Notify message from the UDM that includes localized service information instructing service termination. When the UDM receives the Nnef_EventExposure_Notify message from the NEF or AF, the UDM sends a Nudm_EventExposure_Notify message to the AMF.

[0048] When an AMF registers for an NEF or AF service as described in variant 2 of the first aspect, the AMF receives an Nnef_EventExposure_Notify message from the NEF or AF containing localized service information instructing the service to be terminated.

[0049] (Modification 4 of the first aspect) FIG. 2 shows an adaptive deregistration procedure according to Variant 4 of the first aspect.

[0050] 1. The hosting network AMF registers with the configuration service to deregister the hosting network UE. The registration request includes the hosting network ID, localization service information, and / or the number of UEs registered for the localization service.

[0051] 2. Upon receiving a usage registration request from the hosting network AMF, the home network AMF determines the hosting network and / or localization service specific maximum allowable number of UEs that can return from the hosting network to the home network per unit time, which is used for simultaneous / or unit time deregistration in the hosting network.

[0052] 3. The home network AMF notifies the hosting network of the maximum allowed number of returning UEs to the home network per unit time. The notification includes the hosting network ID, the maximum allowed number of returning UEs for deregistration per unit time, the validity period for complying with this instruction, and / or the localized service information the UE is accessing. The validity period for complying with this instruction is the number of time units within which the notified value of the maximum allowed number of returning UEs is applicable to deregistration of the UE in the hosting network within the unit time.

[0053] 4. The hosting network AMF selects a number of returning UEs from the list of UEs registered for the localization service. The selection is for adaptive simultaneous or sub-unit time deregistration of UEs based on a notification from the home network AMF, and ensures that the number of returning UEs from the hosting network does not exceed the maximum number of UEs that the home network AMF can handle. Alternatively, the selected number of returning UEs is less than or equal to the notified value of the maximum allowed number of returning UEs.

[0054] 5. The hosting network AMF initiates UE deregistration for the selected number of returning UEs to the home network simultaneously or within a unit time.

[0055] 6. The deregistered UE leaves the hosting network and initiates (re)registration with the home network. A number of returning UEs up to the maximum allowed number can initiate the registration procedure with the home network.

[0056] 7. The hosting network AMF deregisters from the configuration service after all UEs registered for the localization service are deregistered. The request to deregister from the configuration service for the temporary localization service includes the hosting network ID and localization service information.

[0057] (Second embodiment (Solution 2)) Referring to Figure 3, this solution solves or at least alleviates the problem of overload in the home network by making the UE wait for a random amount of time before initiating the UE's re-registration procedure with the home network if the number of UEs returning to the home network exceeds a given threshold.

[0058] One of the second aspects is a method for a first node of access and mobility management in a first network, where the first network may be a local network, a SNPN, or a hosting network such as a PNI-NPN.

[0059] In a first step of this aspect, a first access and mobility management node receives a value from a second access and mobility management node included in a second network. The value indicates a number of first UEs allowed to register with the second network per unit time. The number of first UEs may be a maximum allowed number of return UEs from the first network to the second network per unit time. The second network may be a home network such as a PLMN or NPN.

[0060] In a second step of this aspect, the first node transmits a first message to at least one second UE among the third UEs registered in the first network to deregister from the first network within a unit time. The first message may be a deregistration request message or a UE configuration update command instructing the second UE to deregister from the first network. The number of the third UEs is equal to or less than the number of the first UEs.

[0061] In a third step of this aspect, the first node transmits a second message to at least one fourth UE among the fifth UEs registered with the first network to deregister from the first network. The second message includes a first instruction. The first instruction indicates a waiting time for the UE to wait to send a registration request message to the second node. The first instruction may indicate that the UE must wait before sending the registration request message. The waiting time is equal to or greater than a unit time. The fifth UE does not overlap with the third UE. The waiting time may be a random time. The random time may be calculated by the UE, the first node, or the second node.

[0062] The waiting time may be different for each of the fifth UEs.

[0063] This aspect will be described in more detail later. There is a contract between the home network and the hosting network. Based on the contract, the home network provides a maximum allowed number of UEs that can be returned from the hosting network per unit time. This maximum allowed number of UEs (which may be a maximum threshold) may be provided to the hosting network as part of a service contract or via wireless interaction with the home network. If the number of UEs registered with the hosting network to access localized services exceeds the maximum allowed number of UEs provided by the home network, the hosting network AMF indicates a new parameter as "HPLMN / HSNPN Threshold Exceeded" in either the registration accept message or the deregistration accept message. After deregistering from the hosting network, the UE waits for a certain time if instructed. Otherwise, the UE initiates the registration procedure to the home network of the UE immediately after leaving the hosting network. The time may be a random time. The time may be indicated by an instruction. The random time may be calculated by the UE, by the hosting network AMF, or by the home network AMF. The time may vary for each UE.

[0064] Figure 3 will now be described in more detail, purely by way of example, and shows the randomised re-enrolment procedure.

[0065] 1. There is a service agreement between the home network and the hosting network. Based on the agreement, the home network provides a maximum allowed number of UEs that can be returned from the hosting network per unit time. This maximum allowed number of UEs (which may be a maximum threshold) may be provided to the hosting network as part of the service agreement or via wireless interaction with the home network.

[0066] 2a. The UE initiates registration with the hosting network to access localization services, which may be the UE sending a registration request message to the hosting network.

[0067] 2b. An authentication procedure is performed and the UE is allowed to access the localization service.

[0068] Note: The UE's home network credentials for authenticating and authorizing access to localization services can be used to identify the UE's home network. If other credentials are used to access localization services, the UE can share the UE's home network ID with the hosting network when initiating the registration procedure to access localization services. 2c. The hosting network AMF accepts the UE's registration. This may be the hosting network AMF sending a registration acceptance message to the UE.

[0069] If the number of UEs registered to access localized services in the hosting network exceeds a maximum threshold provided by the home network, the hosting network AMF includes an indication in the registration accept message. This is one option for instructing the UE that the HPLMN / HSNPN threshold has been exceeded. The indication may indicate that the UE needs to wait before sending a registration request message to the home network AMF. The indication may indicate a time value that the UE needs to wait before sending a registration request message to the home network AMF.

[0070] 3. The localization service is terminated or discontinued.

[0071] 4a. After the localization service is terminated, the UE initiates a deregistration procedure. This step can be either the hosting network AMF sending a deregistration request message to the UE, or the UE sending a deregistration request message to the hosting network AMF.

[0072] Note: The UE may initiate a deregistration procedure before the localization service is terminated and the hosting network AMF can process it.

[0073] 4b. The hosting network AMF accepts the deregistration of the UE. This step may be that the hosting network AMF sends a deregistration acceptance message to the UE, or that the UE sends a deregistration acceptance message to the hosting network AMF.

[0074] If the number of UEs registered to access localized services in the hosting network exceeds a maximum threshold given by the home network, the hosting network AMF includes an indication in a deregistration accept message from the hosting network AMF to the UE, which is another option for instructing the UE that the threshold has been exceeded.

[0075] Note: After deregistration, the UE puts the hosting network NPN into the temporary barred list and starts the automatic PLMN / SNPN network selection mode.

[0076] 5. If there is an indication in either the registration accept message or the deregistration accept message that the HPLMN / HSNPN threshold has been exceeded, the UE waits for a period of time before initiating the registration procedure with the UE's home network. The period of time may be indicated by the indication. The period of time may be a random period of time. The period of time may vary for each UE. The period of time may be calculated by the UE using the UE's identifier to randomize the deferral time between UEs. The UE's identifier may be the IMSI, SUPI, IMEI, GPSI, or PEI. The UE's identifier may be a subset (or subfield or predefined bit length) of the IMSI, SUPI, IMEI, GPSI, or PEI.

[0077] 6. After the timer as described in step 5 expires, the UE (re)registers with its home network.

[0078] According to this aspect, when the home network exceeds a given threshold, the UE is instructed to wait for a while before starting the registration procedure to the home network, so that the timing of the registration procedure of the UE is dispersed, thereby reducing the load on the home network.

[0079] (Modification 1 of the second aspect) In step 3, the AMF recognizes that the localization service has been discontinued by explicit signaling for the AF.

[0080] When the AMF registers for a UDM service as described in Variant 1 of the first aspect, the AMF receives a Nudm_EventExposure_Notify message from the UDM that includes localized service information instructing service termination. When the UDM receives the Nnef_EventExposure_Notify message from the NEF or AF, the UDM sends a Nudm_EventExposure_Notify message to the AMF.

[0081] When an AMF registers for an NEF or AF service as described in variant 2 of the first aspect, the AMF receives an Nnef_EventExposure_Notify message from the NEF or AF containing localized service information instructing the service to be terminated.

[0082] (Modification 2 of the second aspect) Instead of steps 4a and 4b, a network-initiated deregistration procedure as described in section 4.2.2.3.3 of TS 23.502 is performed, and if the number of UEs registered to access localized services in the hosting network exceeds a maximum threshold given by the home network, the hosting network AMF includes an indication in the deregistration request message from the hosting network AMF to the UE, which is another option for indicating to the UE that the threshold has been exceeded.

[0083] (Modification 3 of the second aspect) FIG. 4 shows a randomized enrollment procedure of Variant 3 of the second embodiment.

[0084] (Option 1) 1. The UE initiates registration with the hosting network to access localization services, which may be the UE sending a registration request message to the hosting network.

[0085] (Option 1) 2. The hosting network AMF accepts the UE's registration. This may be the hosting network AMF sending a registration accept message to the UE. If the number of UEs registered to access localized services in the hosting network exceeds the maximum threshold given by the home network, the hosting network AMF includes an indication in the registration accept message. This is one option for instructing the UE that the HPLMN / HSNPN threshold has been exceeded. The indication may indicate that the UE needs to wait before sending a registration request message to the home network AMF. The indication may indicate a time value that the UE needs to wait before sending a registration request message to the home network AMF.

[0086] (Option 1) 3. The localization service will be terminated or discontinued.

[0087] (Option 2) 4. The UE initiates the deregistration procedure. The UE sends a deregistration request message to the hosting network AMF.

[0088] (Option 2) 5. The hosting network AMF accepts the deregistration of the UE. The hosting network AMF sends a deregistration acceptance message to the UE. If the number of UEs registered to access localized services in the hosting network exceeds the maximum threshold given by the home network, the hosting network AMF includes an instruction in the deregistration acceptance message from the hosting network AMF to the UE.

[0089] 6. If there is an indication in either the registration accept message or the deregistration accept message that the HPLMN / HSNPN threshold has been exceeded, the UE waits for a period of time before initiating the registration procedure with the UE's home network. The period of time may be indicated by the indication. The period of time may be a random period of time. The period of time may vary for each UE. The period of time may be calculated by the UE using the UE's identifier to randomize the deferral time between UEs. The UE's identifier may be the IMSI, SUPI, IMEI, GPSI, or PEI. The UE's identifier may be a subset (or subfield or predefined bit length) of the IMSI, SUPI, IMEI, GPSI, or PEI.

[0090] 7. After the timer as described in step 5 expires, the UE (re)registers with its home network.

[0091] (Third Aspect (Solution 3)) Referring to Figure 5, this solution solves or at least mitigates the problem of overload in the home network by using a UE supporting RRM function that allows the hosting network to instruct the UE to wait a random amount of time before initiating the registration procedure with the UE's home network.

[0092] One of the third aspects is a method for a first node of access and mobility management in a first network, where the first network may be a local network, a SNPN, or a hosting network such as a PNI-NPN.

[0093] In a first step of this aspect, a first node receives a first message from a User Equipment (UE) including a first indication, the first indication indicating that the UE supports waiting a time to send a registration request message to an access and mobility management node of the network.

[0094] In a second step of this aspect, the first node transmits a second message to the UE. The second message indicates a waiting time for the UE before transmitting a registration request message to a second node for access and mobility management of the second network. The waiting time may be a predetermined time. The waiting time may be a random time. The waiting time may be indicated by the hosting network AMF or the home network AMF. The waiting time may be calculated by the UE.

[0095] One of the third aspects may include: the second message includes a list, the list indicating identifiers (IDs) of Public Land Mobile Network Numbers (PLMNs), and the list indicating whether to wait a predetermined time before sending a registration request message to each PLMN.

[0096] This aspect will be described in detail later. When the UE(s) initiate a registration procedure in the hosting network, the UE(s) indicate a UE capability support in the registration request message. The capability may indicate that the UE can wait a time before initiating the registration procedure to the UE's home network. And the capability may be a Randomized Registration Management (RRM) capability. The UE supporting RRM capability enables the hosting network AMF to instruct the UE to wait a time before initiating the registration procedure to the UE's home network.

[0097] A registration accept message or a deregistration accept message from the hosting network AMF to one or more UEs may request the UE to wait a time before initiating a registration procedure with the UE's home network. The time may be a predetermined time. The time may be a random time. The time may be indicated by the hosting network AMF or by the home network AMF. The time may be calculated by the UE. The hosting network AMF may include an RRM request and a PLMN / SNPN list in either the registration accept message or the deregistration accept message. The RRM request may be a request for the UE to wait a certain time before initiating a registration procedure with each PLMN. Alternatively, the RRM request may be a request for the UE to wait a certain time before initiating a registration procedure with a PLMN / SNPN listed in the PLMN / SNPN list. When the UE attempts to register with one of the PLMNs / SNPNs in the list, the RRM request indicates that the UE should wait a certain time before attempting to register with the UE's home network.

[0098] Figure 5 will now be described in more detail, purely by way of example, and shows a procedure for randomised registration management with RRM support.

[0099] 1a. The UE supporting Randomized Registration Management (RRM) functionality is indicated in a registration request message to the hosting network. 1b. An authentication procedure is performed and the UE is allowed to access the localization service.

[0100] Note: The UE's home network credentials for authenticating and authorizing access to localized services can be used to identify the UE's home network PLMN / SNPN. If other credentials are used to access localized services, the UE can share the UE's home network PLMN / SNPN ID with the hosting network when initiating the registration procedure to access localized services.

[0101] 1c. The hosting network AMF accepts the UE's registration.

[0102] Since the RRM function is supported in the UE, the hosting network AMF includes the RRM request and the RRM PLMN / SNPN list in the registration accept message to the UE, which is one option to indicate to the UE what it should wait before initiating the registration procedure to the home network.

[0103] 2. The localization service is terminated or discontinued.

[0104] 3a. After the localization service is terminated, the UE initiates a deregistration procedure in the hosting network. This step may be that the UE sends a deregistration request message to the hosting network AMF. Alternatively, this step may be that the hosting network AMF sends a deregistration request message to the UE. Since the RRM function is supported in the UE, the hosting network AMF includes an RRM request and an RRM PLMN / SNPN list in the deregistration request message to the UE. This is another option for instructing the UE that it should wait.

[0105] 3b. The hosting network AMF accepts the deregistration of the UE. This step may be that the hosting network AMF sends a deregistration acceptance message to the UE. Alternatively, this step may be that the UE sends a deregistration acceptance message to the hosting network AMF.

[0106] Since the RRM function is supported in the UE, the hosting network AMF includes the RRM request and the RRM PLMN / SNPN list in the deregistration accept message to the UE, which is another option to indicate to the UE that it should wait.

[0107] Note: After deregistration, the UE puts the hosting network NPN into the temporary barred list and starts the automatic PLMN / SNPN network selection mode.

[0108] 4. Based on the RRM request, the UE waits a time before initiating a (re)registration procedure in the home network if the UE's home network is in the given RRM PLMN / SNPN list.

[0109] According to this aspect, the registration procedure to the home network is performed in accordance with the capabilities of the UE, which makes it possible to reduce the load on the home network while taking into consideration the capabilities of each UE.

[0110] (Modification 1 of the third aspect) FIG. 6 shows a procedure for registration management with RRM support according to variant 1 of the third aspect.

[0111] 1. The UE supporting Randomized Registration Management (RRM) functionality is indicated in a registration request message to the hosting network.

[0112] (Option 1) 2. The hosting network AMF accepts the UE's registration. Since the RRM function is supported in the UE, the hosting network AMF includes an RRM request and an RRM PLMN / SNPN list in the registration accept message to the UE. This is one option to instruct the UE that it should wait before starting the registration procedure to the home network.

[0113] (Option 2) 3. The UE initiates the deregistration procedure in the hosting network. The UE sends a deregistration request message to the hosting network AMF. Since the RRM function is supported in the UE, the hosting network AMF includes an RRM request and an RRM PLMN / SNPN list in the deregistration request message to the UE.

[0114] (Option 2) 4. The hosting network AMF accepts the UE deregistration. The hosting network AMF sends a deregistration accept message to the UE. Since the RRM function is supported in the UE, the hosting network AMF includes an RRM request and an RRM PLMN / SNPN list in the deregistration accept message to the UE. This is another option to instruct the UE that it should wait.

[0115] 5. Based on the RRM request, the UE waits a time before initiating a (re)registration procedure in the home network if the UE's home network is in the given RRM PLMN / SNPN list.

[0116] (Fourth Aspect (Solution 4)) Referring to Figure 7, this solution solves the problem of overload in the home network by changing the localization service expiration time of the UE when registering with the hosting network.

[0117] A fourth aspect is a method for a first node of a first network access and mobility management, the first network being a local network, a SNPN, or a hosting network such as a PNI-NPN.

[0118] In a first step of this aspect, a first node receives a registration request message from a UE to use a service of a first network, and the UE may attempt to temporarily register with the first network to temporarily use the service.

[0119] In a second step of this aspect, the first node calculates a modified (updated) service end time based on the UE information and the service end time of the service. The UE information is independent for each UE. The modified service end time may be calculated by adding / subtracting / multiplying / dividing the UE information and the service end time of the service. The modified service end time may be calculated by subtracting / dividing the UE information and the UE information. The modified service end time may be calculated by adding / subtracting / multiplying / dividing a value based on the UE information and the service end time of the service. The modified service end time may be calculated by subtracting / dividing the service end time of the service from a value based on the UE information.

[0120] In a third step of this aspect, the first node sends a deregistration message to the UE based on the modified (updated) service end time. The deregistration message may be sent after the modified service end time.

[0121] One of the fourth aspects may include: a first node calculates a first modified (updated) service end time based on first information of a first UE and a first service end time of a service for the first UE; a first node calculates a second modified (updated) service end time based on second information of a second UE and a second service end time of a service for the second UE; a first node sends a first deregistration message to the first UE based on the first modified (updated) service end time; a first node sends a second deregistration message to the second UE based on the second modified (updated) service end time; the first modified (updated) service end time and the second modified (updated) service end time are different.

[0122] This aspect will be described in more detail later. When a UE registers with a hosting network to access localized services, the localized service end time of each UE is slightly modified (e.g., service end time at the UE = actual localized service end time + (-, *, and / or / ) random value) to prevent all UEs from deregistering from the hosting network at the same time. When the assigned service end time of the hosting network AMF expires on the UE side, the UE initiates a deregistration procedure. Because the service end times of the UEs are different due to the added random value, all UEs will not deregister from the hosting network at the same time. Therefore, all UEs will not attempt to register with the UE's home network at the same time.

[0123] FIG. 7 shows the procedure for assigning randomized service termination times.

[0124] 1a. The UE initiates registration with the hosting network to access localization services.

[0125] 1b. An authentication procedure is performed and the UE is allowed to access the localization service.

[0126] 1c. The hosting network AMF accepts the UE registration and shares the localized service end time (e.g., service end time at the UE = actual localized service end time + (-, *, and / or / ) random value) with the UE. The random value may be different for each UE. The random value may be based on UE information. The random value may be based on the UE ID. The random value may be the value of the UE ID.

[0127] 2. The assigned localization service end time expires in the UE.

[0128] 3a. After the localization service is terminated, the UE initiates a deregistration procedure in the hosting network.

[0129] 3b. The hosting network AMF accepts the UE deregistration.

[0130] Note: After deregistration, the UE puts the hosting network NPN into the temporary barred list and starts the automatic PLMN / SNPN network selection mode.

[0131] (Modification 1 of the fourth aspect) FIG. 8 shows a procedure for assigning a randomized service end time according to Variation 1 of the fourth aspect.

[0132] 1. The UE initiates registration with the hosting network to access localization services.

[0133] 2. The hosting network AMF accepts the UE registration and shares the localized service end time (e.g., service end time at the UE = actual localized service end time + (-, *, and / or / ) random value) with the UE. The random value may be different for each UE. The random value may be based on UE information. The random value may be based on the UE ID. The random value may be the value of the UE ID. The UE identifier may be IMSI, SUPI, IMEI, GPSI, or PEI. The UE identifier may be a subset (or subfield or predefined bit length) of IMSI, SUPI, IMEI, GPSI, or PEI.

[0134] 3. The assigned localization service end time expires in the UE.

[0135] (System Overview) FIG. 9 illustrates schematically a telecommunications system 1 for mobile (cellular or wireless) devices (known as user equipment (UE)) to which the above aspects are applicable. The telecommunications system 1 represents a system overview capable of end-to-end communication, e.g., UEs 3 (or user equipment, "mobile devices" 3) communicating with other UEs 3 or service servers in a data network 20 via respective (R)AN nodes 5 and a core network 7.

[0136] The (R)AN node 5 supports any radio access including, for example, 5G radio access technology (RAT), E-UTRA radio access technology, Beyond 5G RAT, 6G RAT, and non-3GPP RAT including wireless local area network (WLAN) technology defined by the Institute of Electrical and Electronics Engineers (IEEE). The (R)AN node 5 may be divided into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU). In some aspects, each of the units may be connected to each other to construct the (R)AN node 5 by adopting an architecture defined by the Open RAN (O-RAN) Alliance, in which case the above units are referred to as an O-RU, O-DU, and O-CU, respectively.

[0137] The (R)AN node 5 may be divided into one or more control plane functions and one or more user plane functions. Additionally, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed across multiple user plane functions, with user traffic on each user plane function being aggregated at both the UE 3 and the (R)AN node 5. This divided architecture is sometimes referred to as "dual connectivity" or "multi-connectivity."

[0138] The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support one of satellite access and terrestrial access.

[0139] The (R)AN node 5 may also be referred to as an access node for non-wireless access, including fixed-line access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0140] The core network 7 may include logical nodes (or "functions") for supporting communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes, among other functions, control plane functions and user plane functions. Each function within a logical node may be considered a network function. A network function may be provided to another node by adapting a Service Based Architecture (SBA).

[0141] By adapting network virtualization techniques such as those defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed in a distributed, redundant, stateless, and scalable manner, providing services from several locations and several running instances in each location. The core network 7 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As is known, a UE 3 may move in and out of areas (i.e., radio cells) served by an (R)AN node 5 as the UE 3 moves within the geographic area covered by the telecommunications system 1. To track the UE 3 and facilitate movement between different (R)AN nodes 5, the core network 7 includes at least one access and mobility management Function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for Beyond 5G or 6G may be used instead of the AMF 70.

[0142] The core network 7 also includes, among other things, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, and a Network Data Analytics Function (NWDAF) 76. When a UE 3 is roaming in a visited Public Land Mobile Network (VPLMN), the UE 3's home Public Land Mobile Network (HPLMN) provides the roaming-out UE 3 with the UDM 75, and at least some of the functionality of the SMF 71, UPF 72, and PCF 73.

[0143] The UE 3 and each serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface, etc.). Adjacent (R)AN nodes 5 are connected to each other via appropriate (R)AN node 5 to (R)AN node interfaces (e.g., a so-called "Xn" interface, etc.). Each (R)AN node 5 is also connected to nodes within the core network 7 (e.g., so-called core network nodes) via appropriate interfaces (e.g., so-called "N2" / "N3" interfaces, etc.). The core network 7 also provides connectivity to a data network 20. The data network 20 can be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. If the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services can be provided by that data network 20. The UE 3 can connect to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types.

[0144] The "Uu" interface may include a control plane and a user plane.

[0145] The user plane of the Uu interface is responsible for carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC, and MAC sublayers over the physical connection. The control plane of the Uu interface is responsible for establishing, modifying, and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers over the physical connection.

[0146] For example, the following messages are communicated over the RRC layer to support AS signaling: RRC Setup Request Message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, any of the following parameters may be included together in the RRC Setup Request message: #establishmentCause and ue-Identity, where ue-Identity may have the value of ng-5G-S-TMSI-Part1 or randomValue. RRC Setup Message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, any of the following parameters may be included together in the RRC Setup message: #masterCellGroup and radioBearerConfig RRC Setup Complete Message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, any of the following parameters may be included together in the RRC Setup Complete message: #guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity

[0147] The UE 3 and the AMF 70 are connected via an appropriate interface (such as, for example, the so-called N1 interface). The N1 interface is responsible for providing communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established via 3GPP access and / or non-3GPP access. For example, the following messages may be communicated via the N1 interface: Registration Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the Registration Request message: #5GS Registration Type, ngKSI, 5GS Mobile Identity, Non-Current Native NAS Keyset Identifier, 5GMM Capabilities, UE Security Capabilities, Requested NSSAI, Last Visited Registration TAI, S1 UE Network Capabilities, Uplink Data Status, PDU Session Status, MICO Indication, UE Status, Additional GUTI, Allowed PDU Session Status, UE Usage Configuration, Requested DRX Parameters, EPS NAS Message Container, LADN Indication, Payload Container Type, Payload Container, Network Slicing Indication, 5GS Update Type, Mobile Station Class Mark 2, Supported Codecs, NAS Message Container, EPS Bearer Context Status, Requested Extended DRX Parameters, T3324 Value, UE Radio Capability ID, Requested Mapping NSSAI, Requested Additional Information, Requested WUS Assistance Information, N5GC Indication and Requested NB-N1 Mode DRX Parameters. Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the registration accept message. #5GS Registration Result, 5G-GUTI, Equivalent PLMN, TAI List, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS Network Capability 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 Deregistration Timer Value, T3502 Value, Emergency Number List, Extended Emergency Number List, SOR Transparent Container, EAP Message, NSSAI Inclusion Mode, Operator-Defined Access Category Definition, Negotiated DRX Parameters, Non-3GPP NW policy, EPS bearer context status, negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID removal indication, pending NSSAI, ciphering key data, CAG information list, aborted 5G-S-TMSI configuration, negotiated WUS assistance information, negotiated NB-N1 mode DRX parameters, and extended Rejected NSSAI. Registration Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the registration complete message: #SOR transparent container. Authentication Request Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the Authentication Request message: #ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge), and EAP message. Authentication Response Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the authentication response message: #Authentication response message identification information, authentication response parameters, and EAP message. Authentication Result Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the Authentication Result message: #ngKSI, EAP Message and ABBA. Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the Authentication Failure message: #Authentication failure message identifier, 5GMM cause and authentication failure parameters. Authentication Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Authentication Rejection message: #EAPMessage. Service Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, any of the following parameters may be included together in the service request message: #ngKSI, Service Type, 5G-S-TMSI, Uplink Data Status, PDU Session Status, Allowed PDU Session Status, NAS Message Container. Service Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, any of the following parameters may be included together in the service accept message: #PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. Service Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, any of the following parameters may be included together in the service rejection message: #5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list. Configuration Update Command Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, any of the following parameters may be included together in the Configuration Update Command message: #Configuration Update Instruction, 5G-GUTI, TAI List, Allowed NSSAI, Service Area List, Network Full Name, Network Short Name, Local Time Zone, Universal Time and Local Time Zone, Network Daylight Saving Time, LADN Information, MICO Instruction, Network Slicing Instruction, Configured NSSAI, Rejected NSSAI, Operator Defined Access Category Definition, SMS Instruction, T3447 Value, CAG Information List, UE Radio Capability ID, UE Radio Capability ID Delete Instruction, 5GS Registration Result, Abort 5G-S-TMSI Configuration, Additional Configuration Instruction and Extended Rejected NSSAI. Configuration Update Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Configuration Update Complete message: #Configuration update complete message identification information.

[0148] User equipment (UE) FIG. 10 is a block diagram illustrating the main components of a mobile device 3 (UE 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit and receive signals to and from connected node(s) via one or more antennas 32. Additionally, the UE 3 may include a user interface 34 for inputting information from the outside or outputting information to the outside. Although not necessarily shown in FIG. 10, the UE 3 may have all the usual functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware, as needed. The software may be pre-installed in memory and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The control unit 33 controls the operation of the UE 3 in accordance with software stored in the memory 36. The software includes, among other things, an operating system 361 and a communication control module 362 having at least one transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for processing (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 10. Such signaling may include, for example, appropriately formatted signaling messages related to access and mobility management procedures (for the UE 3) (e.g., registration request messages and associated response messages). The controller 33 interoperates with one or more Universal Subscriber Identity Modules (USIMs) 35. If equipped with multiple USIMs 35, the controller 33 may activate only one USIM 35 or multiple USIMs 35 simultaneously.

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

[0150] UE3 may be, for example, equipment or machinery for production or manufacturing and / or energy-related machinery (e.g., equipment or machinery such as boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal generators; nuclear generators; batteries; nuclear systems and / or related equipment; heavy electrical equipment; pumps including vacuum pumps; compressors; fans; blowers; hydraulic equipment; pneumatic equipment; metalworking machinery; manipulators; robots and / or application systems thereof; tools; molds or dies; rolls; material 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 environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems for any of the foregoing equipment or machinery, etc.).

[0151] The UE 3 may be, for example, an item of transportation equipment (e.g., transportation equipment such as railcars; automobiles; motorcycles; bicycles; trains; buses; carts; rickshaws; ships or other watercraft; aircraft; rockets; satellites; drones; balloons, etc.).

[0152] The UE 3 may be, for example, an information and communication equipment item (eg, information and communication equipment such as electronic computers and related equipment; communications and related equipment; electronic components, etc.).

[0153] The UE3 may be, for example, a refrigerator, a refrigerator application product, a goods and / or service industry equipment item, a vending machine, an automated service machine, an office machine, a consumer electronic device and an electronic appliance (e.g., consumer appliances such as audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related appliances; vacuum cleaners, etc.).

[0154] The UE 3 may be, for example, an electrical application system or equipment (eg, an electrical application system or equipment such as an X-ray system; a particle accelerator; a radioisotope equipment; a sonic equipment; an electromagnetic application equipment; an electrical application equipment, etc.).

[0155] The UE3 may be, for example, an electronic lamp, lighting fixture, measuring equipment, analyzer, tester, or surveying or sensing equipment (e.g., surveying or sensing equipment such as a smoke detector; a motion sensor; a radio frequency tag; etc.), a wristwatch or watch, inspection equipment, optical equipment, medical equipment and / or systems, weapons, cutlery, hand tools, etc.

[0156] UE3 may be, for example, a wireless-equipped personal digital assistant or related equipment, such as a wireless card or module designed to be attached to or inserted into another electronic device (e.g., a personal computer, electrical measuring instrument).

[0157] The UE 3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below in relation to the "internet of things (IoT)."

[0158] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connections, etc. that enable these devices to collect and exchange data with each other and other communicating devices. IoT devices may comprise automated machinery that follows software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or inactive for extended periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people to be monitored / tracked. It will be appreciated that IoT technology can be implemented on any communication device that can connect to a communication network to send / receive data, whether such communication device is controlled by human input or software instructions stored in memory.

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

[0160] The UE3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).

[0161] The UE3 may be a car, a connected car, or an autonomous car, or a vehicle device, or a motorcycle, or a V2X (Vehicle to Everything) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-pedestrian communication module, and a vehicle-to-network communication module).

[0162] (R)AN Node FIG. 11 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit and receive signals to and from connected UE(s) 3 via one or more antennas 52, and to transmit and receive signals to and from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls operation of the (R)AN node 5 according to software stored in memory 55. The software may, for example, be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (e.g., RMD). The software includes, among other things, an operating system 551 and a communications control module 552 having at least one transceiver control module 5521.

[0163] The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling (e.g., directly or indirectly) 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. The signaling may include, for example, appropriately formatted signaling messages related to the radio connection (for a particular UE 3) and connection with the core network 7, in particular related to connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages over the N2 reference point) and Xn application protocol (XnAP) messages (i.e., messages over the Xn reference point), etc. Such signaling may also include, for example, broadcast information (e.g., master information and system information) in the case of transmission.

[0164] The control unit 54, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

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

[0166] System overview of (R)AN Node 5 based on O-RAN architecture FIG. 12 illustrates schematically an (R)AN node 5 based on an O-RAN architecture to which aspects of the (R)AN node 5 are applicable.

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

[0168] The UE 3 and each serving RU 60 are connected via an appropriate air interface (e.g., a so-called "Uu" interface, etc.). Each RU 60 is connected to a DU 61 via an appropriate interface (e.g., a so-called "fronthaul," "open fronthaul," "F1" interface, etc.). Each DU 61 is connected to a CU 62 via an appropriate interface (e.g., a so-called "midhaul," "open midhaul," "E2" interface, etc.). Each CU 62 is also connected to a node in the core network 7 (e.g., a so-called core network node) via an appropriate interface (e.g., a so-called "backhaul"(s), "open backhaul," "N2" / "N3" interface, etc.). The user plane part of the DU 61 can also be connected to the core network node 7 via an appropriate interface (e.g., a so-called "N3" interface(s)).

[0169] Depending on the functionality divided among the RU 60, DU 61, and CU 62, each unit provides a portion of the functionality provided by the (R)AN node 5. For example, the RU 60 may provide functionality for communicating with the UE 3 over the air interface, the DU 61 may provide functionality for supporting the MAC and RLC layers, and the CU 62 may provide functionality for supporting the PDCP, SDAP, and RRC layers.

[0170] Radio Unit (RU) FIG. 13 is a block diagram illustrating the main components of an exemplary RU 60, e.g., a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit and receive signals to and from connected UE(s) 3 via one or more antennas 602 and to transmit and receive signals to and from other network nodes or units (directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 according to software stored in memory 605. The software may, for example, be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least one transceiver control module 60521.

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

[0172] The control unit 604, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

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

[0174] As mentioned above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any of the functions described for the RU 60 can be implemented in the integrated / combined unit.

[0175] Distributed Unit (DU) FIG. 14 is a block diagram illustrating the main components of an exemplary DU 61, e.g., the DU portion of a base station (e.g., an "eNB" in LTE, a "gNB" in 5G, a 5G Beyond base station, or a 6G base station). As shown, the device includes a transceiver circuit 611 operable to transmit and receive signals to and from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 according to software stored in memory 614. The software may, for example, be pre-installed in memory 614 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least one transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 or other nodes and units.

[0176] The DU61 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

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

[0178] Centralized Unit (CU) FIG. 15 is a block diagram illustrating the main components of an exemplary CU 62, e.g., the CU portion of a base station (e.g., an "eNB" in LTE, a "gNB" in 5G, a 5G Beyond base station, or a 6G base station). As shown, the device includes a transceiver circuit 621 operable to transmit and receive signals to and from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 according to software stored in memory 624. The software may, for example, be pre-installed in the memory 624 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least one transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

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

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

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

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

[0183] SMF 17 is a block diagram illustrating the major components of the SMF 71. As shown, the device includes a transceiver circuit 711 operable to send and receive signals to 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 memory 714. The software may be pre-installed in the memory 714 and / or downloaded over a telecommunications network or from 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 one transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421) is responsible for handling (generating / sending / receiving) signaling between the SMF 71 and other nodes, such as the UPF 72 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., Hypertext Transfer Protocol (HTTP) restful methods based on service-based interfaces) related to session management procedures (for the UE 3).

[0184] The SMF 71 can support a Non-Public Network (NPN), which can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0185] UPF 18 is a block diagram illustrating the major components of the UPF 72. As shown, the device includes a transceiver circuit 721 operable to transmit and receive signals to and 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 memory 724. The software may, for example, be pre-installed in the memory 724 and / or downloaded over a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least one transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating / sending / receiving) signaling 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 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages related to user data processing (for the UE 3) (e.g., GPRS Tunneling Protocol (GTP) for the user plane).

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

[0187] PCF 19 is a block diagram illustrating the major components of the PCF 73. As shown, the device includes a transceiver circuit 731 operable to send and receive signals to 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 memory 734. The software may, for example, be pre-installed in the memory 734 and / or downloaded over a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least one transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signaling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for the UE 3) related to policy management procedures (for example, HTTP restful methods based on service-based interfaces).

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

[0189] NEF 20 is a block diagram illustrating the major components of the NEF 74. As shown, the device includes a transceiver circuit 741 operable to send and receive signals to other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the NEF 74 according to software stored in memory 744. The software may, for example, be pre-installed in the memory 744 and / or downloaded over a telecommunications network or from 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 one transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signaling between the NEF 74 and other nodes, such as the UDM 75 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) related to network publication function procedures (for the UE 3).

[0190] The NEF 74 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0191] UDM 21 is a block diagram illustrating the major components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to send and receive signals to 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 memory 754. The software may, for example, be pre-installed in the memory 754 and / or downloaded over a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least one transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signaling 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 when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) related to mobility management procedures (for the UE 3).

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

[0193] NWDAF 22 is a block diagram illustrating the major components of the NWDAF 76. As shown, the device includes a transceiver circuit 761 operable to send and receive signals to other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NWDAF 76 according to software stored in memory 764. The software may, for example, be pre-installed in the memory 764 and / or downloaded over a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least one transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signaling between the NWDAF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) related to network data analysis function procedures (for the UE 3).

[0194] The NWDAF 76 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0195] Modifications and Alternatives

[0033] Detailed embodiments have been described above. As those skilled in the art will appreciate, many modifications and alternatives may be made to the above embodiments while still having the benefit of the disclosure embodied therein. By way of example only, some of these alternatives and modifications are described herein.

[0196] In the above description, the UE 3 and network devices are described for ease of understanding as having several separate modules (such as a communications control module). These modules may be provided in this manner in certain applications, for example, where an existing system is modified to implement the present disclosure, but in other applications, such as systems designed from the beginning with the features of the present invention in mind, these modules may be incorporated into an overall operating system or code, so that they may not be identifiable as separate entities. These modules may be implemented in software, hardware, firmware, or a combination thereof.

[0197] Each control unit may comprise any suitable form of processing circuitry including, for example (but not limited to), one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses and / or address buses), direct memory access (DMA) facilities, hardware or software-implemented counters, pointers and / or timers, etc.

[0198] In the above embodiments, several software modules have been described. As will be appreciated by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be provided to the UE 3 and network devices as signals over a computer network or on a recording medium. Furthermore, the functionality performed by some or all of this software may be implemented using one or more dedicated hardware circuits. However, the use of software modules is preferred because it facilitates updating the UE 3 and network devices to update their functionality.

[0199] In the above embodiment, 3GPP wireless communication (radio access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technology (e.g., BBF access, cable access, optical access, etc.) may also be used according to the above embodiment.

[0200] An item of user equipment may be, for example, a communication device such as a mobile phone, a smartphone, a user equipment, a personal digital assistant, a laptop / tablet computer, a web browser, an e-book reader, etc. Such mobile (or generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, this application refers to mobile devices (or UE) in the description, but it will be understood that the described techniques may be implemented on any communication device (mobile and / or generally fixed) that can connect to a communication network to send and receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory.

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

[0202] (Addendum) All or part of the exemplary aspects disclosed above can be described as follows, but are not limited to: (Appendix 1) 1. A method for a first node of Access and Mobility Management of a first network, the method comprising: receiving, from a second access and mobility management node included in the second network, a value indicating a number of first User Equipments (UEs) allowed to register with the second network per unit time; sending a first message to at least one second UE among the third UEs registered in the first network to deregister from the first network; Including, The method wherein the number of the third UEs is less than or equal to the number of the first UEs. (Appendix 2) transmitting the first message is transmitted within a unit time; The method is: sending a second message to at least one fourth UE among the fifth UEs registered with the first network to deregister from the first network; further comprising the second message includes a first instruction, the first instruction indicating a waiting time for waiting to send the registration request message to the second node, the waiting time being equal to or greater than a unit time; 2. The method of claim 1, wherein the fifth UE does not overlap with the third UE. (Appendix 3) 3. The method of claim 2, wherein the waiting time is different for each of the fifth UEs. (Appendix 4) 1. A method for a first node of access and mobility management in a first network, the method comprising: receiving, from a User Equipment (UE), a first message including a first indication indicating that waiting a predetermined time to send a registration request message to an access and mobility management node of a network is supported in the UE; sending a second message to the UE, the second message requesting the UE to wait a predetermined time before sending a registration request message to a second node of an access and mobility management of the second network; A method comprising: (Appendix 5) the second message includes a list indicating Public Land Mobile Network Number (PLMN) identifiers (IDs), the list indicating whether to wait a predetermined time before sending a registration request message to each PLMN; The method described in Appendix 4. (Appendix 6) 1. A method for a first node of access and mobility management in a first network, the method comprising: receiving, from the UE, a registration request message for temporarily using a service of the first network; Calculating a modified service end time based on information of the UE and a service end time of the service, where the information of the UE is independent for each UE; sending a deregistration message to the UE based on the modified service end time; A method comprising: (Appendix 7) Calculating a first modified service end time based on the first information of the first UE and a first service end time of the service for the first UE; calculating a second modified service end time based on the second information of the second UE and a second service end time of the service for the second UE; sending a first deregistration message to the first UE based on the first modified service end time; sending a second deregistration message to the second UE based on the second modified service end time; further comprising 7. The method of claim 6, wherein the first modified service end time and the second modified service end time are different. (Appendix 8) 1. A method for a second node of access and mobility management in a second network, the method comprising: receiving a usage registration message from an access and mobility management first node of the first network for a value indicating a number of first User Equipments (UEs) allowed to register with the second network per unit time; transmitting to the first node a value indicating a number of first UEs allowed to register with the second network per unit time; receiving a registration request message within a unit time from at least one second UE among third UEs registered in the first network, wherein at least one second UE is deregistered from the first network within the unit time, and the number of third UEs is less than or equal to the number of first UEs; A method comprising: (Appendix 9) 1. A method for User Equipment (UE), the method comprising: receiving a second message to deregister from the first network from an access and mobility management first node of the first network, the second message including a first instruction, the first instruction indicating a time to wait to send a registration request message to a second access and mobility management second node of the second network; and sending a registration request message to the second node after waiting that time. A method comprising: (Appendix 10) 1. A method for User Equipment (UE), the method comprising: sending a first message to a first network access and mobility management first node, the first message including a first indication indicating that waiting a predetermined time for sending a registration request message to the network access and mobility management node is supported in the UE; receiving a second message from the first node, the second message requesting the UE to wait a predetermined time before sending a registration request message to a second node of an access and mobility management of the second network; A method comprising: (Appendix 11) a first node of an access and mobility management of a first network, a memory storing instructions; receiving, from a second access and mobility management node included in the second network, a value indicating a number of first User Equipment (UE) allowed to register with the second network per unit time; Send a first message to at least one second UE among the third UEs registered in the first network to deregister from the first network. at least one hardware processor configured to process instructions; Equipped with The first node, wherein the number of third UEs is less than or equal to the number of first UEs. (Appendix 12) A first node of an access and mobility management of a first network, the first node comprising: a memory storing instructions; receiving a first message from a User Equipment (UE) including a first indication indicating that waiting a predetermined time to send a registration request message to an access and mobility management node of a network is supported in the UE; Sending a second message to the UE, the second message requesting the UE to wait a predetermined time before sending a registration request message to a second node of the access and mobility management of the second network. at least one hardware processor configured to process instructions; a first node comprising: (Appendix 13) A first node of an access and mobility management of a first network, the first node comprising: a memory storing instructions; receiving, from the UE, a registration request message for temporarily using a service of the first network; Calculate the modified service termination time according to the UE information and the service termination time of the service, and the UE information is independent for each UE; Sending a deregistration message to the UE based on the modified service end time at least one hardware processor configured to process instructions; a first node comprising: (Appendix 14) a second node of an access and mobility management of a second network, the second node comprising: a memory storing instructions; receiving, from a first node of an access and mobility management system of the first network, a usage registration message for a value indicating a number of first User Equipments (UEs) allowed to register with the second network per unit time; transmitting to the first node a value indicating a number of first UEs allowed to register with the second network per unit time; receiving a registration request message from at least one second UE among the third UEs registered in the first network within a unit time; at least one second UE being deregistered from the first network within a unit time; and the number of the third UEs being less than or equal to the number of the first UEs. at least one hardware processor configured to process instructions; a second node comprising: (Appendix 15) a memory storing instructions; receiving a second message to deregister from the first network from a first node of access and mobility management of the first network, the second message including a first instruction, the first instruction indicating a time to wait to send a registration request message to a second node of access and mobility management of the second network; Send a registration request message to the second node after waiting that amount of time at least one hardware processor configured to process instructions; User Equipment (UE) comprising: (Appendix 16) a memory storing instructions; Sending a first message to a first network access and mobility management first node, the first message including a first indication indicating that waiting a predetermined time to send a registration request message to the network access and mobility management node is supported in the UE; receiving a second message from the first node, the second message requesting the UE to wait a predetermined time before sending a registration request message to a second node of the access and mobility management of the second network; at least one hardware processor configured to process instructions; User Equipment (UE) comprising:

[0203] This application claims the benefit of priority from Indian Patent Application No. 202211044606 filed on August 4, 2022, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0204] 20 Data Network 3UE 31 Transceiver Circuit 32 Antenna 33 Control Unit 34 User Interface 35 USIM 36 memory 361 Operating Systems 362 Communication Control Module 3621 Transceiver Control Module 5 (R)AN nodes 51 Transceiver circuit 52 Antenna 53 Network Interface 54 Control Unit 55 memory 551 Operating Systems 552 Communication Control Module 5521 Transceiver Control Module 60RU 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Control Unit 605 memory 6051 Operating System 6052 Communication Control Module 60521 Transceiver Control Module 61 DU 611 Transceiver Circuit 612 Network Interface 613 Control Unit 614 memory 6141 Operating System 6142 Communication Control Module 61421 Transceiver Control Module 62 CU 621 Transceiver Circuit 622 network interface 623 Control Unit 624 memory 6241 Operating System 6242 Communication Control Module 62421 Transceiver Control Module 7 Core Network 70 AMF 701 Transceiver Circuit 702 network interface 703 Control Unit 704 memory 7041 Operating System 7042 Communication Control Module 70421 Transceiver Control Module 71 SMF 711 Transceiver Circuit 712 Network Interface 713 Control Unit 714 memory 7141 Operating System 7142 Communication Control Module 71421 Transceiver Control Module 72 UPF 721 Transceiver Circuit 722 network interface 723 Control Unit 724 memory 7241 Operating System 7242 Communication Control Module 72421 Transceiver Control Module 73 PCF 731 Transceiver Circuit 732 network interface 733 Control Unit 734 memory 7341 Operating System 7342 Communication Control Module 73421 Transceiver Control Module 74 NEF 741 Transceiver Circuit 742 network interfaces 743 Control Unit 744 memory 7441 Operating System 7442 Communication Control Module 74421 Transceiver Control Module 75 UDM 751 Transceiver Circuit 752 network interfaces 753 Control Unit 754 memory 7541 Operating Systems 7542 Communication Control Module 75421 Transceiver Control Module 76 NWDAF 761 Transceiver Circuit 762 network interfaces 763 Control Unit 764 memory 7641 Operating System 7642 Communication Control Module 76421 Transceiver Control Module

Claims

1. 1. A method of an Access and Mobility Management Function (AMF) of a network for providing access to localized services, comprising: registering a plurality of User Equipment (UE) devices for the localized service; and controlling deregistration of a portion of the plurality of UEs when the localization service is terminated. A method comprising:

2. controlling the deregistration includes sending a deregistration request message to the portion of the plurality of UEs. The method of claim 1.

3. 1. A method for User Equipment (UE), comprising: registering with an Access and Mobility Management Function (AMF) of a network that provides access to localized services to a plurality of UEs, including the UE; When the localization service is terminated, deregistration from the AMF is performed. Including, The method, wherein the deregistration is performed by a portion of the plurality of UEs.

4. the deregistration includes receiving a deregistration request message; the deregistration request message is received by the portion of the plurality of UEs. The method of claim 3.

5. An Access and Mobility Management Function (AMF) of a network providing access to localized services, comprising: means for registering a plurality of User Equipments (UEs) for the localization service; means for controlling deregistration of a portion of the plurality of UEs when the localization service is terminated; AMF, which is equipped with

6. the deregistration includes receiving a deregistration request message; the deregistration request message is received by the portion of the plurality of UEs. The AMF of claim 5.

7. User Equipment (UE), means for registering with an Access and Mobility Management Function (AMF) of a network that provides access to localized services to a plurality of UEs, including the UE; means for deregistering from the AMF when the localization service is terminated; Equipped with The deregistration is performed on some of the plurality of UEs.

8. the deregistration includes receiving a deregistration request message; the deregistration request message is received by the portion of the plurality of UEs.

8. The UE of claim 7.

Images