Method and apparatus for secure communication in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a first network entity in a wireless communication system, according to one embodiment of the present disclosure, comprises the steps of: receiving, from a user equipment (UE), an association request including an association identifier (ID) for a first service; in response to receiving the association request, generating, on the basis of the association ID and a key (KSP) for a service plane, at least one of an encryption key (KSPenc) or an integrity protection key (KSPint); transmitting an association response to the UE; and transmitting and receiving a message related to the first service to and from the UE by using at least one of the encryption key (KSPenc) or the integrity protection key (KSPint).

Description

Method and device for secure communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for secure communication when using a user plane-based service.

[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) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand 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) to incorporate 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, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; 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 Artificial Intelligence (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] One embodiment of the present disclosure aims to provide an apparatus and method capable of effectively providing secure communication when using a service in a wireless communication system.

[0009] One embodiment of the present disclosure aims to provide an apparatus and method for establishing a secure connection between a terminal and a network entity without NAS in a wireless communication system.

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

[0011] A method performed by a first network entity in a wireless communication system according to one embodiment of the present disclosure comprises: receiving an association request from a user equipment (UE) including an association identifier (ID) for a first service; responding to the receipt of the association request and a key (K) for the association ID and a service plane. SP Based on ), encryption key (K SPenc ) or integrity protection key(K SPint A step of generating at least one of ); a step of transmitting an association response to the UE; and the encryption key (K SPenc ) or integrity protection key(K SPint It includes the step of transmitting and receiving messages related to the first service to the UE using at least one of the following.

[0012] According to one embodiment of the present disclosure, a method performed by user equipment (UE) in a wireless communication system is based on an association identifier (ID) for a first service and a key (K) for a service plane. SP A step of generating ); a step of transmitting an association request including the association ID to a first network entity; a step of receiving an association response from the first network entity in response to receiving the association request; and a key (K) for the association ID and the service plane. SP Encryption key (K) based on ) SPenc ) or integrity protection key(K SPintIt includes the step of transmitting and receiving messages related to the first service with the first network entity using at least one of the following:

[0013] According to one embodiment of the present disclosure, in a wireless communication system, a first network entity comprises: a transceiver; and at least one processor; wherein the at least one processor receives an association request from a UE (user equipment) comprising an association identifier (ID) for a first service, responds to receiving the association request, and a key (K) for the association ID and a service plane. SP Based on ), encryption key (K SPenc ) or integrity protection key(K SPint Generate at least one of ), transmit an association response to the UE, and the encryption key (K SPenc ) or integrity protection key(K SPint It is configured to transmit and receive messages related to the first service with the UE using at least one of the following.

[0014] According to one embodiment of the present disclosure, in a wireless communication system, user equipment (UE) comprises: a transceiver; and at least one processor; wherein the at least one processor comprises a key (K) for a service plane based on an association identifier (ID) for a first service. SPGenerate ), transmit an association request including the association ID to the first network entity, receive an association response from the first network entity in response to receiving the association request, and a key (K) for the association ID and service plane. SP Encryption key (K) based on ) SPenc ) or integrity protection key(K SPint It is configured to transmit and receive messages related to the first service with the first network entity using at least one of the following.

[0015] The disclosed embodiment provides an apparatus and method capable of effectively providing secure communication when using a service in a wireless communication system.

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

[0017] FIG. 1 illustrates an example of a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0018] FIG. 2 shows an example of a key hierarchy in the case where AnF is present according to one embodiment of the present disclosure.

[0019] FIG. 3 shows an example of a key hierarchy in the absence of AnF according to one embodiment of the present disclosure.

[0020] FIG. 4 is a drawing illustrating an example of a service registration process according to one embodiment of the present disclosure.

[0021] FIG. 5 is a diagram showing an example of a preliminary process for establishing secure communication according to one embodiment of the present disclosure.

[0022] FIG. 6 is a diagram illustrating an example of a process in which a UE dynamically requests a new service after a registration process according to one embodiment of the present disclosure is completed.

[0023] FIG. 7 is a diagram illustrating an example of a process in which a Service NF or UP-CMF receives a key in an on-demand format according to one embodiment of the present disclosure.

[0024] FIG. 8 is a diagram illustrating an example of a process of pre-provisioning a key to a Service NF or UP-CMF according to one embodiment of the present disclosure.

[0025] FIG. 9 is a block diagram illustrating an example of the structure of a terminal according to one embodiment of the present disclosure.

[0026] FIG. 10 is a block diagram illustrating an example of the structure of a base station according to one embodiment of the present disclosure.

[0027] FIG. 11 is a block diagram illustrating an example of the structure of a network entity according to one embodiment of the present disclosure.

[0028] The operating principle of the present invention will be described in detail below with reference to the attached drawings. In describing the present disclosure below, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the essence of the present disclosure, such detailed description will be omitted. Furthermore, the terms described below are defined in consideration of their functions in the present invention. Since this may vary depending on the intentions or conventions of the user or operator, the definitions should be determined according to the content throughout this specification.

[0029] 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 numbers.

[0030] The advantages and features of the present invention 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 invention is not limited to the embodiments disclosed below but can be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.

[0031] At this point, 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 instruction means 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).

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

[0033] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), 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 may be configured to run 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." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0034] In the present disclosure, each of the phrases such as “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 corresponding component from another corresponding component and do not limit the corresponding components in other aspects (e.g., importance or order).

[0035] In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Embodiments of the present disclosure will be described below with reference to the attached drawings.

[0036] Terms used in this disclosure to refer to network entities (network entities or network functions), objects of an Edge Computing system, messages, identification information, etc., are illustrative for the sake of 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.

[0037] For convenience, the present disclosure uses terms and names defined in the LTE and NR specifications, which are the most recent standards defined by the 3GPP (The 3rd Generation Partnership Project) among currently existing communication standards. However, the present invention is not limited by the above terms and names and can be applied equally to systems conforming to other standards. In particular, the present invention can be applied to 3GPP NR (5th generation mobile communication standard) and 6G network systems. Furthermore, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. Additionally, embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, provided that they do not deviate significantly from the scope of the present disclosure.

[0038] A 5G mobile communication network may consist of 5G User Equipment (UE), 5G Radio Access Network (RAN), and a 5G core network. The 5G core network may be composed of Network Functions (NFs) such as Access and Mobility Management Function (AMF) providing mobility management functions for UEs, Session Management Function (SMF) providing session management functions, User Plane Function (UPF) performing data delivery roles, Policy Control Function (PCF) providing policy control functions, Unified Data Management (UDM) providing data management functions such as subscriber data and policy control data, and Unified Data Repository (UDR) storing data from various Network Functions (NFs) including UDM. Of course, the above examples are not limited, and the 5G core network may be composed of more or fewer NFs than the aforementioned NFs.

[0039] 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 can provide services by configuring virtual end-to-end networks called network slices to satisfy the specialized requirements of services / applications. Network slices are distinguished by an identifier called S-NSSAI (Single-Network Slice Selection Assistance Information), and network operators can provide services by providing network slice(s) to terminals.

[0040] Specifically, in a 5G system, when a terminal registers with a network, the terminal transmits identifier information for network slices it wishes to request (i.e., Requested S-NSSAIs) to the AMF, and the AMF may provide the terminal with information on network slices that the terminal can use (Allowed NSSAI) by considering the Requested S-NSSAIs and subscriber information. Even if the terminal does not provide information on the requested slices, the AMF may provide the terminal with the Allowed NSSAI, and in this case, the Allowed NSSAI may include information on default configured slices (Default Configured NSSAI) and information on slices configured by default among the subscribed slices included in the terminal subscriber information (i.e., Default Subscribed S-NSSAIs).

