Methods performed by User Equipment (UE), methods performed by Unified Data Management (UDM), User Equipment and Unified Data Management

Abstract

Aspects of the present disclosure include a method in a user equipment (UE) that communicates with a communication device, the method receiving first signal threshold information from the communication device, and performing PLMN selection based on the first signal threshold information.

Description

Technical Field

[0001] The present disclosure relates to a method for a user equipment (UE), a method for a communication device, a UE, and a communication device.

Background Art

[0002] According to 3GPP (registered trademark) contribution SP-211068 [2], 3GPP defines a new function called Signal Level Enhanced Network Selection in 3GPP Release 18. This function solves the problem of VPLMN selection when IoT devices are not on their home network. There are many cases where IoT devices are not within the home network. For example, the module of an IoT device is deployed outside the country of the provided USIM or for the use of a global USIM for IoT use cases.

Summary of the Invention

Problems to be Solved by the Invention

[0003] The problem of VPLMN selection by IoT devices is summarized as follows. During the initial steps of network selection after switch-on or recovery from coverage loss, and during all steps of periodic reselection, the signal levels of available cells are not taken into account. Only the cell selection criteria broadcast by the PLMN and the priority of the network are considered for cell reselection.

[0004] This can cause a UE to select or remain on a network with insufficient coverage in a particular location. This happens because the UE selects a higher-priority PLMN even though other PLMNs with lower priority are available with much better local coverage. For a typical consumer UE, this is not a problem, as conditions change rapidly due to mobility, and there are users who can recognize the problem and respond by, for example, slightly changing their location or manually selecting a different PLMN. This is desirable behavior as part of roaming steering, avoiding frequent network changes. However, for stationary devices without user oversight, this can be a problem.

[0005] To address this issue, a signal level-enhanced network selection feature was introduced in 3GPP Release 18. This feature allows signal levels to be taken into account during the initial steps of network selection after switch-on or recovery from coverage loss, as well as during all steps of periodic cell reselection and PLMN selection.

[0006] The requirements for signal level augmentation network selection are defined in 3GPP TS 22.011[6], but no mechanism is defined in any 3GPP specification. For example, 3GPP TS 22.011[6] defines the requirements for the signal level extension network selection function as follows:

[0007] For UEs supporting NB-IoT, GERAN EC-GSM-IoT, and E-UTRA categories M1 or M2, or a combination thereof, the 5G system shall support a mechanism having operator-controlled signal thresholds for each access technology on the USIM to be used for network selection. The signal thresholds shall be specific to a particular access technology and shall apply to all PLMNs having the corresponding combination of access technologies.

[0008] There are many aspects that can be taken into consideration in order to comply with this requirement.

[0009] For example, there must be a mechanism that allows a home operator to securely transfer information for operator-controlled signal thresholds for each access technology to the USIM of an IoT device. If information for operator-controlled signal thresholds for each access technology becomes available in the VPLMN that the IoT UE is tuned to, the VPLMN may discard such information in order for the IoT UE to remain within that VPLMN. In this case, the intended VPLMN selection cannot be achieved. As a result, the IoT UE remains in that VPLMN and suffers from insufficient coverage.

[0010] For example, the structure of the information for operator-controlled signal thresholds is unclear. Many wireless parameters affect stable communication between the IoT UE and the network, such as signaling strength, signal quality, and interference level. 3GPP needs to define the structure of the information for operator-controlled signal thresholds. [Means for solving the problem]

[0011] Therefore, this disclosure seeks to provide methods and related apparatus for addressing or at least mitigating the above-mentioned problems (or at least some of them).

[0012] In one aspect, the disclosure relates to User Equipment (UE) including Mobile Termination (MT) and User Services Identity Module (USIM), A transmitter configured to send a registration request message to the Access and Mobility Management Function (AMF) when the signal threshold for each access technology is not set on the USIM or is not applied by the UE, A receiver configured to receive a registration acceptance message from the AMF containing information indicating the signal threshold for each access technology, We provide a user device equipped with the following features.

[0013] In one aspect, this disclosure is, A receiver configured to receive registration request messages from User Equipment (UE), A transmitter configured to send a registration acceptance message to a UE containing information indicating signal thresholds for each access technology, the information being received from Unified Data Management (UDM), and the transmitter and It provides an Access and Mobility Management Function (AMF) that includes the following features.

[0014] In one aspect, this disclosure is, A receiver configured to receive a first request message from the Access and Mobility Management Function (AMF), A transmitter configured to send a second request message to the Steering of Roaming Application Function (SoR-AF) Equipped with, The receiver receives a second response message from SoR-AF containing information indicating the signal threshold for each access technology. The transmitter sends a first response message to the AMF containing information indicating the signal threshold for each access technology. We provide Unified Data Management (UDM).

[0015] In one aspect, the present disclosure relates to a method in User Equipment (UE) including Mobile Termination (MT) and User Services Identity Module (USIM), If the signal threshold for each access technology is not set on the USIM or is not applied by the UE, a registration request message is sent to the Access and Mobility Management Function (AMF). AMF receives a registration acceptance message containing information specifying the signal threshold for each access technology. This provides a method for user devices.

[0016] In one aspect, the disclosure relates to a method in an Access and Mobility Management Function (AMF), A registration request message is received from the User Equipment (UE). A registration acceptance message is sent to the UE containing information specifying the signal threshold for each access technology, and this information is received from Unified Data Management (UDM). This provides a method for access and mobility management functions.

[0017] In one aspect, the disclosure is a method in Unified Data Management (UDM), The Access and Mobility Management Function (AMF) receives the first request message, A second request message is sent to the Steering Of Roaming Application Function (SoR-AF), Receive a second response message from SoR-AF that includes information indicating a signal threshold for each access technology, Transmit a first response message that includes information indicating a signal threshold for each access technology received from SoR-AF, Provide a method for integrated data management.

Advantages of the Invention

[0018] According to the present disclosure, methods for a UE, an AMF, and a UDM, a UE, an AMF, and a UDM are provided.

[0019] The foregoing and additional objects, features, and advantages of the present subject matter will become apparent from the following description of exemplary embodiments when read in conjunction with the accompanying drawings, in which like reference numerals are used to represent like elements.

[0020] However, it should be noted that the accompanying drawings with reference numerals illustrate only typical embodiments of the present subject matter and, therefore, should not be considered as limiting the scope of the present subject matter, which may admit of other equally effective embodiments.

Brief Description of the Drawings

[0021] [Figure 1] It is a signaling diagram of the first example of the first aspect. [Figure 2] It is a signaling diagram of the first example of the second aspect. [Figure 3] It is an existing PLMN selection diagram in 3GPP TS 23.122. [Figure 4] It is a process diagram in a UE of the second example of the second aspect. [Figure 5] It is a process diagram in a UE of the third example of the second aspect. [Figure 6] It is a diagram illustrating a system overview. [Figure 7] It is a block diagram illustrating a UE. [Figure 8] (R)AN node is a block diagram illustrating. [Figure 9] This diagram illustrates the system overview of an (R)AN node based on the O-RAN architecture. [Figure 10] This is a block diagram illustrating RU. [Figure 11] This is a block diagram illustrating DU. [Figure 12] This is a block diagram illustrating a CU (Combined Unit). [Figure 13] This is a block diagram illustrating AMF. [Figure 14] This is a block diagram illustrating a PCF (Picture Control Form). [Figure 15] This is a block diagram illustrating AUSF. [Figure 16] This is a block diagram illustrating UDM (User-Defined Design). [Figure 17] This is a block diagram illustrating NSSF. [Modes for carrying out the invention]

[0022] <abbreviation> For the purposes of this document, 3GPP TR 21.905[1] and the abbreviations listed below apply. Any abbreviation defined in this document takes precedence over the definition of the same abbreviation in 3GPP TR 21.905[1].

