Method in a user equipment (UE), method in an access and mobility management function (AMF), method in a unified data management (UDM), UE, amf and udm

Abstract

Aspects of the disclosure include a method of a user equipment (UE). The method includes communicating with a communication device. The method comprises: receiving first signal threshold information from a communication device; and performing PLMN selection based on the first signal threshold information.

Description

Technical Field

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

[0002] According to 3GPP proposal SP-211068 [2], 3GPP defined a new feature in 3GPP Release 18 called Signal Level Enhanced Network Selection. This feature solves the problem of VPLMN selection when the IoT device is not on its home network. There are many cases where the IoT device is not in the home network. For example, the module of the IoT device is deployed in a country other than the country where the USIM was provided, or because a global USIM is used for IoT use cases. Summary of the invention

[0003] Technical issues

[0004] The issues of VPLMN selection using IoT devices are summarized as follows.

[0005] - During the initial steps of selecting a network after switching on or recovering from a coverage loss and during all steps of periodic reselection, the signal levels of available cells are not taken into account. For cell reselection, only the cell selection criteria as broadcasted by the PLMN and the priority of the network are taken into account.

[0006] - This results in the UE selecting or staying on a network with poor coverage in a particular place. This happens because the UE selects a PLMN with a higher priority, while other PLMNs with lower priority may provide much better local coverage. For typical consumer UEs this is not a problem (due to mobility, conditions are changing rapidly and there are users who are aware of the problem and can react, for example, by slightly changing location or manually selecting another PLMN). This is the expected behavior as part of roaming guidance and avoids frequent changes of networks. But for stationary devices without user supervision this can be a problem.

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

[0008] Although the requirements for the signal level enhanced network selection feature are defined in 3GPP TS 22.011 [6], there is no mechanism defined in any 3GPP specification in the 3GPP specification.

[0009] For example, 3GPP TS22.011 [6] defines requirements for the signal level enhanced network selection feature as follows.

[0010] - For UEs supporting any or a combination of NB-IoT, GERAN EC-GSM-IoT and E-UTRA categories M1 or M2, the 5G system shall support a mechanism with operator-controlled signal thresholds per access technology on the USIM for network selection. The signal threshold is specific to a certain access technology and shall apply to all PLMNs with the corresponding access technology combination.

[0011] In order to comply with this requirement, many aspects are taken into consideration.

[0012] For example, there must be a mechanism that enables secure transfer of information used for operator-controlled signal thresholds per access technology from the home operator to the USIM of the IoT device. If information used 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 so that the IoT UE stays in that VPLMN. In this case, the intended VPLMN selection cannot be achieved. As a result, the IoT UE stays in that VPLMN and suffers from poor coverage.

[0013] For example, it is unclear how the information used by the operator to control the signal threshold is structured. There are many radio aspects that have an impact on stable communication between IoT UE and the network. For example, signaling strength, signal quality, interference level, and so on. 3GPP must define the structure of the information used by the operator to control the signal threshold.

[0014] Solutions for solving problems

[0015] The present disclosure therefore seeks to provide methods and associated apparatus for solving or at least alleviating (at least some of) the problems set out above.

[0016] In one aspect, the present disclosure provides a user equipment (UE), including a mobile terminal (MT) and a user service identity module (USIM), wherein the UE includes:

[0017] a transmitter configured to transmit a registration request message to an access and mobility management function, i.e. AMF, if a signal threshold per access technology is not set on the USIM or applied by the UE; and

[0018] A receiver configured to receive a registration accept message from the AMF, the registration accept message comprising information indicating a signal threshold according to an access technology.

[0019] In one aspect, the present disclosure provides an access and mobility management function, i.e., AMF, including:

[0020] a receiver configured to receive a registration request message from a user equipment (UE); and

[0021] A transmitter is configured to transmit a registration accept message to the UE, wherein the registration accept message includes information indicating a signal threshold according to an access technology, wherein the information is received from a unified data management (UDM).

[0022] In one aspect, the present disclosure provides a unified data management (UDM), including:

[0023] a receiver configured to receive a first request message from an access and mobility management function, i.e., an AMF;

[0024] a transmitter configured to transmit a second request message to a roaming steering application function, i.e., SoR-AF,

[0025] The receiver is configured to receive a second response message from the SoR-AF, the second response message comprising information indicating a signal threshold according to an access technology, and

[0026] The transmitter is configured to transmit a first response message to the AMF, the first response message including information indicating a signal threshold according to an access technology.

[0027] In one aspect, the present disclosure provides a method in a user equipment (UE), wherein the UE includes a mobile terminal (MT) and a user service identity module (USIM), the method comprising:

[0028] In case the signal threshold per access technology is not set on the USIM or applied by the UE, transmitting a registration request message to an access and mobility management function, i.e. AMF; and

[0029] A registration accept message is received from the AMF, the registration accept message including information indicating a signal threshold according to an access technology.

[0030] In one aspect, the present disclosure provides a method in an access and mobility management function (AMF), the method comprising:

[0031] receiving a registration request message from a user equipment (UE); and

[0032] A registration accept message is transmitted to the UE, the registration accept message including information indicating a signal threshold according to an access technology, the information being received from a unified data management (UDM).

[0033] In one aspect, the present disclosure provides a method in unified data management (UDM), the method comprising:

[0034] receiving a first request message from an access and mobility management function, i.e., AMF;

[0035] Transmitting a second request message to a roaming steering application function, i.e., SoR-AF;

[0036] receiving a second response message from the SoR-AF, the second response message comprising information indicating a signal threshold according to an access technology; and

[0037] A first response message is transmitted, the first response message including information received from the SoR-AF indicating a signal threshold according to an access technology.

[0038] Advantageous Effects of the Invention

[0039] According to the present disclosure, a method of UE, a method of AMF, a method of UDM, UE, AMF and UDM are provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The foregoing and further objects, features, and advantages of the present subject matter will become apparent from the following description of exemplary embodiments with reference to the accompanying drawings, wherein like reference numerals are used to represent like elements.

[0041] It is to be noted, however, that the appended drawings, together with reference numerals, illustrate only typical embodiments of the present subject matter and are therefore not to be considered limiting of its scope, for the subject matter may admit to other equally effective embodiments.

[0042] Figure 1 is a signaling diagram of a first example of the first aspect.

[0043] Figure 2 is a signaling diagram of a first example of the second aspect.

[0044] Figure 3 It is the existing PLMN selection diagram in 3GPP TS23.122.

[0045] Figure 4 This is a processing diagram in a UE of a second example for the second aspect.

[0046] Figure 5 This is a processing diagram in a UE of a third example for the second aspect.

[0047] Figure 6 is a diagram illustrating an overview of the system.

[0048] Figure 7 is a block diagram of an exemplary UE.

[0049] Figure 8 is a block diagram of an example (R)AN node.

[0050] Fig. 9 is a diagram illustrating a system overview of an (R)AN node based on an O-RAN architecture.

[0051] Fig.10 is a block diagram of an example RU.

[0052] Fig.11 is a block diagram of an example DU.

[0053] Fig.12 is a block diagram of an example CU.

[0054] Fig.13 is a block diagram illustrating AMF.

[0055] Fig.14 is a block diagram illustrating a PCF.

[0056] Fig.15 is a block diagram illustrating an example of AUSF.

[0057] Fig.16 is a block diagram illustrating the UDM.

[0058] Fig.17 is a block diagram illustrating an example of NSSF. DETAILED DESCRIPTION

[0059] <Abbreviation>

[0060] For the purpose of this document, the abbreviations given in 3GPP TR 21.905 [1] and below apply. Abbreviations defined in this document take precedence over the definition of the same abbreviation (if any) in 3GPP TR 21.905 [1].

[0061] 4G-GUTI 4G Globally Unique Temporary UE Identifier

[0062] 5GC 5G Core Network

[0063] 5GLAN 5G Local Area Network

[0064] 5GS 5G System

[0065] 5G-AN 5G Access Network

[0066] 5G-AN PDB 5G access network packet delay budget

[0067] 5G-EIR 5G-Equipment Identification Register

[0068] 5G-GUTI 5G Globally Unique Temporary Identifier

[0069] 5G-BRG 5G Broadband Home Gateway

[0070] 5G-CRG 5G Cable Home Gateway

[0071] 5G GM 5G Master Clock

[0072] 5G-RG 5G Home Gateway

[0073] 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier

[0074] 5G VN 5G Virtual Network

[0075] 5QI 5G QoS Identifier

[0076] AF Application Function

[0077] AMF Access and Mobility Management Function

[0078] AMF-G Geographically Selected Access and Mobility Management Function

[0079] AMF-NG Non-geo-selective Access and Mobility Management Function

[0080] ANDSF Access Network Discovery and Selection Function

[0081] ARFCN Absolute Radio Frequency Channel Number

[0082] AS Access Layer

[0083] ATSSS access service guidance, switching, and splitting

[0084] ATSSS-LL ATSSS Low Level

[0085] AUSF authentication server function

[0086] AUTN Authentication Token

[0087] BCCH Broadcast Control Channel

[0088] BMCA Best Master Clock Algorithm

[0089] BSF binding support function

[0090] CAG Closed Access Group

[0091] CAPIF 3GPP Northbound API Common API Framework

[0092] CHF billing function

[0093] CN PDB Core Network Packet Delay Budget

[0094] CP Control Plane

[0095] DAPS Dual Active Protocol Stack

[0096] DL Downlink

[0097] DN Data Network

[0098] DNAI DN Access Identifier

[0099] DNN data network name

[0100] DRX Discontinuous Reception

[0101] DS-TT Device-side TSN Converter

[0102] ePDG Evolved Packet Data Gateway

[0103] EBI EPS bearer logo

[0104] EPS Evolved Packet System

[0105] EUI Extended Unique Identifier

