Method performed by a user equipment (UE), method performed by a 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 technology]

[0002] According to 3GPP® contribution SP-211068 [2], 3GPP is defining a new feature called Signal Level Enhanced Network Selection in 3GPP Release 18. This feature solves the problem of VPLMN selection when IoT devices are not on their home network. There are many cases where IoT devices are not in the home network. For example, modules in IoT devices are deployed in a country other than the country of the provided USIM or for use of a global USIM for IoT use cases. Summary of the Invention [Problem to be solved by the invention]

[0003] The problem of VPLMN selection by IOT devices can be 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 and network priorities broadcast by the PLMN are taken into account for cell reselection.

[0004] This can lead to the UE selecting or remaining on a network with poor coverage in a particular location. This occurs because the UE selects a PLMN with a higher priority, even though other PLMNs with lower priority are available with much better local coverage. For a typical consumer UE, this is not a problem; due to mobility, conditions are changing rapidly, and some users are able to recognize the problem and respond by, for example, slightly changing their location or manually selecting a different PLMN. This is a desirable behavior as part of steering roaming, avoiding frequent changes of network. However, for fixed devices without user supervision, this can be problematic.

[0005] To solve this problem, the signal level enhanced network selection feature is introduced in 3GPP Release 18. This feature makes it possible to take the signal level 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 a signal level enhanced network selection function are defined in 3GPP TS 22.011 [6], but there is no mechanism defined in any of the 3GPP specifications. For example, 3GPP TS 22.011 [6] defines the requirements for the signal level enhanced network selection function as follows:

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

[0008] To comply with this requirement, there are many aspects that can be taken into consideration.

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

[0010] For example, it is unclear what the structure of the information for operator-controlled signal thresholds is. There are many radio aspects that affect stable communication between IoT UEs and the network, such as signaling strength, signal quality, interference level, etc. 3GPP needs to define the structure of the information for operator-controlled signal thresholds. [Means for solving the problem]

[0011] SUMMARY Accordingly, the present disclosure seeks to provide a method and associated apparatus that addresses or at least alleviates (at least some of) the problems discussed above.

[0012] In one aspect, the present disclosure provides a User Equipment (UE) including a Mobile Termination (MT) and a User Services Identity Module (USIM), a transmitter configured to send a registration request message to an Access and Mobility Management Function (AMF) when a per access technology signal threshold is not configured on the USIM or is not applied by the UE; a receiver configured to receive a registration accept message from the AMF, the registration accept message including information indicating a signal threshold for each access technology; The present invention provides a user device comprising:

[0013] In one aspect, the present disclosure provides a method for manufacturing a semiconductor device comprising: a receiver configured to receive a registration request message from a User Equipment (UE); a transmitter configured to transmit a registration accept message to the UE, the registration accept message including information indicating a signal threshold for each access technology, the information being received from a Unified Data Management (UDM); It provides an Access and Mobility Management Function (AMF) that includes:

[0014] In one aspect, the present disclosure provides a method for manufacturing a semiconductor device comprising: a receiver configured to receive a first request message from an Access and Mobility Management Function (AMF); a transmitter configured to send a second request message to a Steering Of Roaming Application Function (SoR-AF); Equipped with the receiver receives a second response message from the SoR-AF, the second response message including information indicating a signal threshold for each access technology; The transmitter sends a first response message to the AMF, the first response message including information indicating a signal threshold for each access technology. Provides Unified Data Management (UDM).

[0015] In one aspect, the present disclosure provides a method in a User Equipment (UE) including a Mobile Termination (MT) and a User Services Identity Module (USIM), comprising: If a signal threshold per access technology is not configured on the USIM or is not applied by the UE, sending a registration request message to an Access and Mobility Management Function (AMF); receiving a registration acceptance message from the AMF, the registration acceptance message including information indicating a signal threshold for each access technology; A method for a user device is provided.

[0016] In one aspect, the present disclosure provides a method in an Access and Mobility Management Function (AMF), comprising: receiving a registration request message from a user equipment (UE); sending a registration accept message to the UE, the registration accept message including information indicating a signal threshold for each access technology, the information being received from a Unified Data Management (UDM); It provides methods for access and mobility management functions.

[0017] In one aspect, the present disclosure provides a method in Unified Data Management (UDM), comprising: receiving a first request message from an Access and Mobility Management Function (AMF); sending a second request message to a Steering Of Roaming Application Function (SoR-AF); receiving a second response message from the SoR-AF, the second response message including information indicating a signal threshold for each access technology; transmitting a first response message including information indicating a signal threshold for each access technology received from the SoR-AF; Provides a method for integrated data management. [Effects of the Invention]

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

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

[0020] It should be noted, however, that the accompanying drawings bearing reference numerals illustrate only typical embodiments of the present subject matter and, therefore, should not be considered to limit the scope of the present subject matter, which may admit of other equally effective embodiments. [Brief explanation of the drawings]

[0021] [Figure 1] FIG. 1 is a signaling diagram of a first example of the first embodiment. [Figure 2] FIG. 10 is a signaling diagram of a first example of the second embodiment. [Figure 3] 1 is an existing PLMN selection diagram in 3GPP TS 23.122. [Figure 4] FIG. 10 is a process diagram in a UE of a second example of the second aspect. [Figure 5] FIG. 10 is a process diagram in a UE of a third example of the second embodiment. [Figure 6] FIG. 1 is a diagram illustrating an example of a system overview. [Figure 7] FIG. 1 is a block diagram illustrating a UE. [Figure 8] FIG. 1 is a block diagram illustrating an (R)AN node. [Figure 9] FIG. 1 illustrates a system overview of an (R)AN node based on an O-RAN architecture. [Figure 10] FIG. 1 is a block diagram illustrating an RU. [Figure 11] FIG. 2 is a block diagram illustrating a DU. [Figure 12] FIG. 2 is a block diagram illustrating a CU. [Figure 13] FIG. 1 is a block diagram illustrating an AMF. [Figure 14] FIG. 1 is a block diagram illustrating a PCF. [Figure 15] FIG. 1 is a block diagram illustrating an AUSF. [Figure 16] FIG. 1 is a block diagram illustrating a UDM. [Figure 17] FIG. 1 is a block diagram illustrating an NSSF. DETAILED DESCRIPTION OF THE INVENTION

[0022] <abbreviation> For the purposes of this document, 3GPP TR 21.905 [1] and the abbreviations listed below apply. Abbreviations defined in this document take precedence over definitions of the same abbreviations in 3GPP TR 21.905 [1], if any.