[0023] 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5G LAN 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 AF Application Function AMF Access and Mobility Management Function AMF-G Geographically Selected Access and Mobility Management Function AMF-NG Non-Geographically Selected Access and Mobility Management Function ANDSF Access Network Discovery and Selection Function ARFCN Absolute radio-frequency channel number AS Access Layer ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BCCH (Broadcast Control Channel) BMCA Best Master Clock Algorithm BSF Binding Support Function CAG (Closed Access Group) CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS (Dual Active Protocol Stacks) DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI (Episodic Biological Identity) EPS Bearer Identity (EPS Bearer Identification Information) EPS (Evolved Packet System) EUI (Extended Unique Identifier) FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG (Fixed Network Broadband RG) FN-CRG Fixed Network Cable RG (Fixed Network Cable RG) FN-RG Fixed Network 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) HPLMN Home Public Land Mobile Network HR Home Routed (roaming) IAB Integrated access and backhaul IMEI / TAC IMEI Type Allocation Code IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN (Local Area Data Network) LBO (Local Breakout / Roaming) LMF Location Management Function LoA (Level of Automation) LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume ME Mobile Equipment (Mobile Device) MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM Man In the Middle MNC Mobile Network Code MPS Multimedia Priority Service MPTCP (Multi-Path TCP Protocol) MT Mobile Termination N3IWF Non-3GPP InterWorking Function N3GPP Non-3GPP access N5CW Non-5G-Capable over WLAN (Non-5G compatible over WLAN) NAI (Network Access Identifier) NAS Non-Access-Stratum NEF Network Exposure Function (Network Exposure Function) NF Network Function NGAP (Next Generation Application Protocol) NID (Network Identifier) NPN Non-Public Network NR New Radio NSAG (Network Slice Access Stratum Group) 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 NSSRG (Network Slice Simultaneous Registration Group) NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PCO Protocol Configuration Options PDB Packet Delay Budget PDR Packet Detection Rule PDU (Protocol Data Unit) PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI - NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP (Precision Time Protocol) QFI QoS Flow Identifier QoE (Quality of Experience) RACS Radio Capabilities Signaling Optimization (R)AN (Radio) Access Network RAT Radio Access Technology RG Residential Gateway RIM (Remote Interference Management) RQA Reflective QoS Attribute RQI Reflective QoS Indication RSN Redundancy Sequence Number RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality SA NR Standalone New Radio SBA (Service-Based Architecture) SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SENSE Signal Level Enhanced Network Selection SEPP Security Edge Protection Proxy SIB System Information Block SINR (Signal-to-Interference Ratio plus Noise Ratio) SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN name Serving Network Name SNPN (Stand-alone Non-Public Network) S-NSSAI Single Network Slice Selection Assistance Information SOR Steering Of Roaming SSC (Session and Service Continuity) SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI (Subscription Concealed Identifier) SUPI Subscription Permanent Identifier (International Mobile Subscriber Identifier) SV Software Version TMSI (Temporary Mobile Subscriber Identity) TNAN Trusted Non-3GPP Access Network TNAP: Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL (Transport Network Layer) TNLA (Transport Network Layer Association) TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator (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 UPF User Plane Function UPSI UE Policy Section Identifier URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF (AMF's UE Reachability Request Parameter) URSP UE Route Selection Policy USIM (User Services Identity Module) VID VLAN Identifier VLAN (Virtual Local Area Network) VPLMN (Visited Public Land Mobile Network) W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0024] <Definition> For the purposes of this document, the terms and definitions set forth in 3GPP TR 21.905[1] and below shall apply. Terms defined in this document shall take precedence over the definitions in 3GPP TR 21.905[1] for the same terms. [Prior art documents] [Non-patent literature]

[0025] [Non-Patent Document 1] 3GPP TR 21.905:“Vocabulary for 3GPP Specifications”.V17.1.0(2021-12)

Non-licensed Document 2

Non-licensed Document 4

Non-licensed Document 5

Non-licensed Document 6

Non-licensed Document 7

Non-licensed Document 8

[0026] <General> Those skilled in the art will understand that elements in the drawings are illustrative for simplification and may not necessarily be drawn to scale. Furthermore, with respect to the configuration of the apparatus, one or more components of the apparatus may be represented in the drawings by conventional symbols, and the drawings may show only certain details relating to the understanding of aspects of this disclosure so as not to obscure the drawings with details that would be readily apparent to those skilled in the art who benefit from the description herein. For the purpose of facilitating the understanding of the principles of this disclosure, embodiments illustrated in the drawings are used herein by reference and described using specific terminology. However, it should be understood that this is not intended to limit the scope of this disclosure. Such modifications and further alterations to the illustrated systems, as well as such further applications of the principles of this disclosure that would ordinarily come to mind for those skilled in the art, should be construed as being within the scope of this disclosure.

[0027] The terms “comprises,” “comprising,” or any other variation thereof are intended to encompass non-exclusive inclusions such that a process or method containing a list of steps may include other steps not explicitly enumerated or that are specific to such process or method, rather than including only those steps. Similarly, one or more devices or entities or subsystems or elements or structures or components preceded by “~contains” does not, without further constraint, exclude the existence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, occurrences of the words “in another aspect,” “in another aspect,” and similar wording may, but not necessarily, all refer to the same aspect.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art in which this disclosure pertains. The systems, methods, and examples provided herein are illustrative and not intended to limit the scope of this disclosure.

[0029] In the following specification and claims, certain terms may be defined as having the following meanings: The singular forms “a,” “an,” and “the” include plural references unless the context clearly indicates otherwise. Where used herein, data is meaningful information and represents values ​​resulting from parameters; therefore, information is associated with data and knowledge. Further knowledge represents an understanding of abstract or concrete concepts. This exemplary system is simplified for the sake of illustrating the subject matter being disclosed and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used in addition to, or instead of, the system to implement the embodiments disclosed herein, and all such embodiments are considered to be within the scope of this disclosure.

[0030] Furthermore, each of the embodiments and elements contained in each embodiment described below may be implemented independently or in combination with any of the others. These embodiments include novel features that are different from each other. Therefore, these embodiments contribute to achieving different objectives or solving different problems and to obtaining different advantages.

[0031] An exemplary object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problems.

[0032] <First aspect> This embodiment discloses a mechanism that enables the secure transfer of information for operator-controlled signal thresholds for each access technology from the home operator to the USIM35 installed on the UE3 while the UE3 is roaming on the VPLMN.

[0033] <First example of the first aspect> If information for operator-controlled signal thresholds for each access technology is not provided to UE3, UE3 will initiate a registration procedure to fetch the information from HPLMN using 5GS.

[0034] Figure 1 shows the registration procedure for obtaining operator control signal thresholds for each access technology from a home network.

[0035] Referring to Figure 1, the detailed process of the first example of the first embodiment is described below. Note that MT33 in Figure 1 indicates the mobile terminal of UE3. MT33 may be UE3 excluding USIM35.

[0036] Step 0. The SoR AF201 stores information for signal thresholds for each access technology to subscriber data.

[0037] The SoR AF201 can store signal thresholds for NB-IoT, GERAN EC-GSM-IoT, E-UTRA Category M1, E-UTRA Category M2, and other access technologies. The SoR AF201 can also store signal thresholds for WiFi as a non-3GPP access.

[0038] Step 1. When MT33 in UE3 detects that operator-controlled signal threshold information for each access technology is not provided to USIM35 or is not in the non-volatile memory within UE3, UE3 sends a registration request message to AMF70 including the user ID, SENSE function support, and UE-supported access technology. The SENSE (Signal Level Enhanced Network Selection) function support parameter, or any other notation for a parameter intended to indicate that the UE supports the operator-controlled signal threshold function for each access technology, indicates that UE3 supports the SENSE function. The UE-supported access technology parameter sent from the UE indicates one or more access technologies that UE3 supports. UE support access technologies may include indications that they support NB-IoT, GERAN EC-GSM-IoT, E-UTRA Category M1, E-UTRA Category M2, and other access technologies (e.g., NR). For example, if the UE is configured from manual PLMN mode selection to automatic PLMN mode selection and finds that operator-controlled signal thresholds for each access technology are not configured, the UE also initiates the registration procedure defined in this step.

[0039] The SENSE function support can be named by another name, such as SENSE information query, SENSE request, or any other name that instructs UE3 to request that AMF70 have SENSE-related information. UE-supported access technologies can have a different name. For example, "Access Technology," or any other name that indicates one or more access technologies supported by UE3.

[0040] Step 2. When AMF70 receives a registration request message, AMF70 sends a Nudm_UECM_Registration request message to UDM75 that includes the user ID, SENSE feature support, UE support access technology, and SoR for SENSE support. SENSE feature support parameters and UE support access technology received in Step 1. If AMF70 does not receive SENSE feature support instructions from UE3, AMF70 recognizes that UE3 does not support SENSE features, and AMF70 does not include SENSE features or UE support access technology in the Nudm_UECM_Registration request message. The SoR for SENSE support indicates that AMF70 has the ability to transfer SENSE-related information to UE3 using the SoR mechanism.

[0041] The SENSE function support can be named by another name, such as SENSE information query, SENSE request, or any other name that instructs AMF70 to request UDM75 to have SENSE-related information. UE-supported access technologies can have a different name. For example, "Access Technology," or any other name that indicates one or more access technologies supported by UE3. SoR for SENSE can be another name that indicates the AMF70 has the ability to transfer SENSE-related information to UE3 using the SoR mechanism.

[0042] Step 3. When UDM75 receives a Nudm_UECM_Registration request message containing the user ID, SENSE feature support, UE support access technology, and SoR for SENSE support, UDM75 sends an Nsoraf_SoR_Get request message (or a new message or any existing message) containing the user ID and SENSE feature support instruction and UE support access technology received in Step 2. SENSE feature support may have a different name, for example, SENSE information query, SENSE request, or any other name that instructs UDM75 to request that SoR AF201 have SENSE-related information. If UDM75 does not receive a SENSE function support instruction from AMF70, UDM75 assumes that UE3 does not support the SENSE function and does not send an Nsoraf_SoR_Get request message to SoR-AF201. If UDM75 does not receive an SoR for SENSE support from AMF70, UDM75 assumes that AMF70 does not support the SENSE function and does not send an Nsoraf_SoR_Get request message to SoR-AF201. For example, SENSE feature support is UDM 75 Therefore, AMF can be interpreted as supporting SOR functionality. In this case, UDM 75 is UDM 75 Even if AMF70 does not receive a SoR for SENSE support, it will send an Nsoraf_SoR_Get request message (new or existing message) to SoR-AF201.

[0043] UE-supported access technologies can have a different name. For example, "Access Technology," or any other name that indicates one or more access technologies supported by UE3.

[0044] Step 4. Upon receiving an Nsoraf_SoR_Get request message containing the user ID (e.g., SUPI or GPSI) and SENSE function support and UE support access technology, SoR AF201 retrieves information for the signal threshold for each access technology from the subscriber data record (e.g., memory) of the subscriber identified by the user ID. SoR-AF201 then sends an Nsoraf_SoR_Get response message (e.g., new message or existing message) to UDM75 containing information for the signal threshold for each access technology of UE3.

[0045] Step 5. When UDM75 receives a Nsoraf_SoR_Get response message from SoR-AF201 containing information for the signal thresholds for each access technology of UE3, UDM75 sends a Nausf_SoRProtection request message (new or existing message) to AUSF74 containing information for the signal thresholds for each access technology in order to protect this information. UDM75 may include an ACK instruction in the Nausf_SoRProtection request message to receive instructions from UE3 when the SoR container has been successfully delivered to UE3.

[0046] Step 6. AUSF74 contains information for signal thresholds for each access technology from UDM75. N Upon receiving an ausf_SoRProtection request message, AUSF74 encrypts this information and sends a Nausf_SoRProtection response message to UDM75 containing an SoR container that includes encrypted information for signal thresholds for each access technology.

[0047] Step 7. When UDM75 receives a Nausf_SoRProtection response message from AUSF74 that includes an SoR container containing encryption information for signal thresholds for each access technology, UDM75 sends a Nudm_UECM_Registration response message to AMF70 that includes an SoR container containing encryption information for signal thresholds for each access technology. UDM75 may include an ACK instruction in the Nudm_UECM_Registration response message.

[0048] The SOR container is defined as follows: [Table 1]

[0049] A secure packet is defined as follows: [Table 2]

[0050] Step 8. When AMF70 receives a Nudm_UECM_Registration response message containing an SoR container with encryption information for signal thresholds for each access technology, AMF70 sends a registration acceptance message to UE3 containing an SoR container with encryption information for signal thresholds for each access technology. AMF70 may include an ACK instruction in the registration acceptance message.

[0051] Step 9. When MT33 in UE3 receives a registration acceptance message from AMF70 containing an SoR transparent container with encrypted information for signal thresholds for each access technology, MT33 decrypts the SoR transparent container to obtain the information for signal thresholds for each access technology. MT33 either sends the information to USIM35 or stores the information in the non-volatile memory of UE3. After MT33 decodes the information for each access technology signal threshold from the SoR transparent container, the NAS layer of UE3 notifies the AS layer of UE3 of the signal threshold information for each access technology. For example, the information for each access technology signal threshold may consist of a list of measured signal strength (e.g., RSRP), measured signal quality (e.g., RSRQ), and measured signal-to-noise interference (e.g., SINR) for each access technology.

[0052] If MT33 receives an invalid value for the access technology, UE3 ignores the value, does not store it in USIM35, and does not apply the threshold.

[0053] In one example, the UDM75 sends a fixed value, for example, 0, for each access technology to disable the cell selection or reselection procedure based on a signal threshold for each access technology. When the UE3 receives this value, it does not apply the cell selection or reselection procedure for the access technology.

[0054] Step 10. If UE3 is requested to confirm the successful delivery of information for each access technology signal threshold, UE3 sends a registration complete message to AMF70.

[0055] Step 11. When AMF70 receives a registration completion message from UE3 and is requested by UDM75 to confirm the successful delivery of information for each access technology signal threshold to UE3, AMF70 sends a Nudm_SDM_Info message to UDM75 so that UDM75 can recognize the successful delivery of information for each access technology signal threshold to UE3.

[0056] In this disclosure, the operator-controlled signal thresholds for each access technology may also be expressed using other terms, such as signal thresholds for each access technology, signal quality thresholds for each access technology, or thresholds for each access technology. In this disclosure, user identification information may also be referred to as User ID or UE ID.

[0057] <Modification 1 of the first example of the first aspect> For example, SoR AF201 is This can be included in UDM75. In this case, steps 3 and 4 are performed inside UDM75.

[0058] <Modification 2 of the first example of the first embodiment> In one example, UE3 scans for available PLMNs at its location and, in a registration request message, sends a list of the signal strength or signal quality or both (for example, RSRP (Reference Signal Received Power) and RSRQ (Reference Signal Received Quality) RSSI in EPS) of the strongest cells of each available PLMN at that location. In step 2, AMF70 sends the list of signal strength or signal quality or both to UDM75. UDM75 sends the received list of signal strength or signal quality or both to SoR-AF201. SoR-AF201 determines the signal strength of each access technology based on the received list of signal strength or signal quality or both. For example, a list of signal strength or signal quality is either integrity-protected or encrypted and sent to the UDM75 in a transparent container.

[0059] <Modification 3 of the first example of the first embodiment> In another example, operator-controlled signal threshold information for each access technology may be configured in the AMF70 directly or via OAM based on the operator policy. In this case, while the UE3 is registering with the home PLMN, the operator-controlled signal threshold information for each access technology can be delivered to the UE3 by the AMF70 as shown in steps 8 and 9 of Figure 1. Alternatively, the configured operator-controlled signal threshold information for each access technology within the AMF70 can be delivered to the UE3 via a UE configuration update message while the UE3 is connected to the home PLMN, or whenever the UE3 is in idle mode by first paging the UE3.

[0060] <Modification 4 of the first example of the first embodiment> In another example, operator-controlled signal threshold information for each access technology may be defined as a new rule to trigger cell selection / reselection or PLMN selection / reselection by the UE3 as part of the URSP rules for the UE3 within the PCF, and may be provided to the UE3 within URSP provisioning in the UE policy information via the UE configuration update procedure in accordance with 3GPP TS 23.502[4] and 3GPP TS 23.503[5].

[0061] <Modification 5 of the first example of the first embodiment> In another example, operator-controlled signal threshold information for each access technology may be provided to the UE3 by the AMF70 via OTA (Over The Air) DM (Device Management). In another example, UDM75 can transmit operator-controlled signal threshold information for each access technology in any existing or new message defined between UDM75 and AMF70. When AMF70 receives the operator-controlled signal threshold information for each access technology, AMF70 transmits the received operator-controlled signal threshold information for each access technology to UE3 in an existing or new NAS message. When UE3 receives the operator-controlled signal threshold information for each access technology, UE3 transmits an existing NAS message to AMF instructing it to receive the operator-controlled signal threshold information for each access technology. When AMF70 receives the NAS message from UE3, it transmits a message to UDM75 instructing UE3 to receive the operator-controlled signal threshold information for each access technology. This method of transmitting operator-controlled signal threshold information for each access technology can be used when UE3 is an HPLMN or an equivalent register within an HPLMN.

[0062] <Modification 6 of the first example of the first aspect> In another example, operator-controlled signal thresholds for each access technology may be defined by the service provider (for example, if a mobile terminal belongs to a third-party service provider that has contracted with the PLMN that controls the signal thresholds). In this case, information on operator-controlled signal thresholds for each access technology is provided by the service provider to the UDM75 of the 3GPP network via the NEF entity of the 3GPP network. Along with providing the operator-controlled signal thresholds for each access technology, the service provider may also provide additional information regarding the validity of the provided thresholds or their applicability per UE or per group of UEs, and the service provider may update the operator-controlled signal thresholds for each access technology and the conditions for their applicability at any time.

[0063] <Modification 7 of the first example of the first aspect> In one example, the AS layer of UE3 provides the operator-controlled signal threshold for each access technology to the NG-RAN in an existing or new RRC message. When the NG-RAN receives the operator-controlled signal threshold for each access technology from the AS layer of UE3, it stores it and selects a target cell in the handover procedure if the signal strength of the target cell is equal to or greater than the operator-controlled signal threshold for each access technology.

[0064] <Modification 8 of the first example of the first embodiment> In one example, the AMF70 provides the NG-RAN with operator-controlled signal thresholds for each access technology in an existing or new NGAP message. When the NG-RAN receives the operator-controlled signal thresholds for each access technology, it stores them and selects a target cell in the handover procedure if the signal strength of the target cell is equal to or greater than the operator-controlled signal threshold for each access technology.

[0065] <Modification 9 of the first example of the first aspect> UE3 transparently and securely transmits to UDM75 via AMF70, at any time during, for example, the power-on procedure or any NAS procedure, a list of signal strengths per access technology type and / or a list of signal strengths per PLMN and / or a list of all signal strengths for the best cell of each available access technology for each available PLMN and the current UE location, which UE3 can receive. For example, UE3 transmits the list of signal strengths to AMF70 by a registration request message or registration completion message, or by any NAS message. AMF70 then transmits the received list of signal strengths to UDM75 in an existing or new message defined between AMF70 and UDM75. Upon receiving the list of signal strengths, UDM75 may decide to update the operator-controlled signal thresholds for each access technology based on the signal strength values ​​in the received list and the received current UE location. For example, if the received signal strength of a particular access technique at the location of UE3 is much lower than the operator-controlled signal threshold for that access technique in UDM75, UDM75 reduces the operator-controlled signal threshold for that access technique and updates the newly defined threshold in UE3 using the mechanism disclosed in the first embodiment.

[0066] <Modification 10 of the first example of the first embodiment> UE3 transmits the current value of a stored threshold to UDM via AMF at any time, for example, during the power-on procedure or any NAS procedure. The current value of a stored threshold can be transmitted transparently and securely to UDM75 via AMF70. If UE3 has a stored threshold value that is not stored in UE3's USIM35 or ME memory, UE3 instructs UDM75 that UE3 does not have an operator-specific threshold value. The UDM75 may decide to send operator-controlled signal thresholds for each access technology to the UE3 based on the current value of a stored threshold in the UE3 or instructions from the UE3. For example, if the current value of a stored threshold in the received UE3 is outdated, the UDM75 updates the UE3 with the most recent operator-controlled signal threshold of the access technology using the mechanism disclosed in the first aspect.

[0067] <Modification 11 of the first example of the first embodiment> In steps 2 through 7, AMF70 and UDM75 may use existing or new messages between AMF70 and UDM75.

[0068] <Second aspect> This embodiment discloses how UE3 acquires information for operator-controlled signal thresholds for each access technology via 5GS, and how UE3 uses this information for categories M1 or M2 of NB-IoT, GERAN EC-GSM-IoT, and E-UTRA.

[0069] <First example of the second aspect> A first example of the second embodiment discloses how UE3 obtains information for operator-controlled signal thresholds for each access technology via 5GS, and how UE3 uses this information for categories M1 or M2 of NB-IoT, GERAN EC-GSM-IoT, and E-UTRA.

[0070] Figure 2 shows the UE operation for the SENSE function. Referring to Figure 2, the detailed process of the first example of the second embodiment is described below. Note that MT33 in Figure 2 indicates the mobile terminal of UE3. MT33 may be UE3 excluding USIM35.

[0071] Step 1. UE3 is switched on. Another use case for Step 1 could be when a new SIM35 is inserted into UE3, when UE3 is initialized by the user, or any other case for resetting UE3. Another use case for Step 1 could be recovery from coverage loss, periodic network selection trials, and roaming steering.

[0072] Step 2. MT33 queries USIM35 to see if it holds information for signal thresholds for each access technology. MT33 may specify the access technology in the query message to obtain the signal threshold for that access technology. Access technologies include NB-IoT, GERAN EC-GSM-IoT, E-UTRA Category M1, E-UTRA Category M2, and other access technologies. Access technologies also include WiFi as a non-3GPP access. If the information for the signal thresholds for each access technology is stored in the non-volatile memory within UE3, MT33 does not query USIM35. UE3 refers to that memory and proceeds to step 4.

[0073] Step 3. When USIM35 receives the query message in Step 1, if USIM35 has information for the signal thresholds for each access technology, USIM35 provides the information for the signal thresholds for each access technology to MT33. Otherwise, USIM35 simply sends a negation message to MT33 or provides empty information for the signal thresholds for each access technology.

[0074] Step 4. The following conditions are checked by UE3. If all conditions are met, UE3 proceeds to Step 5. UE3 has the capability to handle SENSE functions. UE3 does not retain information for signal thresholds for each access technology. The UE3 has the ability to access 5GS; in other words, the UE3 supports 5G NAS. The UE3 has the ability to connect to NR or e-URAN, or any other RAT that can connect to 5GC (e.g., WLAN, Wi-Fi, BBF access, cable access, optical access).

[0075] Step 5. Based on the inspection performed in Step 4, UE3 initiates the registration procedure as disclosed in the first example of the first embodiment. For example, if a cell supporting UTRAN, E-UTRAN, GERAN, or NR exists at the current location, UE3 will select a cell that supports 5GS, even if the selected cell is not the best cell available at that location, or if the selected cell does not belong to the last registered PLMN, or belongs to a PLMN that is not a more preferable PLMN available at that location, and will initiate the registration procedure for the selected cell in the PLMN to register it in 5GS.

[0076] For example, suppose PLMN1, PLMN2, and PLMN3 are stored in the operator-priority PLMN list in order of highest to lowest priority, i.e., PLMN1 > PLMN2 > PLMN3. If, at the current location, there is an E-UTRAN cell 1 belonging to PLMN1 that does not support connection to 5GS, and there is a cell 2 belonging to PLMN2's NG-RAN, UE3 will select cell 2 of PLMN2 and start the registration procedure to PLMN2 on cell 2.

[0077] Step 6. Once the registration procedure in Step 5 is successfully completed, the UE3 will move GSM-based GPRS, W-CDMA-based GPRS, or EPS to access using access technologies such as NB-IoT, GERAN EC-GSM-IoT, and E-UTRA Category M1 or M2.

[0078] Step 7. UE3 initiates PLMN selection based on the received information from Step 5 for the signal threshold of the access technology that UE3 is currently matching.

[0079] In this disclosure, the operator-controlled signal thresholds for each access technology may also be expressed using other terms, such as signal thresholds for each access technology, signal quality thresholds for each access technology, or thresholds for each access technology. In this disclosure, user identification information may also be referred to as User ID or UE ID.

[0080] <Second example of the second aspect> A second example of the second embodiment discloses how UE3 uses a signal threshold for PLMN selection. This example can be used in step 7 of the first example of the second embodiment.

[0081] Figure 3 illustrates an existing PLMN selection diagram from 3GPP TS 23.122[8]. This example discloses the following updates to the process in Figure 3.

[0082] <First disclosure to update the process "Select registered PLMN"> Figure 4 shows a signaling measurement based on a signal threshold. The process in the upper left of Figure 3, "Select registered PLMN," is replaced by the process shown in Figure 4, which has the following process flow.

[0083] Process 4001.UE3 checks whether UE3 holds signal threshold information for the access technology it is tuned to. If UE3 holds signal threshold information for the access technology, UE3 does not first look for the last registered PLMN availability at that location after switch-on or recovery from a no-service state, as in the legacy operation in Figure 3. Instead, UE3 proceeds to process 4002. Otherwise, UE3 returns and follows the original procedure in Figure 3.

[0084] Process 4002.UE3 retrieves operator-controlled signal threshold information for each access technology stored in USIM35 or non-volatile memory within UE3 for the UE's radio access (i.e., the radio access to which the UE is tuned), and UE3 retrieves signal strength or signal quality or signal-to-noise interference measurements (e.g., RSRP (Reference Signal Received Power) or RSRQ (Reference Signal Received Quality) or SINR (Signal to Interference plus Noise Ratio)) for all cells of the UE's radio access at the UE location.

[0085] Process 4003. If the measured signal strength (e.g., RSRP), measured signal quality (e.g., RSRQ), or measured signal-to-noise interference (e.g., SINR) of one of the available cells from any PLMN that UE3 is permitted to select at the same UE location on the radio access is greater than or equal to the operator-controlled signal threshold of the access technology, UE3 shall select a cell from that PLMN (i.e., UE3 shall select the cell that has the highest signal strength, highest signal quality, highest signal-to-noise ratio, or combination of the three, belonging to any of the PLMNs that UE3 is permitted to select), and UE3 shall continue the PLMN selection process from point C in the PLMN selection diagram of Figure 3. Otherwise, UE3 shall return to the beginning of the PLMN selection diagram of Figure 3, i.e., begin PLMN selection without considering the operator-controlled signal threshold information for each access technology.

[0086] <Second disclosure to update the process "Select PLMN"> For the processes immediately following connection circle A and connection circle B in Figure 3, these processes are replaced by processes as shown in Figure 4, which have the following process flow.

[0087] Process 4001.UE3 checks whether UE3 holds signal threshold information for the access technology it is tuned to. If UE3 holds signal threshold information for the access technology, process 4001.UE3 checks whether UE3 holds signal threshold information for the access technology. 4002 Proceed. Otherwise, return to the previous process.

[0088] Process 4002.UE3 obtains the threshold of the tuned access technology and measures the signal.

[0089] Process 4003. If the measured signal quality is equal to or greater than the operator-controlled signal threshold of the access technology, return to the original process. Otherwise, skip the original process and proceed to the next process, as indicated by "PLMN Trial". In this case, the "PLMN Trial" process does not start the registration procedure. The "PLMN Bundling" process simply determines whether the next PLMN is in the list, that is, proceed to either the middle line below the "PLMN Trial" process or the right line below the "PLMN Trial" process.

[0090] <Third disclosure to update the process "Select the first available and acceptable PLMN in the list"> Regarding the process located at the bottom of Figure 3, "Select the first available and acceptable PLMN in the list," this process is replaced by the process shown in Figure 4, which has the following process flow.

[0091] Process 4001.UE3 checks whether UE3 holds signal threshold information for the access technology it is tuned to. If UE3 holds the signal threshold information for the access technology, proceed to process 3002. Otherwise, return to the previous process.

[0092] Process 4002.UE3 obtains the threshold of the tuned access technology and measures the signal.

[0093] Process 4003. If the measured signal quality is above the operator-controlled signal threshold of the access technology, return to the original process. Otherwise, proceed to the middle line below the "On PLMN" process.

[0094] <Modification 1 of the second example of the second embodiment> In another example, operator-controlled signal threshold information for each access technology can be considered an offset value; that is, UE3 will select a cell from another PLMN only if the difference in signal strength (e.g., RSRP), signal quality (e.g., RSRQ), or signal-to-noise ratio between the current cell in the home PLMN and a cell from another PLMN is greater than or equal to the operator-controlled signal threshold for each access technology that is favorable to the cell from the other PLMN. In this case, UE3 will select the cell from the other PLMN and register it with the other PLMN.

[0095] <Third example of the second aspect> A third example of the second embodiment discloses how UE3 determines a measurement signal using a signal threshold for PLMN selection. This example is a second example of the second embodiment. Process 4 It can be used in 003.

[0096] Figure 5 illustrates the flow of how UE3 interprets the measurement signal.

[0097] Process 5001.UE3 measures the signal via access technology.

[0098] Process 5002.UE3 compares the received signal level to the RSRP as indicated by the operator-controlled signal threshold of the access technology. If the received signal level is greater than or equal to the operator-controlled signal threshold, proceed to process 5003. Otherwise, proceed to process 5006 and conclude that the SENSE-based signaling check failed.

[0099] Process 5003.UE3 compares the received signal quality to the RSRQ as indicated by the operator-controlled signal threshold of the access technology. If the measured signal quality is equal to or greater than the operator-controlled signal threshold, proceed to process 5004. Otherwise, proceed to process 5006 and conclude that the SENSE-based signaling check has failed.

[0100] Process 5004.UE3 compares the received signal-to-interference noise ratio (SINR) to the SINR as indicated by the operator-controlled signal threshold of the access technology. If the measured signal-to-interference noise ratio is greater than or equal to the operator-controlled signal threshold, the process proceeds to process 5005, where the SENSE-based signaling check is passed and concluded to be successful. Otherwise, the process proceeds to process 5006, where the SENSE-based signaling check is concluded to have failed.

[0101] <Modification 1 of the third example of the second embodiment> In another example, the operator-controlled signal thresholds for each access technology may be applicable only to the difference in signal intensity between cells, or only to the difference in signal quality between cells, or only to the difference in signal-to-noise ratio between cells, or to any combination of these three operator-controlled signal thresholds for each access technology. Depending on the applicability of the operator-controlled signal thresholds for each access technology, the UE3 may compare a home PLMN cell with a cell from another PLMN against the difference in signal intensity, or only to the difference in signal quality, or against the difference in signal-to-noise ratio, or against any other combination of these three types of thresholds, or against all three as shown in Figure 5.

[0102] <System Overview> Figure 6 schematically illustrates a mobile (cellular or wireless) telecommunications system 1 to which the above embodiment can be applied. Telecommunication system 1 represents a system overview capable of end-to-end communication. For example, UE3 (or user device, "mobile device", 3) communicates with other UE3 or service servers in the data network 20 via their respective (R)AN nodes 5 and core network 7. (R)AN Node 5 supports any radio access, including non-3GPP RATs, such as 5G Radio Access Technology (RAT), E-UTRA Radio Access Technology, Beyond 5G RAT, 6G RAT, and Wireless Local Area Network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE). (R)AN node 5 may be divided into Radio Units (RUs), Distributed Units (DUs), and Centralized Units (CUs). In some embodiments, each of the units may be connected to one another and the (R)AN node 5 may be constructed by adopting an architecture defined by the Open RAN (O-RAN) Alliance, and these units may be called O-RUs, O-DUs, and O-CUs, respectively. (R)AN node 5 can be divided into control plane functions and user plane functions. Furthermore, multiple user plane functions can be assigned to support communication. In some embodiments, user traffic may be distributed across multiple user plane functions, and user traffic through each user plane function is aggregated at both UE3 and (R)AN node 5. This divided architecture is sometimes referred to as "dual connectivity" or "multi-connectivity". (R)AN node 5 may also support communications using satellite access. In some embodiments, (R)AN node 5 may support both satellite and ground access. Furthermore, (R)AN node 5 can also be referred to as an access node for non-wireless access. Non-wireless access includes fixed-line access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0103] 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 can be considered a network function. Network functions can be provided to other nodes by adapting a service-based architecture (SBA). Network functions can be deployed as a distributed, redundant, stateless, and scalable system, providing services from several locations and several execution instances at each location, by adapting network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV). Core network 7 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0104] As is well known, UE3 can enter and exit areas (i.e., radio cells) served by (R)AN nodes 5 when UE3 is moving within a geographic area covered by telecommunications system 1. To track UE3 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 (R)AN nodes 5 coupled to the core network 7. In some core networks, instead of the AMF 70, a Mobility Management Entity (MME) or Mobility Management Node may be used for Beyond 5G, or a Mobility Management Node for 6G.

