Method and apparatus for processing signaling of a roaming terminal

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to an embodiment of the disclosure, an operation method of a user equipment (UE) in a wireless communication system can include the steps of: receiving, from an access and mobility management function (AMF), a first message including routing indicator data update information transmitted from a home unified data management (UDM); generating a subscription concealed identifier (SUCI) based on the routing indicator data update information; and transmitting, to the AMF, a second message for a registration request including the SUCI.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to a method for routing and processing signaling of a UE roaming in a mobile communication system. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of 5G mobile communication technology development, to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization was underway regarding beamforming and massive MIMO. This included mitigating radio wave path loss in millimeter waves and increasing transmission distance; parameter sets supporting dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and time slot formats; initial access technologies to support multi-beam transmission and broadband; the definition and operation of the bandwidth portion (BWP); new channel coding methods such as LDPC (low-density parity-check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and new channel coding methods for transmitting and receiving data. Additionally, network slicing was being developed to provide dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization already exists for technologies such as V2X (Vehicle-to-Everything), NR-U (New Radio Unlicensed), NR UE Power Saving, Non-Terrestrial Network (NTN), and positioning. V2X is used to assist autonomous vehicles in making driving decisions and enhancing user convenience based on vehicle location and status information transmitted by the vehicle. NR-U aims to comply with system operations related to various regulations in unlicensed frequency bands. NR UE Power Saving and Non-Terrestrial Network (NTN) are UE-satellite direct communication used to provide coverage in areas where communication with terrestrial networks is impossible.

[0005] In addition, standardization is underway for air interface architectures / protocols such as those for supporting new services through interoperability and convergence with other industries in the Industrial Internet of Things (IIoT); for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and for two-step random access (2-step RACH for NR) to simplify the random access process. Standardization is also underway for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and for system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of connected devices. To this end, new research related to extended reality (XR) is being undertaken to effectively support AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), and other technologies by leveraging artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication, while also improving 5G performance and reducing complexity.

[0007] Furthermore, this development of 5G mobile communication systems will not only serve as the foundation for developing new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, such as full-dimensional MIMO (FD-MIMO), multi-antenna transmission technologies like array antennas and massive MIMO, metamaterial-based lenses and antennas for improving terahertz band signal coverage, and high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum) and RIS (reconfigurable smart surfaces), but will also serve as the foundation for developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technology and enhance system networks, AI-based communication technologies to achieve system optimization and internalize end-to-end AI support by leveraging satellites and AI (artificial intelligence) from the design stage, and next-generation distributed computing technologies to deliver services with complexity exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] When the home network operator operates multiple PLMNs (e.g., when using multiple PLMN IDs), the method of selecting the PLMN to handle signaling for a specific subscriber's roaming and connecting the roaming network to the corresponding PLMN is not supported.

[0010] Methods for routing signaling for roaming UEs to another core network operated by the home network operator or a partner core network of the home network operator are not supported.

[0011] Technical solution

[0012] According to embodiments of this disclosure, a method for operating a user equipment (UE) in a wireless communication system may include: receiving a first message from an access and mobility management function (AMF) including routing indicator data update information sent from a Home Unified Data Management (H-UDM); generating a subscription hidden identifier (SUCI) based on the routing indicator data update information; and sending a second message to the AMF including a registration request for the SUCI.

[0013] A user equipment (UE) in a wireless communication system according to embodiments of the present disclosure includes a transceiver and a controller. The controller can receive a first message from the Access and Mobility Management Function (AMF) including routing indicator data update information sent from the Home Unified Data Management (H-UDM). The controller can generate a Subscription Hidden Identifier (SUCI) based on the routing indicator data update information. The controller can control the sending of a second message, including the SUCI, to the AMF for a registration request.

[0014] Beneficial effects

[0015] The method and apparatus according to embodiments of this disclosure can determine the PLMN that provides roaming value-added services (RVAS), and the signaling services of the roaming UE should be routed to and processed by the PLMN.

[0016] The methods and apparatus according to embodiments of this disclosure can route the signaling and services of a roaming UE to a specific PLMN and process them, or route the UE's services to the core network of a partner operator of the home network operator, according to the intention of the home network operator. Attached Figure Description

[0017] Figure 1a and Figure 1b This illustration shows a 5G system architecture supporting edge computing roaming services according to embodiments of the present disclosure.

[0018] Figure 2 An example of a network architecture for supporting Roaming Value-Added Services (RVAS) according to embodiments of the present disclosure is shown.

[0019] Figure 3a and Figure 3b The present disclosure illustrates a process for providing routing indicator data to a UE and a registration process using the provided routing indicator data, according to embodiments of the present disclosure.

[0020] Figure 4A method for supporting RVAS using route indicator data updates is shown according to embodiments of the present disclosure.

