Method and apparatus for providing external id of terminal in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transfer rates. According to embodiments of the present disclosure, a method, performed by a network exposure function (NEF), for providing an external ID of a terminal in a wireless communication system comprises the steps of: receiving, from an application function (AF), a first message requesting an external ID of a terminal; transmitting, to a unified data management (UDM), a second message requesting the external ID of the terminal; in response to the second message, receiving, from the UDM, a third message including the external ID of the terminal; and in response to the first message, transmitting, to the AF, a fourth message including the external ID of the terminal, wherein the first message includes an Internet protocol (IP) address of the terminal, and the second message includes a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the terminal.

Description

Method and device for providing an external ID of a terminal in a communication system

[0001] The present disclosure relates to a method and device for providing an external ID of a terminal to an external party in a 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) 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 satisfy performance requirements for ultra-wideband services (eMBB: enhanced Mobile Broadband), ultra-reliable / ultra-low-latency communications (URLLC: Ultra-Reliable Low-Latency Communications), and massive Machine-Type Communications (mMTC), including 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 codes for reliable transmission of control information, L2 pre-processing, and specific services. Standardization has been progressed for network slicing, which provides specialized, dedicated networks.

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

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (IIoT: Industrial Internet of Things) 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. Standardization is also in progress for system architecture / services such as 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.

[0006] When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, which will require enhanced functions and performance of 5G mobile communication systems and integrated operation of 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 antennas, and large scale antennas, 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, and AI (Artificial Intelligence) from the design stage and internalize end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources to realize services with complexity that exceeds the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies.

[0008] The present disclosure provides a method and device in a wireless communication system in which an external server can request an external ID of a terminal from a network and provide the external server with the external ID.

[0009] The technical problems to be achieved in the present invention 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 present invention belongs from the description below.

[0010] In addition, according to an embodiment of the present disclosure, a method for providing an external ID of a terminal, performed by a network exposure function (NEF) in a wireless communication system, includes the steps of receiving a first message requesting an external ID of the terminal from an application function (AF), transmitting a second message requesting the external ID of the terminal to a unified data management (UDM), receiving a third message including the external ID of the terminal in response to the second message from the UDM, and transmitting a fourth message including the external ID of the terminal in response to the first message to the AF, wherein the first message includes an internet protocol (IP) address of the terminal, and the second message may include a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the terminal.

[0011] According to an embodiment of the present disclosure, a method for providing an external ID of a terminal, performed by an application function (AF) in a wireless communication system, includes the steps of transmitting a first message requesting an external ID of the terminal to a network exposure function (NEF) and receiving a second message including an external ID of the terminal in response to the first message from the NEF, wherein the first message includes an internet protocol (IP) address of the terminal, the external ID of the terminal included in the second message is obtained based on the IP address of the terminal, and the external ID of the terminal can be received from a unified data management (UDM).

[0012] According to one embodiment of the present disclosure, in a wireless communication system providing an external ID of a terminal, a network exposure function (NEF) entity includes a transceiver and a processor, wherein the processor is configured to receive a first message requesting an external ID of the terminal from an application function (AF) entity, transmit a second message requesting the external ID of the terminal to a unified data management (UDM) entity, receive a third message including the external ID of the terminal in response to the second message from the UDM entity, and transmit a fourth message including the external ID of the terminal to the AF entity in response to the first message, wherein the first message includes an internet protocol (IP) address of the terminal, and the second message may include a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the terminal.

[0013] According to one embodiment of the present disclosure, in a wireless communication system providing an external ID of a terminal, an application function (AF) entity includes a transceiver and a processor, wherein the processor is configured to transmit a first message requesting an external ID of the terminal to a network exposure function (NEF) entity, and receive a second message including an external ID of the terminal from the NEF entity in response to the first message, wherein the first message includes an internet protocol (IP) address of the terminal, and the external ID of the terminal included in the second message is obtained based on the IP address of the terminal, and the external ID of the terminal can be received from a unified data management (UDM).

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

[0015] FIG. 2 is a diagram illustrating a procedure in which an AF requests and receives an External UE ID, which is an external ID of a terminal, through an NEF of 5GC in a DN of an external network according to one embodiment of the present disclosure.

[0016] FIG. 3 is a diagram illustrating a procedure in which an AF requests and receives an MSISDN, which is an external ID of a terminal, through an NEF of 5GC from an external network DN according to one embodiment of the present disclosure.

