Method and apparatus for processing signaling of roaming terminal

Abstract

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

Description

Method and device for processing signaling of a roaming terminal

[0001] The present invention relates to a wireless communication system, and more particularly, to a method for routing and processing signaling of a roaming terminal in a mobile communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] If a home network operator operates multiple PLMNs (e.g., uses multiple PLMN IDs), there is no support for selecting a PLMN to handle signaling for a particular roaming subscriber and associating that PLMN with the network to which the subscriber is roaming.

[0009] Routing signaling from a roaming terminal to another core network operated by the home network operator or to a partner core network of the home network operator is not supported.

[0010] A method of operating a user equipment (UE) in a wireless communication system according to one embodiment of the present disclosure may include receiving a first message including routing indicator data update information transmitted from a home-unified data management (H-UDM) from an access and mobility management function (AMF); generating a subscription concealed identifier (SUCI) based on the routing indicator data update information; and transmitting a second message for a registration request including the SUCI to the AMF.

[0011] In a wireless communication system according to one embodiment of the present disclosure, a user equipment (UE) includes a transceiver; and a control unit. The control unit can receive a first message including routing indicator data update information transmitted by a home-unified data management (H-UDM) from an access and mobility management function (AMF). The control unit can generate a subscription concealed identifier (SUCI) based on the routing indicator data update information. The control unit can control a second message for a registration request including the SUCI to be transmitted to the AMF.

[0012] A method and device according to an embodiment of the present invention can determine a PLMN providing a roaming value added service (RVAS) to which signaling traffic of a roaming terminal should be routed and processed.

[0013] The method and device according to an embodiment of the present invention can process signaling and traffic of a roaming terminal by routing them to a specific PLMN according to the intention of a home network operator, or route the traffic of the terminal to a core network of a partner operator of the home network operator.

[0014] FIG. 1A and FIG. 1B illustrate a 5G system architecture supporting edge computing roaming service according to one embodiment of the present disclosure.

[0015] FIG. 2 illustrates an example of a network structure for supporting roaming value added service (RVAS) according to one embodiment of the present disclosure.

[0016] FIGS. 3A and 3B illustrate a procedure for providing routing indicator data to a terminal and a registration procedure using the provided routing indicator data according to one embodiment of the present disclosure.

[0017] FIG. 4 illustrates a method for supporting RVAS using routing indicator data update according to one embodiment of the present disclosure.

[0018] FIG. 5 is a device diagram of a terminal according to one embodiment of the present disclosure.

[0019] FIG. 6 is a device diagram of a network entity according to one embodiment of the present disclosure.

[0020] FIG. 7 illustrates a procedure for searching and discovering network functions of an RVAS provider PLMN according to one embodiment of the present disclosure.

[0021] The operating principles of the present invention are described in detail with reference to the attached diagram. The terms described below are defined based on their functions within the present invention. These terms may vary depending on the intent or custom of the user or operator, and therefore their definitions should be determined based on the overall content of this specification.

[0022] The terms used in this publication to refer to network entities or network function objects, terms referring to messages, terms referring to identification information, and the like are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms that refer to objects with equivalent technical meanings may be used.

[0023] For convenience, the present invention uses terms and names defined in the 5G system standards, but is not limited by the terms and names, and can be equally applied to systems conforming to other standards.

[0024] FIG. 1A and FIG. 1B illustrate a 5G system architecture supporting edge computing roaming service according to one embodiment of the present disclosure.

[0025] A 5G system architecture supporting edge computing services may include various network functions (NFs), and FIGS. 1A and 1B illustrate some of them, including an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a unified data management (UDM), a data network (DN) or a local part of DN that enables local access to the data network, a user plane function (UPF), a (radio) access network (R)AN, and user equipment (UE).

[0026] Each NF supports the following functions:

[0027] - AMF provides functions for access and mobility management at the UE level, and one UE can be connected to one AMF by default.

[0028] - DN refers to, for example, operator services, Internet access, or third-party services. DN transmits downlink protocol data units (PDUs) to UPF or receives PDUs transmitted from UEs from UPF. Local part of DN refers to a data network with a short data transmission path that allows local access to a portion of the DN. It can be used to refer to a DN where an edge application server supporting edge computing services is deployed.