[0106] FAR forwarding action rule

[0107] FN-BRG Fixed Broadband RG

[0108] FN-CRG Fixed Network Cable RG

[0109] FN-RG Fixed Network RG

[0110] FQDN Fully Qualified Domain Name

[0111] GFBR Guaranteed Streaming Bit Rate

[0112] GMLC Gateway Mobile Location Center

[0113] GPSI General Public Subscription Identifier

[0114] GUAMI Globally Unique AMF Identifier

[0115] GUTI Globally Unique Temporary UE Identifier

[0116] HPLMN Home Public Land Mobile Network

[0117] HR Home Router (Roaming)

[0118] IAB Integration Access and Postbacks

[0119] IMEI / TAC IMEI type allocation code

[0120] IPUPS PLMN Inter-UP Security

[0121] I-SMF Intermediate SMF

[0122] I-UPF Intermediate UPF

[0123] LADN Local Area Data Network

[0124] LBO Local Flow Offload (Roaming)

[0125] LMF Location Management Function

[0126] LoA Automation Level

[0127] LPP LTE Positioning Protocol

[0128] LRF location search function

[0129] MCC Mobile Country Code

[0130] MCX Mission Critical Services

[0131] MDBV Maximum data burst volume

[0132] ME Mobile Devices

[0133] MFBR Maximum Streaming Bit Rate

[0134] MICO Only mobile terminals initiate connections

[0135] MITM

[0136] MNC Mobile Network Code

[0137] MPS Multimedia Priority Service

[0138] MPTCP Multipath TCP Protocol

[0139] MT Mobile Terminal

[0140] N3IWF Non-3GPP Interworking Function

[0141] N3GPP Non-3GPP Access

[0142] N5CW WLAN side does not have 5G capability

[0143] NAI Network Access Identifier

[0144] NAS Non-Access Stratum

[0145] NEF Network Exposure Function

[0146] NF Network Function

[0147] NGAP Next Generation Application Protocol

[0148] NID Network Identifier

[0149] NPN Non Public Network

[0150] NR New Radio

[0151] NSAG Network Slicing Access Layer Group

[0152] NRF Network Repository Features

[0153] NSI ID Network Slice Instance Identifier

[0154] NSSAA Network Slice Specific Authentication and Authorization

[0155] NSSAAF Network Slice Specific Authentication and Authorization Function

[0156] NSSAI Network Slice Selection Assistance Information

[0157] NSSF network slice selection function

[0158] NSSP network slice selection strategy

[0159] NSSRG Network Slicing Simultaneous Registration Group

[0160] NW-TT Network-side TSN converter

[0161] NWDAF network data analysis function

[0162] PCF Policy Control Function

[0163] PCO Protocol Configuration Options

[0164] PDB Packet Delay Budget

[0165] PDR Group Detection Rules

[0166] PDU Protocol Data Unit

[0167] PEI Persistent Equipment Identifier

[0168] PER Packet Error Rate

[0169] PFD Packet Flow Description

[0170] PLMN Public Land Mobile Network

[0171] PNI-NPN Public Network Integrated Non-Public Network

[0172] PPD Paging Policy Differential

[0173] PPF Paging Process Flag

[0174] PPI Paging Policy Indicator

[0175] PSA PDU Session Anchor

[0176] PTP Precision Time Protocol

[0177] QFI QoS Flow Identifier

[0178] QoE Quality of Experience

[0179] RACS Radio Capability Signaling Optimization

[0180] (R)AN (Radio) Access Network

[0181] RAT Radio Access Technology

[0182] RG Home Gateway

[0183] RIM Remote Interference Management

[0184] RQA Reflective QoS Attribute

[0185] RQI Reflective QoS Indicator

[0186] RSN Redundant Sequence Number

[0187] RSRP Reference Signal Received Power

[0188] RSRQ Reference Signal Received Quality

[0189] SANR Standalone New Radio

[0190] SBA Service-Based Architecture

[0191] SBI Service-Based Interface

[0192] SCP Service Communication Proxy

[0193] SD Slice Specifier

[0194] SEAF safety anchor function

[0195] SENSE signal level enhanced network selection

[0196] SEPP Security Edge Protection Proxy

[0197] SIB System Information Block

[0198] SINR Signal to Interference and Noise Ratio

[0199] SMF session management functions

[0200] SMSF Short Message Service Function

[0201] SN Serial Number

[0202] SN Name Service Network Name

[0203] SNPN Standalone Non-Public Network

[0204] S-NSSAI Single Network Slice Selection Auxiliary Information

[0205] SOR Roaming Guidance

[0206] SSC Session and Service Continuity

[0207] SSCMSP Session and Service Continuity Mode Selection Policy

[0208] SST Slice / Service Type

[0209] SUCI Subscription Hidden Identifier

[0210] SUPI Subscription Persistent Identifier

[0211] SV Software Version

[0212] TMSI Temporary Mobile Subscriber Identity

[0213] TNAN Trusted Non-3GPP Access Network

[0214] TNAP Trusted Non-3GPP Access Point

[0215] TNGF Trusted Non-3GPP Gateway Function

[0216] TNL Transport Network Layer

[0217] TNLA Transport Network Layer Association

[0218] TSC Time Sensitive Communications

[0219] TSCAI TSC Auxiliary Information

[0220] TSN Time Sensitive Network

[0221] TSN GM TSN Master Clock

[0222] TSP Business Strategy

[0223] TT TSN Converter

[0224] TWIF Trusted WLAN Intercommunication Function

[0225] UCMF UE radio capability management function

[0226] UDM Unified Data Management

[0227] UDR Unified Data Repository

[0228] UDSF unstructured data storage function

[0229] UE User Equipment

[0230] UL Uplink

[0231] UL CL Uplink Classifier

[0232] UPF User Plane Function

[0233] UPSI UE Policy Part Identifier

[0234] URLLC Ultra-Reliable Low Latency Communications

[0235] URRP-AMF UE reachability request parameters of AMF

[0236] URSP UE routing strategy

[0237] USIM User Service Identity Module

[0238] VID VLAN identifier

[0239] VLAN Virtual Local Area Network

[0240] VPLMN Visited Public Land Mobile Network

[0241] W-5GAN Wired 5G Access Network

[0242] W-5GBAN Wired BBF Access Network

[0243] W-5GCAN Wired 5G Cable Access Network

[0244] W-AGF Wired Access Gateway Function

[0245] <Definition>

[0246] For the purpose of this document, the terms and definitions given in 3GPP TR 21.905 [1] and below apply. Terms defined in this document take precedence over the definition of the same term (if any) in 3GPP TR 21.905 [1].

[0247] Citation List

[0248] Non-patent literature

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

[0250] [2] SP-211068: https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGS_93E_Electronic_2021_09 / Docs / SP-211068.zip

[0251] [3] 3GPP TS23.501: “System architecture for the 5G System (5GS)”. V17.5.0 (2022-06)

[0252] [4] 3GPP TS23.502: “Procedures for the 5G System (5GS)”. V17.5.0 (2022-06)

[0253] [5] 3GPP TS23.503: “Policy and charging control framework for the 5G System (5GS) Stage 2”. V17.5.0 (2022-06)

[0254] [6] 3GPP TS22.011: “Service accessibility”. V18.3.0 (2022-06)

[0255] [7] 3GPP TS24.501: “Non-Access-Stratum (NAS) protocol for 5G System (5GS) Stage 3”. V17.7.1 (2022-06)

[0256] [8] 3GPP TS23.122: “Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode”. V17.7.1 (2022-06)

[0257] <Overall>

[0258] Those skilled in the art will appreciate that the elements in the drawings are illustrated for simplicity and may not necessarily be drawn to scale. Furthermore, one or more components of a device may have been represented in the drawings by conventional symbols with respect to the construction of the device, and the drawings may show only those specific details relevant to understanding aspects of the present disclosure so as not to obscure the drawings with details that would be readily apparent to those skilled in the art having the benefit of the description herein.

[0259] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the aspects illustrated in the accompanying drawings, and specific language will be used to describe these aspects. However, it will be understood that this is not intended to limit the scope of the present disclosure. Such changes and further modifications in the illustrated system and such further applications of the principles of the present disclosure that would normally occur to one skilled in the art will be construed as being within the scope of the present disclosure.

[0260] The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion such that a process or method that comprises a series of steps does not comprise only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or entities or subsystems or elements or structures or components preceded by "comprises ... a" do not exclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components without more constraints. The phrases "in an aspect," "in another aspect," and similar language that appear throughout this specification may, but do not necessarily, all refer to the same aspect.

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

[0262] In the following specification and claims, reference will be made to a number of terms which may be defined to have the following meanings: The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.

[0263] As used herein, information is associated with data and knowledge because data is meaningful information and represents values ​​attributed to parameters. Further knowledge means understanding of abstract or concrete concepts. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of the present disclosure. In addition to or in place of the system, other devices, systems, and configurations may be used to implement the aspects disclosed herein, and all such aspects are considered to be within the scope of the present disclosure.

[0264] The various aspects described below and the elements included in the various aspects can be implemented independently or in combination with each other. These aspects include novel features that are different from each other. Therefore, these aspects help to achieve the purpose or solve different problems from each other, and help to obtain different advantages from each other.

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

[0266] <Aspect 1>

[0267] This aspect discloses a mechanism that enables secure transfer of information used for operator controlled signal thresholds per access technology from the home operator to the USIM 35 installed in the UE 3 when the UE 3 roams to a VPLMN.

[0268] <First Example of the First Aspect>

[0269] When the information used for operator controlled signaling thresholds per access technology is not provided to UE 3, UE 3 initiates a registration procedure to extract information from the HPLMN using 5GS.

[0270] Figure 1 It is a registration process used to extract operator controlled signaling thresholds per access technology from the home network.

