Method and device for supporting heterogeneous network service in wireless communication system
Patent Information
- Application Number
- PCT/KR2026/095241
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-03-27
- Filing Date
- 2026-03-25
- Publication Date
- 2026-10-01
Smart Images
Figure KR2026095241_01102026_PF_FP_ABST
Abstract
Description
Method and device for supporting heterogeneous network services in a wireless communication system
[0001] The present disclosure relates to a method and apparatus for supporting heterogeneous network services in a wireless 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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.
[0008] The present disclosure proposes a method and apparatus for supporting heterogeneous network services in a wireless communication system.
[0009] The technical problems to be solved by the present disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art from the various embodiments of the present disclosure described below.
[0010] A method performed by user equipment (UE) in a wireless communication system according to one embodiment of the present disclosure comprises: receiving UE policy information through an access and mobility management function (AMF) from a policy control function (PCF), the information including first information regarding at least one network entity configured for a non-3GPP (non-3rd Generation Partnership Project) management function; selecting a first network entity configured for a non-3GPP management function based on the first information; transmitting a connection request message to the first network entity; and receiving a response message for the connection request message from the first network entity.
[0011] A method performed by a first network entity configured for a non-3GPP (non-3rd Generation Partnership Project) management function in a wireless communication system according to one embodiment of the present disclosure comprises: receiving a connection request message from a UE (user equipment); and transmitting a response message to the connection request message to the UE, wherein the connection request message is based on UE policy information comprising first information regarding at least one network entity configured for a non-3GPP management function.
[0012] According to one embodiment of the present disclosure, in a wireless communication system, a user equipment (UE) comprises: a transceiver; and at least one processor, wherein the at least one processor receives UE policy information including first information regarding at least one network entity configured for a non-3GPP (non-3rd Generation Partnership Project) management function from a policy control function (PCF) via an access and mobility management function (AMF), selects the first network entity configured for a non-3GPP management function based on the first information, transmits a connection request message to the first network entity, and receives a response message for the connection request message from the first network entity.
[0013] According to one embodiment of the present disclosure, a first network entity configured for a non-3GPP (non-3rd Generation Partnership Project) management function in a wireless communication system comprises: a transceiver; and at least one processor, wherein the at least one processor is configured to receive a connection request message from a UE (user equipment) and to transmit a response message to the connection request message to the UE, and the connection request message is based on UE policy information comprising first information regarding the at least one network entity configured for a non-3GPP management function.
[0014] The present disclosure can improve communication performance by reducing the complexity of interface configuration, as a network entity performing non-3GPP (generation partnership project) management functions to support heterogeneous network services in a wireless communication system supports connection and linkage procedures, authentication procedures, session procedures, etc., of a terminal connected through a non-3GPP network.
[0015] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.
[0016] FIG. 1 illustrates an example of a system structure of a 5G mobile communication network according to one embodiment of the present disclosure.
[0017] FIGS. 2a, 2b, and 2c illustrate an example of a system structure for non-3GPP access in a 5G mobile communication network according to one embodiment of the present disclosure.
[0018] FIG. 3 illustrates an example of a procedure for registering a non-3GPP management function (N3MF) to a network repository function (NRF) according to one embodiment of the present disclosure.
[0019] FIG. 4 illustrates an example of a discovery and selection procedure for N3MF according to one embodiment of the present disclosure.
[0020] FIG. 5 illustrates an example of a connection procedure through an N3MF (e.g., an ePDG (evolved packet data gateway)) of a UE (user equipment) according to one embodiment of the present disclosure.
[0021] FIG. 6 is a diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.
[0022] The drawings are included as reference examples to aid in understanding the present disclosure and are not limited to specific embodiments of the invention. Specific details depicted in the drawings are included to supplement the overall technical background and context of the present disclosure and may provide technical information useful to the present disclosure even if not directly specified in the claims.
[0023] The operating principle of the present invention will be described in detail below with reference to the attached drawings. Furthermore, the terms described below are defined in consideration of their functions within the present invention. Since these definitions may vary depending on the intentions or conventions of the user or operator, they must be determined according to the content throughout this specification. In this regard, it should be noted that identical components in the attached drawings are represented by the same reference numerals whenever possible. Additionally, detailed descriptions of known functions and configurations that could obscure the essence of the present invention will be omitted.
[0024] In describing the embodiments in this specification, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to the present invention are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0025] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference number.
[0026] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. The embodiments provided are merely to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims.
[0027] Terms used in this disclosure to refer to network entities or network functions, objects of a wireless communication system, messages, identification information, etc., are examples provided for convenience of explanation. Accordingly, this disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0028] For convenience, the present disclosure uses terms and names that may be applied to next-generation communication systems or defined in 5G system specifications, but is not limited by said terms and names. The present disclosure may be similarly applied to wireless communication systems following other specifications or next-generation specifications through some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0029] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B (gNB), eNode B (eNB), Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station.
[0030] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0031] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.
[0032] In this embodiment, the term "part" refers to a software or hardware component, such as an FPGA or ASIC, and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to operate one or more processors. Accordingly, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." Furthermore, the components and "parts" may be implemented to operate one or more CPUs within a device or secure multimedia card. In addition, in the embodiment, '~part' may include one or more processors.
[0033] In the present disclosure, each of the phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B, or C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order).
[0034] In this disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and the components included in the network structure of 33 may each refer to a physical entity, or to software that performs an individual function, or to hardware combined with software. Since the relevant description can be found in the standard specifications, a detailed description is omitted.
[0035] Terms used in the following description to identify connection nodes, terms referring to network entities (NE) or network functions (NF), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are provided as examples for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0036] For convenience of explanation below, some terms and names defined in the 3GPP (3rd generation partnership project long term evolution) standard may be used. However, the present disclosure is not limited by the above terms and names and may be equally applied to systems conforming to other standards.
[0037] FIG. 1 illustrates an example of a system structure of a 5G mobile communication network according to one embodiment of the present disclosure.
[0038] A 5G mobile communication network consists of a 5G UE (user equipment, terminal) (100), a 5G RAN (radio access network, base station, gNB (5G nodeB), eNB (evolved nodeB, etc.) (120), and a 5G core network.
[0039] The 5G core network is composed of network functions such as an application function (AF) (130) that provides application service-related control functions, such as QoS policy control and traffic impact information, an access and mobility management function (AMF) (150) that provides mobility management functions for UEs, an external data network (DN) (140) through which terminals access actual services such as the Internet, IMS (IP (internet protocol) multimedia subsystem), and enterprise network, a session management function (SMF) (160) that provides session management functions, a user plane function (UPF) (170) that performs data delivery roles, a policy control function (PCF) (180) that provides policy control functions, a unified data management function (UDM) (153) that provides data management functions such as subscriber data and policy control data, a unified data repository (UDR) that stores data of various network functions such as UDM, and a network slice selection function (NSSF) (190) that provides network slice selection functions.
[0040] In 3GPP systems, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following is an example of a reference point included in the 5G system architecture depicted in Figure 1.
[0041] - N1: Reference point between UE and AMF
[0042] - N2: Reference point between (R)AN and AMF
[0043] - N3: Reference point between (R)AN and UPF
[0044] - N4: Reference point between SMF and UPF
[0045] - N5: Reference point between PCF and AF
[0046] - N6: Reference point between UPF and DN
[0047] - N7: Reference point between SMF and PCF
[0048] - N8: Reference point between UDM and AMF
[0049] - N9: Reference point between 2 core UPFs
[0050] - N10: Reference point between UDM and SMF
[0051] - N11: Reference point between AMF and SMF
[0052] - N12: Reference point between AMF and AUSF
[0053] - N13: Reference point between UDM and the authentication server function (AUSF)
[0054] - N14: Reference point between 2 AMFs
[0055] - N15: Reference point between PCF and AMF in non-roaming scenarios, reference point between PCF and AMF within the visited network in roaming scenarios
[0056] In 5G systems, network slicing technology refers to a technology and structure that enables multiple virtualized, independent logical networks within a single physical network. Network operators provide services by configuring virtual end-to-end networks called network slices to satisfy the specialized requirements of services / applications. At this time, network slices are distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). During a terminal registration procedure (e.g., UE registration procedure), the network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to the terminal, and the terminal transmits and receives application data through a PDU (protocol data unit) session generated via one of these S-NSSAIs (i.e., network slice).
[0057] FIGS. 2a, 2b, and 2c illustrate an example of a system structure for non-3GPP access in a 5G mobile communication network according to one embodiment of the present disclosure.
[0058] Non-3GPP access access technology or heterogeneous network support technology refers to technology that enables UEs connected to a non-3GPP access network (e.g., WiFi, wired network, etc.) to connect to a carrier network.
[0059] Figure 2a shows a structure for non-3GPP access in a 5G mobile communication network.
[0060] Referring to FIG. 2a, heterogeneous network access technology in a 5G system can be performed through a non-3GPP interworking function (N3IWF). The N3IWF can provide access to the 5G core to UEs connected to a non-3GPP access network. Through the N3IWF, the UE registers with the AMF as a non-3GPP access user and can use the services provided by the 5G network. At this time, the N3IWF can transmit and receive control plane data from the UE through a pre-configured N2 connection with the AMF.
[0061] Technologies that use non-3GPP access through 5G N3IWF may increase implementation costs because they require establishing a connection between N3IWF and AMF.
[0062] The present disclosure proposes a new method for providing access to a 5G core to UEs connected to a non-3GPP access network in a 5G mobile communication system.
[0063] Figures 2b and 2c show a structure for non-3GPP access using N3MF (non-3GPP management function).
[0064] Referring to Fig. 2b, a UE connected via non-3GPP access may not perform registration / authentication through an AMF (i.e., N1 message), but may perform registration / authentication for the UE through a network function (NF) other than an AMF (e.g., non-3GPP management function (N3MF)) and a message other than an N1 message (e.g., IKEv2 message). In this case, the N3MF may send a request message for authentication to the AUSF via a service-based interface (SBI) message.
[0065] Additionally, referring to FIG. 2b, to support data transmission between a UE connected via non-3GPP access and a data network, an N3MF (e.g., an ePDG (evolved packet data gateway) or a 5G ePDG) may send a request for session creation to an SMF or an SMF+PGW-C. At this time, the N3MF may send a request message for authentication to an AUSF via an SBI message.
[0066] In one embodiment, N3MF may support at least one of the following functions, but is not limited thereto.
[0067] - Support for UE authentication procedure: In the present disclosure, registration / authentication for a UE connected via non-3GPP access is not performed via an AMF (i.e., N1 message), but rather can be performed via a non-N1 message (e.g., IKEv2 message) by a network function (NF) other than an AMF (e.g., non-3GPP management function (N3MF)). In this case, the N3MF can transmit a request message for authentication to the AUSF via an SBI message (Figs. 2b and 2c).
[0068] - Support for UE session procedures: In the present disclosure, to support data transmission between a UE connected via non-3GPP access and a data network, an N3MF may transmit a request for session creation to an SMF or an SMF+PGW-C. In this case, the N3MF may support one or both of the two support structures shown in FIG. 2b and FIG. 2c. As shown in FIG. 2b, the N3MF may support session management functions through an SBI interface with an SMF or an SMF+PGW-C. Additionally, as shown in FIG. 2b, the N3MF may support the transmission and reception of user plane data (e.g., PDU) through an N3 interface with a UPF or an UPF+PGW-U. Alternatively, as shown in FIG. 2c, the N3MF may support session management functions through S2b (i.e., S2b-C) with an SMF or an SMF+PGW-C. In addition, as shown in FIG. 2c, N3MF can support the transmission and reception of user plane data (e.g., PDU) through the S2b (i.e., S2b-U) interface with UPF or UPF+PGW-U.
[0069] - Manage connection with UE
[0070] - Transmit / manage UE configuration information
[0071] - Function to route control plane messages (e.g., NAS messages) between the UE and other NFs (e.g., routing messages for session management between UE and SMF, UE policy messages between UE and PCF, SoR messages between UE and UDM, etc.)
[0072] - User plane message transmission function between UE and Data network (DN)
[0073] The interfaces (IF) of N3MF are as follows, but are not limited thereto.
[0074] - Connection / interface for UE and control plane messages
[0075] - Connection / interface for UE and user plane messages
[0076] - Connect / interface through one or more UPF and N3 interfaces
[0077] - Connects to / interfaces with one or more access networks
[0078] - Connection / interface with other NFs via SBI
[0079] N3MF can be referred to as a network function entity with various names. For example, it can be one of ePDG, 5G ePDG, enhanced ePDG, or non-3GPP access function.
[0080] In this case, the connection method and protocol between the UE and the new NF can be reused from the connection method / protocol between the UE and the ePDG (evolved packet data gateway). The ePDG is a technology that provides access to the 4G core (i.e., EPC, evolved packet core) for UEs connected to untrusted non-3GPP access networks such as Wi-Fi or the public internet.
[0081] FIG. 3 illustrates an example of a procedure for registering a non-3GPP management function (N3MF) to a network repository function (NRF) according to one embodiment of the present disclosure.
[0082] In step 301, the N3MF (or 5G ePDG, enhanced ePDG, ePDG) may transmit a message (e.g., NF Registration request) to register with the NRF. The message may include at least one of the following information.
[0083] - NF type: Information indicating N3MF
[0084] - Supported S-NSSAIs: Information on S-NSSAI(s) supported by N3MF
[0085] - Capability: Capability information supported by N3MF. The above capability information may include whether slicing function is supported, whether ATSSS is supported, whether N26 interface (i.e., interface for interworking with MME) is supported, whether voice service over 5G is supported, etc.
[0086] - NF address: N3MF address (FQDN, IP Address / port)
[0087] In step 302, the NRF may transmit a response message (e.g., NF Registration response) to the message transmitted in step 1. In one embodiment, the response message may include information regarding the result (acceptance, rejection, etc.) of the registration request.
[0088] FIG. 4 illustrates an example of a discovery and selection procedure for N3MF according to one embodiment of the present disclosure.
[0089] At step 401, the UE may send a registration request message (NAS message) to the AMF via the NG-RAN. The message may include whether N3MF (or 5G ePDG, enhanced ePDG, ePDG) is supported. If the terminal supports non-3GPP access access via N3MF, it may include the corresponding indicator.
[0090] In step 402, the AMF may send a UE policy association request message to the PCF. If the message received in step 401 contains an N3MF support indicator, the AMF may include an N3MF support indicator in the message sent to the PCF.
[0091] In step 403, the PCF may send a message (e.g., N1 message transfer request) to the AMF requesting that a UE policy container containing an access network discovery and selection policy (ANDSP) be sent to the UE.
[0092] That is, the PCF can generate an ANDSP for the UE. Based on the message received in step 402, if the UE supports N3MF, the PCF may include at least one of the following information for each N3MF in the ANDSP for the UE.
[0093] - One or more tuples of FQDN(fully qualified domain name) / IP address of N3MF (or 5G ePDG, enhanced ePDG): Address (IP address or FQDN) of N3MF (eg, 5G ePDG, enhanced ePDG, ePDG)
[0094] - 5GC support status: Information indicating one or more of the following may be included: whether N3MF supports terminal authentication via 5G core (e.g., AUSF / UDM), whether it supports session management via 5G core (e.g., SMF), and whether N3MF supports SBI.
[0095] - Supported S-NSSAI(s): S-NSSAI(s) supported by N3MF
[0096] - PLMN ID: PLMN ID supported by N3MF
[0097] In step 404, the AMF may send a UE configuration update message to the UE. In one embodiment, if the AMF receives a request message from the PCF in step 403 and the message contains a UE policy, the AMF may include such information in a message sent to the UE. If the message received from the AMF contains N3MF information, the UE may store such information. Such information may include one or more of the following information.
[0098] In step 405, the UE can select N3MF to access a non-3GPP access network.
[0099] In one embodiment, if the UE wants to select a 5GC-based N3MF (or ePDG, 5G ePDG), it can select an N3MF that supports 5GC based on the configuration information received in step 404.
[0100] In one embodiment, if S-NSSAI(s) (i.e., requested S-NSSAI(s)) exist and if configuration information for selecting N3MF exists, the UE can select an N3MF that supports the S-NSSAI(s) to be used.
[0101] In step 406, the UE may send an Initial attach request message or a request message to establish a PDU session / PDN Connection to the selected N3MF. In one embodiment, the UE may send an Initial attach request to the N3MF by including it in an IKEv2 message.
[0102] In step 407, N3MF can perform the authentication procedure for the UE and the procedure to establish a PDN Connection / PDU Session.
[0103] The UE can perform an authentication procedure with the selected N3MF. In this case, the IKEv2 protocol may be used. When communicating with the N3MF, the UE may use a local IP address configured from a non-3GPP access network.
[0104] FIG. 5 illustrates an example of a connection procedure through an N3MF (e.g., an ePDG (evolved packet data gateway)) of a UE (user equipment) according to one embodiment of the present disclosure.
[0105] FIG. 5 illustrates a procedure that specifically illustrates the operations of steps 405, 406, and 407 illustrated in FIG. 4.
[0106] FIG. 5 illustrates the operation of an ePDG as an example for N3MF, but 5G ePDGs, enhanced ePDGs, and non-3GPP access functions capable of performing the functions of N3MF can also perform the operation illustrated in FIG. 5 below.
[0107] In step 501, the UE can select N3MF. In one embodiment, the UE can perform local IP address configuration through a non-3GPP access network and perform N3MF selection (e.g., 5G ePDG, or ePDG). The UE can use configuration information received from the core network (e.g., access network selection policy information). In one embodiment, the configuration information may include UE police information received in step 404 of FIG. 4. In one embodiment, the information may include one or more of the following information.
[0108] - N3MF address: Address of the N3MF (e.g., 5G ePDG or ePDG) (IP address or FQDN)
[0109] - 5GC support: Whether 5GC-based N3MF (or ePDG) is supported. In one embodiment, 5G-based N3MF supports terminal authentication through a 5G core (e.g., AUSF / UDM).
[0110] - Supported S-NSSAI(s): S-NSSAI(s) supported by N3MF
[0111] - PLMN ID: PLMN ID supported by N3MF
[0112] In one embodiment, if the UE wants to select a 5GC-based N3MF (or ePDG, 5G ePDG), it can select an N3MF that supports 5GC based on configuration information.
[0113] If S-NSSAI(s) (i.e., requested S-NSSAI(s)) exist and the above configuration information for N3MF selection exists, the UE can select an N3MF that supports the S-NSSAI(s) to be used.
[0114] Afterward, the UE can perform an initial authentication procedure with the selected N3MF. At this time, the IKEv2 protocol may be used. When communicating with the N3MF, the UE may use a local IP address configured from a non-3GPP access network.
[0115] In step 502, the UE may send an attach request to N3MF. The message may include at least one of the following information. The attach request message may be sent in an IKEv2 message.
[0116] - UE ID: The UE may include a temporary identifier for non-3GPP access (e.g., temp ID) if one exists. If not, it may include a SUPI.
[0117] - PDU Session ID: PDU session identifier
[0118] - 5G connection indicator (i.e., an indicator representing a connection to 5G)
[0119] - APN (or DNN): A DNN to which the UE wishes to request a connection. May include DNN(s) that are matched by a URSP rule for information regarding the application traffic that the UE wishes to transmit.
[0120] - S-NSSAI(s): S-NSSAI(s) requested by the UE. May include S-NSSAI(s) that are matched by URSP rules for information on application traffic that the UE intends to transmit.
[0121] In step 503, N3MF may send an authentication request message to AUSF. In one embodiment, if N3MF requires authentication for a UE (e.g., if no security context exists for the UE), it may include a UE ID (e.g., SUCI) in the authentication request message sent to AUSF.
[0122] If authentication is not required for the UE, steps 503 through 510 may be omitted.
[0123] In step 504, when AUSF receives an authentication request message from N3MF, it can send an authentication request message containing SUCI to UDM.
[0124] At step 504, the UDM may receive an authentication message from the AUSF. If the received message contains SUCI, the UDM may convert SUCI to SUPI and determine an authentication method based on SUPI and subscriber information. For example, if the UE is connected via non-3GPP access, the UDM may select 'EAP-AKA'.
[0125] In one embodiment, the UDM can calculate an authentication vector (AV) according to the authentication method.
[0126] In one embodiment, the UDM may include SUPI and AV in the response message sent to the AUSF.
[0127] In one embodiment, for EAP-AKA', AV may include RAND, AUTN (authentication token), XRES (expected response), CK (cipher key)', and IK (integrity key)'.
[0128] In one embodiment, for 5G AKA, AV may include RAND, AUTN, XRES*, and K_AUSF (key for authentication server function).
[0129] At step 505, the UDM may send an authentication response message to the AUSF. The authentication response message may include one or more of SUPI and AV.
[0130] In one embodiment, AUSF can derive K_AUSF based on the message received in step 505.
[0131] In step 506, AUSF may send a challenge request message containing AV in an authentication response message sent to N3MF.
[0132] At step 507, N3MF can send a challenge request included in a message received from AUSF to the UE. The message can be sent included in an IKEv2 message.
[0133] In step 508, the UE can send a challenge response message to N3MF.
[0134] In one embodiment, if the message received from N3MF in step 507 contains a challenge request message, RAND, and AUTN, the UE can calculate RES (response) and MAC (message authentication code)2, and the UE can send a challenge response message containing RES and MAC2 to N3MF. The message may be sent by being included in an IKEv2 message.
[0135] In step 509, when N3MF receives a message from the UE containing a challenge response message, it may send an SBI message containing the challenge response message (e.g., a Nausf_UEAuthentication_Authenticat request message) to AUSF.
[0136] In one embodiment, when AUSF receives the message of step 509 from N3MF, it can perform authentication. AUSF can verify whether the stored XRES* is the same as the RES* included in the message received from N3MF, and if it is the same, it can determine that authentication is successful.
[0137] In step 510, AUSF may send a response message to N3MF regarding the authentication request. The message may include an authentication success indicator (or failure indicator), SUPI, and KAUSF. In one embodiment, the response message may include a different UE identifier instead of SUPI.
[0138] In one embodiment, N3MF may determine that the authentication of the UE is successful if the message received from AUSF includes an indicator indicating successful authentication. In one embodiment, N3MF may store the UE ID received from AUSF in the UE context.
[0139] In step 511, N3MF may perform a procedure to register with the UDM that it is serving N3MF to the UE. N3MF may include the following information in the message sent to the UDM (e.g., Nudm_UECM_registration request):
[0140] - NF type = N3MF (or ePDG, enhanced ePDG, 5G ePDG), N3MF ID / address, access type = non-3GPP
[0141] When a UDM receives a message requesting registration from an N3MF, and there is no NF already registered with non-3GPP for the UE, the UDM may register the N3MF as a serving NF for the UE's non-3GPP access. The UDM may send a response message to the N3MF regarding the registration request.
[0142] In step 512, if the UE authentication is valid (e.g., if a security context for the UE exists in the UE context), the N3MF may send a Subscription information request message to the UDM to obtain subscriber information. In one embodiment, the message may include a UE ID.
[0143] In step 513, when the UDM receives a subscriber information request message containing SUPI from N3MF, it may include the subscriber information in a subscription information response message sent to N3MF.
[0144] In one embodiment, the subscriber information may include an N3MF allowed indicator, subscribed S-NSSAI(s), subscribed DNN(s), SMF selection information, etc.
[0145] In step 514, if the S-NSSAI included in the message received in step 502 is not included in the subscribed S-NSSAI, or if the S-NSSAI included in the message received in step 502 is not included in the S-NSSAI supported by N3MF, N3MF may send a message to the UE containing a result indicating rejection and a cause (e.g., S-NSSAI not allowed or S-NSSAI not supported). Such message may be sent in an IKEv2 message.
[0146] In step 515, N3MF may select an SMF (or SMF+PGW-C) if the S-NSSAI and / or DNN included in the message received in step 501 is allowed. In one embodiment, N3MF may perform S-NSSAI discovery / selection based on SMF selection information if the S-NSSAI and / or DNN included in the message received in step 501 is allowed, obtain SMF (or SMF+PGW-C) address(s) that support S-NSSAI / DNN from NRF, and select an SMF (or SMF+PGW-C).
[0147] In step 516, N3MF may send a message (Create session request) to the selected SMF (or SMF+PGW-C) to establish a session. In one embodiment, the message may be an Nsmf_CreateSMContext request message or an S2b-C message.
[0148] In one embodiment, when the Nsmf_CreateSMContext request message is used, the message may include one or more of the following information.
[0149] - UE ID (SUPI)
[0150] - PDU session ID, DNN, S-NSSAI, RAT type, PDU Session Type
[0151] - N1 SM message included in the message received from the UE
[0152] - User Location Information
[0153] In one embodiment, when an S2b-C message is used, the message may include one or more of the following information.
[0154] - UE ID (IMSI or SUPI)
[0155] - EPS Bearer Identity (identifier assigned by ePDG or PDN Connection / PDU Session ID received from UE), APN (DNN), RAT type, PDN Type, PDN Address
[0156] - ePDG TEID for control plane, ePDG Address for the user plane, ePDG TEID of the user plane
[0157] - N1 SM message included in the message received from the UE
[0158] - APN-AMBR
[0159] - User Location Information
[0160] The remaining session establishment procedure can be performed in Step 517.
[0161] FIG. 6 is a diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.
[0162] A network entity according to one embodiment of the present disclosure may include a control unit (601) that controls the overall operation of the network entity, a transmission and reception unit (602) including a transmission unit and a reception unit, and a memory (603). Of course, it is not limited to the above example, and the network entity may include more configurations than the configuration shown in FIG. 6, or fewer configurations.
[0163] According to one embodiment of the present disclosure, the transmitting and receiving unit (602) may transmit and receive a signal with at least one of other network entities or terminals. The signal transmitted and received with at least one of other network entities or terminals may include control information and data.
[0164] According to one embodiment of the present disclosure, the control unit (601) can control a network entity to perform any one of the above-described embodiments. Meanwhile, the control unit (601), memory (603), and transceiver (602) do not necessarily have to be implemented as separate modules, and can be implemented as a single component in the form of a single chip. Also, the control unit (601) and the transceiver (602) can be electrically connected. Furthermore, the control unit (601) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.
[0165] According to one embodiment of the present disclosure, the memory (603) may store data such as a basic program, an application program, and configuration information for the operation of a network entity. In particular, the memory (603) provides the stored data upon a request from the control unit (601). The memory (603) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, a CD-ROM, and a DVD. Additionally, the memory (603) may be a plurality of. Furthermore, the control unit (601) may execute the aforementioned embodiments based on a program for executing the aforementioned embodiments of the present disclosure stored in the memory (603). The control unit (601) may include at least one processor.
[0166] According to one embodiment of the present disclosure, a terminal can receive user equipement (UE) policy information including an access network discovery and selection policy (ANDSP) from a policy control runction (PCF) through an access and mobility management function (AMF).
[0167] In one embodiment, the terminal can select a first network entity that performs non-3GPP (generation partnership project) management functions based on the access network discovery and selection policy.
[0168] In one embodiment, the terminal can transmit a connection request message to the first network entity.
[0169] In one embodiment, a response message to the connection request message can be received from the first network entity.
[0170] In one embodiment, the first network entity performing the non-3GPP (generation partnership project) management function may include at least one of an ePDG (evolved packet data gateway), a 5G (5th generation) ePDG, an enhanced ePDG, and a non-3GPP access function.
[0171] In one embodiment, the ANDSP may include at least one of address information, information indicating whether 5GC (5th generation core) is supported, supported S-NSSAI (single network slice selection assistance information), and supported PLMN ID for at least one network entity that performs non-3GPP (generation partnership project) management functions.
[0172] In one embodiment, the information indicating whether the 5GC is supported may include at least one of whether at least one network entity performing non-3GPP (generation partnership project) management functions supports terminal authentication through the 5GC, whether it supports session management through the 5GC, and whether it supports a service-based interface (SBI).
[0173] In one embodiment, the connection request message may be included in an IKEv2 message and transmitted.
[0174] A first network entity performing a non-3GPP management function according to one embodiment of the present disclosure can receive a connection request message from a terminal.
[0175] In one embodiment, the first network entity may transmit a response message to the connection request message to the terminal.
[0176] In one embodiment, the connection request message may be based on UE policy information including a connection network discovery and selection policy.
[0177] In one embodiment, the first network entity further includes the step of transmitting an NF registration request message to an NRF; and the NF registration request message may include at least one of type information of the first network entity, S-NSSAI information supported by the first network entity, capability information supported by the first network entity, and address information of the first network entity.
[0178] It should be noted that the aforementioned configuration diagrams, exemplary diagrams of control / data signal transmission methods, exemplary diagrams of operation procedures, and configuration diagrams are not intended to limit the scope of the rights of the present disclosure. That is, all components, entities, or steps of operation described in the embodiments of the present disclosure should not be interpreted as essential components for the implementation of the disclosure, and may be implemented within a scope that does not impair the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined with one another as needed. For example, parts of the methods proposed in the present disclosure may be combined with one another to operate network entities and terminals.
[0179] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading the program code stored in the memory device using a processor or CPU (Central Processing Unit) and executing it.
[0180] Various components of entities, base stations, or terminal devices and modules described herein may be operated using hardware circuits, such as, for example, complementary metal oxide semiconductor-based logic circuits, firmware, software, and / or a combination of hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.
[0181] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.
[0182] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0183] Additionally, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
[0184] In the specific embodiments of the present disclosure described above, the components included in the disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.
[0185] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.
Claims
1. A method performed by UE (user equipment) in a wireless communication system, A step of receiving UE policy information containing first information about at least one network entity configured for a non-3GPP (non-3rd Generation Partnership Project) management function from a PCF (policy control function) via an AMF (access and mobility management function); A step of selecting a first network entity configured for non-3GPP management functions based on the first information above; A step of transmitting a connection request message to the first network entity; and A method characterized by including the step of receiving a response message for the connection request message from the first network entity.
2. In paragraph 1, the first network entity is, A method characterized by including one of an ePDG (evolved packet data gateway), a 5G (5th generation) ePDG, an enhanced ePDG, or a non-3GPP access function.
3. In paragraph 1, the above first information is, Address information for at least one network entity, Information indicating whether the above-mentioned at least one network entity supports 5GC (5th generation core), S-NSSAI (single network slice selection assistance information) supported by at least one network entity, or A method characterized by including at least one of the PLMN IDs (public land mobile network identifiers) supported by at least one network entity.
4. In Paragraph 3, the information indicating whether the above 5GC is supported is, Whether the above at least one network entity supports UE authentication through the 5GC, Whether the above at least one network entity supports session management through the 5GC, or A method characterized by including at least one of whether the above-mentioned at least one network entity supports a service-based interface (SBI).
5. In paragraph 1, the connection request message is transmitted by being included in an IKEv2 message, and A method characterized in that the above-mentioned first information is included in an access network discovery and selection policy (ANDSP).
6. In claim 1, further comprising the step of transmitting information indicating whether the UE supports non-3GPP management functions to the PCF through the AMF, A method characterized by the above UE policy information being based on information indicating whether the above non-3GPP management function is supported.
7. A method performed by a first network entity configured for non-3GPP (non-3rd Generation Partnership Project) management functions in a wireless communication system, A step of receiving a connection request message from UE (user equipment); and The method includes the step of transmitting a response message to the connection request message to the above UE. A method characterized in that the above connection request message is based on UE policy information including first information for at least one network entity configured for non-3GPP management functions.
8. In paragraph 7, the first network entity is, A method characterized by including one of an ePDG (evolved packet data gateway), a 5G (5th generation) ePDG, an enhanced ePDG, or a non-3GPP access function.
9. In Paragraph 7, A step of registering the first network entity in unified data management (UDM) as a network entity configured for non-3GPP management functions serving the UE; and A method characterized by further including the step of receiving subscriber information of the UE from the above UDM.
10. In claim 7, the step of selecting an SMF (session management function) based on the connection request message; A step of transmitting a session creation request to the above SMF; and A method characterized by further including the step of performing a session setup procedure for the above-mentioned UE.
11. In paragraph 7, the above-mentioned first information is, Address information for at least one network entity, Information indicating whether the above-mentioned at least one network entity supports 5GC (5th generation core), S-NSSAI (single network slice selection assistance information) supported by at least one network entity, or A method characterized by including at least one of the PLMN IDs (public land mobile network identifiers) supported by at least one network entity.
12. A method according to claim 7, characterized in that the connection request message is transmitted by being included in an IKEv2 message.
13. In Paragraph 7, It further includes the step of sending a request message to register an NF (network function) to an NRF (network repository function), and A method characterized in that the above NF registration request message includes at least one of type information of the first network entity, S-NSSAI information supported by the first network entity, capability information supported by the first network entity, or address information of the first network entity.
14. In a wireless communication system, regarding the UE (user equipment), Transmitter / receiver; and It includes at least one processor, and the at least one processor, UE policy information including first information about at least one network entity configured for a non-3GPP (non-3rd Generation Partnership Project) management function is received through an AMF (access and mobility management function) from a PCF (policy control function), and Select a first network entity configured for non-3GPP management functions based on the above first information, and Sending a connection request message to the above-mentioned first network entity, and A UE configured to receive a response message to the connection request message from the first network entity.
15. In a first network entity configured for non-3GPP (non-3rd Generation Partnership Project) management functions in a wireless communication system, Transmitter / receiver; and It includes at least one processor, and the at least one processor, Receives a connection request message from UE (user equipment), and The above UE is configured to send a response message to the above connection request message, and A first network entity characterized by the above connection request message being based on UE policy information containing first information for at least one network entity configured for non-3GPP management functions.