Method and apparatus for NEF-based AF authentication and authorization in mobile communication system
The NEF-based AF authentication and authorization method within the 5G mobile communication system addresses the need for secure and efficient service subscription by using the UPF Control Message Protocol for in-band communication, ensuring scalable and secure management of connected devices across diverse frequency bands and network configurations.
Patent Information
- Application Number
- PCT/KR2024/006669
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-16
- Publication Date
- 2024-11-28
AI Technical Summary
In the context of 5G and beyond mobile communication systems, there is a need for efficient authentication and authorization mechanisms within the Network Exposure Function (NEF) to manage the increasing complexity and scalability of connected devices, particularly for user plane functions (UPF) and application functions (AF), ensuring secure service subscription and operation across diverse frequency bands and network configurations.
A method and device for NEF-based AF authentication and authorization in a mobile communication system, where a UPF entity receives a subscription request from an AF entity, transmits authentication/authorization requests to a Network Exposure Function (NEF) entity, and processes responses to facilitate secure service subscription, utilizing the UPF Control Message Protocol (UCMP) for in-band communication, ensuring authentication and authorization procedures are performed effectively.
This solution enhances the security and efficiency of service subscription processes in 5G and beyond mobile communication systems, enabling scalable and secure management of connected devices across various frequency bands and network configurations, supporting advanced services like V2X, XR, and AI-driven communication.
Smart Images