[0271] The following references Figure 1 To illustrate the detailed processing of the first example of the first aspect. Note that Figure 1 The MT 33 in indicates the mobile terminal part of the UE 3. The MT 33 may be the UE 3 which does not include the USIM 35.

[0272] Step 0. SoR AF 201 stores the information used for signal thresholds according to access technology in subscriber data.

[0273] The SoR AF 201 may store signal thresholds for NB-IoT, GERAN EC-GSM-IoT, Category M1 of E-UTRA, Category M2 of E-UTRA, and other access technologies.

[0274] The SoR AF 201 may also store the signal threshold for WiFi as a non-3GPP access.

[0275] Step 1. When the MT 33 in the UE 3 detects that the operator controlled signal threshold information per access technology is not provided to the USIM 35 or is not in the non-volatile memory in the UE 3, the UE 3 sends a registration request message to the AMF 70, which includes 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 for a parameter whose purpose is to indicate that the UE supports the operator controlled signal threshold feature per access technology indicates that the UE 3 supports the SENSE feature. The UE supported access technology parameter transmitted from the UE indicates one or more access technologies supported by the UE 3.

[0276] The access technologies supported by the UE may include indications to support NB-IoT, GERAN EC-GSM-IoT, Category M1 of E-UTRA, Category M2 of E-UTRA, and other access technologies (e.g., NR).

[0277] In one example, when the UE is configured from manual PLMN mode selection to automatic PLMN mode selection and finds that the operator controlled signal threshold per access technology is not configured, the UE will also initiate the registration procedure as defined in this step.

[0278] SENSE feature support may be another name, for example, SENSE information query, SENSE request or any other name indicating that the UE 3 requests to have SENSE related information from the AMF 70.

[0279] The UE supported access technology may be another name, for example, access technology or any other name used to indicate one or more access technologies supported by the UE 3.

[0280] Step 2. When AMF 70 receives the registration request message, AMF 70 sends a Nudm_UECM_Registration request message to UDM 75, which includes user ID, SENSE feature support, UE supported access technology and SoR for SENSE support. The SENSE feature support parameters and UE supported access technology are received in step 1. If AMF 70 does not receive a SENSE feature support indication from UE 3, AMF 70 recognizes that UE 3 does not support the SENSE feature, and AMF 70 neither includes SENSE feature support in the Nudm_UECM_Registration request message nor includes UE supported access technology in the Nudm_UECM_Registration request message. SoR for SENSE support indicates that AMF 70 has the capability to transmit SENSE related information to UE 3 using the SoR mechanism.

[0281] SENSE feature support may be another name, such as SENSE information query, SENSE request, or any other name indicating that the AMF 70 requests SENSE related information from the UDM 75.

[0282] The UE supported access technology may be another name, for example, access technology or any other name used to indicate one or more access technologies supported by the UE 3.

[0283] SoR for SENSE may be another name indicating that the AMF 70 has the capability to transmit SENSE related information to the UE 3 using the SoR mechanism.

[0284] Step 3. When the UDM 75 receives the Nudm_UECM_Registration request message including the user ID, SENSE feature support and UE supported access technologies and the SoR for SENSE support, the UDM 75 sends a Nsoraf_SoR_Get request message (or a new message or any existing message) including the user ID and SENSE feature support indication received in step 2 and the UE supported access technologies. SENSE feature support may be another name. For example, SENSE information query, SENSE request or any other name used to indicate that the UDM 75 requests to have SENSE related information from the SoR AF 201.

[0285] If the UDM 75 does not receive the SENSE feature support indication from the AMF 70, the UDM 75 assumes that the UE 3 does not support the SENSE feature and the UDM 75 does not send the Nsoraf_SoR_Get request message to the SoR-AF 201. If the UDM 75 does not receive the SoR for SENSE support from the AMF 70, the UDM 75 assumes that the AMF 70 does not support the SENSE feature and the UDM 75 does not send the Nsoraf_SoR_Get request message to the SoR-AF 201.

[0286] In one example, SENSE feature support may be interpreted by UDM 70 as AMF supporting SENSE feature. In this case, even if UDM 70 does not receive SoR for SENSE support from AMF 70, UDM 70 sends a Nsoraf_SoR_Get request message (new message or existing message) to SoR-AF 201.

[0287] The UE supported access technology may be another name, for example, access technology or any other name used to indicate one or more access technologies supported by the UE 3.

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

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

[0290] Step 6. When AUSF 74 receives the Nausf_SoRProtection request message including information used for signal thresholds according to access technology from UDM 75, AUSF 74 encrypts the information and AUSF 74 sends a Nausf_SoRProtection response message to UDM 75, which includes a SoR container containing the encrypted information used for signal thresholds according to access technology.

[0291] Step 7. When the UDM 75 receives the Nausf_SoRProtection response message from the AUSF 74, which includes the SoR container containing the encrypted information used for the signal threshold according to the access technology, the UDM 75 sends a Nudm_UECM_Registration response message to the AMF 70, which includes the SoR container containing the encrypted information used for the signal threshold according to the access technology. The UDM 75 may include an ACK indication in the Nudm_UECM_Registration response message.

[0292] A SOR container is defined as follows.

[0293]

[0294] The protected groups are defined as:

[0295] Access Technology Identifier 1 Signal quality or signal strength …Signal Threshold …… Access Technology Identifier 2 Signal quality or signal strength …Signal Threshold

[0296] Step 8. When the AMF 70 receives the Nudm_UECM_Registration response message (the Nudm_UECM_Registration response message includes the SoR container containing the encrypted information used for the signal threshold according to the access technology), the AMF 70 sends a registration acceptance message to the UE 3, the registration acceptance message including the SoR container containing the encrypted information used for the signal threshold according to the access technology. The AMF 70 may include an ACK indication in the registration acceptance message.

[0297] Step 9. When MT 33 in UE 3 receives a registration accept message from AMF 70 (the registration accept message includes a SoR transparent container containing encrypted information for signal thresholds per access technology), MT 33 decrypts the SoR transparent container to obtain information for signal thresholds per access technology. MT 33 either sends the information to USIM 35 or stores the information in a non-volatile memory of UE 3.

[0298] After MT 33 decrypts the information used for signal thresholds per access technology from the SoR transparent container, the NAS layer of UE 3 notifies the AS layer of UE 3 of the information used for signal thresholds per access technology. For example, the information used for signal thresholds per access technology may consist of a list of measured signal strengths (e.g., RSRP), measured signal qualities (e.g., RSRQ), and measured signal to noise interference (e.g., SINR) per access technology.

[0299] In case the MT 33 receives an invalid value for the access technology, the UE 3 ignores the value and does not store it in the USIM 35 and does not apply the threshold.

[0300] In one example, the UDM 75 sends a fixed value (eg, 0) for each access technology to disable a cell selection or reselection process based on a signal threshold per access technology. When the UE 3 receives this value, no cell selection or reselection process is applied for the access technology.

[0301] Step 10. In case UE 3 is requested to confirm the successful delivery of information used according to the signal threshold of the access technology, UE 3 sends a registration complete message to AMF 70.

[0302] Step 11. When AMF 70 receives the registration completion message from UE 3 and AMF 70 is requested by UDM 75 to confirm the successful delivery of the information used according to the signal threshold of the access technology to UE 3, AMF 70 sends a Nudm_SDM_Info message to UDM 75 so that UDM 75 can recognize the successful delivery of the information used according to the signal threshold of the access technology to UE 3.

[0303] In the present disclosure, the operator controlled signal threshold per access technology may be expressed by other terms (eg, signal threshold per access technology, signal quality threshold per access technology, threshold per access technology, and the like).

[0304] In the present disclosure, the user identity may be represented by a user ID or a UE ID.

[0305] <Variation 1 of the First Example of the First Aspect>

[0306] In one example, SoR AF 201 may be included in UDM 75. In this case, steps 3 and 4 are performed inside UDM 75.

[0307] <Variation 2 of the First Example of the First Aspect>