[0041] If no slice can be included in the Allowed NSSAI (for example, if the Default Configured NSSAI and Default Subscribed S-NSSAIs are not present or unavailable), the AMF may send a network registration rejection message to the terminal containing a cause code indicating that the registration rejection is due to the absence of available slices.

[0042] Meanwhile, when an arbitrary slice is to be included in the terminal's Allowed NSSAI, Network Slice Admission Control (NSAC) and Network Slice-Specific Authentication and Authorization (NSSAA) procedures for the said slice may be performed.

[0043] According to one embodiment of the present disclosure, in an NSAC procedure, the acceptance of a slice may be determined based on the number of terminals currently registered in a specific slice and the maximum number of registered terminals allowed in that slice (i.e., determining whether the slice is included in the Allowed NSSAI). Specifically, the Network Slice Admission Control Function (NSACF) monitors the number of registered terminals and the number of PDU sessions established per slice for network slices subject to NSAC, and performs control to ensure that the number of registered terminals and the number of PDU sessions established per slice are each kept below the maximum number of registered terminals and the maximum number of PDU sessions, respectively. At this time, when a new terminal is registered in a slice subject to NSAC or an existing registered terminal is deregistered, the AMF may send an update request message to the NSACF to notify it. When a new PDU session is created or an existing PDU session is released in a slice subject to NSAC, the SMF may send an update request message to the NSACF to notify it. When the NSAC receives a message notifying the registration of a new terminal in a slice or a message notifying the creation of a new PDU session, it determines whether to allow it based on the maximum number of terminals and the maximum number of PDU sessions for the slice, and then includes the allowance status in each response message.

[0044] Meanwhile, for data transmission and reception to and from a specific Data Network (DN) through Allowed Slices (Allowed NSSAIs), the terminal selects one of the Allowed Slices, requests the creation of a Packet Data Unit (PDU) session to a specific Data Network Name (DNN) on that slice, and can transmit and receive data through the created PDU session. The PDU session includes multiple traffic flows, and the traffic flows are composed of two types: a Guaranteed Bitrate Quality-of-Service Flow (GBR QoS Flow) and a non-GBR QoS Flow.

[0045] Meanwhile, situations may arise where a network slice becomes unavailable (e.g., congestion occurs among various 5G network entities belonging to an arbitrary network slice, or usage of a specific slice must be temporarily or permanently suspended due to operational reasons (e.g., equipment replacement and upgrade, etc.), or traffic must be moved to another slice due to performance degradation of the network slice transmitting application traffic), and there may be a function to provide services through an alternative network slice for service continuity. Specifically, the network may transmit information (e.g., mapping information) indicating to the terminal to use the Alternative S-NSSAI instead of the S-NSSAI in order to replace the S-NSSAI currently being used by the terminal with the Alternative S-NSSAI (i.e., the alternative network slice).

[0046] Meanwhile, after the AMF transmits information to the terminal indicating that an Alternative S-NSSAI should be used instead of the S-NSSAI, if the replaced S-NSSAI is not supported in the terminal's current tracking area (TA) or the terminal's serving cell due to reasons such as the terminal's movement, a method is required to process the PDU session associated with the replaced S-NSSAI or the terminal's configuration information.

[0047] FIG. 1 illustrates an example of a communication network including a core network entity in a wireless communication system according to one embodiment of the present disclosure.

[0048] A 5G mobile communication network consists of 5G UE (user equipment, terminal), 5G RAN (radio access network, base station, gNB (5G nodeB), eNB (evolved nodeB, etc.), and a 5G core network.

[0049] A 5G core network may include network functions (or network entities), such as an access and mobility management function (AMF) (150) providing mobility management functions for UEs, a session management function (SMF) (160) providing session management functions, a user plane function (UPF) (170) performing data delivery roles, a policy control function (PCF) (180) providing policy control functions, a unified data management function (UDM) (153) providing data management functions such as subscriber data and policy control data, or a unified data repository (UDR) storing data of various network functions. Of course, it is not limited to the above examples, and a 5G core network may include more or fewer network functions.

[0050] Referring to FIG. 1, a terminal (user equipment, UE) (110) can perform communication through a wireless channel formed with a base station (e.g., eNB, gNB), i.e., an access network. In some embodiments, the terminal (110) may be a device used by a user and configured to provide a user interface (UI). As an example, the UE (110) may be a terminal mounted on a vehicle for driving. In other embodiments, the terminal (110) may be a device that performs machine type communication (MTC) that operates without user involvement, or an autonomous vehicle. In addition to electronic devices, the UE may be referred to as a 'terminal', 'vehicle terminal', 'user equipment (UE)', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', or 'user device', or any other term having an equivalent technical meaning. As a terminal, in addition to the UE, customer-premises equipment (CPE) or dongle-type terminals may be used. While the customer-premises equipment is connected to an NG-RAN node like the UE, it can also provide a network to other communication equipment (e.g., laptops).

[0051] Referring to FIG. 1, the AMF (150) provides functions for connection and mobility management at the terminal (110) level, and can be connected to one AMF (150) by default per terminal (110). Specifically, the AMF (150) can perform at least one of the following functions: signaling between core network nodes for mobility between 3GPP access networks, an interface (N2 interface) between wireless access networks (e.g., 5G RAN) (120), NAS signaling with the terminal (110), identification of the SMF (160), and delivery of session management (SM) messages between the terminal (110) and the SMF (160). Some or all of the functions of the AMF (150) may be supported within a single instance of one AMF (150).

[0052] Referring to FIG. 1, the SMF (160) provides session management functions, and if the terminal (110) has multiple sessions, each session may be managed by a different SMF (160). Specifically, the SMF (160) may perform at least one of the following functions: session management (e.g., session establishment, modification, and release including maintaining a tunnel between the UPF (170) and the access network node), selection and control of UP (user plane) functions, setting up traffic steering to route traffic from the UPF (170) to an appropriate destination, termination of the SM portion of a NAS message, downlink data notification (DDN), and initiator of AN specific SM information (e.g., delivered to the access network via the N2 interface through the AMF (150)). Some or all of the functions of the SMF (160) may be supported within a single instance of a single SMF (160).

[0053] Referring to FIG. 1, the NRF (159) can perform the function of storing information about NFs installed in a mobile carrier network and providing the stored information. The NRF (159) can be connected to all NFs. When each NF starts operating in the carrier network, it notifies the NRF (159) that the NF is operating within the network by registering with the NRF (159).

[0054] UDM (153) is an NF that performs a role similar to a home subscriber server (HSS) of a 4G network and can store the subscription information of the terminal (110) or the context used by the terminal (110) within the network.

[0055] The NEF (155) can perform the role of connecting the NF within the 5G mobile communication system to a third-party server. Additionally, the NEF (155) can perform the role of providing data to, updating, or obtaining data from the UDR (157).

[0056] The UDR (157) can perform the function of storing subscription information of the terminal (110), storing policy information, storing data exposed to the outside, or storing information required by a third-party application. In addition, the UDR (157) can also perform the role of providing stored data to other NFs.

[0057] In 3GPP systems, a conceptual link connecting NFs within a 5G system may be referred to as a reference point. A reference point may be referred to as an interface. The following exemplifies a reference point (hereinafter used interchangeably with interface) included in a 5G system architecture as described across various embodiments of the present disclosure.

[0058] - N1: Reference point between UE (110) and AMF (150)

[0059] - N2: Reference point between (R)AN(120) and AMF(150)

[0060] - N3: Reference point between (R)AN(120) and UPF(170)

[0061] - N4: Reference point between SMF (160) and UPF (170)

[0062] - N5: Reference point between PCF (180) and AF (130)

[0063] - N6: Reference point between UPF (170) and DN (140)

[0064] - N7: Reference point between SMF (160) and PCF (180)

[0065] - N8: Reference point between UDM (153) and AMF (150)

[0066] - N9: Reference point between 2 core UPFs (170)

[0067] - N10: Reference point between UDM (153) and SMF (160)

[0068] - N11: Reference point between AMF (1590) and SMF (160)

[0069] - N12: Reference point between AMF (150) and AUSF (151)

[0070] - N13: Reference point between UDM (153) and authentication server function (AUSF) (151)

[0071] - N14: Reference point between 2 AMFs (150)

[0072] - N15: For non-roaming scenarios, a reference point between PCF (180) and AMF (150); for roaming scenarios, a reference point between PCF (180) and AMF (150) within the visited network.

[0073] According to one embodiment of the present disclosure, network slicing technology in a 5G system represents a technology and structure that enables the implementation of multiple virtualized and independent logical networks within a single physical network. A network operator may provide services by configuring a virtual end-to-end network called a network slice to satisfy the specialized requirements of a service / application. A network slice may be distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). The network may transmit a set of allowed slices (e.g., allowed NSSAI(s)) to a terminal during a terminal registration procedure (e.g., UE registration procedure). The terminal may transmit and receive application data through a PDU (protocol data unit) session created via one of the S-NSSAIs (i.e., network slices) included in the set of allowed slices transmitted from the network to the terminal.

