Method and device for registering terminal in network by using user identifier in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to an embodiment of the present disclosure, a method performed by an AMF entity in a wireless communication system may comprise the steps of: receiving, from a base station, a registration request message for initial registration with a UI; transmitting a target UI to a data storage entity; receiving, from the data storage entity, user profile information associated with the target UI; and transmitting, to an SMF entity, a message for requesting the activation of a PDU session associated with the target UI.

Description

Method and device for registering a terminal to a network using a user identifier in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for registering a terminal to a network using a user identifier in a wireless communication system.

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

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

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

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

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

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

[0008] In one embodiment of the present disclosure, a method performed by an access and mobility management function (AMF) entity in a wireless communication system includes the steps of receiving a registration request message for initial registration with a user identifier (UI) from a base station, transmitting the target UI to a data storage entity, receiving, from the data storage entity, user profile information associated with the target UI, and transmitting, to a session management function (SMF) entity, a message requesting activation of a PDU session associated with the target UI, wherein the registration request message may include at least one of information about a target UI associated with a user equipment (UE) or at least one protocol data unit (PDU) session associated with the target UI.

[0009] In one embodiment of the present disclosure, a network entity in a wireless communication system includes a transceiver and at least one processor connected to the transceiver, wherein the at least one processor receives a registration request message for initial registration with a UI from a base station, transmits the target UI to a data storage entity, receives user profile information associated with the target UI from the data storage entity, and transmits a message requesting activation of a PDU session associated with the target UI to an SMF entity, wherein the registration request message may include at least one of information on a target UI associated with a UE or at least one PDU session associated with the target UI.

[0010] FIG. 1 is a diagram showing an example of the structure of a wireless communication system according to one embodiment of the present disclosure.

[0011] FIG. 2 is a diagram illustrating an example of a user identifier and a user profile according to one embodiment of the present disclosure.

[0012] FIG. 3A is a diagram illustrating an example of a network registration procedure of a terminal providing a user identifier according to one embodiment of the present disclosure.

[0013] FIG. 3b is a diagram illustrating an example of a network registration procedure of a terminal providing a user identifier according to one embodiment of the present disclosure.

[0014] FIG. 4 is a diagram illustrating an example of a user profile update procedure according to one embodiment of the present disclosure.

[0015] FIG. 5 is a diagram illustrating a procedure for setting a user policy based on a user profile according to one embodiment of the present disclosure.

[0016] FIG. 6 is a drawing showing an example of a configuration of a terminal according to one embodiment of the present disclosure.

[0017] FIG. 7 is a diagram illustrating an example of a configuration of a base station or network entity according to one embodiment of the present disclosure.

[0018] FIG. 8 is a flowchart illustrating an example of a method performed by a network entity according to one embodiment of the present disclosure.

[0019] Hereinafter, one or more embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the accompanying drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

[0020] In describing one or more embodiments of the present disclosure, descriptions of technical details that are well known in the technical field to which the present disclosure pertains or are not directly related to the present disclosure may be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanation.

[0021] For the same reason, at least some components in the attached drawings may be exaggerated, omitted, or schematically depicted. Furthermore, the sizes of at least some components depicted in the attached drawings may not entirely reflect their actual sizes. Identical or corresponding components in the attached drawings may be assigned the same reference numbers.

[0022] The effects, advantages, and features of the present disclosure, and methods for achieving them, will become clearer with reference to one or more embodiments described in detail below, together with the accompanying drawings. However, the present disclosure is not limited to the embodiments described below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure may be defined by the scope of the claims. In this disclosure, the same reference numerals may refer to the same components.

[0023] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations may be omitted if they are determined to unnecessarily obscure the gist of the present disclosure. Terms used in this disclosure are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of the present disclosure.

[0024] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

[0025] In addition, although one or more embodiments of the present disclosure may be described below using LTE (Long Term Evolution), LTE-A (LTE-Advanced), or 5G (5th-generation) systems as examples, one or more embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, the fifth-generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0026] It will be appreciated that each block of the flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, such that the instructions, when executed by the processor of the computer or other programmable data processing equipment, create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to perform the functions in a specific manner, such that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0027] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0028] The term '~ unit' used in this disclosure means a software or hardware component such as a Field-Programmable Gate Array (FPGA) or an Application-Specific Integrated Circuit (ASIC), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. Furthermore, in an embodiment, the '~part' may include one or more processors.

[0029] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-A, LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0030] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink. The uplink refers to a wireless link in which a terminal (UE or MS) transmits data or control signals to a base station (eNode B, gNode B, or BS), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0031] As a future communication system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable Low Latency Communication (URLLC).

[0032] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by utilizing a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz bands.

[0033] In 5G communication systems, mMTC is being considered to support application services such as the Internet of Things (IoT). To efficiently provide the Internet of Things, mMTC requires supporting large-scale terminal connection within a cell, improving terminal coverage, extending battery life, and reducing terminal costs. The Internet of Things provides communication functions by attaching various sensors and various devices, so a large number of terminals (e.g., 1,000,000 terminals / km) are required within a cell. 2 ) must be able to support. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements of buildings, due to the nature of the service, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be composed of low-cost terminals, and because it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

[0034] URLLC is a cellular-based wireless communication service used for mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and design requirements may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0035] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0036] In this disclosure, phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used merely to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0037] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of Fig. 1 may each mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ... in the drawings, represent known interfaces between NFs in a 5G core network (CN), and since a related description may refer to the standard specification (TS 23.501), a detailed description will be omitted.

[0038] In the following description, terms used to identify connection nodes, terms referring to network entities (NEs) or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0039] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0040] In one embodiment of the present disclosure, a method and device for registering a terminal with a network using a user identifier in a wireless communication system may be provided. In one embodiment of the present disclosure, a method and device for providing user-based quality of service (QoS) in a communication system may be provided. One embodiment of the present disclosure relates to a method and device for providing quality of service (QoS) based on a user ID and user profile for providing customized network services in a wireless communication system.

[0041] FIG. 1 is a diagram illustrating an example of the structure of a wireless communication system according to one embodiment of the present disclosure. For example, FIG. 1 may illustrate an example of the structure of a 5G communication system.

[0042] Referring to FIG. 1, a 5G network may include at least one of the following network entities (NEs) or network functions (NFs):

[0043] (R)AN ((Radio) Access Network) (104) is an entity that performs radio resource allocation of a terminal (UE) (102), and may be at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0044] The terminal (102) may include a UE, NG UE (Next Generation UE), MS, cellular phone, smartphone, computer, IoT device, or multimedia system capable of performing a communication function.

[0045] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation Core (NG Core) or 5GC (5G Core Network) is defined. This new core network virtualizes all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0046] According to one embodiment of the present disclosure, 5GC may include NFs as illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the number of NFs illustrated in FIG. 1.

[0047] An Access and Mobility Management Function (AMF) (110) may be a network function that manages access and mobility of a terminal (UE) (102). For example, the AMF (110) may perform network functions such as registration, connection, reachability, mobility management, access confirmation, authentication, and mobility event generation of the terminal (102).

[0048] The SMF (Session Management Function) (116) may be a network function that manages a Packet Data Network (PDN) connection provided to a user equipment (UE). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF (116) may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining a tunnel between the User Plane Function (UPF) (112) and the RAN (104) required for this, selection and control of a User Plane (UPF), control of traffic processing in the UPF, and control of collection of charging data.