[0017] FIG. 4 is a diagram illustrating a procedure in which an AF requests and receives an AF specific UE ID and / or MSISDN, which is an external ID of a terminal, from a DN of an external network through an NEF of 5GC according to one embodiment of the present disclosure.

[0018] FIG. 5 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0019] FIG. 6 is a diagram illustrating a configuration of a base station or network entity according to an embodiment of the present disclosure.

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

[0021] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0022] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0023] The advantages and features of the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0024] Furthermore, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below 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 content throughout this specification.

[0025] 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, the downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although LTE, LTE-A, or 5G systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, this may include the fifth-generation mobile communication technology (5G, new radio, NR) developed after LTE-A. The term "5G" below may also encompass existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

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

[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] Here, the term '~ unit' used in the present embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to regenerate 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, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' 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 (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (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 Orthogonal Frequency Division Multiplexing (OFDM) method in the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (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 the perspective of 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 transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0033] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond the reach of cells. Therefore, they may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0034] Finally, URLLC refers to cellular-based wireless communication services used for specific 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, services supporting URLLC 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] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

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

[0039] 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 entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

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

[0041] FIG. 1 is a diagram showing an example of a configuration of a wireless communication system according to an embodiment of the present disclosure, and FIG. 1 exemplifies the configuration of a 5G system.

[0042] Referring to FIG. 1, a 5G network may include at least one of the network entities (NE) or network functions (NF) described below.

[0043] (R)AN ((Radio) Access Network) (101) is an entity that performs radio resource allocation of a terminal (100), 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 wireless access unit, a base station controller, or a node on a network.

[0044] The terminal (100) may include a UE (User Equipment), NG UE (Next Generation UE), MS (Mobile Station), cellular phone, smartphone, computer, IoT (Internet of Things) device, or multimedia system capable of performing a communication function.

[0045] Furthermore, while the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0046] 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 being 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.

[0047] According to one embodiment of the present disclosure, 5GC may include NFs illustrated in FIG. 1. In FIG. 1, 5GC may include network entities such as a User Plane Function (UPF) (102), an Authentication Server Function (AUSF) (104), an Access and Mobility Management Function (AMF) (105), a Session Management Function (SMF) (106), a Service Communication Proxy (SCP) (107), a Network Slice Selection Policy (NSSF) (108), a Network Exposure Function (NEF) (109), a Network Repository Function (NRF) (110), a Policy Control Function (PCF) (111), a Unified Data Management (UDM) (112), and an Application Function (AF) (113). In addition, UPF (102) may communicate with a data network (DN) (103), which is an external network such as the Internet, using a Nupf service. DN (103) may include AF of external network. For example, AF may exist as AF (113) within 5GC and AF included in DN (103) outside 5GC, and AF may be AF that communicates with UPF (102) in DN (103) outside 5GC. Description of entities among the above network entities that are not directly related to the present disclosure will be omitted for convenience. Of course, 5GC is not limited to the example of FIG. 1, and 5GC may include more or fewer NFs than NF illustrated in FIG. 1.

[0048] AMF (105) may be a network function that manages access and mobility of a terminal (UE) (100). For example, AMF (105) may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0049] The SMF (106) may be a network function that manages a Packet Data Network (PDN) connection provided to a user equipment (UE) (100). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF (106) may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining a tunnel between the UPF (102) and the RAN (101) required therefor, selecting and controlling a user plane (UP: User Plane), controlling traffic processing in the UPF (102), and controlling collection of charging data.

[0050] PCF (111) may be a network function that applies a mobile communication service provider's service policy, charging policy, and policy for PDU Session to the terminal (100).

[0051] The UDM (112) may be a network function that stores information about subscribers. For example, the UDM (112) may perform functions such as generating authentication information for 3GPP security, processing user identifiers (User IDs), managing a list of network functions supporting the terminal (100), and managing subscription information.

[0052] NEF (109) may have a function of providing information about the terminal (100) to a server outside the 5G network. In addition, NEF (109) may provide a function of providing information necessary for service to the 5G network and storing it in a Unified Data Repository (UDR) (not shown).

[0053] The UPF (102) may be a gateway that transmits user data (PDU) to the DN (103). More specifically, the UPF (102) may perform a data processing function so that data transmitted by the terminal (100) can be transmitted to an external network or data received from an external network can be transmitted to the terminal (100). For example, the UPF (102) 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.

[0054] NRF (110) can store the profiles of NFs and perform the function of discovering NFs.

[0055] AUSF (104) can perform terminal authentication in 3GPP access networks and non-3GPP access networks.