[0029] - PCF receives information about packet flows from application servers and provides the function to determine policies such as mobility management and session management. Specifically, PCF supports functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane functions(e.g., AMF, SMF, etc.) can enforce the policy rules, and implementing a front end to access relevant subscription information for policy decision within the unified data repository (UDR).

[0030] - SMF provides session management functions, and when a UE has multiple sessions, each session can be managed by a different SMF.

[0031] - UDM stores user subscription data, policy data, etc.

[0032] - UPF transmits downlink PDUs received from DN to UE via (R)AN, and transmits uplink PDUs received from UE via (R)AN to DN. ULCL (uplink classifier) ​​refers to UPF that has the function of classifying and transmitting uplink. L-UPF (local UPF) performs the role of termination (PDU Session Anchor) of sessions transmitted to local part of DN.

[0033] - EASDF processes domain name system queries sent by terminals according to rules provided by the SMF. For example, it can perform actions such as forwarding DNS queries sent by terminals to a DNS server, receiving DNS responses, sending related reports to the SMF, and providing DNS responses to the terminals.

[0034] Figure 1a shows an example of a 5G system architecture for HR (home routing) roaming, and Figure 1b shows an example of a 5G system architecture for LBO (local breakout) roaming.

[0035] In Fig. 1a, for HR roaming, the VPLMN (visited public land mobile network) may include a UE, (R)AN, UPF, AMF, V-SMF (visited-SMF), and V-PCF (visited-PCF), and the HPLMN (home public land mobile network) may include a UPF, DN (data network), H-SMF (home-SMF), H-PCF (home-PCF), AF, and UDM. In Fig. 1b, for LBO roaming, the VPLMN may include a UE, (R)AN, UPF, AMF, V-SMF, and V-PCF, and the HPLMN may include a UDM.

[0036] FIG. 2 illustrates an example of a network structure for supporting a roaming value added service (RVAS) according to one embodiment of the present disclosure. FIG. 2 illustrates a network structure that displays a signaling and traffic transmission path related to a roaming terminal to an RVAS-providing PLMN (hereinafter referred to as an RVAS PLMN) that processes signaling and traffic of a terminal instead of an HPLMN in a situation where a home routing session is used.

[0037] Referring to FIG. 2, the HPLMN may include H-UPF, Data Network, H-SMF, H-PCF, UDM, and AUSF, the VPLMN may include UE, RAN, V-UPF, AMF, V-SMF, and V-PCF, and the RVAS PLMN may include R-AUSF, R-UDM, R-SMF, R-UPF, and Data Network.

[0038] Signaling related to a roaming terminal may be transmitted from the AMF of the VPLMN to the AUSF or UDM of the HPLMN, but may be transmitted to the R-AUSF or R-UDM deployed in the RVAS PLMN. In addition, the user plane data traffic of the roaming terminal may be routed from the VPLMN UPF (V-UPF) to the R-UPF of the RVAS PLMN, rather than to the HPMN UPF (H-UPF).

[0039] FIGS. 3A and 3B illustrate a procedure for providing routing indicator data to a terminal and a registration procedure for using the provided routing indicator data according to one embodiment of the present disclosure.

[0040] Step 1. The home UDM (hUDM) of a terminal (or UE) may determine whether to update routing indicator data to support RVAS by considering terminal subscriber information (subscription data). For example, the hUDM may store at least one of RVAS support information or RVAS allowed information, RVAS provider PLMN ID (RVAS-providing PLMN ID; PLMN information providing RVAS service; rPLMN ID), RVAS-supporting VPLMN information, and RVAS-supporting country information (e.g., MCC information) in the subscription data for a specific terminal (or a specific terminal group, or a specific terminal identifier range, IMSI range), and may determine to update routing indicator data for a terminal that has the corresponding information as subscription data.

[0041] Step 1 may be performed when information indicating that the terminal has applied for a roaming service is provided to the hUDM, or when information indicating that the terminal has registered for a roaming service in a specific country or PLMN is provided to the hUDM. Additionally, whether or not to perform Step 1 may be determined based on operator policies set within the hUDM.