[0049] PCF (Policy Control Function) (130) may be a network function that applies a mobile communication service provider's service policy, charging policy, and policy for PDU Session to a terminal (102).

[0050] Unified Data Management (UDM) (132) may be a network function that stores subscriber information. For example, UDM (132) may perform functions such as generating authentication information for 3GPP security, processing user identifiers, managing a list of network functions supporting UEs, and managing subscription information.

[0051] The Network Exposure Function (NEF) (126) may be a function that provides information about the terminal (102) to a server located outside the 5G network (e.g., DN (114)). In addition, the NEF (126) may provide a function that provides information necessary for service to the 5G network and stores it in the Unified Data Repository (UDR).

[0052] The UPF (User Plane Function) (112) may be a function that performs a gateway role for transmitting user data (PDU) to the DN (Data Network) (114). More specifically, the UPF (112) may perform a role for processing data so that data transmitted by the terminal (102) can be transmitted to an external network (e.g., DN (114)) or data received from an external network (e.g., DN (114)) can be transmitted to the terminal (102). For example, the UPF (112) may perform network functions such as serving as an anchor between Radio Access Technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report creation, and buffering.

[0053] NRF (Network Repository Function) (128) can store the profiles of NFs and perform the function of discovering NFs.

[0054] AUSF (Authentication Server Function) (108) can perform terminal authentication in 3GPP access networks and non-3GPP access networks.

[0055] NSSF (Network Slice Selection Function) (124) can perform a function of selecting a network slice instance provided to a terminal (102).

[0056] NWDAF (Network Data Analytics Function) (122) can collect data from multiple NF(s) for the purpose of efficient operation of the 5GC network. For example, NWDAF (122) can analyze the collected data using a machine learning (ML) model and provide the analyzed results back to the NFs to help each NF provide efficient network services.

[0057] The AF (Application Function) (134) can communicate with the operator network so that an external server (e.g., Application Server) can utilize the network services provided by the operator network. The AF (134) can be divided into an internal AF and an external AF depending on the deployment entity. An internal AF deployed by a network operator can directly communicate with NFs within the operator network. An AF (134) deployed by a service provider (e.g., a 3rd party service provider) may need to go through an NEF (126) to communicate with NFs within the operator network.

[0058] EASDF (Edge Application Server Discovery Function) (136) can discover the IP (internet protocol) address of the relevant EAS (edge ​​application server) for the edge application.

[0059] NSSAAF (Network Slice-Specific Authentication and Authorization Function) (106) can enable management security for a network slice, UE authentication for accessing a network slice, management security for a network slice, UE authentication for accessing a network slice, confidentiality and integrity protection of a network slice identifier, and network slice-specific network function (NF) authorization.

[0060] SCP (service communication proxy) (118) can enable dynamic scaling and management of communications and services in 5G networks.

[0061] NSACF (Network slice admission control function) (120) can manage network resources by limiting the number of PDU sessions of registered UEs in each network slice.

[0062] DN (Data Network) (114) may be a data network that transmits and receives data with a terminal (102) to use a network operator's service or a third party service.

[0063] The terminal (102) may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such an IoT device may be referred to as an ambient IoT device (or simply Ambient IoT).

[0064] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following illustrates a reference point included in the 5G system architecture depicted in Figure 1.

[0065] - N1: Reference point between UE and AMF

[0066] - N2: Reference point between (R)AN and AMF

[0067] - N3: Reference point between (R)AN and UPF

[0068] - N4: Reference point between SMF and UPF

[0069] - N5: Reference point between PCF and AF

[0070] - N6: Reference point between UPF and DN

[0071] - N7: Reference point between SMF and PCF

[0072] - N8: Reference point between UDM and AMF

[0073] - N9: Reference point between two core UPFs

[0074] - N10: Reference point between UDM and SMF

[0075] - N11: Reference point between AMF and SMF

[0076] - N12: Reference point between AMF and AUSF

[0077] - N13: Reference points between UDM and AUSF

[0078] - N14: Reference point between two AMFs

[0079] Additionally, in 3GPP systems, the 5G system architecture may include service-based interfaces such as the following examples.

[0080] - Nnssf: Service-based interface by NSSF

[0081] - Nnssaaf: Service-based interface by NSSAAF (Network Slice-Specific Authentication and Authorization Function)

[0082] - Nnef: Service-based interface by NEF

[0083] - Nausf: Service-based interface by AUSF

[0084] - Nnrf: Service-based interface by NRF

[0085] - Namf: Service-based interface by AMF

[0086] - Npcf: Service-based interface by PCF

[0087] - Nsmf: Service-based interface by SMF

[0088] - Nupf: Service-based interface by UPF

[0089] - Nudm: Service-based interface by UDM

[0090] - Naf: Service-based interface by AF

[0091] - Nasaf: Service-based interface by AUSF

[0092] - Neasdf: Service-based interface by EASDF (Edge Application Server Discovery Function)

[0093] - Nnwdaf: Service-based interface by NWDAF

[0094] According to one embodiment of the present disclosure, mobile communication service providers may use a user identifier (UI) that identifies an actual user using a terminal to provide a network service customized to the actual user of the terminal (e.g., UE) (102). This is because the terminal subscriber and the user who actually uses the terminal may be different, and when mobile communication service providers provide a user-customized service based on terminal subscriber information, the provided service may differ from the service desired by the user who is actually using the terminal. Accordingly, in one embodiment of the present disclosure, mobile communication service providers may additionally store a user profile (UI) including information on a user who actually uses the terminal in the network, and provide a user identifier (ID) of a user currently using the terminal to the network, thereby providing a user-customized network service to the actual terminal user based on the user profile information identified by the user ID. In one embodiment of the present disclosure, the network may store a user profile including information on a user who actually uses the terminal, and may provide a user-customized network service to the actual user based on the user profile (e.g., user profile information) identified by the user ID by using the user ID of the user currently using the terminal.

[0095] In one embodiment of the present disclosure, to provide the above-described actual terminal user-customized service to a user, user profile information including terminal user information may be provided in addition to existing subscriber information. In one embodiment of the present disclosure, to provide the above-described actual terminal user-customized service to a user, a method and device for network registration of a terminal may be provided based on user profile information including terminal user information in addition to existing subscriber information.

[0096] FIG. 2 is a diagram illustrating an example of a user identifier and a user profile according to one embodiment of the present disclosure.

[0097] Scenarios using a user ID can broadly include, but are not limited to, two scenarios. The first scenario can include a case where a single terminal (e.g., terminal (202)) is used by multiple human users (e.g., user 1 (212), user 2 (214), and user 3 (216)). The second scenario can include a case where multiple devices (e.g., device 1 (206) and device 2 (208)) are connected to a single terminal (e.g., terminal (204)). In the first scenario, terminal (202) can include various devices such as not only a mobile phone but also a car, a TV, and a public computer. The first and second scenarios can be combined. For example, a scenario using a user ID can include a case where multiple devices are connected to a single terminal used by multiple human users. Terminal (202) and terminal (204) can be subscribed to a network (e.g., a 5GC (5G core) system (220)).

[0098] Referring to FIG. 2, in one embodiment of the present disclosure, when User 1 (212) uses the terminal (202), the subscriber (e.g., subscriber) of the terminal (202) may not be User 1 (212). For example, the subscriber of the terminal (202) may be the father (e.g., User 2 (214)) or mother (e.g., User 3 (216)) of User 1 (212). In this case, subscriber information (e.g., Subscription Data (222)) based on the subscriber name may include preference information that is different from the preferences of User 1 (212) who is currently using the terminal (202).