[0023] 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function AMF-NG Non-Geographically selected Access and Mobility Management Function ANDSF Access Network Discovery and Selection Function ARFCN Absolute radio-frequency channel number AS Access Stratum 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 EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity 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 Break Out (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 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 NAI Network Access Identifier NAS Non-Access-Stratum NEF 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 Signalling optimisation (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 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 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 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 in 3GPP TR 21.905 [1] and below apply. Terms defined in this document take precedence over any definition of the same term in 3GPP TR 21.905 [1]. [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 6

Non-licensed Document 7

[0026] <General> Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not necessarily be drawn to scale. Further, with respect to the configuration of a device, one or more components of the device may be represented in the figures by conventional symbols, and the figures may show only certain details relevant to an understanding of aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to one of ordinary skill in the art having the benefit of the description herein. For the purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same, it being understood, however, that no limitation of the scope of the disclosure is intended. Such changes and further modifications in the illustrated systems, and such further applications of the principles of the present disclosure as would normally occur to one skilled in the art, are to be construed as being within the scope of the present disclosure.

[0027] The terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that includes a list of steps does not include only those steps, but may also include other steps not expressly listed or inherent in such process or method. Similarly, the term "comprising" precedes one or more devices or entities or subsystems or elements or structures or components, and does not, without further constraints, exclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, the appearances of the phrases "in an embodiment," "in another embodiment," and similar language may, but do not necessarily, all refer to the same embodiment.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0029] In the following specification and claims, reference will be made to a number of terms that may be defined to have the following meanings: The singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. As used herein, information is associated with data and knowledge, as data is meaningful information and represents values ​​attributed to parameters. Further knowledge represents an understanding of abstract or concrete concepts. It should be noted that this exemplary system is simplified to facilitate explanation of the disclosed subject matter and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement aspects disclosed herein, and all such aspects are considered to be within the scope of the present disclosure.

[0030] Furthermore, each of the aspects and elements included in each aspect described below may be implemented independently or in combination with one another. These aspects include novel features that are different from one another. Therefore, these aspects contribute to achieving different objectives or solving different problems, and to obtaining different advantages from one another.

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

[0032] <First aspect> This aspect discloses a mechanism that enables secure transfer of information for operator-controlled signal thresholds per access technology from a home operator to a USIM 35 installed in a UE 3 while the UE 3 is roaming in a VPLMN.

[0033] <First Example of First Aspect> If the UE 3 has not been provided with information for operator-controlled signal thresholds per access technology, the UE 3 will initiate a registration procedure to fetch the information from the HPLMN using 5GS.

[0034] Figure 1 shows the registration procedure for obtaining threshold values ​​for operator control signals for each access technology from a home network.

[0035] A detailed process of the first example of the first aspect is described below with reference to Figure 1. Note that the MT33 in Figure 1 indicates the mobile termination of the UE3. The MT33 may be the UE3 excluding the USIM35.

[0036] Step 0. The SoR AF 201 stores information for signal thresholds per access technology in the subscriber data.

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

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

[0039] The SENSE capability support can be named differently, such as SENSE information query, SENSE request, or any other name to indicate that the UE 3 requests the AMF 70 to have SENSE-related information. The UE supported access technologies may be another name, such as access technology, or any other name to indicate one or more access technologies supported by the UE 3.

[0040] Step 2. When the AMF 70 receives the registration request message, the AMF 70 sends a Nudm_UECM_Registration request message to the UDM 75, including the user ID, SENSE function support, UE supported access technologies, and SoR for SENSE support. The SENSE function support parameters and UE supported access technologies received in step 1. If the AMF 70 does not receive a SENSE function support indication from the UE 3, the AMF 70 recognizes that the UE 3 does not support the SENSE function, and the AMF 70 does not include the SENSE function or the UE supported access technologies in the Nudm_UECM_Registration request message. The SoR for SENSE support indicates that the AMF 70 has the ability to transfer SENSE-related information to the UE 3 using the SoR mechanism.

[0041] The SENSE function support can be named differently, such as SENSE information query, SENSE request, or any other name to indicate that the AMF 70 requests the UDM 75 to have SENSE-related information. The UE supported access technologies may be another name, such as access technology, or any other name to indicate one or more access technologies supported by the UE 3. SoR for SENSE may be another name that indicates that the AMF 70 has the ability to transfer SENSE related information to the UE 3 using the SoR mechanism.

[0042] Step 3. When the UDM 75 receives the Nudm_UECM_Registration request message including the user ID, SENSE capability support, and UE supported access technologies, and SoR for SENSE support, the UDM 75 sends an Nsoraf_SoR_Get request message (or a new message or any existing message) including the user ID, SENSE capability support indication, and UE supported access technologies received in step 2. The SENSE capability support can be named something else, such as SENSE information query, SENSE request, or any other name to indicate that the UDM 75 requests the SoR AF 201 to have SENSE-related information. If the UDM 75 does not receive a SENSE function support indication from the AMF 70, the UDM 75 assumes that the UE 3 does not support the SENSE function, and the UDM 75 does not send an Nsoraf_SoR_Get request message to the SoR-AF 201. If the UDM 75 does not receive an SoR for SENSE support from the AMF 70, the UDM 75 assumes that the AMF 70 does not support the SENSE function, and the UDM 75 does not send an Nsoraf_SoR_Get request message to the SoR-AF 201. In one example, SENSE feature support may be interpreted by UDM 70 as AMF supporting SOR feature, in which case UDM 70 sends an Nsoraf_SoR_Get request message (new or existing) to SoR-AF 201, even if UDM 70 does not receive an SoR for SENSE support from AMF 70.

[0043] The UE supported access technologies may be another name, such as access technology, or any other name to indicate one or more access technologies supported by the UE 3.

[0044] Step 4. Upon receiving the Nsoraf_SoR_Get request message containing the user ID (e.g., SUPI or GPSI) and SENSE feature support and UE supported access technologies, the SoR AF 201 finds information for the signal thresholds per access technology from the subscriber data record (e.g., memory) of the subscriber identified by the user ID. The SoR-AF 201 then sends to the UDM 75 an Nsoraf_SoR_Get response message (e.g., a new message or an existing message) containing information for the signal thresholds per access technology of the UE 3.

[0045] Step 5. When the UDM 75 receives the Nsoraf_SoR_Get response message from the SoR-AF 201, which includes information for the signal thresholds per access technology of the UE 3, the UDM 75 sends a Nausf_SoRProtection request message (a new message or an existing message) to the AUSF 74, which includes information for the signal thresholds per access technology, to protect this information. The UDM 75 may include an ACK indication in the Nausf_SoRProtection request message to receive an indication from the UE 3 when the SoR container has been successfully delivered to the UE 3.

[0046] Step 6. When AUSF74 receives from UDM75 an ausf_SoRProtection request message containing information for the signal thresholds per access technology, AUSF74 encrypts this information and sends to UDM75 an Nausf_SoRProtection response message containing an SoR container containing the encrypted information for the signal thresholds per access technology.

[0047] Step 7. When the UDM 75 receives the Nausf_SoRProtection response message including the SoR container containing encryption information for the signal threshold per access technology from the AUSF 74, the UDM 75 sends a Nudm_UECM_Registration response message including the SoR container containing encryption information for the signal threshold per access technology to the AMF 70. The UDM 75 may include an ACK indication 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 the AMF 70 receives the Nudm_UECM_Registration response message including the SoR container containing encryption information for the signal threshold per access technology, the AMF 70 sends a registration accept message including the SoR container containing encryption information for the signal threshold per access technology to the UE 3. The AMF 70 may include an ACK indication in the registration accept message.

[0051] Step 9. When the MT33 in the UE3 receives the registration accept message including the SoR transparent container containing encrypted information for the signal thresholds per access technology from the AMF 70, the MT33 decrypts the SoR transparent container to obtain the information for the signal thresholds per access technology. The MT33 sends the information to the USIM 35 or stores the information in the non-volatile memory of the UE3. After MT33 deciphers the information for the per-access technology signal threshold from the SoR transparent container, the NAS layer of UE3 notifies the per-access technology signal threshold information to the AS layer of UE3. For example, the information for the per-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 the MT33 receives an invalid value for the access technology, the UE3 ignores the value, does not store the value in the USIM35, and does not apply the threshold.

[0053] In one example, UDM 75 transmits a fixed value, e.g., 0, for each access technology to disable cell selection or reselection procedures based on per-access technology signal thresholds. When UE 3 receives this value, it does not apply the cell selection or reselection procedures for the access technology.

[0054] Step 10. If the UE 3 is required to confirm successful delivery of information for signal thresholds per access technology, the UE 3 sends a registration complete message to the AMF 70.

[0055] Step 11. When AMF 70 receives a registration complete message from UE 3 and AMF 70 is requested by UDM 75 to confirm successful delivery of information for signal thresholds per access technology to UE 3, AMF 70 sends a Nudm_SDM_Info message to UDM 75 so that UDM 75 can recognize successful delivery of information for signal thresholds per access technology to UE 3.

[0056] In this disclosure, operator-controlled signal thresholds per access technology may also be referred to by other terms, such as per access technology signal thresholds, per access technology signal quality thresholds, per access technology thresholds, etc. In the present disclosure, user identification information may also be referred to as a user ID or a UE ID.

[0057] <Modification 1 of the first example of the first aspect> In one example, the SoR AM 201 can be included in the UDM 75. In this case, steps 3 and 4 are performed inside the UDM 75.

[0058] <Modification 2 of the First Example of the First Aspect> In one example, the UE 3 scans for available PLMNs at its location and sends a list of signal strengths and / or signal qualities (e.g., RSRP (Reference Signal Received Power) and RSRQ (Reference Signal Received Quality) RSSI in EPS) of the strongest cells of each PLMN available at its location in a registration request message. The AMF 70 then sends the list of signal strengths and / or signal qualities to the UDM 75 in step 2. The UDM 75 sends the list of received signal strengths and / or signal qualities to the SoR-AF 201. The SoR-AF 201 determines the signal strength for each access technology based on the list of received signal strengths and / or signal qualities. In one example, the list of signal strengths or signal qualities is integrity protected or encrypted and transmitted to the UDM 75 in a transparent container.

[0059] <Modification 3 of the first example of the first aspect> In another example, the per-access technology operator-controlled signal threshold information may be configured in the AMF 70 directly or via OAM based on operator policy. In that case, the per-access technology operator-controlled signal threshold information may be delivered by the AMF 70 to the UE 3 while the UE 3 is registered with the home PLMN, as in steps 8 and 9 of Figure 1. Alternatively, the per-access technology configured operator-controlled signal threshold information in the AMF 70 may be delivered to the UE 3 via a UE Configuration Update message while the UE 3 is connected with the home PLMN, or whenever the UE 3 is in idle mode by initially paging the UE 3.

[0060] <Modification 4 of the first example of the first aspect> In another example, the information of the operator-controlled signal thresholds per access technology may be defined as new rules for triggering cell selection / reselection or PLMN selection / reselection by the UE 3 as part of the URSP rules for the UE 3 in the PCF and provided to the UE 3 in the URSP provisioning in the UE policy information via the UE configuration update procedure according to 3GPP TS 23.502 [4] and 3GPP TS 23.503 [5].

[0061] <Modification 5 of the First Example of the First Aspect> In another example, operator-controlled signal threshold information per access technology may be provided to the UE 3 by the AMF 70 via OTA (Over The Air) DM (Device management). In another example, the UDM 75 can transmit the per-access-technology operator-controlled signal threshold information in any existing or new message defined between the UDM 75 and the AMF 70. When the AMF 70 receives the per-access-technology operator-controlled signal threshold information, the AMF 70 transmits the received per-access-technology operator-controlled signal threshold information to the UE 3 in an existing or new NAS message. When the UE 3 receives the per-access-technology operator-controlled signal threshold information, the UE 3 transmits an existing NAS message to the AMF instructing it to receive the per-access-technology operator-controlled signal threshold information. When the AMF 70 receives the NAS message from the UE 3, it transmits a message to the UDM 75 instructing it to receive the per-access-technology operator-controlled signal threshold information at the UE 3. This method of transmitting the per-access-technology operator-controlled signal threshold information can be used when the UE 3 is a registrant in a HPLMN or an equivalent HPLMN.

[0062] <Modification 6 of the First Example of the First Aspect> In another example, the operator-controlled signal thresholds per access technology may be defined by the service provider (e.g., when the mobile terminal belongs to a third part service provider that has a contract with the PLMN that controls the signal thresholds). In this case, the information of the operator-controlled signal thresholds per access technology is provided by the service provider to the UDM 75 of the 3GPP network via the NEF entity of the 3GPP network. Along with providing the operator-controlled signal thresholds per access technology, the service provider may provide additional information regarding the validity of the provided thresholds or their applicability per UE or per group of UEs, and the service provider can update the operator-controlled signal thresholds per access technology and the conditions of their applicability at any time.

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

[0064] <Modification 8 of the First Example of the First Aspect> In one example, the AMF 70 provides the NG-RAN with the operator-controlled signal threshold per access technology in an existing or new NGAP message. When the NG-RAN receives the operator-controlled signal threshold per access technology, the NG-RAN stores it and selects the target cell in the handover procedure if the signal strength of the target cell is greater than or equal to the operator-controlled signal threshold per access technology.

[0065] <Modification 9 of the First Example of the First Aspect> The UE 3 transparently and securely transmits to the UDM 75 via the AMF 70, for example, at any time during a power-on procedure or any NAS procedure, a list of signal strengths per access technology type that the UE 3 can receive and / or a list of signal strengths per PLMN that the UE 3 can receive and / or a list of all signal strengths of the best cell for each access technology available for each available PLMN that the UE 3 can receive, and the current UE location. For example, the UE 3 transmits the list of signal strengths to the AMF 70 via a registration request message or a registration complete message, or in any NAS message. The AMF 70 then transmits the list of received signal strengths to the UDM 75 in an existing or new message defined between the AMF 70 and the UDM 75. Upon receiving the list of signal strengths, the UDM 75 may decide to update the operator-controlled signal thresholds per 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 technology at the location of UE3 is much lower than the operator-controlled signal threshold for that access technology in UDM75, UDM75 will decrease the threshold for the operator-controlled signal threshold for that access technology and update the newly defined threshold in UE3 using the mechanism disclosed by the first aspect.

[0066] <Modification 10 of the First Example of the First Aspect> The UE 3 sends the current values ​​of the stored thresholds to the UDM via the AMF at any time, for example during a power-on procedure or any NAS procedure. The current values ​​of the stored thresholds may be sent transparently and securely via the AMF 70 to the UDM 75. If the UE 3 has stored threshold values ​​that are not stored in the UE 3's USIM 35 or ME memory, the UE 3 indicates to the UDM 75 that the UE 3 does not have current values ​​of the operator-specific thresholds. The UDM 75 may decide to transmit operator-controlled signal thresholds per access technology to the UE 3 based on received current values ​​of stored thresholds within the UE 3 or instructions from the UE 3 . For example, if the current value of the threshold stored in the received UE3 is out of date, the UDM75 will use the mechanism disclosed by the first aspect to update the UE3 with the latest operator-controlled signal threshold for the access technology.

[0067] <Modification 11 of the First Example of the First Aspect> In steps 2 to 7, the AMF 70 and the UDM 75 may use existing messages or new messages between the AMF 70 and the UDM 75.

[0068] <Second aspect> This aspect discloses the mechanism how UE3 obtains information for operator-controlled signal thresholds per access technology via 5GS and how UE3 uses this information for NB-IoT, GERAN EC-GSM-IoT, and E-UTRA category M1 or M2.

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

[0070] 2 shows UE operations for the SENSE function. A detailed process of a first example of the second aspect will be described below with reference to FIG. 2. Note that the MT33 in FIG. 2 indicates the mobile termination of the UE3. The MT33 may be the UE3 excluding the USIM35.

[0071] Step 1. The UE 3 is switched on. Another use case for step 1 could be that a new SIM 35 is inserted into the UE 3, or the UE 3 is initialized by the user, or any other case for resetting the UE 3. Another use case for step 1 could be recovery from loss of coverage, periodic network selection attempts, and steering of roaming.

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

[0073] Step 3. When USIM 35 receives the inquiry message in step 1, if USIM 35 holds information for the signal threshold per access technology, USIM 35 provides the information for the signal threshold per access technology to MT 33. Otherwise, USIM 35 simply sends a denial message to MT 33 or provides null information for the signal threshold per access technology.

[0074] Step 4. The following conditions are checked by the UE 3: If all conditions are met, the UE 3 proceeds to step 5. The UE3 has the ability to process the SENSE function. The UE 3 does not maintain information for signal thresholds per access technology. UE3 has the capability to access 5GS, i.e., UE3 supports 5G NAS. UE3 has the capability 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 check made in step 4, the UE 3 initiates the registration procedure as disclosed in the first example of the first aspect. In one example, if there is a cell supporting UTRAN or E-UTRAN or GERAN or NR at the current location, the UE 3 shall select a cell supporting 5GS and initiate a registration procedure with the selected cell of the PLMN to register with 5GS, even if the selected cell is not the best cell available at the location, or the selected cell does not belong to the PLMN where it was last registered, or belongs to a PLMN that is not a more preferred PLMN available at the location.

[0076] For example, assume that PLMN1, PLMN2, and PLMN3 are stored in the operator preferred PLMN list in order of priority from highest to lowest, i.e., PLMN1 > PLMN2 > PLMN3. If, at its current location, there exists an E-UTRAN cell 1 belonging to PLMN1 and a cell 2 belonging to NG-RAN of PLMN2 that do not support 5GS connectivity, UE3 shall select cell 2 of PLMN2 and initiate the registration procedure to PLMN2 on cell 2.

[0077] Step 6. Upon successful completion of the registration procedure in step 5, the UE 3 migrates GSM-based GPRS, W-CDMA-based GPRS, or EPS to access with access technologies such as NB-IoT, GERAN EC-GSM-IoT, and E-UTRA category M1 or M2.

[0078] Step 7. The UE 3 initiates PLMN selection based on the received information of step 5 for the signal threshold of the access technology to which the UE 3 is currently tuned.

[0079] In this disclosure, operator-controlled signal thresholds per access technology may also be referred to by other terms, such as per access technology signal thresholds, per access technology signal quality thresholds, per access technology thresholds, etc. In the present disclosure, user identification information may also be referred to as a user ID or a UE ID.

[0080] <Second Example of the Second Aspect> The second example of the second aspect discloses a method of how UE 3 uses signal thresholds for PLMN selection. This example can be used in step 7 of the first example of the second aspect.

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

[0082] <First Disclosure for Updating the Process "Select a Registered PLMN"> Figure 4 is a signaling measurement based on signal threshold. Regarding the process "Select a registered PLMN" in the upper left of Figure 3, this process is replaced with the process as shown in Figure 4, which has the following process flow:

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

[0084] Process 4002. UE3 obtains information of operator-controlled signal thresholds for each access technology stored in USIM35 in UE3 or in non-volatile memory in UE3 for the UE's radio access (i.e., the radio access to which the UE is tuned), and UE3 obtains 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)) of all cells of the UE's radio access at the UE location.

[0085] Process 4003. If the measured signal strength (e.g., RSRP) or 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 UE 3 is allowed to select at the UE location on the same radio access is equal to or greater than the operator-controlled signal threshold for the access technology, UE 3 shall select a cell of that PLMN (i.e., UE 3 shall select the cell with the highest signal strength or highest signal quality or highest signal-to-noise ratio, or a combination of the three, belonging to any of the PLMNs that UE 3 is allowed to select), and UE 3 shall continue the PLMN selection process from point C of the PLMN selection diagram in Figure 3. Otherwise, UE 3 shall go back and start the PLMN selection from the beginning of the PLMN selection diagram in Figure 3, i.e., without considering the operator-controlled signal threshold information per access technology.

[0086] <Second Disclosure for Updating the Process "Select a PLMN"> Regarding the process immediately following connecting circle A and the process immediately following connecting circle B in FIG. 3, these processes are replaced with processes as shown in FIG. 4 having the following process flow:

[0087] Process 4001. UE3 checks whether UE3 has signal threshold information for the access technology to which UE3 is tuned. If UE3 has signal threshold information for the access technology, it proceeds to process 4302. If not, it returns to the original process.

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

[0089] Process 4003. If the measured signal quality is greater than or equal to 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, shown as "Attempt PLMN." In this case, the "Attempt PLMN" process does not initiate the registration procedure. The "PLMN Bundling" process simply determines whether there is a next PLMN in the list, i.e., proceed to either the middle line under "Attempt PLMN" process or the right line under "Attempt PLMN" process.

[0090] <Third Disclosure for Updating the Process "Select the First Available and Acceptable PLMN in the List"> Regarding the process "Select the first available and acceptable PLMN in the list" located at the bottom of FIG. 3, this process is replaced by a process as shown in FIG. 4 with the following process flow:

[0091] Process 4001. UE3 checks whether UE3 has signal threshold information for the access technology to which UE3 is tuned. If UE3 has signal threshold information for the access technology, it proceeds to process 3002. If not, it returns to the original process.

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

[0093] Process 4003. If the measured signal quality is greater than or equal to the operator-controlled signal threshold of the access technology, return to the original process; otherwise, proceed to the middle line under "Over PLMN" process.

[0094] <Modification 1 of the second example of the second aspect> In another example, the information of the per-access technology operator-controlled signal threshold may be considered as an offset value, i.e., the UE 3 shall select a cell from another PLMN only if the difference in signal strength (e.g., RSRP) or the difference in signal quality (e.g., RSRQ) or the difference in signal-to-noise ratio between the current cell of the home PLMN and a cell from another PLMN is equal to or greater than the per-access technology operator-controlled signal threshold that favors a cell from another PLMN. In this case, the UE 3 shall select a cell from the other PLMN and register with the other PLMN.

[0095] <Third Example of the Second Aspect> The third example of the second aspect discloses a method for UE3 to determine the measurement signal using a signal threshold for PLMN selection. This example can be used in step 4003 of the second example of the second aspect.

[0096] FIG. 5 illustrates the flow of how the UE 3 determines the measurement signal.

[0097] Process 5001.UE3 measures signals via access technology.

[0098] In process 5002, UE3 compares the received signal level to the RSRP as dictated by the operator-controlled signal threshold for the access technology. If the received signal level is greater than or equal to the operator-controlled signal threshold, it proceeds to process 5003. If not, it proceeds to process 5006 and concludes that the SENSE-based signaling check failed.

[0099] In process 5003, UE3 compares the received signal quality to the RSRQ as dictated by the operator-controlled signal threshold for the access technology. If the measured signal quality is greater than or equal to the operator-controlled signal threshold, it proceeds to process 5004. If not, it proceeds to process 5006 and concludes that the SENSE-based signaling check failed.

[0100] In process 5004, UE3 compares the received signal-to-interference-plus-noise ratio to the SINR as dictated by the operator-controlled signal threshold for the access technology. If the measured signal-to-interference-plus-noise ratio is greater than or equal to the operator-controlled signal threshold, UE3 proceeds to process 5005 and concludes that the SENSE-based signaling check has passed. Otherwise, UE3 proceeds to process 5006 and concludes that the SENSE-based signaling check has failed.

[0101] <Modification 1 of the third example of the second aspect> In another example, the operator-controlled signal thresholds per access technology may be applicable only to differences in signal strength between cells, or only to differences in signal quality between cells, or only to differences in signal-to-noise ratio between cells, or to any combination of these three operator-controlled signal thresholds per access technology. Depending on the applicability of the operator-controlled signal thresholds per access technology, the UE 3 may compare a home PLMN cell with a cell from another PLMN only to differences in signal strength, or to differences in signal quality, or to differences in signal-to-noise ratio, or to any other combination between these three types of thresholds, or to all three according to Figure 5.

[0102] <System Overview> FIG. 6 illustrates schematically a mobile (cellular or wireless) telecommunications system 1 to which the above aspects are applicable. The telecommunications system 1 represents a system overview capable of end-to-end communication, e.g., UEs 3 (or user equipment, "mobile devices", 3) communicating with other UEs 3 or service servers in a data network 20 via respective (R)AN nodes 5 and a core network 7. The (R)AN node 5 supports any radio access technology, including 5G Radio Access Technology (RAT), E-UTRA radio access technology, Beyond 5G RAT, 6G RAT, and non-3GPP RAT, including Wireless Local Area Network (WLAN) technology defined by the Institute of Electrical and Electronics Engineers (IEEE). The (R)AN node 5 may be divided into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU). In some aspects, each of the units may be connected to each other to construct the (R)AN node 5 by adopting an architecture defined by the Open RAN (O-RAN) Alliance, and these units are referred to as the O-RU, O-DU, and O-CU, respectively. The (R)AN node 5 may be divided into control plane functions and user plane functions. Furthermore, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed across multiple user plane functions, with user traffic via each user plane function being aggregated at both the UE 3 and the (R)AN node 5. This divided architecture is sometimes referred to as "dual connectivity" or "multi-connectivity." The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support satellite access and terrestrial access. The (R)AN node 5 may also be referred to as an access node for non-wireless access, including fixed line access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[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) including, among other functions, control plane functions and user plane functions. Each function within a logical node may be considered a network function. A network function may be provided to another node by adapting a Service Based Architecture (SBA). By adapting network virtualization technology defined as European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed as distributed, redundant, stateless, and scalable, providing services from several locations and several running instances at each location. The core network 7 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0104] As is known, a UE 3 may move in and out of areas (i.e., radio cells) served by an (R)AN node 5 as the UE 3 moves within the geographic area covered by the telecommunications system 1. To track the UE 3 and facilitate movement between different (R)AN nodes 5, the core network 7 comprises at least one Access and Mobility management Function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 coupled to the core network 7. In some core networks, a Mobility Management Entity (MME) or mobility management node for Beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[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 a UE 3 is roaming in a Visited Public Land Mobile Network (VPLMN), the Home Public Land Mobile Network (HPLMN) of the UE 3 provides the roaming-out UE 3 with the UDM 75 and at least some of the functionality of the SMF 71, UPF 72, and PCF 73.

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

[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 carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC, and MAC sublayers over the physical connection. The control plane of the Uu interface is responsible for establishing, modifying, and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers over the physical connection. For example, the following messages are communicated over the RRC layer to support AS signaling:

[0108] RRC Setup Request Message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, 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 the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup message: masterCellGroup and radioBearerConfig.

[0110] RRC Setup Complete Message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup Complete message: guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0111] The UE 3 and the AMF 70 are connected via an appropriate interface (such as the so-called N1 interface). The N1 interface is responsible for providing communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface 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 the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Registration Request message: 5GS Registration Type, ngKSI, 5GS Mobile Identity, Non-Current Native NAS Keyset Identifier, 5GMM Capabilities, UE Security Capabilities, Requested NSSAI, Last Visited Registration TAI, S1 UE Network Capabilities, Uplink Data Status, PDU Session Status, MICO Indication, UE Status, Additional GUTI, Allowed PDU Session Status, UE Usage Configuration, Requested DRX Parameters, EPS NAS Message Container, LADN Indication, Payload Container Type, Payload Container, Network Slicing Indication, 5GS Update Type, Mobile Station Class Mark 2, Supported Codecs, NAS Message Container, EPS Bearer Context Status, Requested Extended DRX Parameters, T3324 Value, UE Radio Capability ID, Requested Mapping NSSAI, Requested Additional Information, Requested WUS Assistance Information, N5GC Indication and Requested NB-N1 Mode DRX Parameters.

[0113] Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the registration accept message: 5GS Registration Result, 5G-GUTI, Equivalent PLMN, TAI List, Accepted NSSAI, Rejected NSSAI, Configured NSSAI, 5GS Network Capability Support, PDU Session Status, PDU Session Reactivation Result, PDU Session Reactivation Result Error Cause, LADN Information, MICO Indication, Network Slicing Indication, Service Area List, T3512 Value, Non-3GPP Deregistration Timer Value, T3502 Value, Emergency Number List, Extended Emergency Number List, SOR Transparent Container, EAP Message, NSSAI Inclusion Mode, Operator Defined Access Category Definition, Negotiated DRX Parameters, Non-3GPP NW policy, EPS bearer context status, negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID removal instruction, pending NSSAI, ciphering key data, CAG information list, aborted 5G-S-TMSI configuration, negotiated WUS assistance information, negotiated NB-N1 mode DRX parameters, and extended rejected NSSAI.

[0114] Registration Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the registration complete message: SOR transparent container.

[0115] Authentication Request Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Authentication 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 the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together 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 the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the Authentication Result message: ngKSI, EAP messages, and ABBA.

[0118] Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the Authentication Failure message: Authentication failure message identification information, 5GMM cause, and authentication failure parameters.

[0119] Authentication Reject Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the authentication reject message: EAP message.

[0120] Service Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the service request message: ngKSI, Service Type, 5G-S-TMSI, Uplink Data Status, PDU Session Status, Accepted PDU Session Status, NAS Message Container.

[0121] Service Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the service accept message: PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0122] Service Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the service rejection 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 the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the Configuration Update Command message: Configuration update instruction, 5G-GUTI, TAI list, allowed NSSAI, service area list, network full name, network short name, local time zone, universal time and local time zone, network daylight saving time, LADN information, MICO instruction, network slicing instruction, configured NSSAI, rejected NSSAI, operator defined access category definition, SMS instruction, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion instruction, 5GS registration result, aborted 5G-S-TMSI configuration, additional configuration instruction, and extended rejected NSSAI.