[0042] Step 2. The hUDM can transmit routing indicator data update information for a specific UE to the AMF, taking into account the subscription data information. The request can be performed by using the Nudm_SDM_Notification message or by transmitting a separate message. The information transmitted by the hUDM to the AMF can include at least one of a routing indicator value, a VPLMN ID, an rPLMN ID, an RVAS network ID, country information (MCC), a Network public key ID, a priority value, a UE acknowledgment requested indication, and a re-registration requested indication. The hUDM can set the routing indicator value to a value that can be used to discover and select an AUSF and UDM (rAUSF and rUDM) deployed in an RVAS provider PLMN (RVAS PLMN or rPLMN), rather than a value used to discover and select an AUSF and UDM of the HPLMN, and transmit it to the AMF.

[0043] The UDM can transmit the VPLMN ID as VPLMN information that can or must use the routing indicator value to the AMF. The RVAS provider PLMN information (rPLMN ID) provided by the hUDM can be mapped to the routing indicator value and the VPLMN ID, and can be information for indicating the PLMN where the AUSF / UDM that must be searched and selected is deployed through the routing indicator value. The network public key ID provided by the hUDM can be provided as a network public key ID that can be used in the RVAS provider PLMN or to search and discover the rAUSF / rUDM when provided together with the RVAS-related information.

[0044] The hUDM can provide a combination of multiple routing indicator values, VPLMN ID, rPLMN ID, RVAS network ID, country information (MCC), and Network public key ID values ​​to the AMF. In addition, the hUDM can provide routing indicator values, VPLMN ID, HPLMN ID, country information, and Home Network public key ID information along with RVAS PLMN-related routing indicator values, VPLMN ID, rPLMN ID, RVAS network ID, and Network public key ID values, and the terminal can use the information received from the hUDM to attempt to connect to the HPLMN when connection to the PLMN providing RVAS fails. For example, the hUDM can transmit to the AMF, together with the routing indicator value, VPLMN ID, rPLMN ID, RVAS network ID, and Network public key ID information related to the RVAS PLMN (for routing signaling to the RVAS PLMN), and the routing indicator value, VPLMN ID, rPLMN ID, RVAS network ID, and Network public key ID information for routing signaling to the HPLMN, and provide the terminal with the information. The RVAS PLMN-related information can be given a higher priority than the HPLMN-related information so that the terminal's signaling can be preferentially routed to the RVAS PLMN, and when routing to the RVAS PLMN is impossible or fails, the terminal signaling can be routed to the HPLMN so that the roaming service can be continued.

[0045] Step 3. If the AMF determines that it cannot immediately transmit the information received from the hUDM to the UE (e.g., the UE is not reachable), it may notify the hUDM of a failure in transmitting the UE Parameter Update data procedure. In this case, the procedures below will not be performed, and the AMF may wait until it can signal the UE.

[0046] Step 4. AMF can transmit the routing indicator data update information received from hUDM to the terminal. The information can be transmitted in the UE Parameter Update container.

[0047] Step 5. If the UE acknowledgement requested indication is included in the information received from the AMF, the terminal can transmit ACK information to the AMF.

[0048] Step 6. AMF can send a message to hUDM notifying that the terminal has successfully received routing indicator data update information.

[0049] Step 7. When the hUDM successfully receives from the AMF that the terminal has received the routing indicator data update, it can notify the AMF and other NFs of the routing indicator value.

[0050] Step 8. When the terminal receives a routing indicator data update through AMF, the terminal can generate a SUCI (Subscription Concealed Identifier) ​​using the information included in the routing indicator data update, rather than the information stored in the existing USIM or ME. The terminal can have multiple IMSIs (International Mobile Subscriber Identities). Each IMSI can be mapped to specific PLMN information (e.g., PLMN ID) or specific country (e.g., MCC) information. The terminal can generate a SUCI by selecting an IMSI that can be used in correspondence with information such as the routing indicator value, VPLMN ID, and rPLMN ID included in the routing indicator data received in the previous step. For example, the terminal may select or identify a VPLMN ID or MCC received from a UDM corresponding to a PLMN ID value selected through a PLMN selection operation, and generate a SUCI using an rPLMN ID or RVAS network ID, routing indicator value, Network public key ID value, and IMSI corresponding to the VPLMN ID or MCC.

[0051] When generating a SUCI for registration to the VPLMN ID selected during PLMN selection in a country other than the HPLMN, the terminal can generate the SUCI using the routing indicator and network public key ID received from the hUDM. If the terminal has received multiple routing indicator and network public key ID combinations from the UDM, the terminal can select and use the routing indicator and network public key ID corresponding to the MCC value or VPLMN ID of the country in which the terminal is roaming.

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