[0074] Meanwhile, in a 6G system, the mobile communication network can be defined as an evolved form of the 5G mobile communication network. In the present invention, the RAN in 6G is named the 6G RAN, and the 6G NFs included in the 6G core network can be named evolved AMF (eAMF), evolved SMF (eSMF), and evolved UPF (eUPF), respectively, corresponding to the NFs of 5G such as AMF, SMF, and UPF. Of course, the names of the NFs are not limited to the above examples, and the RAN in 6G and the 6G core network entities may be referred to by other names. The 6G RAN and 6G core network can additionally support the following functions compared to the 5G RAN and 5G core network (i.e., composed of 5G NFs). Of course, they are not limited to the examples below.

[0075] - 6G RAN: For example, in the case of 6G RAN, a WUS (wake-up signal)-based energy saving function can be supported as a basic function. An energy saving function may mean a function that switches to sleep mode (a low-power state that does not support some functions of the base station) and wakes up to normal operation (supports all functions) only when it receives a WUS from a terminal.

[0076] - 6G RAN can utilize AI capabilities for various basic functions such as channel state prediction, downlink traffic scheduling, uplink packet scheduling, radio resource management, and handover. To this end, 6G RAN can provide AI model management functions tailored to each purpose, AI model application functions based on changed conditions, data collection and training functions for training AI models, and AI model-based inference functions.

[0077] - 6G RAN supports various Radio Access Technologies (RATs) and can support Multi-RAT Spectrum Sharing (MRSS), which allows for dynamic sharing of frequencies among various Radio Access Technologies.

[0078] - While 5G RANs communicated with the 5G core network solely through AMFs, 6G RANs can provide interfaces for direct communication with various NFs of the 6G core network. For example, a 6G RAN can communicate directly with NFs that provide session management functions of the 6G core network (e.g., which may be located in eSMFs or 6G SMFs). Additionally, it can support SCTP (stream control transmission protocol) based protocols, as well as, for example, HTTP protocols and / or QUIC (quick UDP internet connections) based Service-based interfaces (SBIs), and can communicate with other NF(s) and RANs through SBIs.

[0079] - The 6G Core Network provides interfaces for communication with the 6G RAN and 6G UEs. In this case, it may provide interfaces with the 6G UEs not only through the control plane but also through the user plane. Alternatively, the 6G UE may be provided with an interface to communicate with the core network through a Service Plane (SP). A Service Plane (SP) may be a new plane for transmitting service data, logically or physically separated from the Control User Plane (UP) in a mobile communication network. Transmission by the SP may be carried out through the UP or through separate resources.

[0080] - 6G core networks can provide functions such as mobility management, connectivity management, authentication, policies, and service / data exposure. In addition, they can provide various new services such as Converged Computing Service, Integrated Sensing and Communication Service (ISAC), non-3GPP Sensing Service, and AI / ML (artificial intelligence / machine learning).

[0081] In a 6G system, the mobile communication network may consist of 6G UE (user equipment, terminal), 6G RAN (radio access network, base station, evolved gNB (egNB), etc.), and a 6G core network. The 6G core network may be composed of network functions such as the Evolved AMF (eAMF), which provides mobility management functions for the UE; the Evolved SMF (eSMF), which provides session management functions; the Evolved UPF (eUPF), which performs data delivery; the Evolved PCF (ePCF), which provides policy control functions; the Evolved UDM (eUDM), which provides data management functions such as subscriber data and policy control data; and the evolved UDR (eUDR), which stores data for various network functions. Of course, the above examples are not limited, and the 6G core network may be composed of more or fewer network functions.

[0082] Reference points connecting NFs within a 6G system can be represented by adding "Evolved" to each network entity (network function) (e.g., AMF) in the 5G system architecture of FIG. 1 (e.g., in the case of an AMF, it is represented in the form of an Evolved AMF (eAMF)). The network entity in the 6G system architecture (i.e., 6G network entity) corresponding to the network entity (i.e., 5G entity) in the 5G system architecture of FIG. 1 may include some or all of the functions of the 5G network entity, and may also include other functions for 6G services. For example, the eAMF in the 6G system may provide mobility management, authentication management, and connection management functions for terminals provided by the AMF in the 5G system.

[0083] In addition, reference points between 6G network entities can be expressed similarly to the names of reference points between 5G network entities. For example, N1 in a 5G system can be replaced with a different reference point name (e.g., N1+) in a 6G system.

[0084] Meanwhile, the UE can support various 5G / 6G services, and for each service, the UE can communicate with the NF that provides the service (i.e., service NF).

[0085] As used in this disclosure, the term Service NF or Service NF may mean an NF that communicates with a UE for a specific service and may be one of the NFs described in the service examples below. Of course, it is not limited to the examples below.

[0086] - Location service (LCS): This may refer to a service that provides the location of a UE or a service that receives the location of a UE from a network. In the case of a location service, the NF corresponding to the Service NF is an NF that provides the LCS service and may be referred to as an LMF or eLMF.

[0087] - Sensing service: A service based on UE-based sensing information. This may include object detection, fall detection, user health information (e.g., heart rate, blood pressure information, etc.), speed and location information, collision notification services, etc. In the case of a sensing service, the NF corresponding to the Service NF is an NF that provides the sensing service and may be referred to as Sensing NF, ISAC NF, etc.

[0088] - AI Data collection service: This may refer to a service that collects data necessary for training an AI model for AI model-based communication. It may include functions such as a terminal transmitting data necessary for training an AI model to a network, and a terminal receiving data necessary for training an AI model from a network. In the case of an AI Data collection service, the NF corresponding to the Service NF refers to an NF that provides data collection and provision services, and may be referred to by names such as Data Collection NF (DCNF), AI NF, and Data Service NF (DSNF).