[0056] NSSF (108) can perform the function of selecting a Network Slice Instance provided to the terminal (100).

[0057] The Network Data Analytics Function (NWDAF) collects data from multiple NFs (Network Functions) to ensure efficient operation of the 5GC network. This data is analyzed using a machine learning (ML) model, and the results are provided back to the NFs, helping them provide efficient network services.

[0058] AF (113) can communicate with the operator network so that an external server (Application Server) can use the network service provided by the operator network. AF (113) can be divided into internal AF and external AF depending on the deployment entity. Internal AF deployed by the network operator can directly communicate with NFs within the operator network. AF (113) deployed by a service provider (3rd party service provider) must go through NEF (109) to communicate with NFs within the operator network.

[0059] DN (103) may be a data network through which a terminal (100) transmits and receives data in order to use a network operator's service or a third party service.

[0060] The terminal (100) 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 is referred to as an ambient IoT device (or simply Ambient IoT).

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

[0062] - N1: Reference point between UE (100) and AMF (105)

[0063] - N2: Reference point between (R)AN(101) and AMF(105)

[0064] - N3: Reference point between (R)AN(101) and UPF(102)

[0065] - N4: Reference point between SMF (106) and UPF (102)

[0066] - N5: Reference point between PCF (111) and AF (113)

[0067] - N6: Reference point between UPF (102) and DN (103)

[0068] - N7: Reference point between SMF (106) and PCF (111)

[0069] - N8: Reference point between UDM (112) and AMF (105)

[0070] - N9: Reference point between two core UPFs (102)

[0071] - N10: Reference point between UDM (112) and SMF (106)

[0072] - N11: Reference point between AMF (105) and SMF (106)

[0073] - N12: Reference point between AMF (105) and AUSF (104)

[0074] - N13: Reference point between UDM (112) and AUSF (104)

[0075] - N14: Reference point between two AMFs (105)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] According to one embodiment of the present disclosure, a network device or network function located inside or outside a 5G Core Network is proposed to request and obtain an MSISDN (Mobile Station International Subscriber Directory Number), which is an external ID of a terminal.

[0092] A terminal can be assigned a SUPI (Subscription Permanent Identifier), which is an ID used within the network, and a GPSI (Generic Public Subscription Identifier), which is an ID used outside the network. A terminal can be assigned an External UE ID (e.g., an AF-specific UE ID) and an MSISDN using the GPSI, which is an external ID.

[0093] External devices or servers (e.g., AF) can use GPSI to identify a specific terminal when making requests to the network regarding the terminal. For example, GPSI can be used to monitor the terminal's location or to measure the Round Trip Time (RTT) of data transmitted to the terminal. In this case, the external server may not receive the terminal's external ID from the network. Since the external server is transmitting and receiving data with the terminal, the only information it knows about the terminal is the terminal's IP address and associated port number.

[0094] In this disclosure, a method is proposed in which an external server can request and receive an MSISDN, which is an external ID of a terminal, from a network using the terminal's IP address and port number.

[0095] FIG. 2 illustrates a procedure in which an AF requests and receives an External UE ID, which is an external ID of a terminal, through an NEF of 5GC in a DN of an external network according to one embodiment of the present disclosure.

[0096] The basic function of each NF in Fig. 2 can be referred to the description in Fig. 1.

[0097] Referring to FIG. 2, in step 201, the AF (210) transmits an Nnef_UEID_Get request message to the NEF (220) to request a UE ID. The Nnef_UEID_Get request message may include an address of the UE (an IP (internet protocol) address or a MAC (media access control) address) and an AF ID. The Nnef_UEID_Get request message may further include at least one of a port number, Machine Type Communication Provider Information (MTC provider information), an application port ID, an IP domain, a DNN (Data Network Name), and S-NSSAI (Single-Network Slice Selection Assistance Information). Additionally, the AF (210) may further include a UE ID type value in the Nnef_UEID_Get request message to indicate the type of external ID of the requested terminal (UE). In one embodiment, the UE ID type may be set to External UE ID.

[0098] In step 202, NEF (220) can authorize the request of AF (210) in step 201. If AF (210) has the authority, NEF (220) can authorize the request of AF (210) and perform the request. If authorization of AF (210) fails in NEF (220), NEF (220) sends authorization failure message to AF (210) and the request is not performed. NEF (220) determines DNN and S-NSSAI corresponding to the request of AF (210). The information of DNN and S-NSSAI may be provided from AF (210) or may be determined using AF ID and MTC Provider Information included in Nnef_UEID_Get request message. If the Port Number is received from the AF (210) in the above step 201, the NEF (220) can recognize that the IP address of the UE provided by the AF (210) is not a private IP address allocated by 5GC.