[0099] Accordingly, a subscriber-based customized network service may be significantly different from the network service desired by User 1 (212), who is currently using the terminal (202). If a customized network service is provided based on existing subscriber information, a significant gap may arise between the network service desired by User 1 (212), who is a current terminal user, and the network service provided. For example, the services mainly used by subscribers (e.g., User 2 (214) or User 3 (216)) may be Internet surfing and office-related applications, while the services mainly used by User 1 (212) may be games.

[0100] To overcome the limitations of the above-described subscriber information-based personalized network service, in one embodiment of the present disclosure, a user ID and user profile-based actual terminal user personalized network service can be provided. To this end, a network (e.g., a 5GC system (220)) can store not only subscriber information but also user profile information (e.g., user profile 1 (224), user profile 2 (226), and user profile 3 (228)), which is information of one or more users (e.g., user 1 (212), user 2 (212), and user 3 (216)) using a terminal (e.g., terminal (202)).

[0101] In one embodiment of the present disclosure, a user ID capable of distinguishing a user currently using a terminal is provided to the network in addition to the subscriber ID, so that the network can be set to be optimized for a service preferred by the current terminal user based on subscriber information and a user profile. In one embodiment of the present disclosure, the network (e.g., 5GC system (220)) can set a network configuration (e.g., NFs) to be optimized for a service preferred by the current terminal user (e.g., user 1 (212)) based on subscriber information (e.g., subscription data (222)) and user profiles (e.g., user profile 1 (224), user profile 2 (226), and user profile 3 (228)) by additionally using a user ID capable of distinguishing a user currently using a terminal (e.g., terminal (202)).

[0102] Referring to FIG. 2, in one embodiment of the present disclosure, when a user 1 (212), who is a child, uses a terminal (202), network settings may be set to be optimized for a game service preferred by the user 1 with reference to a user profile including subscriber information and information of the user 1. In one embodiment of the present disclosure, when the user 1 (212) uses a terminal (202), the network may set network settings to be related to a service (e.g., a game service) and / or user characteristics (e.g., an age limit) preferred by the user 1 (212) with reference to subscriber information (e.g., subscription data (222)) and a user profile (e.g., user profile 1 (224)) including user information of the user 1 (212).

[0103] Table 1 may illustrate an example of AM (Access and Mobility Management) information among user profile information for providing terminal user-tailored services. Table 1 may illustrate an example of AM information among user profiles for providing terminal user-tailored services according to one embodiment of the present disclosure. A user profile (e.g., User Profile_AM) may include one or more of the fields listed in Table 1.

[0104] Table 1: AM User Profile Information

[0105]

[0106] For example, Table 1 may represent profile information including user AM-related information among user profiles. For example, User Profile_AM is user profile data including user AM-related information among user profiles.

[0107] A User Identifier may be an ID that identifies which user the user profile is about.

[0108] Security Credentials can be values ​​used for user authentication / authorization when a user registers on a network.

[0109] UI-AMBR can represent AMBR (Aggregate Maximum Bit Rate) per user.

[0110] UI-Slice-MBR(s) can represent user-specific Slice-MBR(s).

[0111] UI-Subscribed S-NSSAIs can represent single Network Slice Selection Assistance Information (S-NSSAIs) subscribed per user.

[0112] Slice Usage Policy information can display policy information regarding the Slice subscribed to by each user.

[0113] S-NSSAIs subject to Network Slice-Specific Authentication and Authorization may include information for Authentication / Authorization when using a subscribed Slice for each user.

[0114] Network Slice validity time information may include validity time information regarding the subscribed Slice for each user.

[0115] UI-Charging Characteristics may include information about the charges for a specific user when using a network service, as the network services provided to each user may differ.

[0116] UI-PCF Selection Assistance info may include information regarding PCF selection for each user. UI-PCF Selection Assistance info may include information regarding PCF selection for each user, as PCF selection may vary for each user due to different QoS (quality of service) for providing customized services for each user. The information regarding PCF selection for each user may be used for PCF selection for each user to provide customized services for each user due to different QoS for each user.

[0117] The list of associated SUPI(s) may include a list of subscriber IDs (i.e., SUPI (Subscription Permanent Identifier)) of terminals registered as a user when the user is a user of multiple terminals registered with the same network operator.

[0118] The list of associated PEI(s) may include a list of terminal IDs (i.e. PEI (Permanent Equipment Identifier)) of terminals registered as a user when the user is a user of multiple terminals registered with the same network operator.

[0119] Table 2 may illustrate an example of SM (Session Management) information among user profile information for providing terminal user-tailored services. Table 2 may illustrate an example of SM information among user profile information for providing terminal user-tailored services according to one embodiment of the present disclosure. A user profile (e.g., User Profile_SM) may include one or more of the fields listed in Table 2.

[0120] Table 2: SM User Profile Information

[0121]

[0122] For example, Fig. 2 may represent profile information including SM-related information of a user among user profiles. For example, User Profile_SM is user profile data including SM-related information of a user among user profiles.

[0123] A User Identifier may be an ID that identifies which user the user profile is about.

[0124] The Subscribed DNN list can be a list of DNNs subscribed to by S-NSSAI per user.

[0125] UI-Slice Usage Policy information can display policy information about the Slice subscribed to by each user.

[0126] UI-Subscribed QoS Profile can contain per-user subscribed QoS profiles.

[0127] UI-Charging Characteristics may include information about the charges for a specific user when using a network service, as the network services provided to each user may differ.

[0128] UI-Session-AMBR can represent user-specific Session-AMBR.

[0129] UI-Secondary authentication indication can indicate whether Secondary Authentication is required for access to the subscribed DNN for each user.

[0130] The AF-AAA Server UE IP address allocation indication can indicate whether a UE IP address is requested from the AF used by each user.

[0131] AF-AAA Server addressing / credential information may include information for UI-Secondary authentication indication when a user-specific subscribed DNN has one.

[0132] In one embodiment of the present disclosure, user profile information is not limited to the user profile information described above. For example, user profile information may include more information than the information described above, as needed.

[0133] FIG. 3A is a diagram illustrating an example of a network registration procedure for a terminal providing a user identifier according to an embodiment of the present disclosure. FIG. 3B is a diagram illustrating an example of a network registration procedure for a terminal providing a user identifier according to an embodiment of the present disclosure. For example, FIGS. 3A and 3B may illustrate operations in a network registration procedure for a terminal according to an embodiment of the present disclosure, and FIG. 3B may illustrate subsequent operations of the operations illustrated in FIG. 3A.