[0308] In one example, the UE 3 scans the available PLMNs at the location and sends a list of signal strengths or signal qualities or both (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 the location in a registration request message. In step 2, the AMF 70 sends the list of signal strengths or signal qualities or both to the UDM 75. The UDM 75 sends the list of received signal strengths or signal qualities or both 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 or signal qualities or both.

[0309] In one example, the list of signal strengths or signal qualities is integrity protected or encrypted and sent to the UDM 75 in a transparent container.

[0310] <Variation 3 of the First Example of the First Aspect>

[0311] In another example, the operator control signal threshold information per access technology may be configured in the AMF 70 directly or via OAM based on operator policy. Then, during registration of the UE 3 with the home PLMN, according to Figure 1 In steps 8 and 9 of , the operator controlled signal threshold information per access technology may be delivered by AMF 70 to UE 3. Alternatively, the operator controlled signal threshold information per access technology configured in AMF 70 may be delivered to UE 3 via a UE configuration update message at any time during connection of UE 3 with the home PLMN, or may be first delivered to UE 3 via paging UE 3 when UE 3 is in idle mode.

[0312] <Variation 4 of the First Example of the First Aspect>

[0313] In another example, according to 3GPP TS23.502[4] and 3GPP TS23.503[5], operator controlled signal threshold information per access technology may be defined as new rules for triggering cell selection / reselection or PLMN selection / reselection using UE 3 as part of the URSP rules for UE 3 in the PCF, and provided to UE 3 within the URSP provision within the UE policy information via the UE configuration update procedure.

[0314] <Variation 5 of the First Example of the First Aspect>

[0315] In another example, operator controlled signal threshold information per access technology may be provided by the AMF 70 to the UE 3 via OTA (Over the Air) DM (Device Management).

[0316] In another example, the UDM 75 may send the operator controlled signal threshold information per access technology in any existing message or new message defined between the UDM 75 and the AMF 70. When the AMF 70 receives the operator controlled signal threshold information per access technology, the AMF 70 sends the received operator controlled signal threshold information per access technology to the UE 3 in an existing NAS message or a new NAS message. When the UE 3 receives the operator controlled signal threshold information per access technology, the UE 3 sends an existing NAS message to the AMF indicating that the operator controlled signal threshold information per access technology has been received. When the AMF 70 receives the NAS message from the UE 3, it sends a message to the UDM 75 indicating that the operator controlled signal threshold information per access technology has been received at the UE 3. This transmission method of the operator controlled signal threshold information per access technology may be used when the UE 3 is registered in the HPLMN or an equivalent HPLMN.

[0317] <Variation 6 of the First Example of the First Aspect>

[0318] In another example, the operator controlled signal threshold per access technology may be defined by a service provider (e.g., when the mobile terminal belongs to a third-party service provider contracted with a signal threshold control PLMN). In this case, the operator controlled signal threshold information 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. Together with the provision of the operator controlled signal threshold per access technology, the service provider may provide additional information related to the validity of the provided threshold or its applicability per UE or per group of UEs, and the service provider may update the operator controlled signal threshold per access technology and the conditions for its applicability at any time.

[0319] <Variation 7 of the First Example of the First Aspect>

[0320] In one example, the AS layer of UE 3 provides the operator control signal threshold per access technology to NG-RAN in an existing RRC message or a new RRC message. When NG-RAN receives the operator control signal threshold per access technology from the AS layer of UE 3, NG-RAN stores the operator control signal threshold per access technology and selects the target cell in the handover process when the signal strength of the target cell is equal to or greater than the operator control signal threshold per access technology.

[0321] <Variation 8 of the First Example of the First Aspect>

[0322] In one example, the AMF 70 provides the operator control signal threshold per access technology to the NG-RAN in an existing NGAP message or a new NGAP message. When the NG-RAN receives the operator control signal threshold per access technology, the NG-RAN stores the operator control signal threshold per access technology and selects the target cell in the handover process when the signal strength of the target cell is equal to or greater than the operator control signal threshold per access technology.

[0323] <Variation 9 of the First Example of the First Aspect>

[0324] UE 3 sends a list of signal strengths per access technology type that UE 3 can receive and / or a list of signal strengths per PLMN that UE 3 can receive and / or a list of signal strengths of all best cells for each access technology that can be used for each available PLMN and the current UE location to UDM 75 via AMF 70 in a transparent and securely protected manner at any time (e.g., during the power-on process or during any NAS process). For example, UE 3 sends the list of signal strengths to AMF 70 through a registration request message or a registration complete message or in any NAS message. Then, AMF 70 sends the list of received signal strengths to UDM 75 in an existing message or a new message defined between AMF 70 and UDM 75. Upon receiving the list of signal strengths, UDM 75 can decide to update the operator-controlled signal threshold per access technology based on the value of the signal strength in the received list and the received current UE location.

[0325] For example, if the received signal strength for a specific access technology at the location of UE 3 is much lower than the operator controlled signal threshold for the access technology in UDM 75, UDM 75 lowers the threshold used for the operator controlled signal threshold for the access technology and uses the mechanism disclosed in the first aspect to update the newly defined threshold in UE 3.

[0326] <Variation 10 of the First Example of the First Aspect>

[0327] The UE 3 sends the current value of the stored threshold to the UDM via the AMF at any time (e.g. during the power-on procedure or during any NAS procedure). The current value of the stored threshold may be sent to the UDM 75 via the AMF 70 in a transparent and securely protected manner. If the UE 3 does not store the value of the stored threshold in either the USIM 35 of the UE 3 or in the ME memory of the UE 3, the UE 3 indicates to the UDM 75 that the UE 3 does not have the current value for the operator-specific threshold.

[0328] The UDM 75 may decide to send the operator controlled signal threshold per access technology to the UE 3 based on the current value of the threshold stored in the UE 3 or an indication from the UE 3 received.

[0329] For example, if the current value of the stored threshold received in the UE 3 is out of date, the UDM 75 updates the UE 3 with the latest operator control signal threshold for the access technology using the mechanism as disclosed in the first aspect.

[0330] <Variation 11 of the First Example of the First Aspect>

[0331] 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.

[0332] <Second Aspect>

[0333] This aspect discloses the following mechanisms: how UE 3 obtains information used for operator controlled signal thresholds according to access technology on 5GS, and how UE 3 uses this information for NB-IoT, GERAN EC-GSM-IoT and E-UTRA category M1 or M2.

[0334] <First Example of Second Aspect>

[0335] The first example of the second aspect discloses a method of how UE 3 obtains information used for operator-controlled signal thresholds according to access technology on 5GS, and how UE 3 uses the information for category M1 or M2 of NB-IoT, GERAN EC-GSM-IoT, and E-UTRA.

[0336] Figure 2 It is the UE behavior for SENSE feature. Figure 2 To illustrate the detailed processing of the first example of the second aspect. Note that Figure 2 The MT 33 in indicates the mobile terminal part of the UE 3. The MT 33 may be the UE 3 which does not include the USIM 35.

[0337] Step 1. Turn on the UE 3. Another use case in step 1 could be that a new SIM 35 is inserted into the UE 3, the UE 3 is initialized by a user, or any other situation for resetting the UE 3.

[0338] Another use case in step 1 could be recovery from coverage deficiency, periodic network selection attempts and roaming guidance.

[0339] Step 2. MT 33 queries USIM 35 whether USIM 35 maintains the information used for the signal threshold according to the access technology. MT 33 can indicate the access technology in the query message to obtain the signal threshold for the access technology. Access technologies include NB-IoT, GERAN EC-GSM-IoT, E-UTRA category M1, E-UTRA category M2 and other access technologies. Access technologies also include WiFi as non-3GPP access.

[0340] In case the information used for the signal thresholds per access technology is stored in a non-volatile memory in the UE 3, the MT 33 does not query the USIM 35. The UE 3 refers to the memory and proceeds to step 4.

[0341] Step 3. When the USIM 35 receives the query message in step 1, if the USIM 35 holds the information used for the signal threshold per access technology, the USIM 35 provides the information used for the signal threshold per access technology to the MT 33. Otherwise, the USIM 35 simply sends a negative message to the MT 33 or provides empty information used for the signal threshold per access technology.

[0342] Step 4. UE 3 checks the following conditions. If all conditions are met, UE 3 proceeds to step 5.

[0343] - UE 3 has the capability to handle the SENSE feature.

[0344] - The UE 3 does not keep information about the signal thresholds per access technology.

[0345] -UE 3 has the capability to access 5G. That is, UE 3 supports 5G NAS. UE 3 has the capability to connect to NR or e-URAN or any other RAT (e.g., WLAN, Wi-Fi, BBF access, cable access, optical access) that can connect to 5GC.

[0346] Step 5. Based on the check that took place in step 4, the UE 3 initiates a registration procedure as disclosed in the first example of the first aspect.

[0347] In one example, if there is a cell supporting UTRAN or E-UTRAN or GERAN or NR at the current location, UE 3 should select a cell supporting 5GS, even if the selected cell is not the best cell available at the location, or the selected cell does not belong to the last registered PLMN or the selected cell belongs to a PLMN that is not a higher preferred PLMN available at the location, and UE 3 should initiate a registration procedure on the selected cell of the PLMN to register with 5GS.

[0348] For example, assuming that PLMN 1, PLMN 2, and PLMN 3 are stored in the operator preferred PLMN list in the highest to lowest priority order (i.e., PLMN 1>PLMN 2>PLMN 3). At the current location, there is an E-UTRAN cell 1 belonging to PLMN 1 (which does not support connectivity to 5GS) and there is a cell 2 of the NG-RAN belonging to PLMN 2, then UE 3 should select cell 2 of PLMN 2 and initiate a registration procedure with PLMN 2 on cell 2.

[0349] Step 6. When the registration process in step 5 is successfully completed, UE 3 moves GSM-based GPRS, W-CDMA-based GPRS or EPS to access using access technologies such as NB-IoT, GERAN EC-GSM-IoT, and E-UTRA category M1 or M2.

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

[0351] In the present disclosure, the operator controlled signal threshold per access technology may be expressed by other terms (eg, signal threshold per access technology, signal quality threshold per access technology, threshold per access technology, and the like).

[0352] In the present disclosure, the user identity may be represented by a user ID or a UE ID.

[0353] <Second Example of the Second Aspect>

[0354] The second example of the second aspect discloses a method of how the UE 3 uses the signal threshold for PLMN selection. This example can be used at step 7 of the first example of the second aspect.

[0355] Figure 3 The existing PLMN selection diagram in 3GPP TS23.122 [8] is illustrated. This example discloses Figure 3 The following updates are processed in .

[0356] <First disclosure for updating process "Selecting registered PLMN">

[0357] Figure 4 It is a signaling measurement based on signal threshold. Figure 3 The process "Selecting a registered PLMN" in the upper left part of the figure has the following process flow: Figure 4 Replace with the process shown.

[0358] 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, then UE 3 has not Figure 3 The conventional behavior in UE 3 is to first look for the availability of the last registered PLMN in its location after switching on or after returning from a no-service state. Instead, UE 3 enters process 4002. Otherwise, UE 3 returns to follow Figure 3 The original process in .

[0359] Processing 4002. UE 3 extracts operator-controlled signal threshold information per access technology stored in USIM 35 in UE 3 or in non-volatile memory in UE 3 for the UE's radio access (i.e., the radio access to which the UE is tuned), and UE 3 extracts signal strength or signal quality or signal-to-noise interference measurements (e.g., RSRP (reference signal received power) or RSRQ (reference signal received quality) or SINR (signal-to-interference-plus-noise ratio)) for all cells of the UE's radio access in the UE's location.

[0360] 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 in the UE location on the same radio access is equal to or higher than the operator controlled signal threshold for the access technology, then UE 3 shall select the cell of that PLMN (i.e., UE 3 shall select the cell with the highest signal strength or the highest signal quality or the highest signal to noise ratio or a combination of the three belonging to any PLMN that UE 3 is allowed to select), and UE 3 shall select the cell from Figure 3 Otherwise, UE 3 shall return to point C of the PLMN selection diagram in the figure. Figure 3 The PLMN selection diagram in FIG. 1 starts from the beginning, that is, the PLMN selection according to the operator control signal threshold information of the access technology is not considered.

[0361] <Second disclosure for updating the process of "selecting PLMN">

[0362] for Figure 3 The processing immediately after connecting circle A and the processing immediately after connecting circle B in the above example are as follows: Figure 4 Replace with the process shown.

[0363] Process 4001. UE 3 checks whether UE 3 maintains the signal threshold information for the access technology to which UE 3 is tuned. If UE 3 maintains the signal threshold information for the access technology, proceed to process 4002. Otherwise, return to the original process.

[0364] Process 4002. UE 3 extracts the threshold for the tuned access technology and measures the signal.

[0365] Process 4003. If the measured signal quality is equal to or higher than the operator controlled signal threshold for the access technology, return to the original process. Otherwise, skip the original process and enter the next process as shown in "Try PLMN". In this case, the "Try PLMN" process does not initiate the registration process. The "Try PLMN" process only determines whether there are more PLMNs in the list. That is, enter the middle line under the "Try PLMN" process or the right line under the "Try PLMN" process.

[0366] <Third disclosure for updating the process of "selecting the first available and allowed PLMN in the list">

[0367] For the Figure 3 The lower process in the "select the first available and allowed PLMN in the list" is used as the following process flow Figure 4 Replace with the processing shown.

[0368] Process 4001. UE 3 checks whether UE 3 maintains the signal threshold information for the access technology to which UE 3 is tuned. If UE 3 maintains the signal threshold information for the access technology, proceed to process 3002. Otherwise, return to the original process.

[0369] Process 4002. UE 3 extracts the threshold for the tuned access technology and measures the signal.

[0370] Process 4003. If the measured signal quality is equal to or above the operator controlled signal threshold for the access technology, return to the original process. Otherwise, enter the middle line under the "On PLMN" process.

[0371] <Variation 1 of Second Example of Second Aspect>

[0372] In another example, the operator-controlled signal threshold information per access technology can be considered as an offset value, that is, the UE 3 should select a cell from another PLMN only if the difference in signal strength (e.g., RSRP) or signal quality (e.g., RSRQ) or signal-to-noise ratio between the current cell of the home PLMN and the cell from another PLMN is equal to or higher than the operator-controlled signal threshold per access technology to support the cell from another PLMN. In this case, the UE 3 should select a cell from the other PLMN and register with the other PLMN.

[0373] <Third Example of Second Aspect>

[0374] The third example of the second aspect discloses a method of how UE 3 determines the measured signal by using the signal threshold for PLMN selection. This example can be used at step 4003 of the second example of the second aspect.

[0375] Figure 5 The following is a flow chart showing how UE 3 determines the measured signal.

[0376] Process 5001. UE 3 measures the signal on the access technology.

[0377] Process 5002. UE 3 compares the received signal level with the RSRP as indicated by the operator controlled signal threshold for the access technology. If the received signal level is equal to or higher than the operator controlled signal threshold, proceed to process 5003. Otherwise, proceed to process 5006 and conclude that the SENSE based signaling check has failed.

[0378] Process 5003. UE 3 compares the received signal quality with the RSRQ as indicated by the operator controlled signal threshold for the access technology. If the measured signal quality is equal to or higher than the operator controlled signal threshold, proceed to process 5004. Otherwise, proceed to process 5006 and conclude that the SENSE based signaling check has failed.

[0379] Process 5004. UE 3 compares the received signal to interference plus noise ratio with the SINR as indicated by the operator controlled signal threshold for the access technology. If the measured signal to interference plus noise ratio is equal to or higher than the operator controlled signal threshold, proceed to process 5005 and conclude that the SENSE-based signaling check has passed and is qualified. Otherwise, proceed to process 5006 and conclude that the SENSE-based signaling check has failed.

[0380] <Variation 1 of the Third Example of the Second Aspect>

[0381] In another example, the operator controlled signal threshold per access technology may be applicable only to the difference in signal strength between cells, or only to the difference in signal quality between cells, or only to the difference in signal-to-noise ratio between cells, or to any combination of these three operator controlled signal thresholds per access technology. Figure 5 , the UE 3 may compare the home PLMN cell with the cell from another PLMN only for difference in signal strength or difference in signal quality, or for difference in signal to noise ratio, or for any other combination between these three types of thresholds, or for all three types of thresholds.

[0382] <System Overview>

[0383] Figure 6 A telecommunication system 1 for mobile (cellular or wireless) use is schematically illustrated to which the above aspects are applicable.

[0384] The telecommunications system 1 represents an overview of a system in which end-to-end communications are possible. For example, a UE 3 (or user equipment, "mobile device" 3) communicates with other UEs 3 or service servers in a data network 20 via various (R)AN nodes 5 and a core network 7.

[0385] The (R)AN node 5 supports any radio access 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 as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0386] The (R)AN node 5 may be split 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 and construct the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as O-RU, O-DU, and O-CU, respectively.