[0105] 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, an Authentication Server Function (AUSF) 74, a Unified Data Management (UDM) 75, and a Network Slice Selection Function (NSSF) 76. When UE3 is roaming to a Visited Public Land Mobile Network (VPLMN), UE3's Home Public Land Mobile Network (HPLMN) provides the roaming UE3 with the UDM 75 and at least some of the functions of SMF 71, UPF 72, and PCF 73.

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

[0107] The "Uu" interface may include the control plane of the Uu interface and the user plane of the Uu interface. The user plane of the Uu interface is responsible for transmitting user traffic between UE3 and Serving(R)AN node 5. The user plane of the Uu interface may have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers via physical connections. The Uu interface control plane is responsible for establishing, changing, and releasing connections between UE3 and Serving(R)AN node 5. The Uu interface control plane may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers via physical connections. For example, the following message is communicated via the RRC layer to support AS signaling.

[0108] RRC setup request message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be included together in the RRC setup request message. establishmentCause and ue-Identity. ue-Identity may have the value of ng-5G-S-TMSI-Part1 or randomValue.

[0109] RRC Setup Message: This message is sent from (R)AN node 5 to UE3. In addition to the parameters disclosed in this embodiment, the following parameters may be included in the RRC setup message. masterCellGroup and radioBearerConfig.