[0134] 단계 1에서, 단말은 기지국인 (R)AN으로 Registration Request 메시지를 전송할 수 있다. 예를 들어, Registration Request 메시지는 다음의 파라미터들을 포함할 수 있다; AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, User Identifier, Security Credential, [last visited TAI (if available)], Security parameters, [Requested NSSAI], [Mapping Of Requested NSSAI], [Default Configured NSSAI Indication], [UE Radio Capability Update], [UE MM Core Network Capability], [PDU Session status], [List Of PDU Sessions To Be Activated], [Follow-on request], [MICO mode preference], [Requested Active Time], [Requested DRX parameters for E-UTRA and NR], [Requested DRX parameters for NB-IoT], [extended idle mode DRX parameters], [LADN DNN(s) or Indicator Of Requesting LADN Information], [NAS message container], [Support for restriction of use of Enhanced Coverage], [Preferred Network Behaviour], [UE paging probability information], [Paging Subgrouping Support Indication], [UE Policy Container (list of PSIs,indication of UE support for ANDSP, operating system identifier, Indication of URSP Provisioning Support in EPS, UE capability of reporting URSP rule enforcement to network, UE capability of supporting VPLMN-specific URSP rules)] and [UE Radio Capability ID], [Release Request indication], [Paging Restriction Information], PEI, [PLMN with Disaster Condition], [Requested Periodic Update time], [Unavailability Period] Duration], [Start of Unavailability Period], [Unavailability Type])).,

[0135] If (R)AN is NG-RAN, AN (Access Network) parameters may include the following values: 5G-S-TMSI or GUAMI, Selected PLMN ID (or PLMN ID and NID) and NSSAI information, Establishment cause.

[0136] 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​is a form of terminal ID and may be an abbreviated form of 5G-GUTI (5G Globally Unique Temporary Identifier). 5G-S-TMSI may consist of an AMF Set ID, AMF Pointer, and 5G-TMSI and may be used in wireless signaling procedures.

[0137] GUAMI (Globally Unique AMF Identifier) ​​is a type of AMF ID that can identify one or more AMFs. GUAMI can be composed of MCC, MNC, AMF Region ID, AMF Set ID, and AMF Pointer.

[0138] A Public Land Mobile Network (PLMN) ID can be the mobile carrier's ID. It can consist of a Mobile Country Code (MCC) and a Mobile Network Code (MNC).

[0139] A Network Identifier (NID) may be used to identify a Stand-alone Non-Public Network (SNPN). The PLMN ID and NID may be used together to identify the SNPN.

[0140] The values ​​included in NSSAI (Network Slice Selection Assistance Information) Information can be determined by the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter provided by AMF.

[0141] The Establishment Cause value may indicate the purpose for which the terminal requested the creation of an RRC (Radio Resource Control) connection. In one embodiment of the present disclosure, the Establishment Cause value may be set to “Initial Registration with UI.”

[0142] For example, if the terminal is an IAB (Integrated access and backhaul) node connecting to 5GS (5G System), the AN parameter must include IAB-Indication.

[0143] For example, if the terminal is part of a Mobile Base Station Relay (MBSR) node, the AN parameter must include the MBSR Indication.

[0144] The Registration type value may indicate the purpose for which the terminal requests registration. For example, the Registration type value may be set to one of the following values: Initial Registration, Mobility Registration Update, Periodic Registration Update, Emergency Registration, Disaster Roaming Initial Registration, or Disaster Roaming Mobility Registration Update. In one embodiment of the present disclosure, the Registration type value may be set to “Initial Registration with UI.”

[0145] SUCI (Subscription Concealed Identifier) ​​is a form of terminal ID that may include a concealed SUPI (Subscription Permanent Identifier) ​​value to prevent leakage of the SUPI value.

[0146] 5G-GUTI (5G Globally Unique Temporary Identifier) ​​is a type of terminal ID assigned to a terminal by the AMF. 5G-GUTI can be composed of GUAMI and 5G-TMSI.

[0147] The PEI (Permanent Equipment Identifier) ​​can identify the ME (Mobile Equipment). For example, if the terminal supports at least one 3GPP access technology (i.e., NG-RAN, E-UTRAN (Evolved Universal Terrestrial RAN), UTRAN (Universal Terrestrial RAN), or GERAN (GSM (Global System for Mobile Communications) / EDGE (Enhanced Data rates for GSM Evolution) RAN)), the PEI format must be set to IMEI (International Mobile Equipment Identity) or IMEISV (International Mobile Equipment Identity-Software Version).

[0148] The last visited TAI (Tracking Area Identity) can indicate the TAI value the terminal last visited. The AMF can refer to the last visited TAI value when determining the terminal's RA (Registration Area).

[0149] Security parameters values ​​can be used for terminal authentication and integrity protection.

[0150] The Requested NSSAI value may include the S-NSSAI(s) (Single Network Slice Selection Assistance Information) value corresponding to the Network Slice(s) that the terminal wishes to use. The Mapping Of Requested NSSAI value may include the HPLMN (Home Public Land Mobile Network) S-NSSAI value. The Requested NSSAI value may be set to a different value for each user. The Requested NSSAI value for each user must be a subset of the Subscribed S-NSSAI(s) value of the Subscription data.

[0151] When a terminal uses Evolved UTRA (E-UTRA), it can indicate whether it supports Cellular IoT (CIoT) 5GS optimizations. The support indicated by the terminal can influence AMF selection.

[0152] For example, when a terminal performs Initial Registration or Disaster Roaming Registration, the terminal must indicate its identity in the Registration Request message as follows:

[0153] i. If the terminal has a valid EPS (Evolved Packet System) GUTI, the 5G-GUTI mapped to it.

[0154] ii. If available, the native 5G-GUTI allocated by the PLMN with which the terminal is attempting to register.

[0155] iii. If available, the native 5G-GUTI allocated by the equivalent PLMN of the PLMN in which the terminal is attempting to register.

[0156] iv. If available, native 5G-GUTI allocated by another PLMN.

[0157] v. If none of the above is possible, the terminal must include its SUCI in the Registration Request message.

[0158] In one embodiment of the present disclosure, the terminal may include HPLMN Information (HPLMN ID and terminal GPSI (Generic Public Subscription Identifier of HPLMN) values) in the message. In addition, the terminal may include a Follow-on request to inform the network that the terminal will immediately create a PDU Session after registration.

[0159] The User Identifier value can identify the user currently using the terminal. The terminal subscriber can be identified by the SUPI, and the terminal user can be identified by the User Identifier. Since multiple users can use a single terminal, multiple User Identifiers can be associated with a single terminal. A single user can use a terminal for a specified period of time, and traffic generated during that time may be related to that user.

[0160] Security Credentials can be used for terminal user authentication / authorization. When a terminal registers with a registration type set to "Initial Registration with UI" during network registration, this registration type can indicate that a specific user registered with the network is registering the terminal. In this case, Security Credentials can be used to authenticate / authorize this specific user on the network.

[0161] In addition to this, the List Of PDU Sessions To Be Activated, Preferred Network Behavior, and PDU Session status values ​​can also have different values ​​for each user.

[0162] In step 2, if the NG-RAN, which is a base station, indicates an AMF where 5G-S-TMSI or GUAMI is not included in the AN parameters or where these values ​​are invalid, the (R)AN may select an AMF based on the Requested NSSAI. For example, if the Establishment cause value of the AN parameter is set to “Initial Registration with UI,” the NG-RAN may select an AMF that can perform “Initial Registration with UI.” For example, if the AN parameter includes a User Identifier value, the NG-RAN may select an AMF considering the corresponding user.

[0163] In step 3, the NG-RAN may send a Registration Request message to the selected AMF. For example, the Registration Request message may include N2 parameters and LTE-M Indication. The N2 parameters may include the following values: Selected PLMN ID (PLMN ID and NID if NPN), Location Information and Cell Identity of the UE, and UE Context Request.