[0089] - UE Policy service: This may refer to a service where the Home PLMN provides the terminal with policy information that the terminal must follow. It may include UE Route Selection Policy (URSP) rules (i.e., rules indicating which network path the terminal should use for traffic to be transmitted or received; based on URSP rules, the terminal can determine which DNN and / or session with which network slice to transmit or receive application traffic through), Access network selection rules (rules indicating which non-3GPP access network the terminal should select), etc. In the case of the UE Policy service, the NF corresponding to the Service NF refers to an NF that provides policy information to the terminal and provides the function to verify whether policy execution has been performed, and may be referred to as Policy Control Function (PCF), ePCF, Policy Network Function, etc.

[0090] - UE Configuration service: This may refer to a service that provides the terminal with configuration information to be used by the Home PLMN or Serving PLMN. The configuration information may include various information such as Service Area Restriction information, accessible femto cell IDs, network slice configuration information, and non-3GPP access connection information. In the case of the UE Configuration service, the NF corresponding to the Service NF refers to an NF that provides configuration information to the terminal and provides a function to verify whether it has been received properly. Depending on the configuration information, it may be various NFs such as AMF, eAMF, SMF, eSMF, PCF, ePCF, Policy Network Function, UDM, eUDM, etc.

[0091] - Network Selection Configuration Service: This may refer to a service in which the Home PLMN provides configuration information to control the terminal's network selection and PLMN selection. The information provided by the Home PLMN to the UE in the Network Selection Configuration Service may include one or more of the following: a list containing preferred PLMN IDs, a list containing preferred RATs, and a list containing RAT(s) and / or service(s) supported by each PLMN in the list containing preferred PLMN IDs. In the case of the Network Selection Configuration Service, the NF corresponding to the Service NF refers to an NF that provides the terminal with information necessary for PLMN selection and provides a function to verify whether such information has been received, and may be referred to as UDM, eUDM, SoR AF, SoR Function, etc.

[0092] The UP-CMF (User Plane Connection Management Function) is an entity that assists the UE in communicating with Service NFs, and through the connection established between the UP-CMF and the UE, one or more services can perform service message transmission. Therefore, since the number of connections to manage per service is reduced, there may be an advantage in that the UE's resource usage and management complexity are relatively lower. On the other hand, in the case of a structure that supports message transmission through service connections, the necessary transmission protocol can be used according to the requirements of each service, so it can be used for services with special requirements (e.g., large-scale traffic transmission).

[0093] AnF (Anchor Function) can act as an anchor that receives a specific key from eAUSF, generates a key used for secure communication with the UE (110) and provides it to the Service NF or UP-CMF. The role of AnF can be performed by eAUSF.

[0094] FIG. 2 illustrates an example of a key hierarchy where AnF exists according to an embodiment of the present disclosure. AnF and eSEAF may be the same. That is, K AnF is K eSEAF It could be like that.

[0095] A Service NF can be an NF that provides a specific service. For example, a Service NF may include an eAMF that provides Mobility Management functions, an eSMF that provides Session Management functions, an ePCF that provides Policy Control functions, an NF that provides AI / ML services, an NF that provides Sensing Services, and the like.

[0096] Referring to Fig. 2, eAUSF is K eAUSF From K AnF It can generate. In one embodiment, the input value used may include at least one of the following. Other values ​​may be used as additional inputs.

[0097] - K eAUSF

[0098] - RAND eAUSF : Random value generated by AUSF

[0099] - AnF ID

[0100] - SN name