[0110] RRC setup complete message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be included in the RRC setup complete message. guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0111] The UE3 and AMF70 are connected via an appropriate interface (e.g., the so-called N1 interface). The N1 interface is responsible for providing communication between the UE3 and AMF70 to support NAS signaling. The N1 interface can be established via 3GPP access and non-3GPP access. For example, the following messages are communicated via the N1 interface.

[0112] Registration Request Message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the registration request message. 5GS registration type, ngKSI, 5GS mobile identification information, non-current native NAS keyset identifier, 5GMM capability, UE security capability, requested NSSAI, last visited destination registration TAI, S1 UE network capability, uplink data status, PDU session status, MICO instruction, UE status, additional GUTI, allowed PDU session status, UE usage settings, requested DRX parameters, EPS NAS message container, LADN instruction, payload container type, payload container, network slicing instruction, 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 instruction, and requested NB-N1 mode DRX parameters.

[0113] Registration Acceptance Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the registration acceptance message. 5GS registration results, 5G-GUTI, equivalent PLMN, TAI list, accepted NSSAI, rejected NSSAI, configured NSSAI, 5GS network function support, PDU session status, PDU session reactivation results, PDU session reactivation result error cause, LADN information, MICO instructions, network slicing instructions, 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 deletion instruction, pending NSSAI, encryption key data, CAG information list, terminated 5G-S-TMSI configuration, negotiated WUS support information, negotiated NB-N1 mode DRX parameters, and extended denied NSSAI.