[0164] In step 4, if the selected AMF is a new AMF, the selected AMF may send a Namf_Communication_UEContextTransfer message to the old AMF. Alternatively or additionally, the selected AMF may send a Nudsf_UnstructuredDataManagement_Query message to the Unstructured Data Storage Function (UDSF).

[0165] In step 5, the selected AMF may receive a Namf_Communication_UEContextTransfer response message from the old AMF. This message may contain the following values: SUPI, UE Context in AMF. Alternatively or additionally, the selected AMF may receive a Nudsf_UnstructuredDataManagement_Query message from the UDSF. This message may contain terminal-related data.

[0166] For example, if the Registration type value of the Registration Request is set to “Initial Registration with UI”, the selected AMF may include the User Identifier value in addition to the UE’s 5G-GUTI value when transmitting the Namf_Communication_UEContextTransfer message or Nudsf_UnstructuredDataManagement_Query. Additionally, the User Context value may be included in the received Namf_Communication_UEContextTransfer response message or Nudsf_UnstructuredDataManagement_Query message.

[0167] In step 6, if the selected AMF does not receive SUCI from the terminal and the old AMF, the selected AMF may send an Identity request message requesting SUCI to the terminal.

[0168] In step 7, the selected AMF can receive an Identity response message containing the terminal SUCI from the terminal.

[0169] In step 8, the selected AMF can perform terminal authentication. The selected AMF can select an AUSF based on the terminal's SUPI or SUCI.

[0170] In step 9, if terminal authentication is required, the selected AMF can request terminal authentication from the AUSF selected in step 8.

[0171] If a terminal NAS security context does not exist, NAS security initiation can be performed.

[0172] The selected AMF can perform NGAP (NG Application Protocol) procedures to provide security context to the 5G-AN. The 5G-AN can store the security context provided by the selected AMF and transmit an acknowledgment thereof to the selected AMF.

[0173] In step 10, the selected AMF may send a Namf_Communication_RegistrationStatusUpdate message to the old AMF. This message may contain the PDU Session ID(s) that are being released due to the Slice that the selected AMF cannot provide.

[0174] In step 11, the selected AMF can send an Identity Request message requesting the PEI of the terminal to the terminal and receive an Identity Response message from the terminal.

[0175] In step 12, the selected AMF may perform N5g-eir_EquipmentIdentityChenk_Get to check the terminal ME Identity with the equipment identity register (EIR).

[0176] In step 13, if necessary, the selected AMF can perform UDM selection based on the terminal SUPI. The UDM can perform UDR instance selection. For example, if the Request type is set to "Initial Registration with UI," the selected AMF can select a UDM based on both the SUPI and the User Identifier.

[0177] In step 14a, if the selected AMF has not yet registered the terminal with UDM, it can register the terminal with UDM by sending the Nudm_UECM_Registration message to UDM. For example, if the Request type is set to “Initial Registration with UI,” the selected AMF can include the User Identifier value in the Nudm_UECM_Registration message when registering the terminal with UDM.

[0178] In step 14b, the selected AMF can retrieve subscriber information (e.g., Access and Mobility Subscription data) of the terminal from the UDM. For example, if the Request type is set to “Initial Registration with UI,” the selected AMF can retrieve not only subscriber information of the terminal but also user profile information. To this end, the selected AMF can additionally set User Profile_AM to the Subscription data type(s) of the Nudm_SDM_Get message. For example, the selected AMF can retrieve all User Profile_AM information of all users associated with the terminal, not just the currently registered user. For example, the selected AMF can set UE Context data based on the subscriber information (Access and Mobility Subscription data) received from the UDM, and can set User Context data based on the current user information (User Profile_AM). For example, whether or not to set User Context data can be performed can be determined depending on the result of the User Authentication / Authorization procedure in step 14x.

[0179] In step 14x, the selected AMF can perform user Authentication / Authorization if the Request type is set to “Initial Registration with UI.” This can be performed based on the User Profile_AM information received from the UDM and the User Identifier and Security Credential received from the terminal.

[0180] In step 14c, the selected AMF can send a Nudm_SDM_Subscribe message to the UDM. For example, if the Request type is set to “Initial Registration with UI”, the selected AMF can additionally set User Profile_AM in the Subscription data type(s) of the Nudm_SDM_Subscribe message and include a User Identifier in the Nudm_SDM_Subscribe message. For example, the selected AMF can indicate to the UDM that it wants to be notified about user profile data updates of all users associated with the terminal as well as the currently registering user.

[0181] At step 14d, old AMF may receive a Nudm_UECM_DeregistrationNotification message from UDM.

[0182] At step 14e, old AMF can send Nudm_SDM_Unsubscribe message to UDM.

[0183] In step 15, the selected AMF can perform PCF selection. For example, if the Request type is set to “Initial Registration with UI,” the selected AMF can select a PCF by referring to the UI-PCF Selection Assistance info information included in the User Profile_AM data.

[0184] In step 16, the selected AMF can perform the PCF and AM Policy Association Establishment / Modification procedure. For example, if the Request type is set to “Initial Registration with UI,” the selected AMF can send the PCF not only the SUPI but also the User Identifier. For example, the selected AMF can send not only subscriber information but also user profile information to the PCF, and can receive not only subscriber-related policy information but also user-related policy information from the PCF.

[0185] In step 17, the selected AMF may send Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext messages to SMF.

[0186] For example, if the List Of PDU Session To Be Activated value is included in the Registration Request message, the selected AMF can activate the User Plane connection(s) of the corresponding PDU Session(s) by sending the Nsmf_PDUSession_UpdateSMContext Request message to the SMF.

[0187] For example, if the PDU Session status indicates that the PDU Session(s) have been released, the selected AMF may request the release of the corresponding PDU Session(s) by sending an Nsmf_PDUSession_ReleaseSMContext Request message to the SMF.

[0188] In step 18, the selected AMF may send a UE Context Modification Request message to N3IWF / TNGF / W-AGF.

[0189] In step 19, the selected AMF may receive a UE Context Modification Response message from N3IWF / TNGF / W-AGF.

[0190] In step 19a, the selected AMF may register by sending a Nudm_UECM_Registration message to the UDM after receiving the UE Context Modification Response message from the N3IWF / TNGF / W-AGF in step 19. At this time, the Access Type may be set to “non-3GPP access.”

[0191] In step 19b, UDM may send a Nudm_UECM_DeregistrationNotify message to old AMF.

[0192] At step 19c, old AMF can send a Nudm_SDM_Unsubscribe message to UDM.