[0101] K AnF AnF that received is K AnF From K SP(For example, a key for a Service Plane, or a key provided to an NF (e.g., eAMF, eSMF, ePCF, an NF providing a specific service, an NF that transmits control plane data such as UP-CMF, etc.) can be generated. In one embodiment, the input value used may include at least one of the following. Other values ​​may be used as additional inputs.

[0102] - K AnF

[0103] - Association ID: A value assigned to identify a UE in the network or a value identified by the network to identify a session.

[0104] - RAND UE : Random value generated by the UE

[0105] - SNF / UP-CMF ID: Service NF ID or UP-CMF ID

[0106] K SP If a Service NF or UP-CMF that receives it needs to update the key, the Service NF / UP-CMF / UE uses the K it holds SP The key can be updated using [this]. The UE can also perform the same operation, and the Service NF or UP-CMF can provide the UE with signaling and input values ​​to update the key. In one embodiment, the input used may include at least one of the following. Other values ​​may be used as additional inputs.

[0107] - K SP

[0108] - Uplink COUNT

[0109] - Downlink COUNT

[0110] - COUNT

[0111] Service NF or UP-CMF and UE are K SP From the encryption key (K SPenc ) or integrity protection key(K SPint At least one of ) can be generated. In one embodiment, the input used may include at least one of the following. Other values ​​may be used as additional inputs.

[0112] - K SP

[0113] - ID of the encryption algorithm selected by eAMF

[0114] - ID of the integrity protection algorithm selected by eAMF

[0115] - Cryptographic algorithm ID selected by Service NF or UP-CMF

[0116] - ID of the integrity protection algorithm selected by Service NF or UP-CMF

[0117] FIG. 3 shows an example of a key hierarchy in the absence of AnF according to one embodiment of the present disclosure.

[0118] A Service NF can be an NF that provides a specific service. For example, a Service NF may include an eAMF that provides Mobility Management functions, an eSMF that provides Session Management functions, an ePCF that provides Policy Control functions, an NF that provides AI / ML services, an NF that provides Sensing Services, and the like.

[0119] Referring to Fig. 3, eAUSF is K eAUSF From K SP It can generate. In one embodiment, the input value used may include at least one of the following. Other values ​​may be used as additional inputs.

[0120] - K eAUSF

[0121] - RAND eAUSF : Random value generated by AUSF

[0122] - AnF ID

[0123] - Association ID: A value assigned to identify a UE in the network or a value identified by the network to identify a session.

[0124] - RAND UE : Random value generated by the UE

[0125] - SNF / UP-CMF ID: Service NF ID or UP-CMF ID

[0126] K SP If a Service NF or UP-CMF that receives it needs to update the key, the Service NF / UP-CMF / UE uses the K it holds SP The key can be updated using [this]. The UE can also perform the same operation, and the Service NF or UP-CMF can provide the UE with signaling and input values ​​to update the key. In one embodiment, the input used may include at least one of the following. Other values ​​may be used as additional inputs.

[0127] - K SP

[0128] - Uplink COUNT

[0129] - Downlink COUNT

[0130] - COUNT

[0131] Service NF or UP-CMF and UE are K SP From the encryption key (K SPenc ) or integrity protection key(K SPintAt least one of ) can be generated. In one embodiment, the input used may include at least one of the following. Other values ​​may be used as additional inputs.

[0132] - K SP

[0133] - ID of the encryption algorithm selected by eAMF

[0134] - ID of the integrity protection algorithm selected by eAMF

[0135] - Cryptographic algorithm ID selected by Service NF or UP-CMF

[0136] - ID of the integrity protection algorithm selected by Service NF or UP-CMF

[0137] FIG. 4 is a drawing illustrating an example of a service registration process according to one embodiment of the present disclosure.

[0138] A Service NF can be an NF that provides a specific service. For example, a Service NF may include an eAMF that provides Mobility Management functions, an eSMF that provides Session Management functions, an ePCF that provides Policy Control functions, an NF that provides AI / ML services, an NF that provides Sensing Services, and the like.

[0139] Referring to FIG. 4, in Step 1, a Service NF or UP-CMF may request service registration (NF register request) from the eNRF. In one embodiment, the registration request message may include at least one of an NF type, an available service, an indicator 1, and information of the UP-CMF. A detailed description of the parameters is as follows. It is not limited to the following examples.

[0140] - Directive 1: Indicates whether the UE must communicate with itself through end-to-end protection or communicate through the UP-CMF in order to use the services provided by the Service NF or UP-CMF. It may also indicate the service characteristics of the Service NF or UP-CMF (e.g., low latency required services).

[0141] - UP-CMF information: For example, if the above indicator 1 indicates that communication may be made through the UP-CMF, it may include information on which UP-CMF should be used.

[0142] In step 2, the eNRF may transmit an NF registerer response. In one embodiment, the registerer response message may include at least one of an NF type, a service, and an indicator 2. A detailed description of the parameters is as follows. It is not limited to the examples below.

[0143] - Indicator 2: eNRF may indicate whether direct communication with the UE is possible. Regardless of the request from Service NF or UP-CMF, depending on the operator policy, it may indicate whether the entity receives the key on-demand (Fig. 7) or pre-provisions the key (Fig. 8).

[0144] FIG. 5 is a diagram showing an example of a preliminary process for establishing secure communication according to one embodiment of the present disclosure.

[0145] A Service NF can be an NF that provides a specific service. For example, it may include an eAMF that provides Mobility Management functionality, an eSMF that provides Session Management functionality, an ePCF that provides Policy Control functionality, an NF that provides AI / ML services, an NF that provides Sensing Services, etc.

[0146] Referring to FIG. 5, in step 1, the UE may send a Registration Request message to the eAMF. The Registration Request message may include a list of services that the UE requests and at least one of the indicators 3. A detailed description of the parameters may be as follows, but is not limited to the examples below.

[0147] - Indicator 3: This may be an indicator indicating whether the service requested by the UE communicates directly with the Service NF or must communicate using the UP-CMF. Alternatively, it may be an indicator indicating whether the Service NF or the UP-CMF must receive the key on-demand.

[0148] In step 2, a primary authentication process can be performed between the UE and the network.

[0149] In step 3, eAUSF uses the method described in Fig. 2 to K AnF It can generate. In one example, eAUSF is K AnF (If the structure of Fig. 2 is used) or K eAUSF A key ID (KID) capable of identifying (when the structure of FIG. 3 is used) can be generated. In one embodiment, when generating the KID, at least one of the following inputs may be used. Other additional inputs may be used.

[0150] - K eAUSF

[0151] - SUPI

[0152] - RAND eAUSF

[0153] - AnF ID

[0154] - eAUSF ID

[0155] KID may include a value combined with at least one of the above-mentioned generated output value, the address of AnF / eAUSF, the ID of AnF / eAUSF, or the Routing Indicator (RID) of AnF / eAUSF.

[0156] In step 4, eAUSF may send an authentication response message (Nausf_UEAuthenticattion_Authenticate Response) to eAMF. In one embodiment, the authentication response message is K eAMF , RAND eAUSF It may include at least one of an AnF / AUSF address, an AnF / eAUSF RID, and an AnF / eAUSF ID.

[0157] In Step 5, if AnF is used, eAUSF may request an anchor key register request from AnF. The above anchor key register request is SUPI, K AnF At least one of , KID may be included.

[0158] In step 6, eAMF can make a discovery request to eNRF based on the service requested by the UE in step 1.

[0159] In one embodiment, the eAMF may transmit the indicator 3 received in step 1 together with the eNRF to transmit what type of communication is expected (e.g., whether to communicate directly with the Service NF or to communicate via the UP-CMF). In one embodiment, the eNRF may determine what type of communication is possible by combining various information such as the service information requested by the UE, indicator 3, and the NF type, and transmit indicator 4 to the eAMF, and may provide information that the eAMF can determine. In one embodiment, if information that the eAMF can determine is provided, the eAMF may generate the indicator 4 described below based on that information.

[0160] - Indicator 4: An indicator indicating what type of communication the UE should perform. For example, it may indicate communicating directly with the Service NF or communicating through the UP-CMF. Alternatively, it may be an indicator indicating whether the Service NF or UP-CMF should receive the key on-demand. It may also include information on the security algorithm (e.g., encryption algorithm or integrity protection algorithm) to be used for communication with a specific Service NF or a specific UP-CMF.

[0161] In step 7, the eAMF may transmit a NAS Security Mode Command message to the UE. In one embodiment, the NAS Security Mode Command message may include information about the algorithm selected by the eAMF, Association ID(s), AnF / eAUSF address or RID or ID, RAND eAUSF It may include at least one of the ID of Service NF or UP-CMF, and the indicator 4.

[0162] - Association ID: A value assigned by the network to identify a UE or a session, which can be used to identify a session between a UE and a Service NF, and can be used to identify a session between a UE and a UP-CMF.

[0163] In step 8, the UE can send a NAS Security Mode Complete message.

[0164] In step 9, if discovery was not performed in step 6, eAMF can perform the actions described in step 6 at that step.

[0165] In step 10, if the discovery operation was performed in step 9, the eAMF may transmit the result to the UE via a NAS message. In one embodiment, the NAS message may include Association ID(s), AnF / AUSF address or RID or ID, RAND eAUSF It may include at least one of the ID of Service NF or UP-CMF, and 4 indicators.

[0166] In step 11, if indicator 3 or indicator 4 indicates that the Service NF / UP-CMF needs to receive the key in an on-demand format or needs to communicate directly with the Service NF, the process of FIG. 7 described below may be performed.

[0167] Alternatively, if indicator 3 or indicator 4 indicates that the key does not need to be received in an on-demand format, or indicates that communication must be done via UP-CMF, the process of FIG. 8 described below may be performed.

[0168] FIG. 6 is a diagram illustrating an example of a process in which a UE dynamically requests a new service after a registration process according to one embodiment of the present disclosure is completed.

[0169] A Service NF can be an NF that provides a specific service. For example, a Service NF may include an eAMF that provides Mobility Management functions, an eSMF that provides Session Management functions, an ePCF that provides Policy Control functions, an NF that provides AI / ML services, an NF that provides Sensing Services, and the like.

[0170] Referring to Fig. 6, at step 0, the registration procedure can be performed to complete the registration. That is, the process of Fig. 5 can be performed in advance.

[0171] In Step 1, the UE may send a NAS message to the eAMF. In one embodiment, the NAS message may include a list of services that the UE requests and at least one of the indicator 5. A detailed description of the parameters may be as follows, but is not limited to the examples below.

[0172] - Indicator 5: This may be an indicator indicating whether the service requested by the UE communicates directly with the Service NF or must communicate using the UP-CMF. Alternatively, it may be an indicator indicating whether the Service NF or the UP-CMF must receive the key on-demand.

[0173] In step 2, eAMF can make a discovery request to eNRF based on the service requested by the UE in step 1.

[0174] In one embodiment, the eAMF may transmit the indicator 5 received in step 1 to the eNRF together to transmit what type of communication is expected (e.g., whether to communicate directly with the Service NF or to communicate via the UP-CMF). In one embodiment, the eNRF may determine what type of communication is possible by combining various information such as the service information requested by the UE, indicator 5, and the NF type, and transmit indicator 6 to the eAMF, and may provide information that the eAMF can determine. In one embodiment, if information that the eAMF can determine is provided, the eAMF may generate indicator 6 based on that information.

[0175] - Indicator 6: An indicator indicating what type of communication the UE should perform. For example, it may indicate communicating directly with the Service NF or communicating through the UP-CMF. Alternatively, it may be an indicator indicating whether the Service NF or UP-CMF should receive the key on-demand. It may also include information on the security algorithm (e.g., encryption algorithm or integrity protection algorithm) to be used for communication with a specific Service NF or a specific UP-CMF.

[0176] In step 3, eAMF may transmit a NAS message. The NAS message may include at least one of Association ID(s) and indicator 6.

[0177] - Association ID: A value assigned by the network to identify a UE or a session, which can be used to identify a session between UE and Service NF, and can be used to identify a session between UE and UP-CMF.

[0178] In step 4, if indicator 5 or indicator 6 indicates that the Service NF / UP-CMF needs to receive the key in an on-demand format or needs to communicate directly with the Service NF, the process of FIG. 7 described below may be performed.

[0179] Alternatively, if indicator 5 or indicator 6 indicates that Service NF or UP-CMF does not need to receive the key in an on-demand format, or indicates that communication must be done through UP-CMF, the process of FIG. 8 described below may be performed.

[0180] FIG. 7 is a diagram illustrating an example of a process in which a Service NF or UP-CMF receives a key in an on-demand format according to one embodiment of the present disclosure.

[0181] A Service NF can be an NF that provides a specific service. For example, a Service NF may include an eAMF that provides Mobility Management functions, an eSMF that provides Session Management functions, an ePCF that provides Policy Control functions, an NF that provides AI / ML services, an NF that provides Sensing Services, and the like.

[0182] For example, if the number of Service NF or UP-CMF is so large that it is practically impossible for AnF or eAUSF to provision keys in advance, a process of receiving them on-demand may be necessary.

[0183] Referring to Fig. 7, the process of Fig. 5 or Fig. 6 may have already been performed prior to Step 1.

[0184] In step 1, the UE, like the step 3 operation in Fig. 5, K eAUSF , K AnF, at least one of KID can be generated. In one embodiment, the UE uses the method of FIG. 2 or FIG. 3 to K SP It can generate.

[0185] In one embodiment, if the UE receives a signaling that the Service NF or UP-CMF uses an algorithm such as the algorithm selected by the eAMF in step 7 of FIG. 5, K using the method of FIG. 2 or FIG. 3 SPenc or K SPint It can generate.

[0186] In one embodiment, if the UE has not received the above signaling, or has received a signaling that the Service NF or UP-CMF uses an algorithm different from the algorithm selected by the eAMF, K SP It can only be generated up to, or if the Service NF or UP-CMF has received information about a specific algorithm different from the eAMF, then K SPenc or K SPint It can generate.

[0187] In step 2, the UE may send an Association request to the Service NF or UP-CMF. In one embodiment, the Association request may include at least one of the Association ID(s), the KID generated in step 1, the RANDUE, the address or ID or RID of the AnF / eAUSF, the algorithm(s) selected by the eAMF, a list of algorithms supported by the UE, a COUNT (e.g., which may be divided into Uplink COUNT and Downlink COUNT and may be managed as a single COUNT regardless of direction), and a Message Authentication Code (MAC).

[0188] In Step 3, Service NF / UP-CMF may send a Key get request to AnF or eAUSF. The Key get request includes the ID, KID, and RAND of Service NF or UP-CMF. UE It may include at least one of the following.

[0189] In step 4, eAUSF or AnF uses the method of Fig. 2 or Fig. 3 to K SP It can generate.

[0190] In step 5, eAUSF or AnF may transmit a Key get response to Service NF or UP-CMF. In one embodiment, the Key get response is K SP It may include.

[0191] At step 6, Service NF or UP-CMF is K SPenc or K SPint It can generate. In one embodiment, the input for key generation may include at least one of the following. Other additional inputs may be used.

[0192] - K SP

[0193] - Cryptographic algorithm ID selected by Service NF or UP-CMF

[0194] - ID of the integrity protection algorithm selected by Service NF or UP-CMF

[0195] - ID of the encryption algorithm selected by eAMF

[0196] - ID of the integrity protection algorithm selected by eAMF

[0197] In step 7, Service NF or UP-CMF can send an Association response message.

[0198] In one embodiment, the Association response message may include at least one of algorithm information selected by the Service NF or UP-CMF, a list of algorithms supported by the UE, a COUNT, and a MAC. The MAC includes some or all of the information of the message and K SPint It can be a value generated using .

[0199] At step 8, if K at step 1 SPenc or K SPint If is not generated, K at that step SPenc or K SPint cast It can be generated. In one embodiment, the operation of step 8 can be performed in the same way as the operation of Service NF or UP-CMF in step 6.

[0200] In step 9, the UE and Service NF or UP-CMF are K SPenc or K SPint Secure communication can be performed using . Before sending data to a specific Service NF or UP-CMF, the UE uses the K corresponding to the said Service NF or UP-CMF to encrypt the data or protect its integrity. SPenc or K SPintIt can obtain (or derive) the key. The UE may perform security processing on the data to be sent using the obtained (or derived) key. To this end, the UE may store data in the form shown in Table 1. The COUNT value (which may be separated into Uplink COUNT and Downlink COUNT, or may be a combined COUNT) is a value starting from 0 or 1, can be used as input for encryption or integrity protection algorithms, and can be stored by incrementing the value by 1 after use. The COUNT value is a value stored separately between the UE and a specific Service NF or a specific UP-CMF, and can be synchronized whenever messages are exchanged. For example, before a UE sends data to Service NF 2, if the COUNT associated with that Service NF 2 (Uplink COUNT or integrated COUNT) is 3, 3 or 4 is used as the input value for an encryption or integrity protection algorithm, and after sending the protected data and some or all of the used COUNT (3 or 4 in this example) to Service NF 2, the UE may increment the COUNT value stored associated with Service NF 2 by 1. Upon receiving this, Service NF 2 may decrypt or verify integrity based on the received data, and after performing this process, may increment the COUNT value stored associated with that UE by 1.

[0201] Service NF 1 Service Characteristics or Association IDK SPenc1 K SPint1 COUNTService NF 2 Service Characteristics or Association IDK SPenc2 K SPint2 COUNTUP-CMF 1 Service Characteristics or Association IDK SPenc3 K SPint3COUNTUP-CMF 2 Service Characteristics or Association IDK SPenc4 K SPint4 COUNT...............

[0202] FIG. 8 is a diagram illustrating an example of a process of pre-provisioning a key to a Service NF or UP-CMF according to an embodiment of the present disclosure. A Service NF may be an NF that provides a specific service. For example, a Service NF may include an eAMF that provides a Mobility Management function, an eSMF that provides a Session Management function, an ePCF that provides a Policy Control function, an NF that provides an AI / ML service, an NF that provides a Sensing Service, etc.

[0203] For example, if the number of Service NF or UP-CMF is small and it is realistically possible for AnF or eAUSF to pre-provision the key, the process of Fig. 8 may be required.

[0204] Referring to Fig. 8, prior to Step 1, the process of Fig. 5 or Fig. 6 may already be performed.

[0205] In step 1, the UE can send a NAS message to the eAMF. In one embodiment, the NAS message is RAND UE It may include.

[0206] In step 2, eAMF may send a Key provisioning request to AnF or eAUSF. In one embodiment, the Key provisioning request may include the address of a Service NF or UP-CMF, a list of algorithms selected by eAMF (at least one algorithm), a list of algorithms supported by the UE, UE security capabilities (UE sec cap) (e.g., including a list of algorithms supported by the UE), Association ID(s), and RAND UEIt may include at least one of the following.

[0207] In step 3, eAUSF or AnF uses the method of Fig. 2 or Fig. 3 to K SP It can generate.

[0208] In step 4, AnF or eAUSF may transmit a Key provisioning response to Service NF or UP-CMF. In one embodiment, the Key provisioning response includes a list of algorithms selected by eAMF, a list of algorithms supported by the UE, UE security capabilities (UE sec cap) (e.g., including a list of algorithms supported by the UE), Association ID(s), and K SP It may include at least one of the following.

[0209] In step 5, UE uses the method of FIG. 2 or FIG. 3 to K SP It can generate.

[0210] In one embodiment, the UE may decide to make a service request based on information from a Service NF or UP-CMF previously received from the network (e.g., step 7 or 10 of FIG. 5). In one embodiment, the UE K in the same manner as the AnF or eAUSF performed in step 3. SP It can generate. In one embodiment, if the UE receives a signaling that the Service NF or UP-CMF uses an algorithm such as the algorithm selected by the eAMF in step 7 of FIG. 5, then K can be generated using the method of FIG. 2 or FIG. 3. SPenc or K SPint It can generate. In one embodiment, if the UE does not receive the above signaling, or receives a signaling that uses an algorithm different from the algorithm selected by eAMF, the UE K SPIt can only generate up to, or if the UE receives information about a specific algorithm where the Service NF or UP-CMF is different from the eAMF, the UE K SPenc or K SPint It can generate.

[0211] In step 6, the UE may perform an Association request to the Service NF or UP-CMF. In one embodiment, the Association request may include at least one of the Association ID(s), a list of algorithms selected by the eAMF, a list of algorithms supported by the UE, a COUNT, and a MAC.

[0212] At step 7, Service NF or UP-CMF is K SP From K SPenc or K SPint It can generate. In one embodiment, the input for key generation may include at least one of the following. Other additional inputs may be used.

[0213] - K SP

[0214] - Cryptographic algorithm ID selected by Service NF or UP-CMF

[0215] - ID of the integrity protection algorithm selected by Service NF or UP-CMF

[0216] - ID of the encryption algorithm selected by eAMF

[0217] - ID of the integrity protection algorithm selected by eAMF

[0218] In step 8, the Service NF or UP-CMF may transmit an Association response message. In one embodiment, the Association response message may include at least one of algorithm information selected by the Service NF or UP-CMF, a list of algorithms supported by the UE, a COUNT, and a MAC. The MAC includes some or all of the information of the message and K SPint It can be a value generated using .

[0219] At step 9, if K at step 5 SPenc or K SPint If is not generated, it can be generated at that step. In one embodiment, K SPenc or K SPint The operation to create can be performed in the same way as the operation of Service NF or UP-CMF in step 7.

[0220] In step 10, the UE and Service NF or UP-CMF are K SPenc or K SPint Secure communication can be performed using . Before sending data to a specific Service NF or UP-CMF, the UE uses the K corresponding to the said Service NF or UP-CMF to encrypt the data or protect its integrity. SPenc or K SPintIt can be found. Security processing for the data to be sent can also be performed using the found key. To this end, the UE may store data in the form shown in Table 2. The COUNT value (which may be separated into Uplink COUNT and Downlink COUNT, or may be a combined COUNT) is a value starting from 0 or 1, can be used as input for encryption or integrity protection algorithms, and can be stored by incrementing the value by 1 after use. The COUNT value is a value stored separately between the UE and a specific Service NF or a specific UP-CMF, and can be synchronized whenever messages are exchanged. For example, before a UE sends data to Service NF 2, if the COUNT associated with that Service NF 2 (Uplink COUNT or integrated COUNT) is 3, 3 or 4 is used as the input value for an encryption or integrity protection algorithm, and after sending the protected data and some or all of the used COUNT (3 or 4 in this example) to Service NF 2, the UE may increment the COUNT value stored associated with Service NF 2 by 1. Upon receiving this, Service NF 2 may decrypt or verify integrity based on the received data, and after performing this process, may increment the COUNT value stored associated with that UE by 1.

[0221] Service NF 1 Service Characteristics or Association IDK SPenc1 K SPint1 COUNTService NF 2 Service Characteristics or Association IDK SPenc2 K SPint2 COUNTUP-CMF 1 Service Characteristics or Association IDK SPenc3 K SPint3 COUNTUP-CMF 2 Service Characteristics or Association IDK SPenc4 K SPint4COUNT...............

[0222] A terminal according to one embodiment of the present disclosure may transmit a first message containing first information to a network entity. In one embodiment, the terminal may receive a second message containing second information from the first network entity.

[0223] In one embodiment, the terminal may transmit an Association request to a second network entity based on at least one of the first information or the second information.

[0224] In one embodiment, the terminal may determine the second network entity based on at least one of the first information or the second information. In one embodiment, the second network entity may include one of a service NF (network function) entity and a UP-CMF (user plane-connection management function) entity.

[0225] FIG. 9 is a block diagram illustrating an example of the structure of a terminal (UE) according to one embodiment of the present disclosure.

[0226] As illustrated in FIG. 9, the terminal of the present disclosure may include a processor (920), a transceiver (900), and a memory (910). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than those described above. Furthermore, the processor (920), the transceiver (900), and the memory (910) may be implemented in the form of a single chip.

[0227] According to one embodiment of the present disclosure, a processor (920) can control a series of processes that allow a terminal to operate according to the above-described embodiment of the present disclosure. For example, the processor (920) can control the components of the terminal to perform a user plane-based service discovery method according to the above-described embodiments. The processor (920) can control the components of the terminal so that the above-described embodiments of the present disclosure are performed by executing a program stored in memory (910). Additionally, the processor (920) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0228] According to one embodiment of the present disclosure, the transceiver (900) may transmit and receive signals with a network entity, another terminal, or a base station. The signals transmitted and received with the network entity, another terminal, or a base station may include control information and data. The transceiver (900) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (900), and the components of the transceiver (900) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (900) may receive a signal through a wireless channel and output it to a processor (920), and transmit the signal output from the processor (920) through a wireless channel.