[0114] Registration complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the registration complete message. SOR transparent container.

[0115] Authentication request message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be included in the authentication request message. ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge), and EAP message.

[0116] Authentication response message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the authentication response message. Authentication response message identification information, authentication response parameters, and EAP message.

[0117] Authentication result message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the authentication result message. ngKSI, EAP messages, and ABBA.

[0118] Authentication failure message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the authentication failure message. Authentication failure message identifier, 5GMM cause, and authentication failure parameters.

[0119] Authentication denial message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the authentication denial message. EAP message.

[0120] Service request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the service request message. ngKSI, service type, 5G-S-TMSI, uplink data status, PDU session status, allowed PDU session status, NAS message container.

[0121] Service Acceptance Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the service acceptance message. PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0122] Denial of Service Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the denial of service message. 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0123] Configuration update command message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the configuration update command message. Configuration update instructions, 5G-GUTI, TAI list, allowed NSSAI, service area list, network full name, network short name, local time zone, UTC and local time zone, network daylight saving time, LADN information, MICO instructions, network slicing instructions, configured NSSAI, denied NSSAI, operator-defined access category definitions, SMS instructions, T3447 values, CAG information list, UE radio capability ID, UE radio capability ID deletion instructions, 5GS registration results, terminated 5G-S-TMSI configuration, additional configuration instructions, and extended denied NSSAI.