[0053] When a terminal receives a re-registration request indication, it can perform a registration procedure using the generated SUCI. In this case, the terminal can attempt the registration procedure by generating a SUCI using a combination of a routing indicator and a network public key ID according to the priority value. For example, if registration is attempted using a routing indicator and network public key ID corresponding to a specific MCC or VPLMN ID but fails, a routing indicator and network public key ID with the next priority value can be used.

[0054] Even if the terminal does not receive a re-registration requested indication from the UDM, it can re-perform the registration procedure on its own if it receives RVAS-related routing indicator information.

[0055] Step 9. The terminal may send a registration request message containing the SUCI generated in Step 8 to the AMF. The terminal may also provide the home network ID (HPLMN ID) to the AMF along with the SUCI.

[0056] Step 10. The AMF may perform rAUSF (AUSF of RVAS PLMN) discovery and selection procedure using the routing indicator information or network public key ID included in the SUCI received from the terminal. If rAUSF information corresponding to the routing indicator or network public key ID is set in the AMF, the set information may be used. If rAUSF information (address and identifier) ​​corresponding to the routing indicator or network public key ID is not set, the AMF may transmit an NF discovery request to the vNRF (NRF of VPLMN). The NF discovery request message may include at least one of the SUCI, the routing indicator, or the network public key ID.

[0057] Step 11. The vNRF selects an rNRF (NRF of an RVAS PLMN) using the information received from the AMF, and requests and obtains rAUSF information (address and identifier) ​​by providing at least one of the SUCI, routing indicator, and network public key ID received from the AMF.

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

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

[0060] Step 14. rAUSF can obtain authentication information for the terminal from rUDM (UDM of RVAS PLMN). rAUSF can use internal configuration information or information such as SUCI, routing indicator, and network public key to select the rUDM that provides authentication information. rAUSF provides SUCI when requesting authentication information, and UDM can convert SUCI to SUPI and provide it.

[0061] Step 15. rAUSF can provide authentication information to AMF in the response message of Step 13.

[0062] Step 16. AMF provides authentication information to the terminal for authentication completion, returns a response, and transmits the authentication-related information returned by the terminal to rAUSF to perform authentication-related operations. AMF can obtain successful authentication results and SUPI information from rAUSF.

[0063] Step 17. The AMF can perform search and selection operations for the rUDM using the information in the SUCI received from the terminal and the SUPI acquired in the previous step. If rUDM information corresponding to the routing indicator or network public key ID in the AMF is set, the set information can be used. If rUDM information (address and identifier) ​​corresponding to the 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 can include at least one of the SUPI, SUCI, routing indicator, or network public key ID.

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

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

[0066] Step 20. The AMF can send a registration request and a subscription data request to the rUDM identified by the rUDM information obtained in the previous step. The rUDM can check the SUPI included in the information received from the AMF and confirm whether the terminal is a terminal of an RVAS-targeted subscriber. If the terminal is an RVAS-targeted subscriber, it can provide the AMF with Access and Mobility subscription data and subscription data related to SMF selection.

[0067] Step 21. AMF can send a Registration Accept message to the terminal indicating that it has been successfully registered.

[0068] Step 22. The terminal can send a PDU Session Establishment request message to AMF to receive data services.

[0069] Step 23. When the AMF receives a PDU Session Establishment request message from the terminal, the AMF can select an SMF that can connect to the RVAS provider PLMN that can provide roaming services to the terminal when selecting a vSMF. For example, the AMF can select a vSMF using information such as routing indicator, SUPI, and rPLMN ID that can be obtained through the previous steps. In addition, the AMF can select an rSMF deployed in the RVAS provider PLMN using information such as routing indicator, SUPI, and rPLMN ID, and transmit a PDU Session Establishment request message including the corresponding rSMF information (address and identifier) ​​to the vSMF.

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

[0071] FIG. 4 illustrates a method for supporting RVAS using routing indicator data update according to one embodiment of the present disclosure.