[0021] Figure 5 This is a block diagram illustrating a UE according to an embodiment of the present disclosure.

[0022] Figure 6 This is a block diagram illustrating a network entity according to an embodiment of the present disclosure.

[0023] Figure 7 This invention illustrates a process for searching and discovering network functions of RVAS provider PLMN according to embodiments of the present disclosure. Detailed Implementation

[0024] The operating principles of this disclosure are described below with reference to the accompanying drawings. The terminology described below is defined in consideration of the functions described herein. Since these terms may vary depending on the intent or habits of the user or operator, their definitions should be determined within the context of the entire disclosure.

[0025] For ease of description, terms referring to network entities or network functional entities, terms referring to messages, and terms referring to identification information, as used herein, are provided as examples. Therefore, this disclosure is not limited to these terms, and these terms may be replaced by other terms representing objects having equivalent technical concepts.

[0026] Although the terminology and names defined in the 5G system standard are used herein for ease of description, the embodiments of this disclosure are not limited thereto or thereby, and can also be applied to systems conforming to other standards.

[0027] Figure 1a and Figure 1b This illustration shows a 5G system architecture supporting edge computing roaming services according to embodiments of the present disclosure.

[0028] 5G system architectures that support edge computing services can include various network functions (NFs), some of which are in Figure 1a As shown in 1B, functions such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM), Data Network (DN) or a local portion of a DN capable of local access to a data network, User Plane Function (UPF), (Radio) Access Network ((R)AN), and User Equipment (UE) are included.

[0029] Each NF supports the following functions.

[0030] -AMF provides access and mobility management functions for each UE and can be connected to one AMF for each UE.

[0031] -DN represents, for example, carrier services, internet access, or third-party services. The DN sends downlink protocol data units (PDUs) to the UPF or receives PDUs sent from the UE from the UPF. The local portion of the DN refers to a data network with a short data transmission path because it can locally access a portion of the DN. It can be used to represent a DN in which edge application servers supporting edge computing services are deployed.

[0032] The PCF receives information about packet flows from the application server and provides functions for determining policies such as mobility management or session management. Specifically, the PCF supports functions such as supporting a unified policy framework for controlling network operations, providing policy rules to allow CP functions (e.g., AMF or SMF) to enforce policy rules, and implementing a front-end for accessing subscription information related to policy decisions in the Unified Data Repository (UDR).

[0033] -SMF provides session management functionality, and if the UE has multiple sessions, this can be managed by different SMFs for each session.

[0034] -UDM stores data such as user subscription data and policy data.

[0035] The UPF transmits downlink PDUs received from the DN to the UE via the (R)AN, and uplink PDUs received from the UE to the DN via the (R)AN. The Uplink Classifier (ULCL) refers to a UPF that has the function of classifying and transmitting uplink data. The Local UPF (L-UPF) is used as the PDU session anchor for sessions sent to the local portion of the DN.

[0036] -EASDF processes Domain Name System (DNS) queries sent by the UE according to rules provided by the SMF. For example, it can perform operations such as forwarding DNS queries sent by the UE to a DNS server, receiving DNS responses, sending relevant reports to the SMF, and providing DNS responses to the UE.

[0037] Figure 1a An example of a 5G system architecture for Home Route (HR) roaming is shown; Figure 1b An example of a 5G system architecture for Local Loosening (LBO) roaming is shown.

[0038] exist Figure 1aIn HR roaming, the visited public land mobile network (VPLMN) can include the UE, (R)AN, UPF, AMF, visited SMF (V-SMF), and visited PCF (V-PCF), and the home public land mobile network (HPLMN) can include the UPF, data network (DN), home SMF (H-SMF), home PCF (H-PCF), AF, and UDM. Figure 1b In the context of LBO roaming, VPLMN can include UE, (R)AN, UPF, AMF, V-SMF and V-PCF, and HPLMN can include UDM.

[0039] Figure 2 An example of a network architecture for supporting Roaming Value-Added Services (RVAS) according to embodiments of the present disclosure is shown. Figure 2 This illustrates a network architecture where, when using home routing sessions, the signaling and service transmission paths related to the roaming UE are directed to the RVAS that handles the UE's signaling and services, providing a PLMN (hereinafter referred to as RVAS PLMN) instead of an HPLMN.

[0040] refer to Figure 2 HPLMN may include H-UPF, data network, H-SMF, H-PCF, UDM and AUSF, VPLMN may include UE, RAN, V-UPF, AMF, V-SMF and V-PCF, and RVAS PLMN may include R-AUSF, R-UDM, R-SMF, R-UPF and data network.

[0041] Signaling related to roaming UEs can be sent to the R-AUSF or R-UDM deployed in the RVAS PLMN, instead of being sent from the AMF of the VPLMN to the ASF or UDM of the HPLMMN. Furthermore, user plane data services of roaming UEs can be routed from the VPLMN UPF (V-UPF) to the R-UPF of the RVAS PLMN, instead of the HPMN UPF (H-UPF).