[0387] The (R)AN node 5 may be split into a control plane function and a user plane function. In addition, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed to multiple user plane functions, and user traffic passing through each user plane function may be aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be referred to as "dual connectivity" or "multiple connectivity".

[0388] 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.

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

[0390] 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), which includes control plane functions and user plane functions and other functions. Each function in the logical node may be considered a network function. The network function may be provided to another node by adapting a service-based architecture (SBA).

[0391] Network functions may be deployed as distributed, redundant, stateless and scalable providing services from several locations and several execution instances in each location by adapting network virtualization technologies as defined by European Telecommunications Standards Institute Network Function Virtualization (ETSI NFV).

[0392] The core network 7 may support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0393] As is well known, when the UE 3 is moving around in the geographical area covered by the telecommunication system 1, the UE 3 may enter and leave areas (i.e., radio cells) served by the (R)AN nodes 5. In order to keep track of the UE 3 and facilitate mobility between different (R)AN nodes 5, the core network 7 includes at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 coupled to the core network 7. In some core networks, instead of the AMF 70, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used.

[0394] The core network 7 also includes 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, among others. When the UE 3 is roaming to a visited public land mobile network (VPLMN), the home public land mobile network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functions of the SMF 71, UPF 72, and PCF 73 to the UE 3 roaming away.

[0395] The UE 3 and the corresponding serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via appropriate (R)AN node 5 to (R)AN node interfaces (such as so-called "Xn" interfaces and / or the like). Each (R)AN node 5 is also connected to a node in the core network 7 (such as a so-called core network node, etc.) via an appropriate interface (such as a so-called (one or more than one) "N2" / "N3" interface and / or the like). A connection to a data network 20 is also provided from the core network 7. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. In the case where the data network 20 is provided by a PLMN operator or a mobile virtual network operator (MVNO), IP Multimedia Subsystem (IMS) services may be provided by the data network 20. The UE 3 may be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types. The data network may include a SoR AF 201.

[0396] The "Uu" interface may include a control plane of the Uu interface and a user plane of the Uu interface.

[0397] The user plane of the Uu interface is responsible for transmitting user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers through a physical connection.

[0398] 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 through a physical connection.

[0399] For example, the following messages are communicated through the RRC layer to support AS signaling.

[0400] -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 in the present disclosure, the following parameters may be included together in the RRC Setup Request message.

[0401] -establishmentCause and ue-Identity. ue-Identity can have the value of ng-5G-S-TMSI-Part1 or randomValue.

[0402] -RRC setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the RRC setup message.

[0403] -masterCellGroup and radioBearerConfig

[0404] -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 in the present disclosure, the following parameters may be included together in the RRC Setup Complete message.

[0405] -guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity

[0406] UE 3 and AMF 70 are connected via an appropriate interface (e.g., the so-called N1 interface and / or the like). The N1 interface is responsible for providing communication between UE 3 and AMF 70 to support NAS signaling. The N1 interface can be established through 3GPP access and through non-3GPP access. For example, the following messages are communicated through the N1 interface.

[0407] -Registration Request message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the Registration Request message.

[0408] - 5GS Registration Type, ngKSI, 5GS Mobile Identity, Non-current Local NAS Key Set 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 Settings, Requested DRX Parameters, EPS NAS Message Container, LADN Indication, Payload Container Type, Payload Container, Network Slicing Indication, 5GS Update Type, Mobile Station Class Tag 2, Supported Codecs, NAS Message Container, EPS Bearer Context Status, Requested Extended DRX Parameters, T3324 Value, UE Radio Capability ID, Requested Mapped NSSAI, Requested Additional Information, Requested WUS Assistance Information, N5GC Indication, and Requested NB-N1 Mode DRX Parameters.

[0409] -Registration Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the Registration Accept message.

[0410] - 5GS Registration Result, 5G-GUTI, Equivalent PLMN, TAI List, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS Network Feature Support, PDU Session Status, PDU Session Reactivation Result, PDU Session Reactivation Result Error Cause, LADN Information, MICO Indication, Network Slicing Indication, Service Area List, T3512 Value, Non-3GPP Deregistration Timer Value, T3502 Value, Emergency Number List, Extended Emergency Number List, SOR Transparent Container, EAP Message, NSSAI Include Mode, Operator Defined Access Class Definition, Negotiated DRX Parameters, Non-3GPP NW Policy, EPS Bearer Context Status, Negotiated Extended DRX Parameters, T3447 Value, T3448 Value, T3324 Value, UE Radio Capability ID, UE Radio Capability ID Removal Indication, Pending NSSAI, Encryption Key Data, CAG Information List, Truncated 5G-S-TMSI Configuration, Negotiated WUS Assistance Information, Negotiated NB-N1 Mode DRX Parameters, and Extended Rejected NSSAI.