[0099] In step 202, if NEF (220) recognizes that the IP address of the UE provided by AF (210) is not a private IP address allocated by 5GC (i.e., if it recognizes that it is a public IP address), it performs operations from step 203 to step 206, and if it recognizes that the IP address of the UE provided by AF (210) is a private IP address, the operations from step 203 to step 206 may be omitted. The operations from step 203 to step 206 will be described below.

[0100] In step 203, NEF (220) can obtain the IP address of UPF (250) through NRF (240) using Nnrf_NFDiscovery service operation. Here, UPF (250) is a UPF that changes the private IP address of UE into a public IP address using NAT (Network Address Translation) equipment. The Nnrf_NFDiscovery request message transmitted from NEF (220) to NRF (240) in step 203 can include the public IP address of UE. In addition, Nnrf_NFDiscovery request message can include IP domain, DNN, and S-NSSAI associated with AF ID.

[0101] In step 204, in response to receiving the Nnrf_NFDiscovery request message, the NRF (240) provides the IP address of the UPF (250) that includes or embodies the NAT that changed the private IP address of the UE to a public IP address through the Nnrf_NFDiscovery response message to the NEF (220).

[0102] In step 205, the NEF (220) that has acquired the IP address of the UPF (250) requests the private IP address of the UE from the UPF (250) using the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get service operation. The Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message may include the public IP address and port number of the UE. In addition, the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message may further include at least one of the IP domain, DNN, and S-NSSAI associated with the AF ID.

[0103] In step 206, the UPF (250) transmits a Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message to the NEF (220) in response to receiving the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message. The Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message includes the private IP address of the UE and may optionally further include an IP domain. Since the UPF (250) knows the private IP address of the UE converted using the NAT function to the public IP address of the UE, the UPF (250) can provide the private IP address of the UE to the NEF (220). If the UPF (250) has the SUPI (Subscription Permanent Identifier) ​​or GPSI (e.g., MSISDN Number) information of the UE, the UPF (250) can transmit the SUPI or GPSI (e.g., MSISDN) information to the NEF (220). In this case, steps 207 and 208 may be omitted.

[0104] In steps 207 and 208, the NEF (220) requests the BSF (Binding Support Function) (230) for session binding information of the UE using the Nbsf_Management_Discovery service operation. The Nbsf_Management_Discovery request message transmitted by the NEF (220) to the BSF (230) in step 207 may include at least one of the IP address, IP domain, DNN, and S-NSSAI of the UE. If the session binding information provided from the BSF (230) does not include the SUPI information of the UE, the NEF (220) may transmit a response message including a result value indicating that the ID provision of the UE is not available to the AF (210).

[0105] In step 209, the NEF (220) that has received the session binding information of the UE can request the AF specific UE Identifier (i.e., External UE ID) from the UDM (260) that manages the subscription information of the UE using the Nudm_SDM_Get service operation (i.e., Nudm_SDM_Get request message). The Nudm_SDM_Get request message that the NEF (220) transmits to the UDM (260) in step 209 includes the SUPI or GPSI (MSISDN) of the UE and may further include at least one of the Application Port ID, MTC Provider Information, and AF Identifier.

[0106] In step 211, UDM (260) may transmit a Nudm_SDM_Get response message to NEF (220) in response to the Nudm_SDM_Get request message. In step 211, UDM (260) may provide the AF specific UE Identifier (i.e., External UE ID) requested by AF (210) through the Nudm_SDM_Get response message.

[0107] At step 212, NEF (220) can provide AF (210) with AF specific UE Identifier (i.e., External UE ID) provided from UDM (260).

[0108] Among the above-described procedures, in step 209, the NEF (220) provides the GPSI (MSISDN) to the UDM (260) using the Nudm_SDM_Get request message (i.e., Nudm_SDM_Get service operation) transmitted to the UDM (260), and the UDM (260) can obtain the SUPI value of the UE by performing an identifier translation procedure using the received GPSI information. The UDM (260) can search for the External UE ID value using the SUPI value and the AF ID value and transmit the value to the NEF (220) via the Nudm_SDM_Get response message.

[0109] FIG. 3 illustrates a procedure in which an AF requests and receives an MSISDN, which is an external ID of a terminal, through an NEF of 5GC from an external network DN according to one embodiment of the present disclosure.