[0124] Configuration Update Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be taken together in the Configuration Update Complete message: Configuration update complete message identification information.

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

[0126] The UE 3 may, for example, support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). UE3 may be, for example, an item of equipment and / or energy-related machinery for production or manufacturing (e.g., equipment or machinery such as 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; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems for any of the foregoing equipment or machines).

[0127] The UE 3 may be, for example, an item of transportation equipment (e.g., transportation equipment such as railcars; automobiles; motorcycles; bicycles; trains; buses; carts; rickshaws; ships or other watercraft; aircraft; rockets; satellites; drones; balloons, etc.). The UE 3 may be, for example, an information and communication equipment item (eg, information and communication equipment such as electronic computers and related equipment; communications and related equipment; electronic components, etc.). The UE3 may be, for example, a refrigerator, a refrigerator application product, a goods and / or service industry equipment item, a vending machine, an automated service machine, an office machine, a consumer electronic device and an electronic appliance (e.g., consumer appliances such as audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related appliances; vacuum cleaners, etc.).

[0128] The UE 3 may be, for example, an electrical application system or equipment (eg, an electrical application system or equipment such as an X-ray system; a particle accelerator; a radioisotope equipment; a sonic equipment; an electromagnetic application equipment; an electrical power application equipment, etc.). The UE3 may be, for example, an electronic lamp, lighting fixture, measuring equipment, analyzer, tester, or surveying or sensing equipment (e.g., surveying or sensing equipment such as smoke detectors; motion sensors; radio frequency tags, etc.), a wristwatch or watch, inspection equipment, optical devices, medical equipment and / or systems, weapons, cutlery items, 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, electrical measuring instrument)).

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