[0229] According to one embodiment of the present disclosure, the memory (910) may store programs and data necessary for the operation of the terminal. Additionally, the memory (910) may store control information or data included in signals transmitted and received by the terminal. The memory (910) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, CD-ROM, and DVD. Additionally, the memory (910) may be a plurality of. Additionally, according to one embodiment, the memory (910) may store a program for performing the aforementioned user plane-based service discovery method.

[0230] FIG. 10 is a block diagram illustrating an example of the structure of a base station according to one embodiment of the present disclosure.

[0231] As illustrated in FIG. 10, the terminal of the present disclosure may include a processor (1020), a transceiver (1000), and a memory (1010). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. In addition, the processor (1020), the transceiver (1000), and the memory (1010) may be implemented in the form of a single chip.

[0232] According to one embodiment of the present disclosure, a processor (1020) can control a series of processes that allow a terminal to operate according to the above-described embodiment of the present disclosure. For example, the processor (1020) can control the components of the terminal to perform a user plane-based service discovery method according to the above-described embodiments. The processor (1020) can control the components of the terminal so that the above-described embodiments of the present disclosure are performed by executing a program stored in memory (1010). Additionally, the processor (1020) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0233] According to one embodiment of the present disclosure, the transceiver (1000) can transmit and receive signals with a network entity, another base station, or a terminal. The signals transmitted and received with the network entity, another base station, or a terminal may include control information and data. The transceiver (1000) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (1000), and the components of the transceiver (1000) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1000) may receive a signal through a wireless channel and output it to a processor (1020), and transmit the signal output from the processor (1020) through a wireless channel.