[0042] Figure 3a and Figure 3b The present disclosure illustrates a process for providing routing indicator data to a UE and a registration process using the provided routing indicator data, according to embodiments of the present disclosure.

[0043] Step 1. The UE's home UDM (hUDM) (or UE) can determine to perform a routing indicator data update to support RVAS taking into account the UE's subscription data. For example, in the hUDM, at least one of the following can be stored for a specific UE (or a specific UE group, or a specific UE identifier range, IMSI range): RVAS support information or RVAS permission information, RVAS provider PLMN ID (RVAS provides PLMN ID; PLMN information providing RVAS services; rPLMN ID), RVAS supports VPLMN information, and RVAS supports country information (e.g., MCC information), and it can determine to perform a routing indicator data update for UEs that have the corresponding information as subscription data.

[0044] Step 1 can be executed when the hUDM is provided with information indicating that the UE has applied for roaming services, or when the hUDM is provided with information indicating that the UE has registered for roaming services in a specific country or PLMN. Alternatively, whether to execute Step 1 can be determined based on the operator policy set in the hUDM.

[0045] Step 2. Considering subscription data information, the hUDM can send routing indicator data update information for a specific UE to the AMF. This request can be performed using the Nudm_SDM_Notification message or by sending a separate message. The information sent by the hUDM to the AMF may include at least one of the following: routing indicator value, VPLMN ID, rPLMN ID, RVAS network ID, country information (MCC), network public key ID, priority value, UE confirmation request indication, and re-registration request indication. The hUDM can set the routing indicator value to a value that can be used to search and select AUSF and UDM (rAUSF and rUDM) deployed in an RVAS provider PLMN (RVAS PLMN or rPLMN), instead of the AUSF and UDM values ​​used to search and select an HPLMN, and then send the routing indicator value to the AMF.

[0046] The UDM can send the VPLMN ID as VPLMN information where a routing indicator value can or should be used. The RVAS provider PLMN information (rPLMN ID) provided by the hUDM can be mapped to a routing indicator value and a VPLMN ID, and can be information used to indicate the PLMN in which the AUSF / UDM is deployed, searched and selected via the routing indicator value. When provided along with RVAS-related information, the network public key ID provided by the hUDM can be set and provided as a network public key ID available in the RVAS provider PLMN or a network public key ID that can be used to search for and discover rAUSF / rUDMs.

[0047] The hUDM can provide the AMF with multiple combinations of route indicator values, VPLMN ID, rPLMN ID, RVAS network ID, country information (MCC), and network public key ID. Furthermore, the hUDM can provide route indicator values, VPLMN ID, HPLMN ID, country information, and home network public key ID information together with the RVAS PLMN-related route indicator values, VPLMN ID, rPLMN ID, RVAS network ID, and network public key ID values. And when the UE fails to access the PLMN providing the RVAS using information received from the hUDM, the UE can attempt to access the HPLMN. For example, the hUDM can send the routing indicator value, VPLMN ID, rPLMN ID, RVAS network ID, and network public key ID information related to the RVAS PLMN (used to route signaling to the RVAS PLMN) along with the routing indicator value, VPLMN ID, rPLMN ID, RVAS network ID, and network public key ID information used to route signaling to the HPLMN to the AMF, so as to provide this information to the UE. The hUDM can also set the priority of the RVAS PLMN related information to be higher than that of the HPLMN related information, so that the UE's signaling can be routed to the RVAS PLMN with priority. The hUDM can also set the UE signaling to be routed to the HPLMN to continue roaming service when it is impossible or impossible to route to the RVAS PLMN.

[0048] Step 3. When the AMF determines that the information received from the hUDM cannot be immediately sent to the UE (when the UE is unreachable), the AMF can notify the hUDM that the UE parameter update data transmission process has failed. In this case, the following procedure is not performed, and the AMF can wait until it can signal to the UE.

[0049] Step 4. The AMF can send the routing indicator data update information received from the hUDM to the UE. This information can be included in the UE parameter update container and sent.

[0050] Step 5. When the UE acknowledgment request indication is included in the information received from the AMF, the UE may send ACK information to the AMF.

[0051] Step 6. The AMF can send a message to the hUDM notifying the UE that it has successfully received the routing indicator data update information.

[0052] Step 7. When hUDM receives from AMF that the UE has successfully received the route indicator data update, hUDM can notify AMF and another NF of the route indicator value.