[0411] -Registration Complete message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the Registration Complete message.

[0412] -SOR transparent container.

[0413] -Authentication Request message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the authentication request message.

[0414] -ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge) and EAP message.

[0415] -Authentication response message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the authentication response message.

[0416] -Authentication response message identifier, authentication response parameters and EAP message.

[0417] -Authentication Result message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Authentication Result message.

[0418] -ngKSI, EAP messages and ABBA.

[0419] -Authentication failure message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters can be filled together in the authentication failure message.

[0420] -Authentication failure message identifier, 5GMM reason and authentication failure parameters.

[0421] -Authentication Reject message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the authentication reject message.

[0422] -EAP message.

[0423] -Service Request Message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Service Request message.

[0424] -ngKSI, service type, 5G-S-TMSI, uplink data status, PDU session status, allowed PDU session status, NAS message container.

[0425] -Service Accept message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters can be filled together in the Service Accept message.

[0426] -PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value.

[0427] -Service Reject Message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Service Reject Message.

[0428] -5GMM reason, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.

[0429] -Configuration Update Command message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be filled together in the Configuration Update Command message.

[0430] - Configuration Update Indication, 5G-GUTI, TAI List, Allowed NSSAI, Service Area List, Full Name of Network, Short Name of Network, Local Time Zone, Universal Time and Local Time Zone, Network Daylight Saving Time, LADN Information, MICO Indication, Network Slicing Indication, Configured NSSAI, Rejected NSSAI, Operator Defined Access Class Definitions, SMS Indication, T3447 Value, CAG Information List, UE Radio Capability ID, UE Radio Capability ID Removal Indication, 5GS Registration Result, Truncated 5G-S-TMSI Configuration, Additional Configuration Indication, and Extended Rejected NSSAI.

[0431] -Configuration Update Complete message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Configuration Update Complete message.

[0432] - Configuration update complete message indicator.

[0433] <User Equipment (UE)>

[0434] Figure 7 3 is a block diagram illustrating the main components of UE 3 (mobile device 3). As shown, UE 3 includes a transceiver circuit 31, which is operable to transmit signals to and receive signals from connected (one or more) nodes via one or more antennas 32. In addition, UE 3 may include a user interface 34 for inputting information from the outside or outputting information to the outside. Although not necessarily shown in this figure, UE 3 can have all the common functions of a conventional mobile device, and this can be appropriately provided by any one or any combination of hardware, software and firmware. For example, the software can be pre-installed in the memory and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). Controller 33 controls the operation of UE 3 according to the software stored in memory 36. The software includes an operating system 361 and a communication control module 362 having at least a transceiver control module 3621, as well as other. The communication control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes (such as (R)AN node 5 and AMF70, etc.). Such signaling may, for example, include appropriately formatted signaling messages related to access and mobility management procedures (for UE 3) (e.g., registration request messages and associated response messages). The controller 33 communicates with one or more universal subscriber identity modules (USIM) 35. If multiple USIM 35 are equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIM 35 simultaneously.

[0435] The UE 3 may, for example, support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0436] UE 3 can, for example, be a device for production or manufacturing and / or an energy-related machine (for example, equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal generators; nuclear power generators; batteries; nuclear systems and / or related equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil pressure equipment; pneumatic equipment; metal processing machinery; manipulators; robots and / or their application systems; tools; injection molding molds or die-casting molds; reels; conveying equipment; lifting equipment; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper processing machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or tools 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 of any of the aforementioned equipment or machinery; etc.).

[0437] UE 3 may be, for example, a transportation device (e.g., a transportation device such as: a rolling stock; a motor vehicle; a motorcycle; a bicycle; a train; a bus; a cart; a rickshaw; a ship and other watercraft; an airplane; a rocket; a satellite; a drone; a balloon; etc.).

[0438] UE 3 may be, for example, an information and communication device (eg, information and communication devices such as: electronic computers and related devices; communication and related devices; electronic components; etc.).

[0439] UE 3 can be, for example, a refrigerator, a product using a refrigerator, a trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, consumer electronics and electronic equipment (for example, consumer electronic equipment such as the following: audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related equipment; vacuum cleaners; etc.).

[0440] UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as: x-ray system; particle accelerator; radioisotope device; sonic wave device; electromagnetic application device; electronic power application device; etc.).

[0441] UE 3 can be, for example, an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a mapping or sensing instrument (e.g., a mapping or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag; etc.), a watch or clock, a laboratory instrument, an optical device, a medical device and / or system, a weapon, a piece of cutlery, a hand tool, or the like.

[0442] UE 3 may be, for example, a wirelessly 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 such as a personal computer, electrical measuring machine, etc.

[0443] UE 3 may be a part of or a device that provides applications, services and solutions related to the “Internet of Things (IoT)” described below using various wired and / or wireless communication technologies.

[0444] IoT devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like that make it possible for these devices to collect and exchange data with each other and with other communication devices. IoT devices may include automated devices that follow software instructions stored in internal memory. IoT devices may operate without 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 (usually) stationary equipment. IoT devices may also be embedded in non-stationary equipment (e.g., vehicles), or attached to animals or people to be monitored / tracked.

[0445] It will be appreciated that IoT technology may be implemented on any communication device that can connect to a communication network for sending / receiving data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0446] It will be appreciated that IoT devices are sometimes also referred to as Machine Type Communication (MTC) devices or Machine to Machine (M2M) communication devices or Narrowband IoT UEs (NB-IoT UEs).It will be appreciated that the UE 3 may support one or more than one IoT or MTC applications.

[0447] UE 3 may be a smart phone or a wearable device (eg, smart glasses, a smart watch, a smart ring, or a hearable device).

[0448] UE 3 can be a car, a connected car, or an autonomous car, or a vehicle device, or a motorcycle, or a V2X (vehicle to everything) communication module (e.g., vehicle to vehicle communication module, vehicle to infrastructure communication module, vehicle to person communication module, and vehicle to network communication module).

[0449] <(R)AN Node>

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

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

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

[0453] The (R)AN node 5 may support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0454] 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 denoted as a RAN node, a RAN, a (R)AN, or the like.

[0455] <System Overview of (R)AN Node 5 Based on O-RAN Architecture>

[0456] Fig. 9 The (R)AN node 5 of the O-RAN architecture to which the (R)AN node 5 is applicable is schematically illustrated.

[0457] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is split into a radio unit (RU) 60, a distributed unit (DU) 61, and a centralized unit (CU) 62. In some aspects, the units can be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, and the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any function in the description of a unit (e.g., one of the RU 60, DU 61, and CU 62) can be implemented in the above integrated / combined unit. In addition, the CU 62 can be divided into two functional units such as a CU control plane (CP) and a CU user plane (UP). The CU CP has a control plane function in the (R)AN node 5. The CU UP has a user plane function in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as a so-called "E1" interface and / or the like).

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

[0459] According to the functions split between RU 60, DU 61 and CU 62, each unit provides some of the functions provided by (R)AN node 5. For example, RU 60 may provide functions for communicating with UE 3 over an air interface, DU 61 may provide functions for supporting MAC layer and RLC layer, and CU 62 may provide functions for supporting PDCP layer, SDAP layer and RRC layer.

[0460] <Radio Unit (RU)>

[0461] Fig.10 6 is a block diagram illustrating the main components of an exemplary RU 60 (e.g., the RU portion of a base station ("eNB" in LTE, "gNB" in 5G, base stations beyond 5G, base stations for 6G)). As shown, the RU 60 includes a transceiver circuit 601 that is operable to transmit signals to and receive signals from connected (one or more) UEs 3 via one or more antennas 602, and to transmit signals to and receive signals from other network nodes or network elements via a network interface 603 (directly or indirectly). The controller 604 controls the operation of the RU 60 according to software stored in the memory 605. For example, the software may be pre-installed in the memory and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521, among others.

[0462] The communication control module 6052 (using its transceiver control submodule) is responsible for handling (e.g., directly or indirectly) signaling between the RU 60 and other nodes or units (such as a UE 3, another RU 60, and a DU 61, etc.). This signaling may, for example, include appropriately formatted signaling messages related to the radio connection (for a particular UE 3) and the connection with the RU 60, and in particular to the MAC layer and the RLC layer.

[0463] The controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or mobile trajectory estimation when implemented.

[0464] RU 60 can support non-public network (NPN). NPN can be stand-alone non-public network (SNPN) or public network integrated NPN (PNI-NPN).

[0465] As described above, the RU 60 may be integrated / combined into an integrated / combined unit with the DU 61. Any functions described for the RU 60 may be implemented in the above integrated / combined unit.

[0466] <Distributed Unit (DU)>

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

[0468] DU 61 can support non-public network (NPN). NPN can be stand-alone non-public network (SNPN) or public network integrated NPN (PNI-NPN).

[0469] As described above, the RU 60 may be integrated / combined as an integrated / combined unit with the DU 61 or the CU 62. Any functions described for the DU 61 may be implemented in one of the above integrated / combined units.

[0470] <Centralized Unit (CU)>

[0471] Fig.12 62 (e.g., the CU portion of a base station ("eNB" in LTE, "gNB" in 5G, base stations beyond 5G, base stations of 6G)). As shown, the device includes a transceiver circuit 621, which is operable to transmit signals to other nodes or units (including DU 61) and receive signals from these other nodes or units via a network interface 622. The controller 623 controls the operation of the CU 62 according to the software stored in the memory 624. For example, the software can be pre-installed in the memory 624 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 6241 and a communication control module 6242 having at least a transceiver control module 62421, as well as other. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units (such as DU 61 and other nodes and units, etc.).