[0234] According to one embodiment of the present disclosure, the memory (1010) may store programs and data necessary for the operation of the terminal. Additionally, the memory (1010) may store control information or data included in signals transmitted and received by the terminal. The memory (1010) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (1010) may be a plurality of. Additionally, according to one embodiment, the memory (1010) may store a program for performing the aforementioned user plane-based service discovery method.

[0235] FIG. 11 is a block diagram illustrating an example of the structure of a network entity according to one embodiment of the present disclosure.

[0236] As illustrated in FIG. 11, the network entity of the present disclosure may include a processor (1120), a transceiver (1100), and a memory (1110). However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more components or fewer components than the components described above. Furthermore, the processor (1120), the transceiver (1100), and the memory (1110) may be implemented in the form of a single chip. Additionally, according to one embodiment of the present disclosure, the network entity may refer to a network function (NF), and the NF may include a RAN, AMF, PCF, UDM, AF, NEF, and UTM, etc.

[0237] According to one embodiment of the present disclosure, a processor (1120) can control a series of processes in which an NF can operate according to the above-described embodiment of the present disclosure. For example, the processor (1120) can control the components of a network entity to perform a user plane-based service discovery method according to the above-described embodiments. The processor (1120) can control the components of a terminal to perform the above-described embodiments of the present disclosure by executing a program stored in memory (1110). Additionally, the processor (920) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0238] According to one embodiment of the present disclosure, the transceiver (1100) may transmit and receive signals with another network entity, base station, or terminal. The signals transmitted and received with another network entity or terminal may include control information and data. The transceiver (900) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (1100), and the components of the transceiver (1100) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1100) may receive a signal through a wireless channel and output it to a processor (1120), and transmit the signal output from the processor (1120) through a wireless channel.