[0110] The basic function of each NF in Fig. 3 can be referred to the description in Fig. 1.

[0111] Referring to FIG. 3, in step 301, the AF (310) transmits an Nnef_UEID_Get request message to the NEF (320) to request a UE ID. The Nnef_UEID_Get request message includes an address (IP address or MAC address) of the UE and an AF ID. The Nnef_UEID_Get request message may further include at least one of a Port Number, MTC Provider Information, an Application Port ID, an IP domain, a DNN, and an S-NSSAI. Additionally, the AF (310) may further include a UE ID type value in the Nnef_UEID_Get request message to indicate the type of external ID of the requesting UE. In one embodiment, the UE ID type may be set to MSISDN.

[0112] In step 302, NEF (320) can approve the request of AF (310) in step 301. If AF (310) is authorized, NEF (320) can approve the request of AF (310) and perform the request. If approval of AF (310) fails in NEF (320), NEF (320) sends an approval failure message to AF (310) and the request is not performed. NEF (320) determines the DNN and S-NSSAI corresponding to the request of AF (310). The information of DNN and S-NSSAI may be provided by AF (310) or may be determined using AF ID and MTC Provider Information included in Nnef_UEID_Get request message. If the Port Number is received from the AF (310) in the above step 301, the NEF (320) can recognize that the IP address of the UE provided by the AF (310) is not a private IP address allocated by 5GC.

[0113] In step 302, if NEF (320) recognizes that the IP address of the UE provided by AF (310) is not a private IP address allocated by 5GC (i.e., if it recognizes that it is a public IP address), it performs operations from step 303 to step 306. If it recognizes that the IP address of the UE provided by AF (310) is a private IP address, operations from step 303 to step 306 may be omitted. The operations from step 303 to step 306 will be described below.

[0114] In step 303, NEF (320) can obtain the IP address of UPF (350) through NRF (340) using Nnrf_NFDiscovery service operation. Here, UPF (350) is a UPF that changes the private IP address of UE into a public IP address using NAT equipment. The Nnrf_NFDiscovery request message transmitted from NEF (320) to NRF (340) in step 303 can include the public IP address of UE. In addition, Nnrf_NFDiscovery request message can include IP domain, DNN, and S-NSSAI associated with AF ID.

[0115] In step 304, in response to receiving the Nnrf_NFDiscovery request message, the NRF (340) provides the NEF (320) with the IP address of the UPF (250) that includes or embodies the NAT that changed the private IP address of the UE to a public IP address through the Nnrf_NFDiscovery response message.

[0116] In step 305, the NEF (320) that obtained the IP address of the UPF (350) requests the private IP address of the UE from the UPF (350) using the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get service operation. The Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message may include the public IP address and port number of the UE. In addition, the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message may include the IP domain, DNN, and S-NSSAI associated with the AF ID.

[0117] In step 306, the UPF (350) transmits a Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message to the NEF (320) in response to receiving the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message. The Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message includes the private IP address of the UE and may optionally further include an IP domain. Since the UPF (350) knows the private IP address of the UE converted to the public IP address of the UE using the NAT function, the UPF (350) can provide the private IP address of the UE to the NEF (320). If the UPF (350) has SUPI or GPSI (e.g., MSISDN Number) information of the UE, the UPF (350) can transmit the SUPI or GPSI (e.g., MSISDN) information to the NEF (320). If UPF (350) transmits SUPI, steps 307 and 308 may be omitted. If UPF (350) transmits GPSI (e.g., MSISDN), steps 307 to 311 may be omitted.

[0118] In steps 307 and 308, the NEF (320) requests the BSF (330) for session binding information of the UE using the Nbsf_Management_Discovery service operation. The Nbsf_Management_Discovery request message transmitted by the NEF (320) to the BSF (330) in step 307 may include at least one of the IP address, IP domain, DNN, and S-NSSAI of the UE. If the session binding information provided from the BSF (330) does not include the SUPI information of the UE, the NEF (320) may transmit a response message including a result value indicating that the ID provision of the UE is not available to the AF (310).

[0119] In step 309, the NEF (320) that has received the session binding information of the UE can request the MSISDN of the UE from the UDM (360) that manages the subscription information of the UE using the Nudm_SDM_Get service operation (i.e., Nudm_SDM_Get request message). The Nudm_SDM_Get request message that the NEF (320) transmits to the UDM (360) in step 309 includes the SUPI of the UE and may further include at least one of the Application Port ID, MTC Provider Information, and AF Identifier.