[0472] The CU 62 may support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0473] As described above, the CU 62 may be integrated / combined into an integrated / combined unit with the DU 61. Any functions described for the CU 62 may be implemented in the above integrated / combined unit.

[0474] <amf>

[0475] Fig.13 70 is a block diagram illustrating the main components of AMF 70. As shown, the device includes a transceiver circuit 701, which is operable to transmit signals to other nodes (including UE 3, NSSF 76) via a network interface 702 and receive signals from these other nodes. A controller 703 controls the operation of AMF 70 according to the software stored in the memory 704. For example, the software can be pre-installed in the memory 704 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421, as well as other. The communication control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signaling between AMF 70 and other nodes (such as UE 3 (for example, via (R) AN node 5) and other core network nodes (including core network nodes in the HPLMN of UE 3 when UE 3 is roaming into) etc.). Such signalling may, for example, comprise appropriately formatted signalling messages related to access and mobility management procedures (for the UE 3) (eg registration request messages and associated response messages).

[0476] AMF 70 can support non-public networks (NPN). NPN can be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). AMF 7001 and AMF 7002 can have the same components as AMF 70.

[0477] <pcf>

[0478] Fig.14 73 is a block diagram illustrating the main components of PCF 73. As shown, the device includes a transceiver circuit 731, which is operable to transmit signals to other nodes (including AMF 70) via a network interface 732 and receive signals from these other nodes. The controller 733 controls the operation of PCF 73 according to the software stored in the memory 734. For example, the software can be pre-installed in the memory 734 and / or can be downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes an operating system 7341 and a communication control module 7342 having at least a transceiver control module 73421, as well as others. The communication control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signaling between PCF 73 and other nodes (such as AMF 70 and other core network nodes (including core network nodes in the HPLMN of UE 3 when UE 3 is roaming into) etc.). Such signalling may, for example, comprise appropriately formatted signalling messages (eg, according to HTTP restful methods of a service-based interface) relating to policy management procedures (for the UE 3).

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

[0480] <ausf>

[0481] Fig.15 74 is a block diagram illustrating the main components of the AUSF 74. As shown, the device includes a transceiver circuit 741, which is operable to transmit signals to other nodes (including UDM 75) via a network interface 742 and receive signals from these other nodes. The controller 743 controls the operation of the AUSF 74 according to the software stored in the memory 744. For example, the software can be pre-installed in the memory 744 and / or can be downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes an operating system 7441 and a communication control module 7442 having at least a transceiver control module 74421, as well as others. The communication control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signaling between the AUSF 74 and other nodes (such as the AMF 70 and other core network nodes (including the core network nodes in the HPLMN of UE 3 when UE3 is roaming into) etc.). Such signalling may, for example, comprise appropriately formatted signalling messages (eg, according to HTTP restful methods of a service-based interface) relating to policy management procedures (for the UE 3).

[0482] The AUSF 74 may support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0483] <udm>

[0484] Fig.16 75 is a block diagram illustrating the main components of the UDM 75. As shown, the device includes a transceiver circuit 751, which is operable to transmit signals to other nodes (including AMF 70) and receive signals from these other nodes via a network interface 752. The controller 753 controls the operation of the UDM 75 according to the software stored in the memory 754. For example, the software can be pre-installed in the memory 754 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421, as well as other. The communication 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 AMF 70 and other core network nodes (including core network nodes in the VPLMN of UE 3 when UE 3 is roaming away) etc.). Such signalling may for example comprise appropriately formatted signalling messages (eg according to HTTP restful methods of a service based interface) related to mobility management procedures (for the UE 3).

[0485] The UDM 75 may support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0486] <nssf>

[0487] Fig.17 76 is a block diagram illustrating the main components of the NSSF 76. As shown, the device includes a transceiver circuit 761, which is operable to transmit signals to other nodes (including AMF 70) via a network interface 762 and receive signals from these other nodes. The controller 763 controls the operation of the NSSF 76 according to the software stored in the memory 764. For example, the software can be pre-installed in the memory 764 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 7641 and a communication control module 7642 having at least a transceiver control module 76421, as well as other. The communication 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 AMF 70 and other core network nodes (including core network nodes in the VPLMN of UE3 when UE 3 is roaming away) etc.). Such signalling may for example comprise appropriately formatted signalling messages (eg according to HTTP restful methods of a service based interface) related to mobility management procedures (for the UE 3).

[0488] The NSSF 76 may support a non-public network (NPN). The NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0489] All or part of the exemplary aspects disclosed above may be described as, but not limited to, the following.

[0490] <Modifications and Replacements>

[0491] Detailed aspects have been described above. As will be appreciated by those skilled in the art, many modifications and substitutions may be made to the above aspects while still benefiting from the disclosures embodied in these aspects. Many of these substitutions and modifications will now be described only by way of example.

[0492] In the above description, for ease of understanding, the UE 3 and the network device are described as having multiple discrete modules (such as a communication control module, etc.). Although these modules may be provided in this way for certain applications, for example, in the case where an existing system has been modified to implement the present disclosure, in other applications, such as in a system designed from the outset to take advantage of the present inventive features, these modules may be built into the entire operating system or code, and therefore these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware, or a mixture of these.

[0493] Each controller may include any suitable form of processing circuitry, including (but not limited to) for example: one or more hardware-implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memory / cache (program and / or data); processing registers; communications buses (e.g., control, data and / or address buses); direct memory access (DMA) functionality; hardware or software-implemented counters, pointers and / or timers; and / or the like.

[0494] In the above aspects, a plurality of software modules are 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 supplied to the UE 3 and network devices as signals over a computer network or on a recording medium. In addition, one or more dedicated hardware circuits may be used to perform the functions performed by part or all of the software. However, the use of software modules is preferred because the use facilitates updating the UE 3 and network devices to update their functions.

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

[0496] Items of user equipment may include, for example, communication devices such as mobile phones, smart phones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine type communication (MTC) devices may also be connected to a network. For simplicity, the present application refers to mobile devices (or UEs) in the description, but it will be understood that the described techniques may be implemented on any communication device (mobile and / or generally stationary) that can be connected to a communication network for sending / receiving data, regardless of whether such a communication device is controlled by human input or by software instructions stored in a memory.

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

[0498] As will be appreciated by those skilled in the art, the present disclosure can be embodied as methods and systems.Therefore, the present disclosure can take the form of a complete hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0499] It will be understood that each frame of the block diagram 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 device to produce a machine, so that these instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in the flow chart and / or one or more frames of the block diagram. A general-purpose processor can be a microprocessor, but in an alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, for example, multiple microprocessors, one or more microprocessors, or any other such configuration.

[0500] The method or algorithm described in conjunction with the examples disclosed herein can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium can be coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium can be integrated with the processor. The processor and the storage medium can reside in an ASIC.

[0501] The foregoing 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 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 should be given the widest scope consistent with the principles and novel features disclosed herein.

[0502] Although the present disclosure has been particularly shown and described with reference to the exemplary aspects of the present disclosure, the present disclosure is not limited to these aspects. It will be understood by those of ordinary skill in the art that various changes in form and detail may be made herein without departing from the spirit and scope of the present disclosure as defined in this document. For example, the above aspects are not limited to 5GS, and these aspects may also be applied to communication systems other than 5GS (e.g., 6G systems, systems beyond 5G).

[0503] This application is based upon and claims the benefit of priority from Indian patent application no. 202211051126 filed on September 7, 2022, the disclosure of which is incorporated herein in its entirety by reference.

[0504] <Supplementary Notes>

[0505] The whole or part of the exemplary aspects disclosed above may be described as, but not limited to, the following supplementary notes.

[0506] (Supplementary Note 1)

[0507] A user equipment, namely, UE, includes a mobile terminal, namely, MT, and a user service identification module, namely, USIM, wherein the UE includes:

[0508] a transmitter configured to transmit a registration request message to an access and mobility management function, i.e., AMF, if an operator controlled signaling threshold per access technology is not set on the USIM or applied by the UE; and

[0509] A receiver is configured to receive a registration accept message from the AMF, the registration accept message including information indicating an operator controlled signal threshold according to access technology.

[0510] (Supplementary Note 2)

[0511] The UE according to Supplementary Note 1, wherein:

[0512] The registration request message includes a user ID, first information, and second information,

[0513] The first information is used to indicate whether the UE supports a signal level enhanced network selection feature, namely, a SENSE feature, and

[0514] The second information is used to indicate the access technology supported by the UE.

[0515] (Supplementary Note 3)

[0516] The UE according to Supplementary Note 2, wherein:

[0517] The access technologies include NB-IoT, GERAN EC-GSM-IoT, E-UTRA category M1, E-UTRA category M2, Wi-Fi and new air interface technology, namely NR technology.

[0518] (Supplementary Note 4)

[0519] The UE according to Supplementary Note 1, wherein:

[0520] The MT stores the information indicating the operator control signal threshold according to the access technology received from the AMF in the USIM or in the non-volatile memory of the UE.

[0521] (Supplementary Note 5)

[0522] The UE according to Supplementary Note 1, wherein:

[0523] The processor performs a cell selection process, a cell reselection process, and a public land mobile network selection process, ie, a PLMN selection process, by using information indicating an operator control signal threshold value according to an access technology.

[0524] (Supplementary Note 6)

[0525] An access and mobility management function, AMF, includes:

[0526] a receiver configured to receive a registration request message from a user equipment (UE); and

[0527] A transmitter is configured to transmit a registration accept message to the UE, wherein the registration accept message includes information indicating a signal threshold according to an access technology, wherein the information is received from a unified data management (UDM).

[0528] (Supplementary Note 7)