[0053] Step 8. When the UE receives a routing indicator data update via the AMF, when generating a Subscription Hidden Identifier (SUCI), the UE can use the information included in the routing indicator data update to generate the SUCI instead of using the information stored in the existing USIM or ME. Multiple International Mobile Subscriber Identity (IMSI) codes can be configured in the UE. Each IMSI can be mapped to specific PLMN information (e.g., PLMN ID) or specific country information (e.g., MCC). The UE can generate the SUCI by selecting an available IMSI corresponding to information such as the routing indicator value, VPLMN ID, and rPLMN ID included in the routing indicator data received in previous steps. For example, the UE can select or identify the VPLMN ID or MCC corresponding to the PLMN ID value selected through the UE's PLMN selection operation received from the UDM, and can use the rPLMN ID or RVAS network ID, the routing indicator value, the network public key ID value, and the IMSI corresponding to the VPLMN ID or MCC to generate the SUCI.

[0054] When generating a SUCI for registration to a VPLMN ID selected during PLMN selection in a roaming country other than the HPLMN, the UE can use a routing indicator and network public key ID received from the hUDM to generate the SUCI. If the UE has already received multiple combinations of routing indicators and network public key IDs from the UDM, the UE can choose to use a routing indicator and network public key ID corresponding to either the MCC value or the VPLMN ID of the country the UE is roaming in.

[0055] Multiple combinations of routing indicators and network public key IDs provided by the UDM can be provided, and multiple combinations of routing indicators and network public key IDs corresponding to the MCC or VPLMN ID can exist, and a priority value can be set for each combination.

[0056] When a UE receives a re-registration request indication, it can use the generated SUCI to perform the registration process. In this case, the UE can attempt the registration process by generating a SUCI using a combination of a routing indicator and a network public key ID based on a priority value. For example, if registration fails using a combination of a routing indicator and a network public key ID corresponding to a specific MCC or VPLMN ID, a routing indicator and a network public key ID with the next higher priority value can be used.

[0057] Even if the UE has not yet received a re-registration request indication from the UDM, the UE can independently re-execute the registration process upon receiving RVAS-related routing indicator information.

[0058] Step 9. The UE may send a registration request message including the SUCI generated in step 8 to the AMF. The UE may also provide the Home Network ID (HPLMN ID) along with the SUCI to the AMF.

[0059] Step 10. The AMF can use the routing indicator information or network public key ID included in the SUCI received from the UE to perform the process of searching for and selecting the rAUSF (RVAS PLMN's AUSF). When the rAUSF information corresponding to the routing indicator or network public key ID is set in the AMF, the set information can be used. When the rAUSF information (address and identifier) ​​corresponding to the routing indicator or network public key ID is not set, the AMF can send an NF discovery request to the vNRF (VPLMN's NRF). The NF discovery request message can include at least one of the SUCI, routing indicator, or network public key ID.

[0060] Step 11. The vNRF can use the information received from the AMF to select the rNRF (NRF of the RVAS PLMN), and can request and obtain the rAUSF information (address and identifier) ​​while providing at least one of the SUCI, routing indicator and network public key ID received from the AMF.

[0061] Step 12. vNRF can provide the rAUSF information obtained in the previous steps to AMF.

[0062] Step 13. The AMF may send an authentication request to the rAUSF identified by the rAUSF information obtained in the previous steps. The authentication request message may include the SUCI, routing indicator, and network public key information received from the UE.

[0063] Step 14. The rAUSF can obtain authentication information for the UE from the rUDM (the UDM of the RVAS PLMN). The rAUSF can select the rUDM to provide authentication information using internal configuration information or information such as SUCI, routing indicators, and network public keys. The rAUSF can provide SUCI when requesting authentication information, and the UDM can convert SUCI to SUPI and provide SUPI.

[0064] Step 15. rAUSF can provide the authentication information as a response message to AMF in step 13.

[0065] Step 16. The AMF can provide authentication information to the UE to complete authentication and receive its response. It can also forward authentication-related information received from the UE to the rAUSF to perform authentication-related operations. The AMF can obtain successful authentication results and SUPI information from the rAUSF.

[0066] Step 17. The AMF can use the information in the SUCI received from the UE and the SUPI obtained in the previous steps to perform a search and selection operation for the rUDM. When rUDM information corresponding to a routing indicator or network public key ID is set in the AMF, the set information can be used. When rUDM information (address and identifier) ​​corresponding to a SUPI, routing indicator, or network public key ID is not set, the AMF can send an NF discovery request to the vNRF. The NF discovery request message may include at least one of SUPI, SUCI, routing indicator, or network public key ID.

[0067] Step 18. The vNRF can use the information received from the AMF to select the rNRF, and can request and obtain rUDM information (address and identifier) ​​while providing at least one of the SUPI, SUCI, routing indicator and network public key ID received from the AMF.

[0068] Step 19. vNRF can provide the rUDM information obtained in the previous steps to AMF.