[0120] In step 311, UDM (360) may transmit a Nudm_SDM_Get response message to NEF (320) in response to the Nudm_SDM_Get request message. In step 311, UDM (360) may provide the MSISDN of the UE requested by AF (310) through the Nudm_SDM_Get response message.

[0121] In step 312, NEF (320) may provide the MSISDN of the UE provided from UDM (360) or UPF (350) to AF (310).

[0122] Among the above-described procedures, in step 309, NEF (320) provides the SUPI to UDM (360) using the Nudm_SDM_Get request message (i.e., Nudm_SDM_Get service operation) transmitted to UDM (360), and UDM (360) can obtain the MSISDN value of the UE by performing an identifier translation procedure using the received SUPI information. UDM (360) can transmit the MSISDN value of the UE to NEF (320) via Nudm_SDM_Get response message.

[0123] FIG. 4 illustrates a procedure in which an AF requests and receives an AF specific UE ID and / or MSISDN, which is an external ID of a terminal, from a DN of an external network through an NEF of a 5GC according to one embodiment of the present disclosure.

[0124] The basic function of each NF in Fig. 4 can be referred to the description in Fig. 1.

[0125] Referring to FIG. 4, in step 401, the AF (410) transmits an Nnef_UEID_Get request message to the NEF (420) to request a UE ID. The Nnef_UEID_Get request message includes an address (IP address or MAC address) of the UE and an AF ID. The Nnef_UEID_Get request message may further include at least one of a Port Number, MTC Provider Information, an Application Port ID, an IP domain, a DNN, and an S-NSSAI. Additionally, the AF (410) may further include a UE ID type value in the Nnef_UEID_Get request message to indicate the type of external ID of the requesting UE. In one embodiment, the UE ID type may be set to one of an AF specific UE ID and MSISDN or an AF specific UE ID and an MSISDN.

[0126] In step 402, NEF (420) can approve the request of AF (410) in step 401. If AF (410) is authorized, NEF (420) can approve the request of AF (410) and perform the request. If approval of AF (310) in NEF (420) fails, NEF (420) sends an approval failure message to AF (410) and the request is not performed. NEF (420) determines the DNN and S-NSSAI corresponding to the request of AF (410). The information of DNN and S-NSSAI may be provided by AF (410) or may be determined using AF ID and MTC Provider Information included in Nnef_UEID_Get request message. If the Port Number is received from AF (410) in the above step 401, NEF (420) can recognize that the IP address of the UE provided by AF (410) is not a private IP address allocated by 5GC.

[0127] In step 402, if NEF (420) recognizes that the IP address of the UE provided by AF (410) is not a private IP address allocated by 5GC (i.e., if it recognizes that it is a public IP address), it performs operations from step 403 to step 406. If it recognizes that the IP address of the UE provided by AF (410) is a private IP address, operations from step 403 to step 406 may be omitted. The operations from step 403 to step 406 will be described below.

[0128] In step 403, NEF (420) can obtain the IP address of UPF (450) through NRF (440) using Nnrf_NFDiscovery service operation. Here, UPF (450) is a UPF that changes the private IP address of UE into a public IP address using NAT equipment. The Nnrf_NFDiscovery request message transmitted from NEF (420) to NRF (440) in step 403 can include the public IP address of UE. In addition, Nnrf_NFDiscovery request message can include IP domain, DNN, and S-NSSAI associated with AF ID.

[0129] In step 404, in response to receiving the Nnrf_NFDiscovery request message, the NRF (440) provides the IP address of the UPF (450) that includes or embodies the NAT that changed the private IP address of the UE to a public IP address through the Nnrf_NFDiscovery response message to the NEF (420).

[0130] In step 405, the NEF (420) that obtained the IP address of the UPF (450) requests the private IP address of the UE from the UPF (450) using the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get service operation. The Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message may include the public IP address and port number of the UE. In addition, the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message may include the IP domain, DNN, and S-NSSAI associated with the AF ID.

[0131] In step 406, UP (450)F sends Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message to NEF (420) in response to receiving Nupf_GetUEPrivateIPaddrAndIdentifiers_Get request message. The Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message includes the private IP address of the UE and may optionally further include an IP domain. Since UPF (450) knows the private IP address of the UE converted using NAT function to the public IP address of the UE, UPF (450) can provide the private IP address of the UE to NEF (420). If AF (410) requests AF specific UE ID and UPF (450) has SUPI or MSISDN information of the UE, UPF (450) can send SUPI or MSISDN information to NEF (420). If UPF (450) transmits SUPI or MSISDN, steps 407 and 408 may be omitted.