[0072] Step 1. In the home UDM (hUDM) of the terminal, at least one of RVAS support information or RVAS allowed information, RVAS provider PLMN ID (RVAS-providing PLMN ID; PLMN information providing RVAS service; rPLMN ID), RVAS-supporting VPLMN information (VPLMN ID), RVAS-supporting country information (e.g., MCC information), and rUDM information (address and identifier) ​​deployed in the RVAS provider PLMN may be set for a specific terminal (or a specific terminal group, or a specific terminal identifier range, IMSI range). Subscription data for a roaming terminal corresponding thereto may be set in the rUDM (UDM deployed in the RVAS provider PLMN and capable of connecting to the hUDM).

[0073] Step 2. The terminal can send a Registration Request message to the AMF located in the VPLMN of the country being visited to receive roaming services. This message includes SUCI information.

[0074] Step 3. AMF selects hAUSF and hUDM to convert the terminal's SUCI to SUPI and performs the authentication procedure. After successful authentication, it can send a UE Context Management Registration or subscription data request message to hUDM.

[0075] Step 4. When the hUDM receives a Registration request or a Subscription data request message from the AMF in the previous step, if RVAS service support / allowance information is stored in the hUDM for the VPLMN ID currently registered by the terminal or the country being visited (country information identified by MCC), the hUDM may decide to redirect signaling for the roaming terminal. The RVAS service support / allowance information may be set to correspond to a specific VPLMN ID or country information (MCC) value for a specific terminal, a specific terminal group, or a specific terminal identifier range (e.g., SUPI or IMSI range). In addition, a list of rPLMN IDs corresponding to the VPLMN IDs or country information (MCC) associated with the RVAS service support / allowance information, and rUDM address and identifier information for each rPLMN ID may be stored in the hUDM.

[0076] Step 5. hUDM may provide RVAS redirection information to AMF in a response message to Step 3. The RVAS redirection information may include rPLMN ID, rAUSF, and rUDM address information.

[0077] Step 6. AMF performs authentication operation between the terminal and the rPLMN using the rAUSF and rUDM address information received from the hUDM, and after successful authentication, can send a UE Context Management Registration or subscription data request message to the rUDM.

[0078] Step 7. The rUDM can verify subscriber information for the roaming terminal and provide subscription data required for access and mobility management-related operations and SMF selection operations to the AMF within the rPLMN.

[0079] Step 8. When AMF successfully receives subscription data from rUDM, it can send a registration accept message to the terminal.

[0080] Step 9. The terminal can send a PDU Session Establishment request message to AMF to use future data services.

[0081] Step 10. The AMF may send a PDU Session Creation Request message to the vSMF. The message may contain an rSMF identifier and address information selected by the AMF. The AMF may search for and select an rSMF (SMF deployed in the RVAS provider PLMN) based on the rPLMN ID obtained through the previous steps, rather than an hSMF that can be identified by the HPLMN ID available in the SUPI of the terminal or terminal-related subscription data information, and provide the rSMF to the vSMF. The vSMF may send a PDU Session Creation Request message to the rSMF received from the AMF.

[0082] FIG. 5 is a device diagram of a terminal according to one embodiment of the present disclosure.

[0083] In the embodiment of FIG. 5, the terminal may be a UE or terminal illustrated in FIGS. 1 to 4 and FIG. 7, respectively. Referring to FIG. 5, the terminal may include a transceiver (510), a control unit (520), and a storage unit (530). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit, or at least one processor.

[0084] The transceiver (510) can transmit and receive signals with a base station or network entity. The transceiver (510) can transmit and receive data with a base station or network entity, for example, using wireless communication.

[0085] The control unit (520) can control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (520) can control the signal flow between each block to perform the operations described with reference to FIGS. 1 to 4 and FIG. 7.

[0086] The storage unit (530) can store at least one of the information transmitted and received through the transmission and reception unit (510) and the information generated through the control unit (520). For example, the storage unit (530) can store information and data required for the method described with reference to FIGS. 1 to 4 and FIG. 7, for example.

[0087] FIG. 6 is a device diagram of a network entity according to one embodiment of the present disclosure.

[0088] In the embodiment of FIG. 6, the network entity may be implemented as one of a base station (RAN), AMF, hUDM (UDM of HPLMN), vNRF (NRF of VPLMN), rNRF (NRF of RVAS), rAUSF (AUSF of RVAS), rUDM (UDM of RVAS), rSMF (SMF of RVAS) as shown in FIGS. 1 to 4 and FIG. 7, respectively.