[0069] Step 20. The AMF may send a registration request and a subscription data request to the rUDM identified by the rUDM information obtained in the previous steps. The rUDM may verify the SUPI included in the information received from the AMF and may identify whether the UE is a UE that is a target subscriber for RVAS. In the case of a target UE for RVAS, the rUDM may provide the AMF with access and mobility subscription data as well as subscription data related to SMF selection.

[0070] Step 21. AMF can send a registration acceptance message to notify the UE that registration has been successfully completed.

[0071] Step 22. The UE can send a PDU session establishment request message to the AMF to receive data services.

[0072] Step 23. When the AMF receives a PDU session establishment request message from the UE, it can select an SMF that can connect to an RVAS provider PLMN capable of providing roaming services to the UE during the vSMF selection process. For example, the AMF can use information such as the routing indicator, SUPI, and rPLMN ID available through previous steps to select the vSMF. Furthermore, the AMF can use information such as the routing indicator, SUPI, and rPLMN ID to select an rSMF deployed in an RVAS provider PLMN, and can send a PDU session establishment request message including rSMF information (address and identifier) ​​to the vSMF.

[0073] vSMF can send a PDU session creation request message to rSMF based on the information received in step 23.

[0074] Figure 4 A method for supporting RVAS using route indicator data updates is shown according to embodiments of the present disclosure.

[0075] Step 1. In the UE's home UDM (hUDM), at least one of the following can be set for a specific UE (or a specific UE group, or a specific UE identifier range, IMSI range): RVAS support information or RVAS permission information, RVAS provider PLMN ID (PLMN ID providing RVAS; PLMN information providing RVAS services; rPLMN ID, RVAS support VPLMN information (VPLMNID), RVAS support country information (e.g., MCC information), and at least one of the rUDM information (address and identifier) ​​deployed in the RVAS provider PLMN within the subscription data. The subscription data for the corresponding roaming UE can be set in the rUDM (UDM deployed in the RVAS provider PLMN and connectable to the hUDM).

[0076] Step 2. The UE can send a registration request message to the AMF deployed in the VPLMN of the access country to receive roaming services. This message includes SUCI information.

[0077] Step 3. The AMF selects hAUSF and hUDM to convert the UE's SUCI to SUPI and performs the authentication process. After successfully performing the authentication process, the AMF can send a UE context management registration or subscription data request message to the hUDM.

[0078] Step 4. When the hUDM receives a registration request or subscription data request message from the AMF in the previous steps, if RVAS service support / allowance information is stored in the hUDM for the UE's currently registered VPLMN ID or access country (country information identified by the MCC), the hUDM can determine the signaling to be redirected for the roaming UE. The RVAS service support / allowance information can be set in correspondence with a specific VPLMN ID or country information (MCC) value for a specific UE or a specific UE group or a specific UE identifier range (e.g., SUPI or IMSI range). Furthermore, a list of rPLMN IDs corresponding to the VPLMN IDs or country information (MCC) associated with the RVAS service support / allowance information, along with the rUDM address and identifier information for each rPLMN ID, can be stored in the hUDM.

[0079] Step 5. The hUDM can provide RVAS redirection information to the AMF as a response message to step 3. The RVAS redirection information may include the rPLMN ID, rAUSF, and rUDM address information.

[0080] Step 6. The AMF can use the rAUSF and rUDM address information received from the hUDM to perform authentication between the UE and the rPLMN, and can send a UE context management registration or subscription data request message to the rUDM after successful authentication.

[0081] Step 7. The rUDM can identify subscriber information for roaming UEs and can provide the AMF with subscription data required for access and mobility management operations within the rPLMN and for SMF selection operations.

[0082] Step 8. When the AMF successfully receives subscription data from the rUDM, the AMF can send a registration acceptance message to the UE.

[0083] Step 9. The UE can send a PDU session establishment request message to the AMF so that it can use data services later.

[0084] Step 10. The AMF can send a PDU session creation request message to the vSMF. This message may include the rSMF identifier and address information selected by the AMF. The AMF can search for and select the rSMF (the SMF deployed in the RVAS provider PLMN) based on the rPLMN ID obtained through previous steps, instead of the hSMF specified by the HPLMN ID, which can be obtained from the UE's SUPI or subscription data information associated with the UE, and can provide the rSMF to the vSMF. The vSMF can send the PDU session creation request message received from the AMF to the rSMF.

[0085] Figure 5 This is a block diagram illustrating a UE according to an embodiment of the present disclosure.

[0086] exist Figure 5 In the embodiments, the UE can be as shown in Figures 1 to 12. Figure 4 and Figure 7 Each of the UEs or UEs illustrated in the table. (See reference.) Figure 5 The UE may include a transceiver 510, a controller 520, and a storage unit 530. In this disclosure, the controller may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0087] Transceiver 510 can send and receive signals to / from a base station or network entity. Transceiver 510 can send and receive data to / from a base station or network entity using, for example, wireless communication.