[0529] The AMF according to Supplementary Note 6, wherein

[0530] The receiver is configured to receive the registration request message from the UE, the registration request message including a UE-ID, first information, and second information,

[0531] The first information is used to indicate whether the UE supports a signal level enhanced network selection feature, namely, a SENSE feature,

[0532] The second information is used to indicate an access technology supported by the UE,

[0533] The transmitter is configured to transmit a first request message to the UDM based on the first information and the second information,

[0534] The receiver is configured to receive a first response message from the UDM, the first response message including information indicating an operator controlled signal threshold per access technology, and

[0535] The transmitter is configured to transmit the registration accept message to the UE, wherein the registration accept message includes information indicating an operator controlled signal threshold according to an access technology.

[0536] (Supplementary Note 8)

[0537] The AMF according to Supplementary Note 7, wherein

[0538] In the case where the first information indicates that the UE supports the SENSE feature, the first request message includes the first information, the second information and the third information, and

[0539] In the case where the first information indicates that the UE does not support the SENSE feature, the first request message includes the third information, wherein:

[0540] The third information is used to indicate whether the AMF has the capability to transmit information related to a signal level enhanced network selection feature, namely, a SENSE feature, to the UE by using a roaming guidance mechanism, namely, a SOR mechanism.

[0541] (Supplementary Note 9)

[0542] The AMF according to Supplementary Note 7, wherein

[0543] The first request message includes a Nudm_UECM_Registration request message, and

[0544] The first response message includes a Nudm_UECM_Registration response message.

[0545] (Supplementary Note 10)

[0546] A unified data management, or UDM, includes:

[0547] a receiver configured to receive a first request message from an access and mobility management function, i.e., an AMF;

[0548] a transmitter configured to transmit a second request message to a roaming steering application function, i.e., SoR-AF,

[0549] The receiver is configured to receive a second response message from the SoR-AF, the second response message comprising information indicating an operator controlled signal threshold per access technology, and

[0550] The transmitter is configured to transmit a first response message to the AMF, the first response message comprising information indicating an operator controlled signal threshold according to access technology.

[0551] (Supplementary Note 11)

[0552] The UDM according to Supplementary Note 10, wherein

[0553] The transmitter is configured to transmit the first response message to the AMF in response to the first request message received from the AMF, the first response message including information indicating an operator controlled signal threshold according to access technology.

[0554] (Supplementary Note 12)

[0555] The UDM according to Supplementary Note 10, wherein

[0556] The first request message includes a Nudm_UECM_Registration request message,

[0557] The first response message includes a Nudm_UECM_Registration response message,

[0558] The second request message includes an Nsoraf_SoR_Get request message, and

[0559] The second response message includes an Nsoraf_SoR_Get response message.

[0560] (Supplementary Note 13)

[0561] The UDM according to Supplementary Note 10, wherein

[0562] The transmitter is configured to transmit a third request message including information indicating operator controlled signal thresholds per access technology to an authentication server function (AUSF) to protect the information indicating operator controlled signal thresholds per access technology, and

[0563] The receiver is configured to receive a third response message from the AUSF, the third response message comprising protected information indicating an operator controlled signal threshold per access technology, the protected information being protected by the AUSF.

[0564] (Supplementary Note 14)

[0565] A method in a user equipment (UE), wherein the UE includes a mobile terminal (MT) and a user service identity module (USIM), the method comprising:

[0566] transmitting a registration request message to an access and mobility management function (AMF) in case the operator controlled signaling threshold per access technology is not set on the USIM or applied by the UE; and

[0567] A registration accept message is received from the AMF, the registration accept message including information indicating an operator controlled signal threshold according to access technology.

[0568] (Supplementary Note 15)

[0569] A method in an access and mobility management function, i.e., an AMF, the method comprising:

[0570] receiving a registration request message from a user equipment (UE); and

[0571] A registration accept message is transmitted to the UE, the registration accept message including information indicating a signal threshold according to an access technology, the information being received from a unified data management (UDM).

[0572] (Supplementary Note 16)

[0573] A method in unified data management (UDM), the method comprising:

[0574] receiving a first request message from an access and mobility management function, i.e., AMF;

[0575] Transmitting a second request message to a roaming steering application function, i.e., SoR-AF;

[0576] receiving a second response message from the SoR-AF, the second response message comprising information indicating an operator controlled signal threshold per access technology; and

[0577] A first response message is transmitted, the first response message including information received from the SoR-AF indicating a per-access-technology operator-controlled signal threshold.

[0578] Reference numerals list

[0579] 1 System

[0580] 3UE

[0581] 5(R)AN Node

[0582] 60RU

[0583] 61DU

[0584] 62CU

[0585] 7Core Network

[0586] 70AMF

[0587] 71SMF

[0588] 72UPF

[0589] 73PCF

[0590] 74AUSF

[0591] 75UDM

[0592] 76NSSF

[0593] 20Data Network

[0594] 33MT

[0595] 35USIM

[0596] 201SoR OF< / nssf> < / udm> < / ausf> < / pcf> < / amf>

Claims

1. A user equipment, namely UE, comprises a mobile terminal, namely MT, and a user service identity module, namely USIM, wherein the UE comprises: a transmitter configured to transmit a registration request message to an access and mobility management function, i.e., AMF, if a signal threshold per access technology is not set on the USIM or applied by the UE; as well as A receiver configured to receive a registration accept message from the AMF, the registration accept message comprising information indicating a signal threshold according to an access technology.

2. The UE according to claim 1, wherein: The registration request message includes a user ID, first information, and second information, The first information is used to indicate whether the UE supports a signal level enhanced network selection feature, namely, a SENSE feature, and The second information is used to indicate the access technology supported by the UE.

3. The UE according to claim 2, wherein: The access technologies include NB-IoT, GERAN EC-GSM-IoT, E-UTRA category M1, E-UTRA category M2, Wi-Fi and new air interface technology, namely NR technology.

4. The UE according to claim 1, wherein: The MT stores the information indicating the signal threshold according to the access technology received from the AMF in the USIM or in the non-volatile memory of the UE.

5. The UE according to claim 1, wherein: The processor performs a cell selection process, a cell reselection process, and a public land mobile network selection process, ie, a PLMN selection process, by using information indicating a signal threshold value according to an access technology.

6. An access and mobility management function, namely AMF, including: A receiver configured to receive a registration request message from a user equipment (UE); as well as A transmitter is configured to transmit a registration accept message to the UE, wherein the registration accept message includes information indicating a signal threshold according to an access technology, wherein the information is received from a unified data management (UDM).

7. The AMF according to claim 6, wherein: The receiver is configured to receive the registration request message from the UE, the registration request message including a UE-ID, first information, and second information, The first information is used to indicate whether the UE supports a signal level enhanced network selection feature, namely, a SENSE feature, The second information is used to indicate an access technology supported by the UE, The transmitter is configured to transmit a first request message to the UDM based on the first information and the second information, The receiver is configured to receive a first response message from the UDM, the first response message including information indicating a signal threshold according to an access technology, and The transmitter is configured to transmit the registration accept message to the UE, wherein the registration accept message includes information indicating a signal threshold according to an access technology.

8. The AMF according to claim 7, wherein: In the case where the first information indicates that the UE supports the SENSE feature, the first request message includes the first information, the second information and the third information, and In the case where the first information indicates that the UE does not support the SENSE feature, the first request message includes the third information, wherein: The third information is used to indicate whether the AMF has the capability to transmit information related to a signal level enhanced network selection feature, namely, a SENSE feature, to the UE by using a roaming guidance mechanism, namely, a SOR mechanism.

9. The AMF according to claim 7, wherein: The first request message includes a Nudm_UECM_Registration request message, and The first response message includes a Nudm_UECM_Registration response message.

10. A unified data management, or UDM, includes: a receiver configured to receive a first request message from an access and mobility management function, i.e., an AMF; a transmitter configured to transmit a second request message to a roaming steering application function, i.e., SoR-AF, The receiver is configured to receive a second response message from the SoR-AF, the second response message comprising information indicating a signal threshold according to an access technology, and The transmitter is configured to transmit a first response message to the AMF, the first response message including information indicating a signal threshold according to an access technology.

11. The UDM according to claim 10, wherein: The transmitter is configured to transmit the first response message to the AMF in response to the first request message received from the AMF, the first response message including information indicating a signal threshold according to an access technology.

12. The UDM of claim 10, wherein: 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, and The second response message includes an Nsoraf_SoR_Get response message.

13. The UDM of claim 10, wherein: The transmitter is configured to transmit a third request message including information indicating a signal threshold per access technology to an authentication server function (AUSF) to protect the information indicating a signal threshold per access technology, and The receiver is configured to receive a third response message from the AUSF, the third response message including protected information indicating a signal threshold according to an access technology, the protected information being protected by the AUSF.

14. A method in a user equipment (UE), wherein the UE comprises a mobile terminal (MT) and a user service identity module (USIM), the method comprising: In case the signalling threshold per access technology is not set on the USIM or applied by the UE, transmitting a registration request message to an access and mobility management function, i.e. AMF; as well as A registration accept message is received from the AMF, the registration accept message including information indicating a signal threshold according to an access technology.

15. A method in an access and mobility management function (AMF), the method comprising: Receiving a registration request message from a user equipment (UE); as well as A registration accept message is transmitted to the UE, the registration accept message including information indicating a signal threshold according to an access technology, the information being received from a unified data management (UDM).

16. A method in unified data management (UDM), the method comprising: receiving a first request message from an access and mobility management function, i.e., AMF; Transmitting a second request message to a roaming steering application function, i.e., SoR-AF; receiving a second response message from the SoR-AF, the second response message comprising information indicating a signal threshold according to an access technology; as well as A first response message is transmitted, the first response message including information received from the SoR-AF indicating a signal threshold according to an access technology.

Images