[0130] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, etc. that enable these devices to collect and exchange data with each other and with other communicating devices. IoT devices may comprise automated machines that follow software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or inactive for long periods of time. 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 appreciated 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 will be appreciated that an IoT device may also be referred to as a Machine-Type Communication (MTC) device or a Machine-to-Machine (M2M) communication device or a Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0132] The UE 3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device). The UE3 may be an automobile, or a connected car, or an autonomous automobile, or a vehicle device, or a motorcycle, or a V2X (Vehicle to Everything) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-roadside communication module, a vehicle-to-pedestrian communication module, and a vehicle-to-network communication module).

[0133] <(R)AN node> FIG. 8 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station (e.g., an LTE "eNB," a 5G "gNB," a 5G Beyond base station, or a 6G base station). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from connected UE(s) 3 via one or more antennas 52, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls operation of the (R)AN node 5 in accordance with software stored in memory 55. 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 software includes, among other things, an operating system 551 and a communications 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 (for example). 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), particularly those related to connection establishment and maintenance, such as Radio Resource Control (RRC) connection establishment and other RRC messages, NG Application Protocol (NGAP) messages (i.e., messages based on the N2 reference point), and Xn Application Protocol (XnAP) messages (i.e., messages based on 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, RAN, (R)AN, etc.

[0136] <System Overview of (R)AN Node 5 Based on the 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 aspects, the units may be combined. For example, the RU 60 may be combined with the DU 61 as a combined / combined unit, and the DU 61 may be combined with the CU 62 as a combined / combined unit. Any functionality described in the description of a unit (e.g., one of the RU 60, DU 61, and CU 62) may be implemented in the combined / combined unit. Furthermore, the CU 62 may be separated into two functional units, such as a CU Control Plane (CP) and a CU User Plane (UP). The CU CP performs the control plane function in the (R)AN node 5. The CU UP performs the user plane function in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface “E1.”

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

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

[0140] <Radio Unit (RU)> FIG. 10 is a block diagram illustrating the main components of an exemplary RU 60, e.g., a base station (eNB for LTE, gNB for 5G, 5G Beyond base station, 6G base station). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from connected UE(s) 3 via one or more antennas 602, and to transmit signals to and receive signals from other network nodes or units (directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 according to software stored in memory 605. The software may be pre-installed in the memory 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 6051 and a communications control module 6052 having at least a transceiver control module 60521.

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

[0142] The controller 604, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation. The RU 60 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As mentioned above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any function in the description of the RU 60 can be implemented in the integrated / combined unit.

[0143] <Distributed Unit (DU)> FIG. 11 is a block diagram illustrating the main components of an exemplary DU 61, e.g., a DU section of a base station (e.g., an LTE "eNB," a 5G "gNB," a 5G Beyond base station, or a 6G base station). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including the RU 60) via a network interface 612. A control unit 613 controls the operation of the DU 61 in accordance with software stored in memory 614. The software may be pre-installed in memory 614 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 6141 and a communications 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 / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0144] The DU 61 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As mentioned above, the RU 60 can be integrated / combined with the DU 61 or the CU 62 as an integrated / combined unit. Any function described for the DU 61 can be implemented in the integrated / combined unit.