[0193] In step 21, the selected AMF may send a Registration Accept message to the terminal. For example, the Registration Accept message may include the following values: 5G-GUTI, 5G-UserTempID, Registration Area, [Mobility restrictions], [PDU Session status], [Allowed NSSAI], [Mapping Of Allowed NSSAI], [Partially Allowed NSSAI], [Mapping Of Partially Allowed NSSAI], [TAI List for S-NSSAIs in Partially Allowed NSSAI], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI], [NSSRG Information], [NSAG Information], [rejected S-NSSAIs], [TAI List for any rejected S-NSSAI Partially in the RA], [Pending NSSAI], [Mapping Of Pending NSSAI], [Periodic Registration Update timer], [Active Time], [Strictly Periodic Registration Timer Indication], [LADN Information], [MICO Indication], [IMS Voice over PS session supported Indication], [Emergency Service Support indicator], [Accepted DRX parameters for E-UTRA and NR], [Accepted DRX parameters for NB-IoT], [extended idle mode DRX parameters], [Paging Time Window],[Network support of Interworking without N26], [Access Stratum Connection Establishment NSSAI Inclusion Mode], [Network Slicing Subscription Change Indication], [Operator-defined access category definitions], [List of equivalent PLMNs], [Enhanced Coverage Restricted information], [Supported Network Behaviour], [Service Gap Time], [PLMN-assigned UE Radio Capability ID], [PLMN-assigned UE Radio Capability ID deletion], [WUS Assistance Information], [AMF PEIPS Assistance Information], [Truncated 5G-S-TMSI Configuration], [Connection Release Supported], [Paging Cause Indication for Voice Service Supported], [Paging Restriction Supported], [Reject Paging Request Supported], [Paging Restriction Information acceptance / rejection], ["List of PLMN(s) to be used in Disaster Condition"], [Disaster Roaming wait range information], [Disaster Return wait range information], [Forbidden TAI(s)], [List of equivalent SNPNs], [Registered NID], [Unavailability Period Support],[MBSR authorization information], [Return To Coverage Notification Not Required], [Unavailability Period Duration], [Start of Unavailability Period], [S-NSSAI location availability information], [Mapping Of Alternative NSSAI], [Slice Usage Policy], [Maximum Time Offset].,

[0194] 5G-UserTempID may be a temporary ID in the short form of User Identifier. This ID may include GUAMI information among the AMF ID information for routing messages to the Serving AMF.

[0195] For example, if the Registration type is set to “Initial Registration with UI”, the following values ​​can be set to different values ​​for each user: Registration Area, Mobility restrictions, Forbidden TAI(s), Supported Network Behavior, Slice Usage Policy, PDU Session status, Allowed NSSAI, and all related values.

[0196] In addition to the values ​​described above, different values ​​can be set for each user.

[0197] In step 21b, the selected AMF can perform PCF and UE Policy Association Establishment.

[0198] In step 22, the terminal that received the Registration Accept message can transmit a Registration Complete message to the selected AMF.

[0199] In step 23, the selected AMF can send and receive Nudm_SDM_info to UDM.

[0200] In step 23a, when the terminal registers using 3GPP access, if the selected AMF does not release the signaling connection to (R)AN, RRC Inactive Assistance Information can be transmitted to (R)AN.

[0201] At step 24, the selected AMF may send a Nudm_UECM_Update message to UDM.

[0202] In step 25, if the terminal indicates that it can perform Network Slice-Specific Authentication and Authorization in the UE MM (Mobility Management) Core Network Capability and if Network Slice-Specific Authentication and Authorization is required among the requested S-NSSAIs, the selected AMF can initiate the Network slice-specific authentication and authorization procedure.

[0203] FIG. 4 illustrates a user profile update procedure according to one embodiment of the present disclosure. In this embodiment, the user profile may be stored in a UDM (e.g., UDM (132)). In various embodiments, the user profile may be stored in a NF (e.g., UDR) or other storage location other than the UDM (132). For the purpose of describing the user profile update procedure, this embodiment assumes that the user profile is stored in the UDM.

[0204] Referring to FIG. 4, at operation 410, the UDM (132) may decide to update a user profile based on reasons such as, for example, a change in network policy or user subscription information.

[0205] At operation 420, the UDM (132) may notify the terminal (102) (e.g., one or more users) of updated information of the user profile through the AMF (110) / SMF (116) based on a determination that the changed information of the user profile may affect the user. In one embodiment, the user profile may include QoS information for one or more users associated with the terminal (102). For example, the UDM (132) may transmit a notification message (e.g., Nudm_SDM_Notification) including the updated user profile to the AMF (110) / SMF (116). At this time, the UDM (132) may include in the notification message first information requesting an ACK (e.g., ACK of operation 450) from the terminal (102) for receiving the updated information according to the updated information of the user profile and / or second information requesting re-registration and / or re-authentication of the terminal (102) to set the updated information to the network. In operation 430, the AMF (110) / SMF (116) may transmit a message (e.g., Nudm_SDM_Info) indicating that the notification message has been received to the UDM (132).

[0206] At operation 440, the AMF (110) / SMF (116) may transmit to the terminal (102) information of the notification message (e.g., the updated user profile, the first information requesting the ACK, and / or the second information requesting the re-registration and / or re-authentication) in a UPU (UE Parameter Update) container of a DL (downlink) NAS (Non Access Stratum) TRANSPORT message. For example, if the ACK is requested by the first information, at operation 450, the AMF (110) / SMF (116) may receive from the terminal (110) a message (e.g., an UL (uplink) NAS TRANSPORT message) including an ACK (e.g., a UPU ACK) for reception of the NAS TRANSPORT message. At operation 460, the AMF (110) / SMF (116) may forward a message including the UPU ACK (e.g., a Nudm_SDM_Info message) to the UDM (132). At operation 460a, the UDM (132) may send a Nudm_SDM_Notification message to the AMF (110) / SMF (116).

[0207] For example, if the UDM (132) requests re-registration and / or re-authentication to the terminal (102) based on the second information, the terminal (102) may initiate re-registration and / or re-authentication with the same user ID in operation 470. In one embodiment, the terminal (102) may initiate re-registration and / or re-authentication by transmitting a re-registration request message and / or a re-authentication request message to the AMF (110) / SMF (116) or another AMF / SMF. Upon receiving the registration request message and / or the re-authentication request message from the terminal (102), the AMF (110) / SMF (116) may process the re-registration procedure and / or the re-authentication procedure of the terminal (102) with the same user ID. In one embodiment, if a user other than the user corresponding to the updated user profile is using the terminal, re-connection may not be performed.

[0208] FIG. 5 illustrates a procedure for setting a user policy based on a user profile according to one embodiment of the present disclosure.

[0209] Referring to FIG. 5, in operation 510, the AMF (110) may determine to establish an AM Policy Association based on AM information (e.g., User Profile_AM of Table 1) included in a user profile received from the UDM (132). In one embodiment, if UI-PCF Selection Assistance info exists in the AM information, the AMF (110) may select a PCF (e.g., PCF (130)) based on the UI-PCF Selection Assistance info and determine that it is necessary to form an AM Policy Association with the selected PCF (130) in order to receive a user-related AM Policy (e.g., user policy). In one embodiment, the PCF (130) may be a PCF belonging to the same network as the AMF (110), or may be a Visited PCF (V-PCF) belonging to a different network from the AMF (110).

[0210] In operation 520, the AMF (110) may transmit a creation request message (e.g., Npcf_AMPolicyControl Create) to the PCF (130) that additionally includes, in addition to subscriber information, a user profile (e.g., at least one of SUPI, User Identifier, UI-AMBR, or UI-Slice-MBR(s)) or at least one of UI-Allowed NSSAI(s). The PCF (130) may generate a user-related AM policy based on the subscriber information and user profile transmitted by the AMF (110). In operation 530, the PCF (130) may transmit, to the AMF (110), a creation response message (e.g., Npcf_AMPolicyControl_Create response) that includes information of the generated user-related AM policy.

[0211] In operation 540, the AMF (110) may deploy the user-related AM policy. The user-related AM policy may include at least one of Service Area Restriction information, UI-AMBR, or UI-Slice-MBR(s). In one embodiment, the AMF (110) may provide information based on the user policy to at least one NF (e.g., RAN (104) and / or SMF (116)) and / or the terminal (102).