[0124] Configuration update complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the configuration update complete message. Configuration update complete message identification information.

[0125] <User Equipment (UE)> Figure 7 is a block diagram illustrating the main components of UE3 (Mobile Device 3). As shown, UE3 includes a transceiver circuit 31 capable of transmitting signals to (one or more) connected nodes via one or more antennas 32 and receiving signals from (one or more) connected nodes. Furthermore, UE3 may include a user interface 34 for inputting information from or outputting information to the outside. Although not necessarily shown in the figure, UE3 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, for example, via a telecommunications network or from a removable data storage device (RMD). The control unit 33 controls the operation of UE3 according to the software stored in 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 communication control module 362 (using its transceiver control module 3621) is responsible for processing (generating / transmitting / receiving) signaling and uplink / downlink data packets between the UE3 and other nodes such as the (R)AN node 5 and AMF70. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE3). The control unit 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. If multiple USIMs 35 are installed, the control unit 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0126] UE3 may support, for example, a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). UE3 may be, for example, equipment for production or manufacturing and / or energy-related machinery (e.g., boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power plants; 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 their application systems; tools; molds or dies; rolls; conveying equipment; lifting equipment; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; paperwork machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or equipment 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 aforementioned equipment or machinery).

[0127] UE3 can be, for example, a transportation equipment item (e.g., transportation equipment such as railway cars; automobiles; motorcycles; bicycles; trains; buses; carts; rickshaws; ships and other vessels; aircraft; rockets; satellites; drones; balloons, etc.). UE3 may also be an information and communication equipment item (for example, electronic computers and related equipment; communication and related equipment; electronic components, etc.). UE3 may include, for example, refrigerators, refrigerator applications, merchandise and / or service industry equipment items, vending machines, automated service machines, office equipment, consumer electronics and electronic devices (e.g., consumer electrical appliances such as audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related devices; vacuum cleaners, etc.).

[0128] UE3 may be, for example, an electrical application system or device (e.g., X-ray systems; particle accelerators; radioisotope equipment; sound wave equipment; electromagnetic application equipment; power application equipment, etc., or other power application systems or devices). UE3 may include, for example, electronic lamps, lighting fixtures, measuring instruments, analyzers, testers, or surveying or sensing equipment (e.g., smoke detectors; motion sensors; wireless tags, etc.), wristwatches or clocks, inspection equipment, optical devices, medical equipment and / or systems, weapons, cutlery products, hand tools, etc. UE3 may be, for example, a wireless-equipped personal digital assistant or related device (such as a wireless card or module designed to be attached to or inserted into another electronic device, e.g., a personal computer, an electrical measuring instrument).

[0129] UE3 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 with respect to the Internet of Things (IoT).

[0130] Internet of Things (IoT) devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, etc., that enable them to collect and exchange data with each other and with other communication devices. IoT devices may include automated devices that follow software instructions stored in internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices may also remain stationary and / or inactive for extended periods. IoT devices may be implemented as part of (generally) stationary devices. IoT devices may also be incorporated into non-stationary devices (e.g., vehicles) or attached to animals or people to be monitored / tracked.

[0131] It will be understood that IoT technology can be implemented on any communication device that can connect to a communication network to send / receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory. It should be understood that IoT devices are sometimes called Machine-Type Communication (MTC) devices, Machine-to-Machine (M2M) communication devices, or Narrow Band IoT UEs (NB-IoT UEs). It should be understood that a UE3 can support one or more IoT or MTC applications.

[0132] UE3 may be a smartphone or a wearable device (e.g., smart glasses, smartwatch, smart ring, or hearable device). UE3 may be an automobile, or a connected car, or an autonomous vehicle, or a vehicle system, 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).

[0133] <(R)AN node> Figure 8 is a block diagram illustrating the main components of an exemplary (R)AN node 5, such as a base station (LTE "eNB", 5G "gNB", 5G Beyond base station, 6G base station). As shown in the figure, the (R)AN node 5 includes a transceiver circuit 51 that is operable to transmit signals to (one or more) connected UE3s via one or more antennas 52, receive signals from (one or more) connected UE3s, transmit signals to other network nodes (directly or indirectly) via a network interface 53, and receive signals from other network nodes. The control unit 54 controls the operation of the (R)AN node 5 according to software stored in memory 55. The software may be pre-installed in memory and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communication control module 552 having at least a transceiver control module 5521.

[0134] The communication control module 552 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, another (R)AN node 5, the AMF 70, the UPF 72, etc., either directly or indirectly. The signaling may include, for example, properly formatted signaling messages related to the radio connection and the connection to the core network 7 (for a specific UE 3), especially those related to connection establishment and maintenance, such as RRC connection establishment and other RRC messages, NG Application Protocol (NGAP) messages (i.e., messages at the N2 reference point), and Xn application protocol (XnAP) messages (i.e., messages at the Xn reference point). Such signaling may also include, for example, broadcast information (such as master information and system information) in the case of transmission.

[0135] The control unit 54 is also configured (by software or hardware) to process related tasks such as UE mobility estimation and / or movement trajectory estimation when implemented. (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). The current RAN 501 and the candidate RAN 502 may have the same components as the (R)AN node 5. The (R)AN node 5 may be represented as a RAN node, a RAN, an (R)AN, etc.

[0136] <System Overview of (R)AN Node 5 Based on O-RAN Architecture> Figure 9 schematically illustrates the (R)AN node 5 based on the O-RAN architecture to which the aspects of the (R)AN node 5 are applicable.

[0137] 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 embodiments, each unit can be combined. For example, RU 60 can be combined with DU 61 as an integration / combination unit, and DU 61 can be combined with CU 62 as an integration / combination unit, and any function in the description of a unit (e.g., one of RU 60, DU 61, and CU 62) can be implemented in the above integration / combination units. Furthermore, CU 62 can be separated into two functional units, such as a Control Plane (CP) and a User Plane (UP). The CU CP has the control plane function in the (R)AN node 5. The CU UP has the user plane function in the (R)AN node 5. Each CU CP is connected to the CU UP via the appropriate interface "E1".

[0138] Each UE3 and each serving RU60 is connected via an appropriate air interface (e.g., a so-called "Uu" interface). Each RU60 is connected to a DU61 via an appropriate interface (e.g., a so-called "fronthaul", "open fronthaul", or "F1" interface). Each DU61 is connected to a CU62 via an appropriate interface (e.g., a so-called "midhaul", "open midhaul", or "E2" interface). Each CU62 is also connected to a node in the core network 7 (a so-called core network node) via an appropriate interface (e.g., a so-called (one or more) "backhaul", "open backhaul", or "N2" / "N3" interface). The user plane portion of the DU61 can also be connected to the core network node 7 via an appropriate interface (e.g., a so-called (one or more) "N3" interface).

[0139] Depending on the functions divided between RU60, DU61, and CU62, each unit provides a portion of the functions provided by (R)AN node 5. For example, RU60 may provide the function to communicate with UE3 via the air interface, DU61 may provide the function to support the MAC layer and RLC layer, and CU62 may provide the function to support the PDCP layer, SDAP layer, and RRC layer.