[0145] <Centralized Unit (CU)> FIG. 12 is a block diagram illustrating the main components of an exemplary CU 62, e.g., a CU unit of a base station (e.g., an LTE "eNB," a 5G "gNB," a 5G Beyond base station, or a 6G base station). As shown, the device includes a transceiver circuit 621 operable to transmit signals to and receive signals from other nodes or units (including the DU 61) via a network interface 622. A control unit 623 controls the operation of the CU 62 in accordance with software stored in memory 624. The software may be pre-installed in memory 624 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 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0146] CU62 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As mentioned above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any function in the description of the CU 62 can be implemented in the integrated / combined unit.

[0147] <amf> 13 is a block diagram illustrating the main components of the AMF 70. As shown, the device includes a transceiver circuit 701 operable to transmit signals to and receive signals from other nodes (including UE 3, NSSF 76) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in memory 704. The software may be pre-installed in memory 704 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 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signaling between the AMF 70 and other nodes, such as the UE 3 (e.g., via the (R)AN node 5) and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages related to access and mobility management procedures (for the UE 3) (e.g., registration request messages and associated response messages).

[0148] The AMF 70 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). The AMF 7001 and the AMF 7002 may have the same components as the AMF 70.

[0149] <pcf> 14 is a block diagram illustrating the main components of the PCF 73. As shown, the device includes a transceiver circuit 731 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 according to software stored in a memory 734. The software may be pre-installed in the 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 communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for processing (generating / sending / receiving) signaling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE3) related to policy management procedures (for example, HTTP RESTful methods based on service-based interfaces).