[0212] FIG. 6 is a drawing showing an example of a configuration of a terminal according to one embodiment of the present disclosure.

[0213] A terminal (e.g., terminal (102)) according to one embodiment of the present disclosure may include a processor (620) that controls the overall operation of the terminal, a transceiver (600) including a transmitter and a receiver, and a memory (610). Of course, the present invention is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 6.

[0214] According to one embodiment of the present disclosure, the transceiver (600) can transmit and receive signal(s) with network entities or other terminals. The signal(s) transmitted and received with the network entities can include control information and data. In addition, the transceiver (600) can receive signals via a wireless channel, output them to the processor (620), and transmit the signals output from the processor (620) via the wireless channel.

[0215] According to one embodiment of the present disclosure, the processor (620) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (620), the memory (610), and the transceiver (600) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (620) and the transceiver (600) can be electrically connected. In addition, the processor (620) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0216] According to one embodiment of the present disclosure, the memory (610) can store data such as a basic program for the operation of the terminal, an application program, and setting information. In particular, the memory (610) provides the stored data upon request of the processor (620). The memory (610) can be configured as a storage medium or a combination of storage media such as a read only memory (ROM), a random access memory (RAM), a hard disk, a compact disc ROM (CD-ROM), and a digital video disc (DVD). In addition, there can be a plurality of memories (610). In addition, the processor (620) can perform the above-described embodiments based on a program (e.g., instructions) for performing the above-described embodiments of the present disclosure stored in the memory (610). The instructions, when executed by the processor (620), can cause the terminal to operate according to the above-described embodiments.

[0217] FIG. 7 is a diagram illustrating an example of a configuration of a base station or network entity according to one embodiment of the present disclosure.

[0218] A network entity (e.g., a base station (104), an AMF (110), a UDM (132), or a PCF (130)) according to one embodiment of the present disclosure may include a processor (720) for controlling the overall operation of the network entity, a transceiver (700) including a transmitter and a receiver, and a memory (710). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than the configuration illustrated in FIG. 7.

[0219] According to one embodiment of the present disclosure, the transceiver (700) can transmit and receive signal(s) with at least one of other network entities or terminals. The signal(s) transmitted and received with at least one of other network entities or terminals can include control information and data.

[0220] According to one embodiment of the present disclosure, the processor (720) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (720), memory (710), and transceiver (700) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. Furthermore, the processor (720) and the transceiver (700) may be electrically connected. Furthermore, the processor (720) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0221] According to one embodiment of the present disclosure, the memory (710) can store data such as basic programs, application programs, and setting information for the operation of the network entity. In particular, the memory (710) provides the stored data upon request of the processor (720). The memory (710) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (710). In addition, the processor (720) can perform the above-described embodiments based on a program (e.g., instructions) for performing the above-described embodiments of the present disclosure stored in the memory (710). The instructions, when executed by the processor (720), can cause the network entity to operate according to the above-described embodiments.

[0222] In one embodiment of the present disclosure, at least one processor may receive a registration request message for initial registration with a UI from a base station. In one embodiment of the present disclosure, the registration request message may include at least one of information about a target UI associated with a UE or at least one PDU session associated with the target UI. In one embodiment of the present disclosure, the at least one processor may transmit the target UI to a data storage entity. In one embodiment of the present disclosure, the at least one processor may receive user profile information associated with the target UI from the data storage entity. In one embodiment of the present disclosure, the at least one processor may transmit a message requesting activation of a PDU session associated with the target UI to an SMF entity. In one embodiment of the present disclosure, the data storage entity may include at least one of a UDM entity or a UDR entity.

[0223] In one embodiment of the present disclosure, at least one processor may perform at least one of user authentication or user authorization based on security credentials and user profile information (e.g., user profile information received from a data storage entity) included in a registration request message.

[0224] In one embodiment of the present disclosure, user profile information (e.g., AM related profile information) associated with a target UI may include at least one of security credentials, PCF selection support information, SUPI, or PEI associated with the target UI.

[0225] In one embodiment of the present disclosure, at least one processor may receive information requesting re-registration for a target UI from a UDM entity. In one embodiment of the present disclosure, at least one processor may transmit the information requesting re-registration for the target UI to a UE. In one embodiment of the present disclosure, the UE may initiate re-registration for the target UI based on the information received from a network entity (e.g., an AMF).

[0226] In one embodiment of the present disclosure, at least one processor may receive information requesting re-authentication for a target UI from a UDM entity. In one embodiment of the present disclosure, at least one processor may transmit the information requesting re-authentication for the target UI to a UE. In one embodiment of the present disclosure, the UE may initiate re-authentication for the target UI based on the information received from a network entity (e.g., an AMF).

[0227] In one embodiment of the present disclosure, the UE may receive information requesting at least one of re-registration or re-authentication for the target UI from the UDM entity via the SMF entity. In one embodiment of the present disclosure, the UE may initiate at least one of re-registration or re-authentication for the target UI based on the received information.

[0228] In one embodiment of the present disclosure, an SMF entity may receive SM-related user profile information from a data storage entity (e.g., UDM, UDR, etc.). In one embodiment of the present disclosure, the SM-related user profile information may include at least one of a target UI, quality of service (QoS) profile information associated with the target UI, or charging characteristic information.

[0229] FIG. 8 is a flowchart illustrating an example of a method performed by a network entity according to one embodiment of the present disclosure.

[0230] Referring to FIG. 8, the method (800) includes, but is not limited to, steps 810 to 840. For example, the method (800) may further include steps not illustrated in FIG. 8, or at least some of the steps illustrated in FIG. 8 may be omitted. In one embodiment of the present disclosure, the method of FIG. 8 may be performed by an AMF, but is not limited thereto.

[0231] In step 810, the network entity may receive a registration request message for initial registration with the UI from the base station. In one embodiment of the present disclosure, the network entity may receive the registration request message for initial registration with the UI from the UE through the base station. In one embodiment of the present disclosure, the registration request message may include at least one of information about a target UI associated with the UE or at least one protocol data unit (PDU) session associated with the target UI.

[0232] In step 820, the network entity may transmit the target UI to a data storage entity. In one embodiment of the present disclosure, the data storage entity may include at least one of a UDM entity or a UDR entity.

[0233] In step 830, the network entity may receive user profile information associated with the target UI from the data storage entity. In one embodiment of the present disclosure, the user profile information associated with the target UI may include at least one of security credentials, PCF selection support information, SUPI, or PEI associated with the target UI.

[0234] In one embodiment of the present disclosure, the network entity may perform at least one of user authentication or user authorization based on the security credentials included in the registration request message and the user profile information.

[0235] At step 840, the network entity may send a message to the SMF entity requesting activation of a PDU session associated with the target UI.

[0236] In one embodiment of the present disclosure, a network entity may receive information requesting re-registration for a target UI from a UDM entity. In one embodiment of the present disclosure, the network entity may transmit the information requesting re-registration for the target UI to the UE. In one embodiment of the present disclosure, the UE may initiate re-registration for the target UI based on the information received from the network entity (e.g., AMF).

[0237] In one embodiment of the present disclosure, a network entity may receive information requesting re-authentication for a target UI from a UDM entity. In one embodiment of the present disclosure, the network entity may transmit the information requesting re-authentication for the target UI to a UE. In one embodiment of the present disclosure, the UE may initiate re-authentication for the target UI based on the information received from the network entity (e.g., AMF).