[0140] <Radio Unit (RU)> Figure 10 is a block diagram illustrating the main components of the RU section of an exemplary RU60, for example, a base station (LTE "eNB", 5G "gNB", 5G Beyond base station, 6G base station). As shown in the figure, the RU60 includes a transceiver circuit 601 that is operable to transmit signals to (one or more) connected UE3s via one or more antennas 602, receive signals from (one or more) connected UE3s, transmit signals to other network nodes or network units (directly or indirectly) via a network interface 603, and receive signals from other network nodes or network units. The control unit 604 controls the operation of the RU60 according to software stored in memory 605. The software may be pre-installed in memory and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521.

[0141] The communication control module 6052 (using its transceiver control submodule) is responsible for handling (generating / transmitting / receiving) signaling between RU60 and other nodes or units such as UE3, another RU60, DU61, etc., (e.g., directly or indirectly). The signaling may include, for example, appropriately formatted signaling messages related to the wireless connection and the connection with RU60 (for a particular UE3), particularly related to the MAC and RLC layers.

[0142] The control unit 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation when implemented. RU60 may support Non-Public Networks (NPNs), which may be Stand-alone Non-Public Networks (SNPNs) or Public Network Integrated NPNs (PNI-NPNs). As described above, RU60 can be integrated / coupled with DU61 as an integration / coupling unit. Any of the functions described in the RU60 description can be implemented in the above integration / coupling unit.

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

[0144] DU61 may support Non-Public Networks (NPNs), which may be Stand-alone Non-Public Networks (SNPNs) or Public Network Integrated NPNs (PNI-NPNs). As described above, RU60 can be integrated / coupled with DU61 or CU62 as an integration / coupling unit. Any of the functions described in the DU61 description can be implemented in the above integration / coupling unit.

[0145] <Centralized Unit (CU)> Figure 12 is a block diagram illustrating the main components of the CU section of an exemplary CU62, for example, a base station (LTE "eNB", 5G "gNB", 5G Beyond base station, 6G base station). As shown, the device includes a transceiver circuit 621 that can operate to transmit signals to and receive signals from other nodes or units (including DU61) via a network interface 622. A control unit 623 controls the operation of the CU62 according to software stored in memory 624. The software may be pre-installed in memory 624 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241 and a communication control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / transmitting / receiving) signaling between CU62 and other nodes or units such as DU61 and other nodes and units.

[0146] CU62 may support Non-Public Networks (NPNs), which may be Stand-alone Non-Public Networks (SNPNs) or Public Network Integrated NPNs (PNI-NPNs). As described above, CU62 can be integrated / coupled with DU61 as an integration / coupling unit. Any of the functions described in the CU62 description can be implemented in the above integration / coupling unit.

[0147] <amf> Figure 13 is a block diagram illustrating the main components of the AMF70. As shown, the device includes a transceiver circuit 701 that can operate to transmit signals to and receive signals from other nodes (including UE3 and NSSF76) via a network interface 702. The control unit 703 controls the operation of the AMF70 according to software stored in memory 704. The software may be pre-installed in memory 704 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421. The communication control module 7042 (using its transceiver control module 70421) is responsible for processing (generating / transmitting / receiving) signaling between the AMF 70 and other nodes, such as UE3 (e.g., via (R)AN node 5) and other core network nodes (including core network nodes in UE3's HPLMN when UE3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages related to access and mobility management procedures (for UE3) (e.g., registration request messages and associated response messages).

[0148] AMF70 can support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). AMF7001 and AMF7002 may have the same components as AMF70.

[0149] <pcf> Figure 14 is a block diagram illustrating the main components of PCF73. As shown, the device includes a transceiver circuit 731 that can operate to transmit signals to and receive signals from other nodes (including AMF70) via a network interface 732. The control unit 733 controls the operation of PCF73 according to software stored in memory 734. The software may be pre-installed in memory 734 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7341 and a communication control module 7342 having at least a transceiver control module 73421. The communication control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / transmitting / receiving) signaling between PCF73 and other nodes such as AMF70 and other core network nodes (including core network nodes in the HPLMN of UE3 when UE3 is roaming in). Such signaling may include, for example, well-formatted signaling messages related to policy management procedures (for UE3) (e.g., an HTTP RESTful method based on a service-based interface).

[0150] PCF73 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). PCF7301 and PCF7302 may have the same components as PCF73.

[0151] <ausf> Figure 15 is a block diagram illustrating the main components of AUSF74. As shown, the device includes a transceiver circuit 741 capable of transmitting signals to and receiving signals from other nodes (including UDM75) via a network interface 742. A control unit 743 controls the operation of AUSF74 according to software stored in memory 744. The software may be pre-installed in memory 744 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / transmitting / receiving) signaling between AUSF74 and other nodes such as AMF70 and other core network nodes (including core network nodes in the HPLMN of UE3 when UE3 is roaming in). Such signaling may include, for example, well-formatted signaling messages related to policy management procedures (for UE3) (e.g., an HTTP RESTful method based on a service-based interface).

[0152] AUSF74 can support Non-Public Networks (NPNs), which may be Stand-alone Non-Public Networks (SNPNs) or Public Network Integrated NPNs (PNI-NPNs).