[0150] The PCF 73 may support a non-public network (NPN), which may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). The PCF 7301 and the PCF 7302 may have the same components as the PCF 73.

[0151] <ausf> FIG. 15 is a block diagram illustrating the main components of the AUSF 74. As shown, the device includes a transceiver circuit 741 operable to transmit signals to and receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the AUSF 74 according to software stored in a memory 744. The software may be pre-installed in the 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 processing (generating / sending / receiving) signaling between the AUSF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (for UE3) related to policy management procedures (for example, HTTP RESTful methods based on service-based interfaces).

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

[0153] <udm> 16 is a block diagram illustrating the major components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in memory 754. The software may be pre-installed in memory 754 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 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) related to mobility management procedures (for the UE 3).

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

[0155] <nssf> 17 is a block diagram illustrating the major components of the NSSF 76. As shown, the device includes a transceiver circuit 761 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NSSF 76 in accordance with software stored in memory 764. The software may be pre-installed in memory 764 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 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signaling between the NSSF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) related to mobility management procedures (for the UE 3).

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

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

[0158] <Modifications and Alternatives>

[0033] Having described detailed embodiments above, those skilled in the art will appreciate that several modifications and alternatives can be made to the above embodiments while still benefiting from the disclosure embodied therein. By way of example only, some of these alternatives and modifications are now described.

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