[0238] In one embodiment of the present disclosure, the UE may receive information requesting at least one of re-registration or re-authentication for the target UI from the UDM entity via the SMF entity. In one embodiment of the present disclosure, the UE may initiate at least one of re-registration or re-authentication for the target UI based on the received information.

[0239] In one embodiment of the present disclosure, an SMF entity may receive SM-related user profile information from a data storage entity. In one embodiment of the present disclosure, the SM-related user profile information may include at least one of a target UI, QoS profile information associated with the target UI, or charging characteristic information.

[0240] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

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

[0242] The various components and modules of the entity, base station or terminal device described in the present disclosure may operate using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, 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] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0244] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, non-transitory memory, Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0245] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0246] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0247] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

[0248] The present disclosure may aim to provide a method and device for providing customized network services to users actually using a terminal based on a user ID and user profile in a wireless communication system. The technical challenges to be addressed in this disclosure are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be readily apparent to those skilled in the art.

[0249] The present disclosure provides a method and device capable of providing a customized network service to an actual terminal user by referring to not only subscriber information but also information about a user who is actually using the terminal in order to provide a customized network service to the user in a wireless communication system.

[0250] One or more embodiments of the present disclosure may provide a device and method that can effectively support quality of service (QoS) service in a wireless communication system.

[0251] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the embodiments of the present disclosure belong from the description below.

[0252] The present disclosure provides a method for processing a control signal in a wireless communication system, which may include a step of receiving a first control signal transmitted from a base station, a step of processing the received first control signal, and a step of transmitting a second control signal generated based on the processing to the base station.

[0253] In one embodiment of the present disclosure, a device and method for effectively providing services in a wireless communication system may be provided. The technical effects of one embodiment of the present disclosure are not limited to those described in the present disclosure, and other effects not described in the present disclosure will be readily apparent to those skilled in the art from the detailed description of the present disclosure.

[0254] According to one embodiment of the present disclosure, a method performed by a base station in a wireless communication system includes the steps of receiving a registration request message including at least one user identifier (UI) from a terminal, identifying an Access and Mobility Management Function (AMF) that supports initial registration with UI based on the registration request message, and transmitting a registration request message for the terminal to the AMF, wherein the registration request message may include information indicating initial registration with the user identifier.

[0255] A method performed by an access and mobility management function (AMF) in a communication system according to one embodiment of the present disclosure includes receiving a first message from a network entity including updated information of a user profile associated with a terminal (UE), and transmitting a forwarding message including the updated information of the user profile to the terminal, wherein the user profile may include quality of service (QoS) information for one or more users associated with the terminal.

[0256] In one embodiment of the present disclosure, an AMF in a communication system includes a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to perform an operation of receiving a first message including updated information of a user profile associated with a terminal (UE) from a network entity, and an operation of transmitting a forwarding message including the updated information of the user profile to the terminal, wherein the user profile may include quality of service (QoS) information for one or more users associated with the terminal.

[0257] A method performed by an access and mobility management function (AMF) in a communication system according to one embodiment of the present disclosure includes receiving a first message from a network entity including updated information of a user profile associated with a terminal (UE), and transmitting a forwarding message including the updated information of the user profile to the terminal, wherein the user profile may include quality of service (QoS) information for one or more users associated with the terminal.

[0258] In one embodiment of the present disclosure, an AMF in a communication system includes a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to perform an operation of receiving a first message including updated information of a user profile associated with a terminal (UE) from a network entity, and an operation of transmitting a forwarding message including the updated information of the user profile to the terminal, wherein the user profile may include quality of service (QoS) information for one or more users associated with the terminal.

[0259] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method performed by an AMF (access and mobility management function) entity in a wireless communication system, A step of receiving a registration request message for initial registration with a UI (user identifier) ​​from a base station, wherein the registration request message includes at least one of information about a target UI associated with a UE (user equipment) or at least one protocol data unit (PDU) session associated with the target UI; A step of transmitting the target UI to a data storage entity; A step of receiving user profile information associated with the target UI from the data storage entity; A method comprising the step of transmitting a message requesting activation of a PDU session associated with the target UI to a session management function (SMF) entity.

2. In paragraph 1, A method further comprising the step of performing at least one of user authentication or user authorization based on the security credentials and the user profile information included in the registration request message.

3. In paragraph 1, A method wherein the user profile information associated with the target UI includes at least one of a security credential, a policy control function (PCF) selection support information, a subscription permanent identifier (SUPI), or a permanent equipment identifier (PEI) associated with the target UI.

4. In paragraph 1, A step of receiving information requesting re-registration for the target UI from a UDM (unified data management) entity; and Further comprising a step of transmitting information requesting re-registration for the target UI to the UE, A method in which the UE initiates re-registration for the target UI based on information received from the AMF.

5. In paragraph 1, A step of receiving information requesting re-authentication for the target UI from a UDM (unified data management) entity; and Further comprising a step of transmitting information requesting re-authentication for the target UI to the UE, A method in which the UE initiates re-authentication for the target UI based on information received from the AMF.

6. In paragraph 1, The UE receives information requesting at least one of re-registration or re-authentication for the target UI from a UDM (unified data management) entity through the SMF entity, A method in which the UE initiates at least one of re-registration or re-authentication for the target UI based on the received information.

7. In paragraph 1, The above SMF entity receives SM (session management) related user profile information from the above data storage entity, A method wherein the SM-related user profile information includes at least one of the target UI, QoS (quality of service) profile information associated with the target UI, or billing characteristic information.

8. In a network entity in a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, At least one processor, Receive a registration request message for initial registration with a UI (user identifier) ​​from a base station, wherein the registration request message includes at least one of information about a target UI associated with a UE (user equipment) or at least one protocol data unit (PDU) session associated with the target UI; Send the target UI to the data storage entity, Receive user profile information associated with the target UI from the data storage entity; A network entity that sends a message to a session management function (SMF) entity requesting activation of a PDU session associated with the above target UI.

9. In paragraph 8, At least one processor, A network entity that performs at least one of user authentication or user authorization based on the security credentials and the user profile information included in the registration request message.

10. In paragraph 8, A network entity, wherein the user profile information associated with the target UI includes at least one of security credentials, policy control function (PCF) selection support information, subscription permanent identifier (SUPI), or permanent equipment identifier (PEI) associated with the target UI.

11. In paragraph 8, At least one processor, Receive information requesting re-registration of the target UI from a UDM (unified data management) entity, Transmit information requesting re-registration for the target UI to the UE, A network entity that initiates re-registration for the target UI based on information received from the network entity.

12. In paragraph 8, At least one processor, Receive information requesting re-authentication for the target UI from a UDM (unified data management) entity, Transmit information requesting re-authentication for the target UI to the UE, A network entity that initiates re-authentication for the target UI based on information received from the network entity.

13. In paragraph 8, The UE receives information requesting at least one of re-registration or re-authentication for the target UI from a UDM (unified data management) entity through the SMF entity, A network entity that initiates at least one of re-registration or re-authentication for the target UI based on the received information.

14. In paragraph 8, The above SMF entity receives SM (session management) related user profile information from the above data storage entity, A network entity, wherein the SM-related user profile information includes at least one of the target UI, quality of service (QoS) profile information associated with the target UI, or billing characteristic information.

15. In paragraph 8, The above network entity is a network entity that is an access and mobility management function (AMF) entity.

Images