[0089] Referring to FIG. 6, a network entity may include a transceiver (610), a control unit (620), and a storage unit (630). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0090] The transceiver (610) can transmit and receive signals with a terminal, a base station, or another network entity. The transceiver (610) can transmit and receive data with a terminal, a base station, or another network entity, for example, using wireless communication.

[0091] The control unit (620) can control the overall operation of a network entity according to an embodiment proposed in the present disclosure. For example, the control unit (620) can control the signal flow between each block to perform the operations described with reference to FIGS. 1 to 4 and FIG. 7.

[0092] The storage unit (630) can store at least one of the information transmitted and received through the transmission and reception unit (610) and the information generated through the control unit (620). For example, the storage unit (630) can store information and data required for the method described with reference to FIGS. 1 to 4 and FIG. 7, for example.

[0093] According to one embodiment, the RVAS provider PLMN related information (a set of information including at least one of rAUSF, rUDM, and RVAS provider PLMN ID) may be modified to route signaling to the RVAS provider PLMN using the routing indicator information described in the embodiments of FIGS. 3a and 3b.

[0094] After step 9 of FIG. 3a, the AMF or the NF of the PLMN where the UE is roaming can perform rAUSF (AUSF of RVAS PLMN) discovery and selection procedure using the routing indicator information or network public key ID included in the acquired SUCI (e.g., received from the UE). If rAUSF information corresponding to the MNC, MCC, or roaming service-related PLMN ID, routing indicator, or network public key ID is set in the AMF, the set information can be used. If the rAUSF information (address and identifier) ​​corresponding to the received routing indicator or network public key ID is not set, the AMF can transmit an NF discovery request to the vNRF (NRF of VPLMN). The NF discovery request message can include at least one of the SUCI, the routing indicator, or the network public key ID.

[0095] In one embodiment, the vNRF may decide to send an NF discovery request to the hNRF considering information received from the AMF. For example, the vNRF may decide to send an NF discovery request to the hNRF considering MNC and MCC information. The NF discovery request that the vNRF sends to the hNRF may include at least one of SUCI, routing indicator information, network public key ID, VPLMN ID, etc. acquired by the AMF in the previous step, and NF information to be discovered (NF information pointing to an AUSF or UDM).

[0096] In one embodiment, when the hNRF receives an NF discovery request from the vNRF including at least one of SUCI, routing indicator information, network public key ID, VPLMN ID, etc., and confirms that the NF discovery request is a discovery request for an AUSF or UDM, the hNRF may perform an operation to determine or obtain AUSF or UDM information located in an RVAS provider PLMN that matches the information. For example, the hNRF may store RVAS provider PLMN-related information (e.g., rAUSF identifier / address information, rUDM identifier / address information, RVAS provider PLMN ID, MCC, MNC information, etc.) that may correspond to a combination of information including at least one of SUCI, IMSI range, SUPI range, PLMN ID, MCC, MNC, routing indicator, network public key ID.

[0097] According to one 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 corresponding to the information received from the vNRF from the RVAS provider PLMN. 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 located in the RVAS provider PLMN. The hNRF can transmit an NF discovery request including at least one of the following information: SUCI, routing indicator information, network public key ID, VPLMN ID, etc. to the rNRF.

[0098] According to one embodiment, the vNRF may perform authentication and SUCI deconcealment operations for a roaming terminal using RVAS provider PLMN-related information (e.g., rAUSF identifier / address information, rUDM identifier / address information, RVAS provider PLMN ID, MCC, MNC information, etc.) received from the hNRF, and may obtain and use subscription data from the rUDM deployed in the RVAS provider PLMN.

[0099] According to one embodiment, the rNRF may be an NRF deployed in an RVAS provider PLMN, a local hNRF deployed in an HPLMN, or an NRF storing information related to the RVAS provider PLMN. For example, the hNRF may identify an RVAS provider PLMN corresponding to the information received from the vNRF and request rAUSF or rUDM information from another hNRF (e.g., a local hNRF, a specific hNRF, or an NRF that can perform the role of an rNRF) that stores information related to the RVAS provider PLMN. Such an operation may be performed through the procedure of FIG. 7.

[0100] FIG. 7 illustrates a procedure for searching and discovering network functions of an RVAS provider PLMN according to one embodiment of the present disclosure.

[0101] Step 1. The terminal may transmit a registration request message to the AMF, which includes at least one of 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.