[0088] According to an embodiment, controller 520 can control the overall operation of the UE. For example, controller 520 can control the signal flow between blocks to perform operations as shown in FIG1 to... Figure 4 and Figure 7 The described operation.

[0089] Storage unit 530 can store at least one of the information transmitted and received by transceiver 510 and the information generated by controller 520. For example, storage unit 530 can store information referring to Figures 1 to 520. Figure 4 and Figure 7 The information and data required for the described method.

[0090] Figure 6 This is a block diagram illustrating a network entity according to an embodiment of the present disclosure.

[0091] exist Figure 6 In the embodiments described, the network entity can be implemented as shown in Figures 1 to 12. Figure 4 and Figure 7 Each of the following is represented as one of the following: RAN, AMF, hUDM (UDM of HPLMN), vNRF (NRF of VPLMN), rNRF (NRF of RVAS), rAUSF (AUSF of RVAS), rUDM (UDM of RVAS), and rSMF (SMF of RVAS).

[0092] refer to Figure 6 The network entity may include a transceiver 610, a controller 620, and a storage unit 630. In this invention, the controller may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0093] Transceiver 610 can send and receive signals to / from a UE, a base station, or another network entity. Transceiver 610 can use, for example, wireless communication to send / receive data to / from a UE, a base station, or other network entity.

[0094] According to the embodiments presented in this disclosure, controller 620 can control the overall operation of network entities. For example, controller 620 can control the signal flow between blocks to perform actions as shown in FIG1 to... Figure 4 and Figure 7 The described operation.

[0095] Storage unit 630 can store at least one of the information transmitted and received by transceiver 610 and the information generated by controller 620. For example, storage unit 630 can store information referring to Figures 1 to 620. Figure 4 and Figure 7 The information and data required for the described method.

[0096] According to an embodiment, in order to use in Figure 3a and Figure 3bThe routing indicator information described in the embodiments routes signaling to the RVAS provider PLMN and can modify RVAS provider PLMN related information (including a set of information of at least one of rAUSF, rUDM and RVAS provider PLMN ID).

[0097] exist Figure 3a Following step 9, the AMF or NF of the PLMN in which the UE is roaming can use the routing indicator information or network public key ID included in the obtained (e.g., received from the UE) SUCI to perform the process of searching for and selecting rAUSF (RVAS PLMN's AUSF). When rAUSF information corresponding to the PLMN ID, routing indicator, or network public key ID associated with the MNC, MCC, or roaming service is set in the AMF, the set information can be used. When rAUSF information (address and identifier) ​​corresponding to the received routing indicator or network public key ID is not set, the AMF can send an NF discovery request to the vNRF (VPLMN's NRF). The NF discovery request message can include at least one of the SUCI, routing indicator, or network public key ID.

[0098] According to an embodiment, the vNRF can consider information received from the AMF to determine which NF discovery request to send to the hNRF. For example, the vNRF can consider MNC and MCC information to identify the hNRF and send the NF discovery request to the hNRF. The NF discovery request sent by the vNRF to the hNRF may include at least one of the following: SUCI, routing indicator information or network public key ID, and VPLMN ID information obtained by the AMF in previous steps, as well as the NF information to be searched (NF information indicating ASF or UDM).

[0099] According to one embodiment, when the hNRF receives an NF discovery request from the vNRF including at least one of SUCI, routing indication information, or network public key ID and VPLMN ID, and identifies that the request is a search request for an AUSF or UDM, the hNRF can perform operations to determine or obtain AUSF or UDM information deployed in the RVAS provider PLMN corresponding to information in the hNRF. For example, the hNRF can store RVAS provider PLMN related information (e.g., rAUSF identifier / address information, rUDM identifier / address information, RVAS provider PLMN ID, MCC, MNC information, etc.), which can correspond to a combination of information including at least one of SUCI, IMSI range, SUPI range, PLMN ID, MCC, MNC, routing indication, and network public key ID.

[0100] According to an embodiment, the hNRF can identify the RVAS provider PLMN using at least one of the information received from the vNRF (e.g., routing indicator, MCC, MNC). The hNRF can also obtain information from the RVAS provider PLMN corresponding to the information received from the vNRF. The hNRF can identify the RVAS provider PLMN corresponding to the information received from the vNRF and request rAUSF or rUDM information from the rNRF deployed in the RVAS provider PLMN. The hNRF can send an NF discovery request to the rNRF including at least one of SUCI, routing indicator information or network public key ID, and VPLMN ID.

[0101] According to the embodiments, the vNRF can use RVAS provider PLMN related information received from the hNRF (e.g., rAUSF identifier / address information, rUDM identifier / address information, RVAS provider PLMN ID, MCC, MNC information, etc.) to perform authentication and SUCI unsubscription operations for roaming UEs, and can obtain and use subscription data from the rUDM deployed in the RVAS provider PLMN.