[0132] If AF (410) requests MSISDN and UPF (450) has SUPI information of UE, UPF (450) can transmit SUPI information to NEF (420). If UPF (450) transmits SUPI, steps 407 and 408 can be omitted.

[0133] If AF (410) requests MSISDN and UPF (450) has MSISDN information of UE, UPF (450) can transmit MSISDN information to NEF (420). If UPF (450) transmits MSISDN, steps 407 to 411 can be omitted. In steps 407 and 408, NEF (420) requests session binding information of UE from BSF (430) using Nbsf_Management_Discovery service operation. In step 407, Nbsf_Management_Discovery request message transmitted by NEF (420) to BSF (430) can include at least one of IP address, IP domain, DNN, and S-NSSAI of UE. If the session binding information provided from the BSF (430) does not include the SUPI information of the UE, the NEF (420) can send a response message to the AF (410) including a result value indicating that the provision of the ID of the UE is not available.

[0134] In step 409, the NEF (420) that has received the session binding information of the UE can request the GPSI (AF specific UE ID or MSISDN) of the UE from the UDM (460) that manages the subscription information of the UE using the Nudm_SDM_Get service operation (i.e., Nudm_SDM_Get request message). The Nudm_SDM_Get request message that the NEF (420) transmits to the UDM (460) in step 409 includes the SUPI of the UE and may further include at least one of the Application Port ID, MTC Provider Information, and AF Identifier.

[0135] In step 411, UDM (460) may transmit a Nudm_SDM_Get response message to NEF (420) in response to the Nudm_SDM_Get request message. In step 411, UDM (460) may provide GPSI of the UE requested by AF (410) through the Nudm_SDM_Get response message.

[0136] At step 412, NEF (420) may provide the GPSI of the UE received from UDM (460) or UPF (450) to AF (410).

[0137] Among the above-described procedures, in step 409, NEF (420) provides the SUPI to UDM (460) using the Nudm_SDM_Get request message (i.e., Nudm_SDM_Get service operation) transmitted to UDM (460), and UDM (460) can obtain the GPSI value of the UE by performing an identifier translation procedure using the received SUPI information. UDM (460) can transmit the GPSI value of the UE to NEF (420) via Nudm_SDM_Get response message.

[0138] FIG. 5 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0139] A terminal according to one embodiment of the present disclosure may include a processor (501) that controls the overall operation of the terminal, a transceiver (503) including a transmitter and a receiver, and a memory (505). Of course, the present invention is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 5.

[0140] According to one embodiment of the present disclosure, the transceiver (503) can transmit and receive signals with network entities or other terminals. The signals transmitted and received with the network entities may include at least one of control information and data. In addition, the transceiver (503) can receive signals via a wireless channel, output them to the processor (501), and transmit the signals output from the processor (501) via the wireless channel.

[0141] According to one embodiment of the present disclosure, the processor (501) can control the operation of the terminal to perform at least one operation among the embodiments of FIGS. 2 to 4 described above. Meanwhile, the processor (501), the memory (505), and the transceiver (503) 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 (501) and the transceiver (503) can be electrically connected. In addition, the processor (501) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0142] According to one embodiment of the present disclosure, the memory (505) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (505) provides the stored data upon request of the processor (501). The memory (505) 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 (505). In addition, the processor (501) can perform at least one of the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (505).

[0143] FIG. 6 is a diagram illustrating the configuration of a base station or network entity according to an embodiment of the present disclosure.

[0144] A network entity according to one embodiment of the present disclosure may include a processor (601) that controls the overall operation of the network entity, a transceiver (603) including a transmitter and a receiver, and a memory (605). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 6.

[0145] According to one embodiment of the present disclosure, the transceiver (603) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of other network entities or terminals may include at least one of control information and data. When the network entity of FIG. 6 is a base station, the transceiver (603) may include a transceiver for transmitting and receiving wireless signals with the terminal, and a transceiver or communication interface for transmitting and receiving signals with other network entities in the core network.

[0146] According to one embodiment of the present disclosure, the processor (601) can control the operation of a network entity to perform at least one operation among the embodiments of FIGS. 2 to 4 described above. Meanwhile, the processor (601), the memory (605), and the transceiver (603) 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 (601) and the transceiver (603) can be electrically connected. In addition, the processor (601) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0147] According to one embodiment of the present disclosure, the memory (605) can store data such as basic programs, application programs, and setting information for the operation of the network entity. In particular, the memory (605) provides the stored data upon request of the processor (601). The memory (605) 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 (605). In addition, the processor (601) can perform at least one of the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (605).

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