[0102] Step 2. AMF can send NF discovery request to vNRF. The message can include at least one of SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, NF information (type or identifier, or group identifier; for example, NF type information corresponding to AUSF as information that can notify AUSF of discovery request).

[0103] Step 3. Based on the information received from the AMF, the terminal can identify the HPLMN and send an NF discovery request message to the hNRF. The message can include at least one of SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (type or identifier, or group identifier, for example, NF type information corresponding to AUSF).

[0104] Step 4. The hNRF can determine the PLMN capable of processing signaling of the corresponding terminal based on the information received from the vNRF. For example, the hNRF can use the information received from the vNRF to obtain subscription data from the hUDM to confirm that the corresponding terminal is an RVAS target and determine the RVAS provider PLMN (rPLMN ID). Alternatively, the hNRF can check the SUCI and routing indicator information in the information received from the vNRF based on local configuration information to determine whether a specific SUCI or a specific routing indicator value is an RVAS target (to determine whether search and discovery for network functions deployed in the RVAS provider PLMN should be performed). According to one embodiment, the hNRF may store information (such as addresses and identifiers) of NFs deployed in the RVAS provider PLMN, and the hNRF may provide information of NFs deployed in the RVAS provider PLMN to the vNRF without additional interworking with the rNRF. In this case, steps 5 and 6 can be omitted.

[0105] Step 5. The hNRF may determine the RVAS provider PLMN using the information received from the vNRF, and may transmit an NF discovery request message to the rNRF deployed in the RVAS provider PLMN. The message may include at least one of the following information received from the vNRF: SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, 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 can identify the RVAS provider PLMN corresponding to the information received from the vNRF and request rAUSF or rUDM information from another hNRF (e.g., a local hNRF or a specific hNRF, or an NRF that can perform the rNRF role) that stores information related to the RVAS provider PLMN. In this case, the rNRF in the step below may be the hNRF requested by the vNRF, not the hNRF.

[0106] Step 6. The rNRF can determine the rAUSF using at least one of the information received from the hNRF, namely SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (type or identifier, or group identifier), and transmit the information (address, identifier, etc.) of the rAUSF to the hNRF.

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

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

[0109] Steps 9-12. The AMF can perform authentication operations using the rAUSF information acquired in the previous steps. For example, the AMF sends an authentication request message including at least one of SUCI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID to the rAUSF, and the rAUSF can search for and determine the rUDM using the information received from the AMF. The rAUSF can acquire authentication information from the rUDM and provide it to the AMF and the terminal. In this process, the AMF can acquire SUPI information.

[0110] Step 13. After completing the authentication operation, the AMF can obtain the SUPI of the terminal that requested the registration procedure, and can perform an operation to search and select an rUDM using at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID. For example, the AMF can transmit an NF discovery request including at least one of the SUPI, routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, network public key ID, and NF information (NF type, identifier, group identifier, etc. corresponding to the UDM) to the vNRF.

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

[0112] Step 15. The hNRF can determine the PLMN (HPLMN or RVAS provider PLMN) corresponding to the SUPI using the information received from the vNRF, the information configured in the hNRF, or the information obtainable from the hUDM. The hNRF can use the information configured in the hNRF or obtain subscription data from the hUDM to determine the PLMN corresponding to the SUPI (e.g., whether signaling for the SUPI should be processed in the HPLMN or the RVAS provider PLMN). For example, at least one of a PLMN ID list (such as an HPLMN ID or an RVAS provider PLMN ID) corresponding to the SUPI range (IMSI range) in the hNRF, a PLMN ID list (such as an HPLMN ID or an RVAS provider PLMN ID) corresponding to the SUPI range (IMSI range), RVAS target information, and RVAS authorization information may be configured. A list of PLMN IDs (such as HPLMN ID or RVAS provider PLMN ID) corresponding to the SUPI range (IMSI range) in hUDM, information on whether RVAS is targeted, and RVAS authorization information may be set, and the information may be provided to hNRF.The hNRF can determine an RVAS provider PLMN corresponding to at least one piece of information from among SUPI and routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID, and obtain rUDM information from the rNRF by requesting it (wherein the hNRF requests the rNRF while providing at least one piece of information from among SUPI and routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID to the rNRF), or determine rUDM information set in the hNRF. The rNRF can determine information of rUDM information (such as an address and identifier) ​​corresponding to at least one piece of information from among SUPI and routing indicator, VPLMN ID, HPLMN ID, rPLMN ID, and network public key ID, and provide it to the hNRF.