[0102] According to embodiments, the rNRF can be an NRF deployed in the RVAS provider PLMN, a local hNRF deployed in the HPLMN, or an NRF storing information related to the RVAS provider PLMN. For example, the hNRF can identify the RVAS provider PLMN corresponding to information received from the vNRF and request rAUSF or rUDM information from another hNRF storing information related to the RVAS provider PLMN (e.g., a local hNRF or a specific hNRF, an NRF with a role capable of performing the rNRF). This can be achieved through... Figure 7 The process is used to perform such operations.

[0103] Figure 7 This invention illustrates a process for searching and discovering network functions of RVAS provider PLMN according to embodiments of the present disclosure.

[0104] Step 1. The UE may send a registration request message to the AMF that includes at least one of the following: SUCI (which may include information such as SUCI type and home network ID), routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID.

[0105] Step 2. The AMF may send an NF discovery request to the vNRF. This message may include at least one of the following: SUCI, routing indicator, VPLMNID, HPLMN ID, rPLMN ID, network public key ID, and NF information (type or identifier, or group identifier; for example, NF type information corresponding to the ASF as a notification of a search request against the ASF).

[0106] Step 3. Based on the information received from the AMF, the UE can identify the HPLMN, and the vNRF can send an NF discovery request message to the hNRF. This message may include at least one of the following: SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (type or identifier, or group identifier, e.g., NF type information corresponding to AUSF).

[0107] Step 4. The hNRF can determine the PLMN capable of processing the UE's signaling based on information received from the vNRF. For example, the hNRF can use information received from the vNRF to obtain subscription data from the hUDM, identify the UE as an RVAS target, and determine the RVAS provider PLMN (rPLMN ID). Alternatively, the hNRF can identify SUCI and routing indication information from information received from the vNRF based on local configuration information to determine whether a specific SUCI or routing indication value is an RVAS target (whether a search and discovery of network functions deployed in the RVAS provider PLMN should be performed). According to an embodiment, NF information (addresses and identifiers, etc.) deployed in the RVAS provider PLMN can be stored in the hNRF, and the hNRF can provide the information of NFs deployed in the RVAS provider PLMN to the vNRF without additional communication with the rNRF. In this case, steps 5 and 6 can be omitted.

[0108] Step 5. The hNRF can use the information received from the vNRF to determine the RVAS provider PLMN and can send an NF discovery request message to the rNRF deployed in the RVAS provider PLMN. This message may include at least one of the following as information received from the vNRF: SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (type or identifier, or group identifier). According to another embodiment, the rNRF may be an NRF deployed in the RVAS provider PLMN, a local hNRF deployed in the HPLMN, or an NRF storing information related to the RVAS provider PLMN. For example, the hNRF may identify the RVAS provider PLMN corresponding to the information received from the vNRF and request rAUSF or rUDM information from another hNRF storing information related to the RVAS provider PLMN (e.g., a local hNRF or a specific hNRF, an NRF capable of performing the rNRF role). In this case, the rNRF in the following steps may be an hNRF other than the hNRF requested by the vNRF.

[0109] Step 6. The rNRF can use at least one of the following as information received from the hNRF: SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (type or identifier or group identifier) ​​to determine the rAUSF, and can send the rAUSF information (address, identifier, etc.) to the hNRF.

[0110] Step 7. hNRF can provide the rAUSF information obtained through the previous steps to vNRF.

[0111] Step 8. vNRF can provide the rAUSF information obtained through the previous steps to AMF.

[0112] Steps 9 to 12. The AMF can use the rAUSF information obtained in the previous steps to perform authentication operations. For example, the AMF can send an authentication request message to the rAUSF including at least one of SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID, and the rAUSF can use the information received from the AMF to search for and identify the rUDM. The rAUSF can obtain authentication information from the rUDM and provide the authentication information to the AMF and the UE. During this process, the AMF can obtain SUPI information.

[0113] Step 13. After completing the authentication process, the AMF can obtain the SUPI of the UE requesting the registration process and can use at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID to perform operations for searching and selecting rUDM. For example, the AMF can send an NF discovery request to the vNRF including at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (corresponding to the NF type, identifier, group identifier, etc. of the UDM).

[0114] Step 14. The vNRF can use the information received from the AMF to determine the hNRF and can send an NF discovery request message. This message may include at least one of SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID.