[0160] Each control unit may comprise 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) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers and / or timers, etc.

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

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

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

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

[0165] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and a system, and therefore may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0166] It will be understood that each block of the block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to create a machine such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, cause means to perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can 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 connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0168] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the 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 shown and described in detail with reference to exemplary embodiments thereof, 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 without departing from the spirit and scope of the present disclosure as defined herein. 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 from Indian Patent Application No. 202211051126 filed on September 7, 2022, the disclosure of which is incorporated herein by reference in its entirety.

[0171] <Additional Notes> The exemplary aspects disclosed above can be explained in whole or in part as follows, but are not limited to the following:

[0172] (Appendix 1) A User Equipment (UE) including a Mobile Termination (MT) and a User Services Identity Module (USIM), a transmitter configured to send a registration request message to an Access and Mobility Management Function (AMF) when an operator-controlled signal threshold per access technology is not configured on the USIM or is not applied by the UE; a receiver configured to receive a registration acceptance message from the AMF, the registration acceptance message including information indicating an operator-controlled signal threshold for each access technology; A user device comprising:

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

[0174] (Appendix 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. 3. A user device as described in Supplementary Note 2.

[0175] (Appendix 4) The MT stores information received from the AMF indicating the operator-controlled signal thresholds for each access technology in a non-volatile memory of the USIM or the UE; 10. A user device as described in Supplementary Note 1.

[0176] (Appendix 5) the processor performs cell selection procedures, cell reselection procedures, and Public Land Mobile Network (PLMN) selection procedures by using the information indicating operator-controlled signal thresholds for each access technology; 10. A user device as described in Supplementary Note 1.

[0177] (Appendix 6) a receiver configured to receive a registration request message from a User Equipment (UE); a transmitter configured to transmit a registration accept message to the UE, the registration accept message including information indicating a signal threshold for each access technology, the information being received from a Unified Data Management (UDM); An Access and Mobility Management Function (AMF) comprising:

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

[0179] (Appendix 8) the first request message includes first information, second information, and, if the first information indicates that the UE supports the SENSE function, third information; the first request message includes 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 capability to transfer information related to the Signal Level Enhanced Network Selection (SENSE) function to the UE by using a Steering Of Roaming (SOR) mechanism; Access and mobility management functions as described in Appendix 7.

[0180] (Appendix 9) The first request message includes a Nudm_UECM_Registration request message; The first response message includes a Nudm_UECM_Registration response message; Access and mobility management functions as described in Appendix 7.

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

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

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

[0184] (Appendix 13) the transmitter sends to an Authentication Server Function (AUSF) a third request message including information indicating per-access-technology operator-controlled signal thresholds to protect the information indicating per-access-technology operator-controlled signal thresholds; the receiver receives from the AUSF a third response message including protected information indicating an operator-controlled signal threshold per access technology, the protected information being protected by the AUSF; Integrated data management as described in Appendix 10.

[0185] (Appendix 14) 1. A method in a user equipment (UE) including a Mobile Termination (MT) and a User Services Identity Module (USIM), comprising: sending a registration request message to an Access and Mobility Management Function (AMF) if an operator-controlled signal threshold per access technology is not configured on the USIM or is not applied by the UE; receiving a registration acceptance message from the AMF, the registration acceptance message including information indicating a signal threshold for each access technology; A method for a user device.

[0186] (Appendix 15) 1. A method in an Access and Mobility Management Function (AMF), comprising: receiving a registration request message from a user equipment (UE); sending a registration accept message to the UE, the registration accept message including information indicating a signal threshold for each access technology, the information being received from a Unified Data Management (UDM); Methods for access and mobility management functions.

[0187] (Appendix 16) 1. A method in Unified Data Management (UDM), comprising: receiving a first request message from an Access and Mobility Management Function (AMF); sending a second request message to a Steering Of Roaming Application Function (SoR-AF); receiving a second response message from the SoR-AF, the second response message including information indicating an operator-controlled signal threshold for each access technology; transmitting a first response message including information indicating the operator-controlled signal thresholds for each access technology received from the SoR-AF; Integrated data management methods. [Explanation of symbols]

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

Claims

1. A User Equipment (UE) including a Mobile Termination (MT) and a User Services Identity Module (USIM), a transmitter configured to send a registration request message to an Access and Mobility Management Function (AMF) if a per access technology signal threshold is not configured on the USIM or is not applied by the UE; and a receiver configured to receive, from the AMF, a registration accept message including information indicating a signal threshold for each access technology; A user device comprising:

2. the registration request message includes a user ID, first information, and second information; the first information indicates whether the UE supports a Signal Level Enhanced Network Selection (SENSE) feature; the second information indicating the access technologies supported by the UE. The user device of claim 1 .

3. The access technologies include NB-IoT, GERAN EC-GSM-IoT, E-UTRA Category M1, E-UTRA Category M2, Wi-Fi, and New Radio (NR) technologies; 3. The user device of claim 2.

4. The MT stores the information received from the AMF indicating the signal threshold for each access technology in the USIM or a non-volatile memory of the UE. The user device of claim 1 .

5. a processor for performing cell selection, cell reselection, and Public Land Mobile Network (PLMN) selection procedures by using the information indicating signal thresholds for each access technology; The user device of claim 1 .

6. a receiver configured to receive a registration request message from a User Equipment (UE); a transmitter configured to transmit a registration accept message to the UE, the registration accept message including information indicating a signal threshold for each access technology, the information being received from a Unified Data Management (UDM); An Access and Mobility Management Function (AMF), comprising:

7. the receiver receives the registration request message from the UE, the registration request message including a UE-ID, first information, and second information; the first information indicates whether the UE supports a Signal Level Enhanced Network Selection (SENSE) feature; the second information indicating access technologies supported by the UE; the transmitter sends a first request message to the UDM based on the first information and the second information; the receiver receives a first response message from the UDM, the first response message including information indicating a signal threshold for each of the access technologies; the transmitter sends the registration accept message to the UE, the registration accept message including the information indicating a signal threshold for each access technology. The access and mobility management function of claim 6.

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, 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 capability to transfer information related to a Signal Level Enhanced Network Selection (SENSE) function to the UE by using a Steering Of Roaming (SOR) mechanism; The access and mobility management function of claim 7.

9. the first request message includes a Nudm_UECM_Registration request message; The first response message includes a Nudm_UECM_Registration response message. The access and mobility management function of claim 7.

10. a receiver configured to receive a first request message from an Access and Mobility Management Function (AMF); a transmitter configured to send a second request message to a Steering Of Roaming Application Function (SoR-AF); Equipped with the receiver receives a second response message from the SoR-AF, the second response message including information indicating a signal threshold for each access technology; The transmitter sends a first response message to the AMF, the first response message including the information indicating a signal threshold for each access technology. Unified Data Management (UDM).

11. The transmitter sends the first response message to the AMF in response to the first request message received from the AMF, the first response message including the information indicating the signal threshold for each access technology. The integrated data management of claim 10.

12. the first request message includes a Nudm_UECM_Registration request message; the first response message includes a Nudm_UECM_Registration response message; the second request message comprises an Nsoraf_SoR_Get request message; the second response message comprises an Nsoraf_SoR_Get response message; The integrated data management of claim 10.

13. the transmitter sends to an Authentication Server Function (AUSF) a third request message including the information indicating per-access technology signal thresholds to protect the information indicating per-access technology signal thresholds; the receiver receives from the AUSF a third response message including protected information indicating a signal threshold for each access technology, the protected information being protected by the AUSF; The integrated data management of claim 10.

14. 1. A method in a user equipment (UE) including a Mobile Termination (MT) and a User Services Identity Module (USIM), comprising: If a per-access technology signal threshold is not configured on the USIM or is not applied by the UE, sending a registration request message to an Access and Mobility Management Function (AMF); receiving a registration accept message from the AMF, the registration accept message including information indicating a signal threshold for each access technology; A method for a user device.

15. 1. A method in an Access and Mobility Management Function (AMF), comprising: receiving a registration request message from a user equipment (UE); sending a registration accept message to the UE including information indicating signal thresholds per access technology, the information being received from a Unified Data Management (UDM); Methods for access and mobility management functions.

16. 1. A method in Unified Data Management (UDM), comprising: receiving a first request message from an Access and Mobility Management Function (AMF); sending a second request message to a Steering Of Roaming Application Function (SoR-AF); receiving a second response message from the SoR-AF, the second response message including information indicating a signal threshold for each access technology; transmitting a first response message including the information indicating the signal thresholds for each of the access technologies received from the SoR-AF; Integrated data management methods.

Images