[0113] Step 16. hNRF can provide the rUDM information acquired through the above-described steps to vNRF.

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

[0115] Step 18. The AMF can obtain subscription data by providing the rUDM with at least one of the SUPI, routing indicator, VPLMN ID, and HPLMN ID. The rUDM may contain RVAS authorization information corresponding to the SUPI. The AMF can use the subscription data received from the rUDM to complete the registration procedure and send a registration accept message to the terminal.

Claims

1. In a method of operating a UE (user equipment) in a wireless communication system, An operation of receiving a first message including routing indicator data update information transmitted by H-UDM (home-unified data management) from AMF (access and mobility management function); An operation of generating a subscription concealed identifier (SUCI) based on the above routing indicator data update information; and A method characterized by comprising the action of transmitting a second message for a registration request including said SUCI to said AMF.

2. In paragraph 1, the routing indicator data update information is: A method characterized by including at least one of a routing indicator value, a visited public land mobile network (VPLMN) ID, a registered PLMN (RPLMN) ID, a roaming value added service (RVAS) network ID, a mobile country code (MCC), a network public key ID, a priority value, a UE acknowledgement requested indication, and a re-registration requested indication.

3. In paragraph 1, Multiple IMSIs (international mobile subscriber identities) are set up in the above UE, A method characterized in that each IMSI is mapped to a specific PLMN (public land mobile network) ID or a specific MCC (mobile country code).

4. In paragraph 2, A method characterized in that the method further includes an operation of transmitting ACK information to the AMF if the routing indicator data update information includes the UE acknowledgement requested indication.

5. In paragraph 2, A method further comprising an operation of generating the SUCI by selecting an international mobile subscriber identity (IMSI) corresponding to the routing indicator value, the VPLMN ID, or the RPLMN ID included in the routing indicator data update information.

6. In paragraph 2, A method characterized by further including an operation of generating the SUCI using the routing indicator value and the network public key ID when generating the SUCI for registration to the VPLMN ID.

7. In paragraph 2, A method characterized in that, when there are multiple combinations of the routing indicator value and the network public key ID corresponding to the MCC or the VPLMN ID, a priority value is set for each combination.

8. In paragraph 2, A method characterized in that it further includes an action of performing a registration procedure using the generated SUCI if the above routing indicator data update information includes the re-registration requested indication.

9. In a wireless communication system, in the UE (user equipment), Transmitter and receiver; and comprising a control unit, said control unit comprising: Receive a first message including routing indicator data update information transmitted by H-UDM (home-unified data management) from AMF (access and mobility management function), Generate a SUCI (subscription concealed identifier) ​​based on the above routing indicator data update information, A UE characterized by controlling to transmit a second message for a registration request including the SUCI to the AMF.

10. In paragraph 9, the routing indicator data update information is: A UE characterized by including at least one of a routing indicator value, a visited public land mobile network (VPLMN) ID, a registered PLMN (RPLMN) ID, a roaming value added service (RVAS) network ID, a mobile country code (MCC), a network public key ID, a priority value, a UE acknowledgement requested indication, and a re-registration requested indication.

11. In paragraph 9, Multiple IMSIs (international mobile subscriber identities) are set up in the above UE, A UE characterized in that each IMSI is mapped to a specific public land mobile network (PLMN) ID or a specific mobile country code (MCC).

12. In paragraph 10, the control unit, A UE characterized in that it controls to transmit ACK information to the AMF if the above routing indicator data update information includes the UE acknowledgement requested indication.

13. In paragraph 10, the control unit, A UE characterized in that it generates the SUCI by selecting the IMSI (international mobile subscriber identity) corresponding to the routing indicator value, the VPLMN ID, or the RPLMN ID included in the routing indicator data update information.

14. In paragraph 10, the control unit, A UE characterized in that when generating a SUCI for registration to the above VPLMN ID, the SUCI is generated using the routing indicator value and the network public key ID.

15. In paragraph 10, A UE characterized in that, when there are multiple combinations of the routing indicator value and the network public key ID corresponding to the MCC or the VPLMN ID, a priority value is set for each combination.

Images