[0149] 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).

[0150] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0151] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0152] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may include multiple copies.

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

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

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

[0156] 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 for providing an external ID of a terminal, performed by a network exposure function (NEF) in a wireless communication system, A step of receiving a first message requesting an external ID of a terminal from an AF (application function); A step of transmitting a second message requesting an external ID of the terminal using UDM (unified data management); A step of receiving a third message including an external ID of the terminal in response to the second message from the UDM; and A step of transmitting a fourth message including an external ID of the terminal in response to the first message using the AF, The first message includes the IP (internet protocol) address of the terminal, and A method wherein the second message includes a SUPI (subscription permanent identifier) or GPSI (generic public subscription identifier) of the terminal.

2. In paragraph 1, The above first message further includes information indicating the ID type of the terminal, A method in which information indicating the ID type of the above terminal is set as an external UE ID (external user equipment identifier) or MSISDN (mobile station international subscriber directory number).

3. In paragraph 1, A method wherein the third message further includes MSISDN (mobile station international subscriber directory number) information of the terminal.

4. In paragraph 1, A method wherein the fourth message further includes MSISDN (mobile station international subscriber directory number) information of the terminal.

5. A method for providing an external ID of a terminal, performed by an AF (application function) in a wireless communication system, A step of transmitting a first message requesting an external ID of a terminal to NEF (network exposure function); and A step of receiving a second message including an external ID of the terminal in response to the first message from the NEF; The above first message includes the IP (internet protocol) address of the terminal, The external ID of the terminal included in the second message is obtained based on the IP address of the terminal, and The external ID of the above terminal is received from UDM (unified data management).

6. In paragraph 5, The above first message further includes information indicating the ID type of the terminal, A method in which information indicating the ID type of the above terminal is set as an external UE ID (external user equipment identifier) or MSISDN (mobile station international subscriber directory number).

7. In paragraph 5, The above first message further includes information indicating the ID type of the terminal, A method in which information indicating the ID type of the above terminal is set to an AF specific UE ID (application function specific user equipment identifier) or MSISDN (mobile station international subscriber directory number).

8. In paragraph 5, A method wherein the second message further includes MSISDN (mobile station international subscriber directory number) information of the terminal.

9. In a wireless communication system, for the NEF (network exposure function) entity, Transmitter and receiver; and A processor; comprising: a processor configured to receive a first message requesting an external ID of a terminal from an AF (application function) entity; A second message requesting the external ID of the terminal is sent to the UDM (unified data management) entity, Receive a third message including the external ID of the terminal in response to the second message from the UDM entity, and configured to transmit a fourth message including the external ID of the terminal in response to the first message to the AF entity; The first message includes the IP (internet protocol) address of the terminal, and The second message is an NEF entity that includes the SUPI (subscription permanent identifier) or GPSI (generic public subscription identifier) of the terminal.

10. In paragraph 9, The above first message further includes information indicating the ID type of the terminal, Information indicating the ID type of the above terminal is set to an external UE ID (external user equipment identifier) or MSISDN (mobile station international subscriber directory number), NEF entity.

11. In paragraph 9, The third message further includes the MSISDN (mobile station international subscriber directory number) information of the terminal, NEF entity.

12. In paragraph 9, The fourth message further includes the MSISDN (mobile station international subscriber directory number) information of the terminal, NEF entity.

13. In the AF (application function) entity in a wireless communication system, Transmitter and receiver; and A processor; comprising: Sends a first message requesting the external ID of the terminal to the NEF (network exposure function) entity, and configured to receive a second message including the external ID of the terminal in response to the first message from the NEF entity; The above first message includes the IP (internet protocol) address of the terminal, The external ID of the terminal included in the second message is obtained based on the IP address of the terminal, and The external ID of the above terminal is an AF entity received from UDM (unified data management).

14. In paragraph 13, The above first message further includes information indicating the ID type of the terminal, Information indicating the ID type of the above terminal is set to an external UE ID (external user equipment identifier) or MSISDN (mobile station international subscriber directory number), AF entity.

15. In paragraph 13, The above first message further includes information indicating the ID type of the terminal, Information indicating the ID type of the above terminal is set to an AF entity, such as an AF specific UE ID (application function specific user equipment identifier) or MSISDN (mobile station international subscriber directory number).

Images