[0239] According to one embodiment of the present disclosure, the memory (1110) may store programs and data necessary for the operation of a network entity. Additionally, the memory (1110) may store control information or data included in signals transmitted and received by the network entity. The memory (1110) 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, there may be multiple memory (1110). Additionally, according to one embodiment, the memory (1110) may store a program for performing the aforementioned user plane-based service discovery method.

[0240] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission and reception methods, and exemplary diagrams of operation procedures illustrated in FIGS. 1 to 11 are not intended to limit the scope of the embodiments of the present disclosure. That is, all components, entities, or steps of operation described in FIGS. 1 to 11 should not be interpreted as essential components for implementing the disclosure, and may be implemented to the extent that the essence of the disclosure is not compromised even if only some components are included.

[0241] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading the program code stored in the memory device by a processor or a CPU (Central Processing Unit) and executing it.

[0242] The entities or various components of terminal devices and modules described in this disclosure 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.

[0243] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0244] 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 claims or embodiments described in the specification of this disclosure.

[0245] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in a memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0246] Additionally, the program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, LAN (local area network), WAN (wide area network), or SAN (storage area network), 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.

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

[0248] 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 a first network entity in a wireless communication system, A step of receiving an association request from a UE (user equipment) that includes an association identifier (ID) for a first service; Responding to the receipt of the above association request, and the key (K) for the above association ID and service plane. SP Based on ), encryption key (K SPenc ) or integrity protection key(K SPint A step of generating at least one of ); A step of transmitting an association response to the above UE; and The above encryption key (K SPenc ) or integrity protection key(K SPint A method characterized by including the step of transmitting and receiving a message related to the first service to the UE using at least one of the following.

2. In Paragraph 1, A key identifier (KID) for an AnF (anchor function) key or an eAUSF (authentication server function) key, or a random value (RAND) generated by the UE UE The step of transmitting a key acquisition request, including at least one of ), to a second network entity for performing authentication; and In response to the above key acquisition request, the K from the above second network entity SP The method further includes the step of receiving a key acquisition response including; and The above association request is the above KID or RAND UE A method characterized by including at least one of the following.

3. In Paragraph 1, The method further includes the step of receiving a key provisioning response from a second network entity for authentication before receiving the association request. The above key provisioning response is the K generated based on the above association ID. SP A method characterized by including 4. In Paragraph 3, The above K SP RAND included in the key provisioning request UE A method characterized by being generated by 5. In Paragraph 1, Based on an identifier representing an encryption or integrity protection algorithm, the encryption key (K SPenc ) or integrity protection key(K SPint It further includes a step of generating ), A method characterized in that an identifier representing the encryption or integrity protection algorithm is selected by the first network entity or the network entity providing the mobility management function.

6. In Paragraph 1, Based on an identifier representing an encryption or integrity protection algorithm, the encryption key (K SPenc ) or integrity protection key(K SPint It further includes a step of generating ), A method characterized in that an identifier representing the encryption or integrity protection algorithm is included in the association request or the association response.

7. In paragraph 1, the first network entity is, A method characterized by being one of a network entity that provides a service or a network entity that provides a user plane connection management function.

8. In paragraph 1, the first network entity is, A method characterized by being one of a network entity providing mobility management functions, a network entity providing session management functions, a network entity providing policy control functions, a network entity providing AI / ML services, and a network entity providing sensing services.

9. In a method performed by a UE (user equipment) in a wireless communication system, Key (K) for the service plane based on the association identifier (ID) for the first service SP Step of generating ); A step of transmitting an association request including the association ID to a first network entity; In response to receiving the association request, the step of receiving an association response from the first network entity; and Key (K) for the above association ID and service plane SP Encryption key (K) based on ) SPenc ) or integrity protection key(K SPint A method characterized by including the step of transmitting and receiving a first network entity and a first service-related message using at least one of the following:

10. In Paragraph 9, A key identifier (KID) for an AnF (anchor function) key or an eAUSF (authentication server function) key, or a random value (RAND) generated by the UE UE It further includes the step of generating at least one of ), The above association request is the above KID or RAND UE A method characterized by including at least one of the following.

11. In Paragraph 9, Based on an identifier representing an encryption or integrity protection algorithm, the encryption key (K SPenc ) or integrity protection key(K SPint It further includes a step of generating ), A method characterized in that an identifier representing the encryption or integrity protection algorithm is included in the association request or the association response.

12. In Paragraph 9, Based on an encryption or integrity protection algorithm based on a count value corresponding to the first network entity, the encryption key (K SPenc ) or integrity protection key(K SPint A method characterized by further including the step of generating at least one of ).

13. In Paragraph 12, A method characterized in that an identifier representing the encryption or integrity protection algorithm is included in the association request or the association response.

14. In a first network entity in a wireless communication system, Transmitter / receiver; and It includes at least one processor; and the at least one processor, Receive an association request from a UE (user equipment) containing an association identifier (ID) for a first service, and Responding to the receipt of the above association request, and the key (K) for the above association ID and service plane. SP Based on ), encryption key (K SPenc ) or integrity protection key(K SPint Generate at least one of ), and Sending an association response to the above UE, and The above encryption key (K SPenc ) or integrity protection key(K SPint A first network entity characterized by being configured to transmit and receive messages related to the first service with the UE using at least one of the following.

15. 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, Key (K) for the service plane based on the association identifier (ID) for the first service SP Create ) and, Transmit an association request including the association ID to the first network entity, and In response to receiving the above association request, receive an association response from the first network entity, and Key (K) for the above association ID and service plane SP Encryption key (K) based on ) SPenc ) or integrity protection key(K SPint A UE characterized by being configured to transmit and receive messages related to the first service with the first network entity using at least one of the following:

Images