Figure KR2024006669_28112024_PF_FP_ABST
Abstract
Description
NEF-based AF authentication and authorization method and device in a mobile communication system
[0001] The present disclosure relates to a method and device for NEF-based AF authentication and authorization in a mobile communication system, and relates to a method and device for performing authentication and authorization for an AF (application function) when subscribing to a UPF (user plane function) service based on a user plane (UP).
[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 (THz) band (for example, 3 THz 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] A method of a user plane function (UPF) entity according to one embodiment of the present disclosure may include the steps of receiving a subscribe request message related to a UPF event exposure service from an application function (AF) entity, transmitting an authentication and / or authorization request message for the AF entity to a network exposure function (NEF) entity, receiving an authentication and / or authorization response message for the authentication and / or authorization request message from the NEF entity, and transmitting a subscribe response message for the subscribe request message to the AF based on the authentication and / or authorization response message.
[0009] The disclosed embodiment provides a device and method capable of effectively providing a service in a wireless communication system.
[0010] FIG. 1 illustrates the structure of a 5G network according to one embodiment of the present disclosure.
[0011] FIG. 2 shows a TCP / IP protocol stack and a datagram header (Packet Header) of an IP Layer (IPv4-based) according to one embodiment of the present disclosure.
[0012] FIG. 3 illustrates an IP layer including a UCMP protocol according to one embodiment of the present disclosure.
[0013] FIG. 4 illustrates an IP datagram including a UCMP protocol message and a UCMP protocol message format according to one embodiment of the present disclosure.
[0014] FIG. 5 illustrates an example of the operation of the UCMP protocol according to one embodiment of the present disclosure.
[0015] FIG. 6 illustrates two methods for performing AF authentication and authorization through NEF according to one embodiment of the present disclosure.
[0016] FIG. 7 is a diagram illustrating a signaling procedure according to one embodiment of the present disclosure.
[0017] FIG. 8 is a diagram illustrating a signaling procedure according to another embodiment of the present disclosure.
[0018] FIG. 9 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.
[0019] FIG. 10 is a diagram showing the configuration of a network entity according to an embodiment of the present disclosure.
[0020] A method of a user plane function (UPF) entity according to one embodiment of the present disclosure may include the steps of receiving a subscribe request message related to a UPF event exposure service from an application function (AF) entity, transmitting an authentication and / or authorization request message for the AF entity to a network exposure function (NEF) entity, receiving an authentication and / or authorization response message for the authentication and / or authorization request message from the NEF entity, and transmitting a subscribe response message for the subscribe request message to the AF based on the authentication and / or authorization response message.
[0021] In one embodiment of the present disclosure, the authentication and / or authorization response message may include at least one of an authentication and / or authorization result and a credential for the AF entity.
[0022] In one embodiment of the present disclosure, the credential may include at least one of event identification information and a timer.
[0023] In one embodiment of the present disclosure, the subscription request message may include an IP header including a value indicating that the IP packet includes a UPF Control Message Protocol (UCMP) message, a UPF service name field indicating the UPF event exposure service, a service operation field indicating service subscription, and an operation semantics field indicating a service request, and UCMP data including at least one value required for a subscription request for the UPF event exposure service.
[0024] A method of a Network Exposure Function (NEF) entity according to one embodiment of the present disclosure may include the steps of receiving an authentication and / or authorization request message for an application function (AF) entity from a user plane function (UPF) entity, performing an authentication and / or authorization procedure for the AF entity, and transmitting an authentication and / or authorization response message for the authentication and / or authorization request message to the UPF entity.
[0025] In one embodiment of the present disclosure, the authentication and / or authorization response message may include at least one of an authentication and / or authorization result and a credential for the AF entity.
[0026] In one embodiment of the present disclosure, the credential may include at least one of event identification information and a timer.
[0027] According to one embodiment of the present disclosure, a user plane function (UPF) entity includes a transceiver and a controller coupled to the transceiver, wherein the controller receives a subscription request message related to a UPF event exposure service from an application function (AF) entity, transmits an authentication and / or authorization request message for the AF entity to a Network Exposure Function (NEF) entity, receives an authentication and / or authorization response message for the authentication and / or authorization request message from the NEF entity, and transmits a subscription response message for the subscription request message to the AF based on the authentication and / or authorization response message.
[0028] In one embodiment of the present disclosure, the authentication and / or authorization response message may include at least one of an authentication and / or authorization result and a credential for the AF entity. UPF entity.
[0029] In one embodiment of the present disclosure, the credential may include at least one of event identification information and a timer.
[0030] In one embodiment of the present disclosure, the subscription request message may include an IP header including a value indicating that the IP packet includes a UPF Control Message Protocol (UCMP) message, a UPF service name field indicating the UPF event exposure service, a service operation field indicating service subscription, and an operation semantics field indicating a service request, and UCMP data including at least one value required for a subscription request for the UPF event exposure service.
[0031] A Network Exposure Function (NEF) entity according to one embodiment of the present disclosure includes a transceiver and a controller coupled to the transceiver, wherein the controller receives an authentication and / or authorization request message for an application function (AF) entity from a user plane function (UPF) entity, performs an authentication and / or authorization procedure for the AF entity, and controls transmission of an authentication and / or authorization response message for the authentication and / or authorization request message to the UPF entity.
[0032] In one embodiment of the present disclosure, the authentication and / or authorization response message may include at least one of an authentication and / or authorization result and a credential for the AF entity.
[0033] In one embodiment of the present disclosure, the credential may include at least one of event identification information and a timer.
[0034] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.
[0035] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.
[0036] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0037] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only 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. Like reference numerals refer to like elements throughout the specification.
[0038] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0039] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0040] Here, the term '~ unit' used in the present embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.
[0041] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.
[0042] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0043] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.
[0044] FIG. 1 illustrates the structure of a 5G network according to one embodiment of the present disclosure.
[0045] Referring to Figure 1, the network entities or network nodes that constitute the 5G network are described as follows.
[0046] (R)AN ((Radio) Access Network) is an entity that performs wireless resource allocation of a terminal, and may be at least one of an eNode B, Node B, BS (Base Station), NG-RAN (NextGeneration Radio Access Network), 5G-AN, a wireless access unit, a base station controller, or a node on a network.
[0047] A terminal may include a UE (User Equipment), an NG UE (NextGeneration UE), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, while the embodiments of the present disclosure will be described below using a 5G system as an example, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.
[0048] As wireless communication systems evolve from 4G to 5G, a new core network, NextGen Core (NG Core) or 5GC (5G Core Network), is defined. This new core network virtualizes all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function (NF) may refer to a network entity, a network component, or a network resource.
[0049] According to one embodiment of the present disclosure, 5GC may include NFs as illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the number of NFs illustrated in FIG. 1.
[0050] The Access and Mobility Management Function (AMF) may be a network function that manages the access and mobility of a terminal (UE). For example, AMF may perform network functions such as registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.
[0051] The Session Management Function (SMF) may be a network function that manages the Packet Data Network (PDN) connection provided to the user equipment (UE). The PDN connection may be referred to as a Packet Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through the establishment, modification, and release of sessions and the maintenance of tunnels between the UPF (131) and the RAN required for this, the allocation and management of the IP (Internet protocol) address of the UE, the selection and control of the user plane, the control of traffic processing in the UPF, and the control of the collection of charging data.
[0052] PCF (Policy Control Function) may be a network function that applies the mobile carrier's service policy, charging policy, and PDU Session policy to the terminal.
[0053] Unified Data Management (UDM) can be a network function that stores subscriber information. For example, UDM can perform functions such as generating authentication information for 3GPP security, processing user identifiers (user IDs), managing a list of network functions supporting UEs, and managing subscription information.
[0054] The Network Exposure Function (NEF) may provide information about a terminal to a server outside the 5G network. Additionally, NEF may provide the ability to store information necessary for 5G network services in the UDR.
[0055] The User Plane Function (UPF) may be a gateway function that transmits user data (PDU) to the Data Network (DN). More specifically, the UPF may perform a data processing function so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF (131) may perform network functions such as serving as an anchor between radio access technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report creation, and buffering.
[0056] NRF (Network Repository Function) can perform the function of discovering NF.
[0057] AUSF (Authentication Server Function) can perform terminal authentication in 3GPP access networks and non-3GPP access networks.
[0058] NSSF (Network Slice Selection Function) can perform the function of selecting a Network Slice Instance provided to a terminal.
[0059] DN (Data Network) can be a data network where terminals transmit and receive data to use network operator services or third-party services.
[0060] In one embodiment of the present disclosure, equipment (i.e. AF) located in the DN can use the N6 Interface (User Plane, In-band) to exchange control messages with the UPF.
[0061] According to one embodiment of the present disclosure, when a network device or network function located inside or outside a 5G Core Network makes a request for UP-based UPF service subscription in order to use a service provided by a UPF (User Plane Function), a method is proposed for providing Authentication and Authorization of the corresponding NF.
[0062] FIG. 2 shows a TCP / IP protocol stack and a datagram header (Packet Header) of an IP Layer (IPv4-based) according to one embodiment of the present disclosure.
[0063] According to one embodiment of the present disclosure, the user plane function (UPF) and the application function (AF) are router and server devices, respectively, and can communicate via the N6 interface using the transmission control protocol (TCP) / internet protocol (IP) protocol stack to transmit user data. Since the UPF is a router device, it basically includes the IP Layer (Internet Protocol Layer). Therefore, an in-band protocol for transmitting control messages between the UPF and the AF can exist in the IP Layer.
[0064] An IP datagram header may include a Protocol field. Based on IPv6, the next header field can perform the function of the Protocol field. This disclosure is described based on the IPv4 protocol, but it can be equally applied to the IPv6 protocol. The Protocol field (next header field based on IPv6) is an 8-bit field that defines a higher layer protocol that uses the services of the IP layer. Various types of higher layer protocols such as TCP, UDP (user datagram protocol), ICMP (internet control message protocol), and IGMP (internet group management protocol) can use the IP layer.
[0065] In one embodiment of the present disclosure, the UCMP (UPF Control Message Protocol) protocol is used as an in-band protocol. However, the present invention is not limited thereto, and other in-band protocols may also be used.
[0066] The UCMP protocol can be assigned one of the unused Protocol fields. In this disclosure, number 144 is described as being assigned. However, this is not limited to this, and new protocol names and IP protocol numbers can be used in various ways, not limited to the embodiments of this disclosure.
[0067] FIG. 3 illustrates an IP layer including a UCMP protocol according to one embodiment of the present disclosure.
[0068] The UCMP protocol can be incorporated into the IP layer, like existing IGMP, ICMP, and ARP (Address Resolution Protocol) protocols. Furthermore, the UCMP protocol can also exist above the IP layer. The UCMP protocol illustrated in Figure 3 is based on IPv4, but is not limited thereto and can be applied equally to IPv6.
[0069] FIG. 4 illustrates an IP datagram including a UCMP protocol message and a UCMP protocol message format according to one embodiment of the present disclosure.
[0070] As described above, the Protocol field of the IP header is set to 144, indicating the UCMP protocol. The UCMP header contains the UPF service name, service operation, and operation semantic values. The UCMP data contains parameter values required for the UPF service.
[0071]
[0072] FIG. 5 illustrates an example of the operation of the UCMP protocol according to one embodiment of the present disclosure.
[0073] Referring to FIG. 5, an external server, AF, can request UPF to subscribe to a UPF service in order to use a specific UPF service. To do this, AF can create a UCMP protocol message, include it in an IP datagram, and transmit it to UPF. As described above, the protocol field of the IP header can be entered with the value '144' to indicate that the IP datagram contains a UCMP message. The source IP address field can be entered with the IP address of AF, '179.153.110.3'. The destination address field can be entered with the IP address of the terminal, '192.110.33.5'.
[0074] According to one embodiment of the present disclosure, the following values are entered in the UCMP header. The Service Name field is entered with the value 'Nupf_EventExposure', which is the UPF service name.
[0075] According to one embodiment of the present disclosure, the Service Operations field may be entered with the value 'Subscribe', which represents a service subscription. This indicates the name of the service that the AF will request from the UPF. This indicates the service operation that the AF requests from the UPF.
[0076] According to one embodiment of the present disclosure, the Operation Semantics field is populated with a value of 'Request', which is a service request. This represents a definition of an operation indicating that the AF is requesting a service from the UPF.
[0077] According to one embodiment of the present disclosure, the UCMP Data field includes parameter values required for a corresponding service subscription request. The parameter values may be various values, such as an Event ID, a terminal IP address, a Generic Public Subscription Identifier (GPSI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI). Of course, the present disclosure is not limited to the above examples.
[0078] According to one embodiment of the present disclosure, the IP datagram is transmitted to the PSA (PDU Session Anchor) UPF, which is the home router of the terminal (step 1). The UPF can process the header of the IP datagram. At this time, since the value of the protocol field is '144', it can recognize that the IP datagram contains a UCMP message. That is, the UPF that received the IP datagram can identify that the IP datagram does not contain user data transmitted to the user (terminal) but contains a UCMP message requesting a service from the UPF serving the terminal. The UPF can read the UCMP message and process the requested service subscription. The UPF can discard the IP datagram without transmitting it to the terminal.
[0079] After that, UPF can send the result of processing the requested service subscription to AF (step 2). For this, UPF generates a UCMP message. The UCMP header contains the following values. The Service Name field contains the UPF service name, 'Nupf_EventExposure'. The Service Operations field contains the service subscription value, 'Subscribe'. The Operation Semantics field contains the response to the service request, 'Response'. The UCMP Data field may contain parameter values required for the corresponding service subscription request response.
[0080] The IP datagram and UCMP protocol message illustrated in FIG. 5 are examples and are not limited thereto, and may be modified in various ways depending on system settings, UPF services requested by AF, etc.
[0081] FIG. 6 illustrates two methods for performing AF authentication and authorization through NEF according to one embodiment of the present disclosure.
[0082] An external NF, AF, can send a request message to NEF when requesting to subscribe to the UPF Event Exposure service. At this time, NEF performs authentication and authorization of the AF that sent the subscription request message. If the AF directly performs a UPF service subscription request to the UPF using the N6 interface, authentication and authorization for the AF cannot be performed because the AF does not send a service subscription request message to the NEF. In one embodiment of the present disclosure, a method for performing authentication and authorization for an AF using N6 in-band signaling is described.
[0083] ALT 1. According to one embodiment of the present disclosure, before the AF requests UPF service to N6 in-band, the AF may first request Authentication / Authorization from the NEF.
[0084] ALT 2. According to another embodiment of the present disclosure, after the AF sends a UPF service subscription request to the UPF, the UPF may request the NEF for Authentication / Authorization of the AF.
[0085] According to one embodiment of the present disclosure, the signaling methods of ALT 1 and ALT 2 can be selectively used depending on the type of AF, the type of UPF service that the AF is requesting, and whether NEF has previously performed Authentication / Authorization for the AF.
[0086] FIG. 7 is a diagram illustrating a signaling procedure according to one embodiment of the present disclosure.
[0087] The signaling procedure illustrated in Fig. 7 represents the signaling procedure of ALT 1 described above.
[0088] In Step 1, AF requests NEF to subscribe to the UPF service. UPF services are those that can be subscribed directly to UPF using N6 in-band. If a service cannot be subscribed directly using N6 in-band, AF can perform the subscription process using NEF based on the Control Plane (CP).
[0089] Before sending a subscription request message to the NEF via the N6 in-band for the UPF service, the AF can send the Nnef_AFAuthorization / Authentication_Request Request message to the NEF based on the CP to perform AF Authentication / Authorization. The Nnef_AFAuthorization / Authentication_Request Request message can include the AF ID, and can also include information required for subscribing to the UPF service (e.g., Event ID(s), Event Reporting Information, etc.). The name of the message can be changed, and the parameters of the message are not limited to the values listed here.
[0090] In Step 2, NEF can perform the Authentication / Authorization procedure for AF and send the result and credentials to AF by including them in the Nnef_AFAuthorization / Authentication_Request Response message. If AF has valid credentials in Step 1, Steps 1 and 2 can be omitted. The credentials received by AF may differ depending on the Event ID and may have a timer, making them invalid after a certain period of time.
[0091] In step 3, AF adds the credentials received in step 2 to the Nupf_EventExposure_Subscribe / Unsubscribe Request message and sends it to UPF.
[0092] In step 4, the UPF can send the Nnef_AFAuthorization / Authentication_Confirmation Request / Response message containing the credentials and AF ID received in step 3 to the NEF. Upon receiving the Nnef_AFAuthorization / Authentication_Confirmation Request / Response message, the NEF performs validation of the credentials and sends the result to the UPF.
[0093] In step 5, if AF passes Authentication / Authorization, UPF notifies AF of the result of the service subscription request by sending the Nupf_EventExposure_Subscribe / Unsubscribe Response message.
[0094] FIG. 8 is a diagram illustrating a signaling procedure according to another embodiment of the present disclosure.
[0095] The signaling procedure illustrated in Fig. 7 represents the signaling procedure of ALT 2 described above.
[0096] In Step 1, AF requests NEF to subscribe to the UPF service. UPF services are those for which direct UPF subscription is possible via N6 in-band. If direct subscription via N6 in-band is not possible, AF may perform the subscription process via NEF based on the Control Plane (CP).
[0097] AF sends a subscription request message to NEF via N6 in-band for UPF service. The Nupf_EventExposure_Subscribe / Unsubscribe Request message contains information required for UPF service subscription (e.g., Event ID(s), Event Reporting Information, etc.) and may also include credentials previously received from NEF. The name of the message can be changed, and the parameters of the message are not limited to the values listed here.
[0098] In step 2, if the credentials in the UPF service subscription message are missing or invalid, the UPF sends the Nnef_AFAuthorization / Authentication_Request Request message to the NEF to request AF Authentication / Authorization. The Nnef_AFAuthorization / Authentication_Request Request message may include the AF ID, and may also include information required for UPF service subscription (e.g., Event ID(s), Event Reporting Information, etc.). The name of the message can be changed, and the parameters of the message are not limited to the values listed here.
[0099] UPF may reject a UPF join request instead of requesting AF Authentication / Authorization by sending a Nnef_AFAuthorization / Authentication_Request Request message to NEF.
[0100] In Step 3, NEF can perform the Authentication / Authorization procedure for AF and send the result and credentials to AF in the Nnef_AFAuthorization / Authentication_Request Response message. The received credentials may vary depending on the Event ID and may have a timer, making them invalid after a certain period of time. NEF can also perform the Authentication / Authorization procedure and send only the result to UPF.
[0101] In Step 4, if the AF passes Authentication / Authorization, the UPF notifies the service subscription request of the result by sending a Nupf_EventExposure_Subscribe / Unsubscribe Response message. If credentials were received from the NEF in Step 3, the UPF can include the credentials in the Nupf_EventExposure_Subscribe / Unsubscribe Response message and send it to the AF.
[0102] FIG. 9 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.
[0103] A terminal according to one embodiment of the present disclosure may include a processor (530) that controls the overall operation of the terminal, a transceiver (510) including a transmitter and a receiver, and a memory (520). Of course, the present invention is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 5.
[0104] According to one embodiment of the present disclosure, the transceiver (510) can transmit and receive signals with network entities or other terminals. The signals transmitted and received with the network entities may include control information and data. In addition, the transceiver (510) can receive signals via a wireless channel, output them to the processor (530), and transmit the signals output from the processor (530) via the wireless channel.
[0105] According to one embodiment of the present disclosure, the processor (530) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (530), the memory (520), and the transceiver (510) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (530) and the transceiver (510) can be electrically connected. In addition, the processor (530) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.
[0106] According to one embodiment of the present disclosure, the memory (520) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (520) provides the stored data upon request of the processor (530). The memory (520) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (520). In addition, the processor (530) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (520).
[0107] FIG. 10 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.
[0108] A network entity according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the network entity, a transceiver (610) including a transmitter and a receiver, and a memory (620). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 6.
[0109] According to one embodiment of the present disclosure, the transceiver (610) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.
[0110] According to one embodiment of the present disclosure, the processor (630) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (630), the memory (620), and the transceiver (610) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the processor (630) and the transceiver (610) can be electrically connected. In addition, the processor (630) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.
[0111] According to one embodiment of the present disclosure, the memory (620) can store data such as basic programs, application programs, and setting information for the operation of a network entity. In particular, the memory (620) provides the stored data upon request of the processor (630). The memory (620) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (620). In addition, the processor (630) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (620).
[0112] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made within a scope that does not detract from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.
[0113] 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 and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).
[0114] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or 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.
[0115] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The 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 the present disclosure.
[0116] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0117] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a 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 via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.
[0118] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.
[0119] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the scope of the claims. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of the above embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.
[0120] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. In the method of UPF (user plane function) entity, A step of receiving a subscribe request message related to a UPF event exposure service from an AF (application function) entity; A step of transmitting an authentication and / or authorization request message for the above AF entity to a Network Exposure Function (NEF) entity; A step of receiving an authentication and / or authorization response message to the authentication and / or authorization request message from the NEF entity; and A method comprising the step of transmitting a subscription response message to the subscription request message to the AF based on the authentication and / or authorization response message.
2. In paragraph 1, The above authentication and / or authorization response message, A method comprising at least one of authentication and / or authorization results and credentials for the AF entity.
3. In paragraph 2, The above credentials are, A method comprising at least one of event identification information and a timer.
4. In paragraph 1, The above subscription request message is, Received as part of an IP (internet protocol) packet, The above IP packet is, An IP header containing a value indicating that it contains a UCMP (UPF Control Message Protocol) message; A UCMP header including a UPF service name field indicating the UPF event exposure service, a service operation field indicating service subscription, and an operation semantics field indicating a service request, and A method comprising UCMP data including at least one value required for a subscription request to the above UPF event exposure service.
5. In the method of NEF (Network Exposure Function) entity, A step of receiving an authentication and / or authorization request message for an application function (AF) entity from a user plane function (UPF) entity; A step of performing authentication and / or authorization procedures for the above AF entity; and A method comprising the step of transmitting an authentication and / or authorization response message to the UPF entity for the authentication and / or authorization request message.
6. In paragraph 5, The above authentication and / or authorization response message, A method comprising at least one of authentication and / or authorization results and credentials for the AF entity.
7. In paragraph 6, The above credentials are, A method comprising at least one of event identification information and a timer.
8. In the UPF (user plane function) entity, Transceiver; and Including a controller coupled with the above transceiver, The above control unit, Receive a subscribe request message related to the UPF event exposure service from the AF (application function) entity, Transmits an authentication and / or authorization request message for the above AF entity to the NEF (Network Exposure Function) entity, Receive an authentication and / or authorization response message for the authentication and / or authorization request message from the NEF entity; A UPF entity controlling to transmit a subscription response message to the subscription request message based on the authentication and / or authorization response message.
9. In paragraph 8, The above authentication and / or authorization response message, A UPF entity comprising at least one of authentication and / or authorization results and credentials for the AF entity.
10. In paragraph 9, The above credentials are, A UPF entity containing at least one of event identification information and a timer.
11. In paragraph 8, The above subscription request message is, Received as part of an IP (internet protocol) packet, The above IP packet is, An IP header containing a value indicating that it contains a UCMP (UPF Control Message Protocol) message; A UCMP header including a UPF service name field indicating the UPF event exposure service, a service operation field indicating service subscription, and an operation semantics field indicating a service request, and A UPF entity containing UCMP data including at least one value required for a subscription request to the above UPF event exposure service.
12. For the NEF (Network Exposure Function) entity, Transceiver; and Including a controller coupled with the above transceiver, The above control unit, Receive an authentication and / or authorization request message from a UPF (user plane function) entity to an AF (application function) entity, Performs authentication and / or authorization procedures for the above AF entities; A NEF entity that controls sending an authentication and / or authorization response message to the above authentication and / or authorization request message to the above UPF entity.
13. In paragraph 12, The above authentication and / or authorization response message, A NEF entity comprising at least one of authentication and / or authorization results and credentials for said AF entity.
14. In paragraph 13, The above credentials are, A NEF entity containing at least one of event identification information and a timer.
Citation Information
Patent Citations
Method for service subscription resource-based authentication in wireless communication system
KR1020160091314A
Skin massager
KR1020220028380A
Method for manufacturing a three-dimensional circular structures and three-dimensional circular structures manufactured thereby
KR102558565B1
User equipment (UE) service over a network exposure function (NEF) in a wireless communication network
US20220377514A1