[0153] <udm> Figure 16 is a block diagram illustrating the main components of the UDM 75. As shown, the device includes a transceiver circuit 751 that can operate to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. The control unit 753 controls the operation of the UDM 75 according to software stored in memory 754. The software may be pre-installed in memory 754 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / transmitting / receiving) signaling between the UDM75 and other nodes, such as the AMF70 and other core network nodes (including core network nodes in the UE3's VPLMN when the UE3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages related to mobility management procedures (for the UE3) (e.g., in an HTTP RESTful way based on a service-based interface).

[0154] UDM75 can support Non-Public Networks (NPNs), which may be Stand-alone Non-Public Networks (SNPNs) or Public Network Integrated NPNs (PNI-NPNs).

[0155] <nssf> Figure 17 is a block diagram illustrating the main components of the NSSF76. As shown, the device includes a transceiver circuit 761 that can operate to transmit signals to and receive signals from other nodes (including the AMF70) via a network interface 762. A control unit 763 controls the operation of the NSSF76 according to software stored in memory 764. The software may be pre-installed in memory 764 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7641 and a communication control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / transmitting / receiving) signaling between the NSSF76 and other nodes, such as the AMF70 and other core network nodes (including core network nodes in the UE3's VPLMN when the UE3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages related to mobility management procedures (for the UE3) (e.g., in an HTTP RESTful way based on a service-based interface).

[0156] NSSF76 can support Non-Public Networks (NPNs), which may be Stand-alone Non-Public Networks (SNPNs) or Public Network Integrated NPNs (PNI-NPNs).

[0157] The exemplary embodiments disclosed above, in whole or in part, can be described as follows, but are not limited thereto.

[0158] <Examples of corrections and alternatives> Detailed embodiments have now been described. As those skilled in the art will understand, several modifications and substitutions can be made to the embodiments described above while still benefiting from the disclosure as embodied therein. Some of these substitutions and modifications are described herefor illustrative purposes only.

[0159] For the sake of clarity, the above description assumes that the UE3 and network device have several separate modules (such as a communications control module). These modules may be provided in this way in certain applications, for example, where an existing system is modified to implement the present disclosure. However, in other applications, such as systems designed from the outset with the features of the present invention in mind, these modules may be integrated into the overall operating system or code, and therefore may not be identifiable as separate entities. These modules may also be implemented as software, hardware, firmware, or a combination thereof.

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

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

[0162] In the above embodiments, 3GPP wireless communication (wireless access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed-line communication technologies (e.g., BBF access, cable access, optical access, etc.) may also be used in accordance with the above embodiments.

[0163] The category of user devices may include, for example, communication devices such as mobile phones, smartphones, personal digital assistants, laptop / tablet computers, web browsers, and e-book readers. Such mobile (or more generally, fixed) devices are typically operated by a user, but it is also possible to connect so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices to a network. For simplicity, this application refers to mobile devices (or UEs) in the description, but it will be understood that the described technology can be implemented on any communication device (mobile and / or generally fixed) that can connect to a communication network to send and receive data, whether such communication devices are controlled by human input or software instructions stored in memory.

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

[0165] As those skilled in the art will understand, this disclosure can be embodied as a method and system. Accordingly, this disclosure can take the form of entirely hardware embodiments, software embodiments, or embodiments combining software and hardware embodiments.

[0166] It will be understood that each block in the block diagram can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general-purpose computer, a dedicated computer, or other programmable data processing device to generate a machine such that instructions executed via the processor of the computer or other programmable data processing device produce means to perform the functions / operations specified in one or more blocks of the flowchart and / or block diagram. The general-purpose processor may be a microprocessor, but instead, the processor may be any conventional processor, control unit, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.

[0167] The methods or algorithms described in relation to the examples disclosed herein may be embodied in hardware directly, in software modules executed by a processor, or in a combination of the two. The software modules may be in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. The storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. The processor and storage medium may be located within an ASIC.

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

[0169] Although the present disclosure has been illustrated and described in detail with reference to its exemplary embodiments, the present disclosure is not limited to these embodiments. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this specification. For example, the above embodiments are not limited to 5GS, and these embodiments are also applicable to communication systems other than 5GS (e.g., 6G systems, 5G Beyond systems).

[0170] This application claims the benefit of priority based on Indian Patent Application No. 202211051126, filed on September 7, 2022, the disclosure of which is hereby incorporated in its entirety by reference.

[0171] <Appendix> The whole or part of the exemplary embodiments disclosed above can be described as follows, but not limited thereto.

[0172] (Appendix 1) A user equipment (UE) including mobile termination (MT) and a user services identity module (USIM), A transmitter configured to send a registration request message to the Access and Mobility Management Function (AMF) when the operator control signal threshold for each access technology is not set on the USIM or is not applied by the UE, A receiver configured to receive registration acceptance messages from the AMF containing information indicating operator control signal thresholds for each access technology, A user device equipped with the following features.

[0173] (Note 2) The registration request message includes the user ID, the first piece of information, and the second piece of information. The first piece of information indicates whether the UE supports the Signal Level Enhanced Network Selection (SENSE) feature. The second piece of information indicates the access technologies supported by the UE. User device as described in Appendix 1.

[0174] (Note 3) Access technologies include NB-IoT, GERAN EC-GSM-IoT, E-UTRA Category M1, E-UTRA Category M2, Wi-Fi, and New Radio (NR) technologies. User equipment as described in Appendix 2.

[0175] (Note 4) The MT stores information received from the AMF, which indicates the operator control signal threshold for each access technology, in the non-volatile memory of the USIM or UE. User device as described in Appendix 1.

[0176] (Note 5) The processor performs cell selection, cell re-selection, and Public Land Mobile Network (PLMN) selection procedures by using information that specifies the operator-controlled signal thresholds for each access technology. User device as described in Appendix 1.

[0177] (Note 6) A receiver configured to receive registration request messages from User Equipment (UE), A transmitter configured to send a registration acceptance message to a UE containing information indicating signal thresholds for each access technology, the information being received from Unified Data Management (UDM), and It includes an Access and Mobility Management Function (AMF).

[0178] (Note 7) The receiver receives a registration request message from the UE, and the registration request message includes the UE-ID, the first piece of information, and the second piece of information. The first piece of information indicates whether the UE supports the Signal Level Enhanced Network Selection (SENSE) feature. The second piece of information indicates the access technologies supported by the UE. The transmitter sends a first request message to the UDM based on the first and second pieces of information. The receiver receives a first response message from the UDM containing information indicating the operator control signal threshold for each access technology. The transmitter sends a registration acceptance message to the UE containing information indicating the operator control signal thresholds for each access technology. Access and mobility management functions as described in Appendix 6.

[0179] (Note 8) The first request message includes the first information, the second information, and, if the first information indicates that the UE supports the SENSE function, the third information. The first request message includes the third information if the first information indicates that the UE does not support the SENSE function. The third information indicates whether the AMF has the ability to transfer information related to the Signal Level Enhanced Network Selection (SENSE) function to the UE by using the Steering Of Roaming (SOR) mechanism. The access and mobility management function described in Appendix 7.

[0180] (Appendix 9) The first request message includes the Nudm_UECM_Registration request message. The first response message includes the Nudm_UECM_Registration response message. The access and mobility management function described in Appendix 7.

[0181] (Appendix 10) A receiver configured to receive the first request message from an Access and Mobility Management Function (AMF); A transmitter configured to transmit a second request message to a Steering Of Roaming Application Function (SoR-AF); comprising The receiver receives a second response message including information indicating an operator-controlled signal threshold for each access technology from the SoR-AF. The transmitter transmits a first response message including information indicating an operator-controlled signal threshold for each access technology to the AMF. Unified Data Management (UDM).

[0182] (Note 11) The transmitter, in response to a first request message received from the AMF, sends a first response message to the AMF containing information indicating the operator control signal threshold for each access technology. Integrated data management as described in Appendix 10.

[0183] (Note 12) The first request message includes the Nudm_UECM_Registration request message, The first response message includes the Nudm_UECM_Registration response message, The second request message includes the Nsoraf_SoR_Get request message, The second response message includes the Nsoraf_SoR_Get response message, Integrated data management as described in Appendix 10.

[0184] (Note 13) The transmitter sends a third request message to the Authentication Server Function (AUSF) containing information specifying the operator control signal threshold for each access technology in order to protect the information specifying the operator control signal threshold for each access technology. The receiver receives a third response message from AUSF containing protected information that specifies the operator control signal threshold for each access technology, and the protected information is protected by AUSF. Integrated data management as described in Appendix 10.

[0185] (Note 14) A method in user equipment (UE) including mobile termination (MT) and a user services identity module (USIM), If the operator control signal thresholds for each access technology are not set on the USIM or are not applied by the UE, a registration request message is sent to the Access and Mobility Management Function (AMF). AMF receives a registration acceptance message containing information specifying the signal threshold for each access technology. User device method.

[0186] (Note 15) A method in the Access and Mobility Management Function (AMF), A registration request message is received from the User Equipment (UE). A registration acceptance message is sent to the UE containing information specifying the signal threshold for each access technology, and this information is received from Unified Data Management (UDM). Methods for access and mobility management functions.

[0187] (Note 16) A method in Unified Data Management (UDM), The Access and Mobility Management Function (AMF) receives the first request message, A second request message is sent to the Steering Of Roaming Application Function (SoR-AF), The SoR-AF receives a second response message containing information indicating the operator control signal threshold for each access technology. A first response message is sent from the SoR-AF containing information indicating the operator control signal threshold for each access technology received. Methods for integrated data management. [Explanation of Symbols]

[0188] 1 System 3 UE 5 (R)AN Node 60 RU 61 DU 62 CU 7 Core Network 70 AMF 71 SMF 72 UPF 73 PCF 74 AUSF 75 UDM 76 NSSF 20 Data Networks 33 MT 35 USIM 201 SoR AF< / nssf> < / udm> < / ausf> < / pcf> < / amf>

Claims

1. A method performed by a user device (UE) roaming on a first network, In order to obtain information regarding signal thresholds for each access technology from the Integrated Data Management (UDM) located in the Home Public Land Mobile Network (HPLMN), a Registration Request message for initial registration is sent to the Access and Mobility Management Function (AMF) located in the first network. The AMF receives a Registration Accept message, which includes the signal threshold for each access technology. The signal threshold for each access technology received is used for selecting the next public land mobile network (PLMN). User device method.

2. The first network includes either the HPLMN or the Visited Public Land Mobile Network (VPLMN), The method according to claim 1.

3. A method performed by integrated data management (UDM) located in a home public land mobile network (HPLMN), A first request message is received from an Access and Mobility Management Function (AMF) located in the first network, and the first request message is a message transmitted by the AMF based on a Registration Request message for initial registration received from a User Equipment (UE), When the user device performs the registration procedure on the first network, A second request message is sent to the first device. The first device receives a second response message, which includes a Secured Packet. The AMF receives a first response message containing a signal threshold for each access technology formed based on the secure packet, and requests the AMF to send a Registration Accept message containing the signal threshold for each access technology to the user device. Methods for integrated data management.

4. The first network includes either the HPLMN or the Visited Public Land Mobile Network (VPLMN), The method according to claim 3.

5. A user device (UE) roaming on a first network, One or more memory locations for storing instructions, The system comprises one or more processors configured to process the instructions and control the user device, The one or more processors control the user device, In order to obtain information regarding signal thresholds for each access technology from the Integrated Data Management (UDM) located in the Home Public Land Mobile Network (HPLMN), a Registration Request message for initial registration is sent to the Access and Mobility Management Function (AMF) located in the first network. The AMF receives a Registration Accept message, which includes the signal threshold for each access technology. The signal threshold for each access technology received is used for selecting the next public land mobile network (PLMN). User device.

6. The first network includes either the HPLMN or the Visited Public Land Mobile Network (VPLMN), The user device according to claim 5.

7. Integrated data management (UDM) located in a home public land mobile network (HPLMN), One or more memory locations for storing instructions, The system comprises one or more processors configured to process the instructions and control the UDM, The one or more processors control the UDM, A first request message is received from an Access and Mobility Management Function (AMF) located in the first network, and the first request message is a message transmitted by the AMF based on a Registration Request message for initial registration received from a User Equipment (UE), When the user device performs the registration procedure on the first network, A second request message is sent to the first device. The first device receives a second response message, which includes a Secured Packet. The AMF receives a first response message containing a signal threshold for each access technology formed based on the secure packet, and requests the AMF to send a Registration Accept message containing the signal threshold for each access technology to the user device. Integrated data management.

8. The first network includes either the HPLMN or the Visited Public Land Mobile Network (VPLMN), Integrated data management according to claim 7.

Images