[0115] Step 15. The hNRF can use information received from the vNRF, information set in the hNRF, or information obtainable from the hUDM to determine the PLMN (HPLMN or RVAS provider PLMN) corresponding to the SUPI. The hNRF can use information set in the hNRF, or can obtain subscription data from the hUDM, to perform the determination of the PLMN corresponding to the SUPI (determining whether the SUPI signaling should be processed in the HPLMN or RVAS provider PLMN). For example, at least one of the following can be set in the hNRF: a list of PLMN IDs (HPLMN ID or RVAS provider PLMN ID, etc.) corresponding to the SUPI range (IMSI range), RVAS target information corresponding to the list of PLMN IDs (HPLMN ID or RVAS provider PLMN ID, etc.) corresponding to the SUPI range (IMSI range), and RVAS authorization information. A list of PLMN IDs (HPLMN ID or RVAS provider PLMN ID, etc.) corresponding to the SUPI range (IMSI range), RVAS target information, and RVAS authorization information can be set in the hUDM, and this information can be provided to the hNRF. The hNRF can identify the RVAS provider PLMN corresponding to at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID, and can request and obtain rUDM information from the rNRF (the hNRF requests this information by providing the rNRF with at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID), or can identify the rUDM information set in the hNRF. The rNRF can identify rUDM information (address and identifier, etc.) corresponding to at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID, and can provide the rUDM information to the hNRF.

[0116] Step 16. hNRF can provide the rUDM information obtained through the above steps to vNRF.

[0117] Step 17. vNRF can provide the rUDM information obtained through the previous steps to AMF.

[0118] Step 18. The AMF can provide the rUDM with at least one of the SUPI, routing indicator, VPLMN ID, and HPLMN ID, and obtain subscription data. The RVAS authorization information corresponding to the SUPI can be included in the rUDM. The AMF can use the subscription data received from the rUDM to complete the registration process and send a registration acceptance message to the UE.

Claims

1. A method for operating a user equipment (UE) in a wireless communication system, the method comprising: Receive a first message from the Access and Mobility Management Function (AMF) including route indicator data update information sent from the Home Unified Data Management (H-UDM); The Subscription Hidden Identifier (SUCI) is generated based on the route indicator data update information. as well as Send a second message to AMF, including SUCI, for the registration request.

2. The method according to claim 1, wherein, The route indicator data update information includes at least one of the following: route indicator value, visited public land mobile network (VPLMN) ID, registered PLMN (RPLMN) ID, roaming value-added service (RVAS) network ID, mobile country code (MCC), network public key ID, priority value, UE confirmation request indication or re-registration request indication.

3. The method according to claim 1, wherein, The UE is configured with multiple International Mobile Subscriber Identity (IMSI), and each IMSI is mapped to a specific Public Land Mobile Network (PLMN) ID or a specific Mobile Country Code (MCC).

4. The method according to claim 2, further comprising: Based on the routing indicator data update information, which includes the UE confirmation request indication, send ACK information to AMF.

5. The method according to claim 2, further comprising: SUCI is generated by selecting the International Mobile Subscriber Identity (IMSI) corresponding to the route indicator value, VPLMN ID, or RPLMN ID included in the route indicator data update information.

6. The method according to claim 2, further comprising: The SUCI is generated based on the route indicator value and the network public key ID, which are used to register to the VPLMN ID.

7. The method according to claim 2, wherein, Based on multiple combinations of existing routing indication values ​​and network public key IDs corresponding to MCC or VPLMN IDs, a priority value is set for each combination.

8. The method according to claim 2, further comprising: The registration process is performed using the generated SUCI, based on the updated routing indicator data, which includes a re-registration request indication.

9. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as The controller, wherein the controller is configured as follows: Receive a first message from the Access and Mobility Management Function (AMF) including route indicator data update information sent from the Home Unified Data Management (H-UDM); Generate Subscription Hidden Identifier (SUCI) based on route indicator data update information; and The control sends a second message to the AMF, including SUCI, for the registration request.

10. The UE according to claim 9, wherein, The route indicator data update information includes at least one of the following: route indicator value, visited public land mobile network (VPLMN) ID, registered PLMN (RPLMN) ID, roaming value-added service (RVAS) network ID, mobile country code (MCC), network public key ID, priority value, UE confirmation request indication or re-registration request indication.

11. The UE according to claim 9, wherein, The UE is configured with multiple International Mobile Subscriber Identity (IMSI), and each IMSI is mapped to a specific Public Land Mobile Network (PLMN) ID or a specific Mobile Country Code (MCC).

12. The UE according to claim 10, wherein, The controller is configured to control the sending of ACK information to the AMF based on routing indicator data update information including a UE acknowledgment request indication.

13. The UE according to claim 10, wherein, The controller is configured to generate a SUCI by selecting an International Mobile Subscriber Identity (IMSI) corresponding to the route indicator value, VPLMN ID, or RPLMN ID included in the route indicator data update information.

14. The UE according to claim 10, wherein, The controller is configured to generate a SUCI based on the generated SUCI for registration to the VPLMN ID, using a routing indicator value and a network public key ID.

15. The UE according to claim 10, wherein, A priority value is set for each combination based on the existence of a routing indicator value and a network public key ID corresponding to an MCC or VPLMN ID.

Images