Method and apparatus for subscribing to network in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for a unified data management (UDM) entity in a wireless communication system, according to an embodiment of the present disclosure, comprises the steps of: receiving a subscription request message for at least one ambient internet of things (IoT) terminal from an application function (AF); storing subscription information of the at least one ambient IoT terminal on the basis of the subscription request message for the at least one ambient IoT terminal; and transmitting a response message to the subscription request message to the AF, wherein the subscription information includes at least one of subscription management subscription information, access and mobility subscription information, and session management subscription information.

Description

Method and device for joining a network in a wireless communication system

[0001] The present disclosure relates to a method and device for joining a network in a wireless communication system, and more particularly, to a method and device for providing a method for joining an ultra-low power device to a network.

[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 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). These include beamforming and massive MIMO (Massive MIMO) to alleviate 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 aims to provide a method for allowing a device that does not use battery power or operates at low power to join a mobile network operator network in a wireless communication system.

[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 a wireless communication system according to one embodiment of the present disclosure, a method of a unified data management (UDM) entity includes the steps of: receiving a subscription request message for at least one ambient IoT (internet of things) terminal from an application function (AF); storing subscription information of the at least one ambient IoT terminal based on the subscription request message for the at least one ambient IoT terminal; and transmitting a response message for the subscription request message to the AF entity; wherein the subscription information includes at least one of subscription management subscription information, access and mobility subscription information, and session management subscription information.

[0011] In a wireless communication system according to one embodiment of the present disclosure, a UDM (unified data management) entity comprises: a transceiver; and at least one processor; wherein the at least one processor is configured to receive a subscription request message for at least one ambient IoT (internet of things) terminal from an AF (application function) entity, store subscription information of the at least one ambient IoT terminal based on the subscription request message for the at least one ambient IoT terminal, and transmit a response message for the subscription request message to the AF entity, wherein the subscription information includes at least one of subscription management subscription information, access and mobility subscription information, and session management subscription information.

[0012] One embodiment of the present invention provides a device and method capable of effectively providing a service in a wireless communication system.

[0013] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

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

[0015] FIG. 2 illustrates an example of a scenario in which an ambient IoT device is used in a communication system according to one embodiment of the present disclosure.

[0016] FIG. 3 illustrates an example configuration of a Device ID (identifier), which is identification information of an Ambient IoT device according to one embodiment of the present disclosure.

[0017] FIG. 4 illustrates a Subscription State Diagram indicating a network subscription status of an Ambient IoT device according to one embodiment of the present disclosure.

[0018] FIG. 5 illustrates an Ambient IoT device subscription procedure according to one embodiment of the present disclosure.

[0019] FIG. 6 illustrates an Ambient IoT device unsubscription procedure according to one embodiment of the present disclosure.

[0020] FIG. 7 illustrates a BSS (Business Support System)-based Ambient IoT device subscription procedure according to one embodiment of the present disclosure.

[0021] FIG. 8 is a diagram illustrating the configuration of a network entity according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0028] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams 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 flow diagram 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 flow diagram 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).

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

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

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

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

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

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

[0035] 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, improved 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, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage 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 comprised of low-cost terminals, and because frequent battery replacement is difficult, they may require extremely long battery lifespans, such as 10 to 15 years.

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

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

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

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

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

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

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

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

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

[0045] (R)AN ((Radio) Access Network) is an entity that performs wireless resource allocation of a terminal, and may be at least one of an eNode B, 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.

[0046] The terminal 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 communication functions.

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

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

[0049] According to one embodiment of the present disclosure, 5GC may include NFs 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 NFs illustrated in FIG. 1.

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

[0051] A Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a user equipment (UE). A PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, an SMF may perform network functions such as session management through the establishment, modification, and release of sessions and the maintenance of tunnels between the User Plane Function (UPF) and the RAN, selection and control of the User Plane (UPF), control of traffic processing in the UPF, and control of charging data collection.

[0052] PCF (Policy Control Function) may be a network function that applies the mobile carrier's service policy, charging policy, and PDU Session policy to the terminal.

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

[0054] The Network Exposure Function (NEF) may provide information about a terminal to a server outside the 5G network. Additionally, NEF may provide the information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0055] The User Plane Function (UPF) may function as a gateway that transmits user data (PDU) to the Data Network (DN). More specifically, the UPF may process data so that it can transmit data transmitted by a terminal to an external network or transmit data received from an external network to the terminal. For example, the UPF 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 generation, and buffering.

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

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

[0058] NSSF (Network Slice Selection Function) can perform the function of selecting a Network Slice Instance provided to a terminal.

[0059] 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 to the NFs, helping them provide efficient network services.

[0060] An Application Function (AF) can communicate with a network operator to enable external servers (Application Servers) to utilize network services provided by the network operator. Depending on the deployment entity, AFs can be categorized as internal AFs and external AFs. Internal AFs deployed by network operators can communicate directly with network functions (NFs) within the network operator. AFs deployed by third-party service providers (3rd-party service providers) must go through an NEF to communicate with NFs within the network operator.

[0061] DN (Data Network) can be a data network where terminals transmit and receive data to use network operator services or third-party services.

[0062] The terminal 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 IoT devices are referred to as ambient IoT devices (or simply Ambient IoT).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] - N14: Reference point between two AMFs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093] According to one embodiment of the present disclosure, an Ambient IoT device is a device that does not have a battery or has very limited energy storage capacity, and also has very limited communication and computing capabilities. Accordingly, the device is very inexpensive, and typically hundreds of thousands to millions of devices are deployed in an area of ​​interest and operate to perform common tasks. The present disclosure proposes an efficient data transmission method for Ambient IoT devices having the above-described characteristics.

[0094] Typically, an Ambient IoT device may have at least one of the following characteristics:

[0095] - Very low power consumption for device operation (e.g. 1-500μW)

[0096] - The device is very cheap (e.g. $0.01-$0.5)

[0097] - Very low data transfer speed (e.g. 10kbps)

[0098] - The number of devices being deployed is very large (e.g., hundreds, thousands, tens of thousands, hundreds of thousands, or more than 1,000,000).

[0099] - It has very low computational power, simple structure, and very small device size.

[0100] - May not include USIM (Universal Subscriber Identity Module)

[0101] - May not include complex communication protocol stacks such as TCP / IP (Transmission Control Protocol / Internet Protocol)

[0102] - It can be deployed mainly in environments that are difficult for people to access, making maintenance after deployment impossible (e.g. high pressure, extremely high / low temperature, humid environment)

[0103] In the present disclosure, Ambient IoT devices can be divided into three types as shown in Table 1, depending on the presence or absence of a battery within the device and the communication method used by the device. The types of Ambient IoT devices in the present disclosure are not limited to the examples in Table 1 below, and it is also possible to distinguish the types of Ambient IoT devices through other criteria.

[0104] Device Type Description Device Type A (TY_A) - No Energy Storage (Battery) - Independent signal generation / amplification not possible Device Type B (TY_B) - With Energy Storage (Battery) - Independent signal generation / amplification not possible Device Type C (TY_C) - With Energy Storage (Battery) - Independent signal generation / amplification possible (including active RF components)

[0105] In addition, in the present disclosure, Ambient IoT devices may have a connection topology classified into four types, as shown in the examples in Table 2 below. The connection types of Ambient IoT devices in the present disclosure are not limited to the examples in Table 2 below, and connections by various combinations of the connection topologies classified into the four types are also possible.

[0106] Connection Topology Types DescriptionTopology 1 (T1) - Connection between base station and Ambient IoT device (Base Station - Ambient IoT device)Topology 2 (T2) - Connection between base station and Ambient IoT device via intermediate node (Base Station - Intermediate node - Ambient IoT device)Topology 3 (T3) - Connection between base stations via auxiliary node and Ambient IoT device (Base Station - Assisting node - Ambient IoT device - Base Station)Topology 4 (T4) - Connection between terminal and Ambient IoT device (UE - Ambient IoT device)

[0107] The traffic types of Ambient IoT devices can also be defined as follows: - Device-Terminated (DT): Traffic type that receives data from the network.

[0108] - Device-Originated-Device-Terminated Triggered (DO-DTT): A traffic type in which data received from the network triggers device data transmission.

[0109] FIG. 2 illustrates an example scenario of using an Ambient IoT device in a communication system according to an embodiment of the present disclosure.

[0110] The communication system of FIG. 2 may include a data network including a plurality of Ambient IoT devices deployed in a mountainous area, at least one base station capable of communicating with at least one of the Ambient IoT devices, a core network to which the at least one base station is connected, and an AF communicably connected to the core network. The basic functions and configuration of the data network including the base station, the core network, and the AF in the example of FIG. 2 may refer to the example of FIG. 1.

[0111] Referring to Figure 2, the Korea Forest Service or the National Fire Agency can deploy millions of Ambient IoT devices into the air over forests for early detection of forest fires. Because the number of Ambient IoT devices and the vast deployment areas are often difficult for humans to access, they are often deployed by air. For the reasons mentioned above, maintenance (e.g., battery replacement, replacement of faulty components, etc.) of deployed Ambient IoT devices may be impossible. Once deployed, Ambient IoT devices must operate and perform their duties for at least 10 years and up to 20 years. Therefore, it is crucial for Ambient IoT devices to operate with minimal battery consumption.

[0112] For example, in the scenario of FIG. 2, the Ambient IoT devices deployed thereafter can monitor a fire around a mountain. At least one Ambient IoT device that detects a fire among the Ambient IoT devices can transmit information notifying the fire to the NG-RAN (in the case of a 5G network) using a wireless network, and the information can be transmitted to an AF (a 3rd party server / provider, for example, a server of the National Fire Agency) via the 5G network and a data network. As in the embodiment of FIG. 2, Ambient IoT devices can be deployed for the same purpose, such as notifying the occurrence of a fire, and the information notifying the occurrence of a fire and / or data related to the information can be transmitted to a 3rd party server (AF). Although the example of FIG. 2 exemplifies a fire occurrence scenario on a mountain, Ambient IoT devices can be deployed to provide relevant information in various disaster situations or in various commercial services, such as sports stadiums or shopping malls used by many people.

[0113] FIG. 3 illustrates an example configuration of a Device ID (identifier), which is identification information of an Ambient IoT device according to an embodiment of the present disclosure.

[0114] Devices operating according to 3GPP standards can use the Subscription Permanent Identifier (SUPI) / International Mobile Subscriber Identity (IMSI), which is the identification information contained in the USIM chip, as the device's ID. However, Ambient IoT devices cannot use USIM chips, or the number of Ambient IoT devices is so large that it is impossible for mobile carriers to assign a unique ID to each device. Therefore, FIG. 3 illustrates an example of an Ambient IoT device ID.

[0115] Since the number of Ambient IoT devices is large as in the scenario of FIG. 2, it may be efficient to group the Ambient IoT devices in order to control their operations. The Ambient IoT devices can be grouped according to their tasks, for example, based on the 3rd party provider of the AF that communicates with the Ambient IoT devices. The Ambient IoT devices can be grouped for various reasons, such as by region, purpose, or simply the number of Ambient IoT devices in the 3rd party provider. In addition, grouping by Ambient IoT Device Type as exemplified in Table 1 or Connectivity Type as exemplified in Table 2 is also possible, and Ambient IoT devices can be grouped according to specific Use Cases and task scenarios. The embodiment of FIG. 3 illustrates an example of one Device ID of an Ambient IoT device, and various other values ​​can be used as the Device ID of an Ambient IoT device.

[0116] In this embodiment, the definitions of each field that constitutes the Device ID of an Ambient IoT device are as shown in the example below. In the following description, the 3rd party provider can be understood as AF or a 3rd party provider server.

[0117] - MNO ID: Indicates the mobile carrier ID used by third-party providers to communicate with Ambient IoT devices. This ID may include at least one of a Mobile Country Code (MCC) and a Mobile Network Code (MNC), or may consist solely of an MNC.

[0118] Enterprise ID: This indicates the company to which the third-party provider belongs. When conducting business using multiple third-party servers, this ID can be used to identify all Ambient IoT devices belonging to the company.

[0119] - AF ID: This ID identifies a third-party provider / server. It can identify all Ambient IoT devices performing a single task or all Ambient IoT devices communicating with a single AF.

[0120] - TASK ID: This is an ID that can be used to group Ambient IoT devices that perform a series of common tasks.

[0121] - Group ID: Because there are so many Ambient IoT devices, grouping them is necessary for control. Group IDs can be used for this purpose. Ambient IoT devices can be grouped based on various classification criteria, such as purpose, capabilities, and status.

[0122] - Device Type ID: Ambient IoT devices can be classified into types A (TY_A), B (TY_B), and C (TY_C) according to their battery capacity and communication capabilities, as shown in the example in Table 1 above. This ID represents this. Ambient IoT devices can also be grouped by Device Type using this ID.

[0123] - Connectivity Type ID: Ambient IoT devices can be categorized into Topology 1 (T1), Topology 2 (T2), Topology 3 (T3), and Topology 4 (T4) based on their ability to communicate with networks and terminals, as shown in the example in Table 2 above. This ID represents this. Ambient IoT devices can also be grouped by Connectivity Type using this ID.

[0124] - Use Case Specific ID: This ID is an ID that can be assigned according to the use case or scenario in which the Ambient IoT device is used. For example, in a scenario for detecting a forest fire, each Ambient IoT device must report the location of the fire when it detects a fire. In other words, the location of the Ambient IoT device is important. In this case, if the location of the Ambient IoT device is used as the Use Case Specific ID of the Ambient IoT device, the Ambient IoT device only needs to send a notification that a forest fire has occurred without having to separately send the location of the forest fire as data, and a 3rd party provider can identify the location with only the ID of the Ambient IoT device. This is just one embodiment, and this ID can be utilized in various other use cases.

[0125] - Unique Device ID: This ID is a unique ID to distinguish each Ambient IoT device. When used with MNO ID, Enterprise ID, AF ID, etc., the Unique Device ID can become a globally unique Device ID. Since the number of Ambient IoT devices is so large, 3rd party providers can arbitrarily assign a range of Unique Device IDs, or they can replace it with the manufacturing number of each device. The Unique Device ID can be defined as any value that can uniquely distinguish each device within the 3rd party provider or mobile carrier.

[0126] The elements that constitute the Device ID of the above Ambient IoT device are only examples, and each value that constitutes the Device ID can be freely configured according to the purpose of use of the Ambient IoT device or the capabilities of the device. In addition, a Group ID can be configured using various components to group Ambient IoT devices. In addition, various components not mentioned in this embodiment may be added depending on the purpose of use or function of the Ambient IoT device. Among each component, at least the AF ID and Unique Device ID can be included in the Device ID of the Ambient IoT device.

[0127] Table 3 below shows an example of subscription data for an Ambient IoT device. The contents of Table 1 are only a portion of the subscription data and may include more values.

[0128] Subscription data typeFieldDescriptionAccess and Mobility Subscription dataAF IDID of 3 rd Party Service Provider (AF)Usage ID / TASK IDID of TASK of Ambient IoTs. It may have NAI format (host part + realm part)List of Ambient IoT ID(s)List of each Ambient IoT ID(s) which take part in common TASK identified by Usage IDSubscribed S-NSSAINetwork Slice that the TASK subscribes toSubscribed DNNSubscribed DNN for the TASKInvoke NEF indicationWhen present, NEF based infrequent small data transfer shall be used for the PDU SessionSMF IDPre-configured SMF ID for handling this TASKPCF IDPre-configured PCF ID for handling this TASKShared PDU Session ID(s)List of Shared PDU Session ID(s) for TASKSession Management Subscription dataAF IDID of 3 rdParty Service Provider (AF)Usage ID / TASK IDID of TASK of Ambient IoTs. It may have NAI format (host part + realm part)List of Ambient IoT ID(s)List of each Ambient IoT ID(s) which take part in common TASK identified by Usage IDSubscribed S-NSSAINetwork Slice that the TASK subscribes toSubscribed DNNSubscribed DNN for the TASKPCF IDPre-configured PCF ID for handling this TASKPDU Session TypePre-configured PDU Session Type for Shared PDU SessionSSC modePre-configured SSC mode for Shared PDU Session5GS Subscribed QoS profilePre-configured 5GS Subscribed QoS profile for Shared PDU SessionNEF Identity for NIDD(non-IP(internet protocol) data delivery)When present, indicates, per S-NSSAI and per DNN, the identity of the NEF to anchor Unstructured PDU Session. When not present for the S-NSSAI and DNN, the PDU session terminates in UPFNIDD informationPre-configured information for SMF-NEF connectionSubscription Management Subscription dataAF IDID of 3 rdParty Service Provider (AF)List of Usage ID(s) / TASK ID(s)ID of TASK of Ambient IoTs. It may have NAI format (host part + realm part)List of Ambient IoT ID(s)List of each Ambient IoT ID(s) which take part in common TASK identified by Usage IDAuthentication / Authorization information for AFInformation for EAP-AKA between 5GC and AFList of Credentials of Ambient IoTsCredential information of Ambient IoTsTASK InformationDescription of TASK identified by Usage IDSubscription Management(SM) States of Ambient IoTsSM states of each Ambient IoT (either SM_Subscribed or SM_Unsubscribed)Registration Management(RM) States of Ambient IoTsRM states of each Ambient IoT (either RM_Registered or RM_Deregistered)Other informationOther information regarding subscription

[0129] FIG. 4 illustrates a Subscription State Diagram indicating the network subscription status of an Ambient IoT device according to one embodiment of the present disclosure. The Ambient Subscription State can be stored in the AF or Ambient IoT device and in the UDM. The Subscription State consists of two states: the SUB-UNSUBSCRIBED State and the SUB-SUBSCRIBED State.

[0130] Ambient IoT devices in the SUB-UNSUBSCRIBED State may not store any information about the Ambient IoT device in any subscription data other than the Subscription Management Subscription data, in addition to the Access and Mobility Subscription data and Session Management Subscription data of the UDM. Related information may only be stored in the Subscription Management Subscription data. The Subscription Management Subscription data of an Ambient IoT device is stored between the network operator and the 3rd party that uses the Ambient IoT device for business. rd When entering into an SLA (Service Level Agreement) agreement with a party service provider, 3 rd Information provided by the party service provider may be stored in accordance with the SLA agreement and the provider's policies.

[0131] Additionally, Ambient IoT devices in the SUB-UNSUBSCRIBED State may not be assigned credential information required for authentication from the network.

[0132] Ambient IoT devices in the SUB-SUBSCRIBED State can store information about the Ambient IoT device in other subscription data besides the Subscription Management Subscription data of the UDM, Access and Mobility Subscription data, and Session Management Subscription data. Information about the Ambient IoT device stored in other subscription data besides the Access and Mobility Subscription data and Session Management Subscription data is shared with the network operator and 3rd party. rd It can be stored based on the SLA agreement and business policy information concluded with the party service provider.

[0133] Additionally, Ambient IoT devices in the SUB-SUBSCRIBED State can be assigned credential information required for authentication from the network.

[0134] Ambient IoT devices in the SUB-UNSUBSCRIBED state can transition to the SUB-SUBSCRIBED state after completing the subscription procedure and receiving a Subscription Accept message. However, if they receive a Subscription Reject message after completing the subscription procedure, they may remain in the SUB-UNSUBSCRIBED state.

[0135] Ambient IoT devices in the SUB-SUBSCRIBED state can transition to the SUB-UNSUBSCRIBED state upon receiving an Unsubscription Accept message after an Unsubscription procedure. When an Ambient IoT device transitions to the SUB-UNSUBSCRIBED state, all subscription data except for Subscription Management Subscription data information in the UDM may be deleted from the UDM. Additionally, previously assigned credential information may become invalid.

[0136] FIG. 5 illustrates an Ambient IoT device subscription procedure according to one embodiment of the present disclosure.

[0137] AF(3 rd When a Party Service Provider (PSP) tries to perform a task using Ambient IoT devices that have already been stored in the Subscription Management Subscription data of UDM (or Ambient IoT Data Management, ADM) at the SLA stage with the network operator, these devices must subscribe to the network operator using the subscription procedure in order to use the network service.

[0138] In step 501, the AF may transmit an AmbientIoT Subscription request to the network (NEF), including an AF ID, a Usage ID or a TASK ID, a List of Ambient IoT ID(s) participating in the TASK, and Information about the TASK. The TASK Information may include a description of what task will be performed using the Ambient IoTs. In one embodiment, the TASK information may include information indicating that tasks such as forest fire monitoring, temperature reporting, and logistics management will be performed. In one embodiment, the TASK information may also include information about network service usage related to the TASK. In one embodiment, the TASK information may include a communication pattern, a volume of transmitted and received data, a Latency Requirement, a Reliability Requirement, a Coverage Area, and the like. Other Subscription data information of the UDM may be determined based on the TASK information. In one embodiment, Subscription date information such as QoS, AM Policy, and SM Policy of the UDM may be determined based on the TASK information.

[0139] In step 502, NEF can perform authorization for AF's AmbientIoT Subscription request. To do this, it can request Subscription Management Subscription data from UDM and reference it. If there is no issue with authorization for the AF request, NEF can forward the AmbientIoT Subscription request to UDM.

[0140] In step 503, the UDM can handle subscription requests from ambient IoT devices together with the PCF / UDR. The AUSF can also participate to assign authentication / authorization information to the AF and assign credentials to the ambient IoT devices.

[0141] In one embodiment, the UDM may assign information for mutual authentication with the network to an AF that may perform subsequent network registration requests and Ambient IoT device authentication requests on behalf of the Ambient IoT devices requesting subscription. In one embodiment, authentication information for the AF may be assigned for each TASK. In one embodiment, if the AF performs network registration and authentication of a large number of Ambient IoT devices on behalf of the AF, authentication for the AF may require authentication as strong as the authentication performed by 3GPP. Accordingly, authentication for each AF TASK may include 5G-AKA or EAP-AKA for terminal authentication in 3GPP. Alternatively, an authentication procedure equivalent thereto may be performed. In one embodiment, the network may assign information required for future mutual authentication / authorization with the AF to the AF.

[0142] In one embodiment, the UDM / AUSF may assign credentials to Ambient IoT devices requesting subscription. In one embodiment, the UDM and PCF may set QoS-related information, Policy-related information, etc. by considering TASK information, SLA contract information, or network policy information provided by AF to store various subscription data regarding the Ambient IoT devices requesting subscription in the UDM. In one embodiment, the UDM may transition the Subscription State of the Ambient IoT devices requesting subscription, stored in the UDM, to SUB-SUBSCRIBED. In one embodiment, the UDM may determine an AMF and an SMF suitable for performing the requested TASK using the NRF.

[0143] In step 504, if the UDM has determined an AMF and an SMF suitable for performing the TASK requested in step 503, it can pre-configure the information necessary for performing the TASK to the AMF and SMF.

[0144] In steps 505 and 506, the UDM may transmit the results of the Ambient IoT Subscription request to the AF. The NEF may store some of the information received from the UDM to perform future TASK-related requests.

[0145] Data transmitted by UDM to AF may include:

[0146] - Authentication / Authorization information data required for mutual authentication between AF / TASK and the network

[0147] - List of Credentials of Ambient IoTs

[0148] - List of ID(s) of Ambient IoTs

[0149] - QoS, Policy, PDU Session related information

[0150] - Selected AMF ID

[0151] - Ambient IoT device subscription request result

[0152] - Other subscription-related information

[0153] In addition to the information listed above, it may include additional information necessary to use network services.

[0154] If the subscription result of the Ambient IoT devices is Accepted, AF can transition the Subscription State of the Ambient IoT devices it is storing to SUB-SUBSCRIBED.

[0155] FIG. 6 illustrates an Ambient IoT device unsubscription procedure according to one embodiment of the present disclosure.

[0156] AF(3 rd A Party Service Provider (PSP) can perform tasks using Ambient IoT devices and then deregister the Ambient IoT devices when they no longer need to perform the tasks.

[0157] In step 601, the AF may transmit the AF ID and the Usage ID or TASK ID from which it wishes to unsubscribe to the network.

[0158] In step 602, NEF can perform authorization for AF's AmbientIoT Unsubscription request. If there is no problem with authorization for the AF request, the relevant information stored in NEF can be deleted and the request can be sent to UDM.

[0159] In step 603, the Ambient IoT device's Unsubscription request can be handled with UDM and PCF / UDR. The AUSF can also participate to delete the AF / TASK's Authentication / Authorization information and release the credentials assigned to the Ambient IoT device.

[0160] In one embodiment, the UDM may release information allocated for AF and Mutual Authentication / Authorization. In one embodiment, the UDM / AUSF may release credentials allocated to the corresponding Ambient IoT devices. In one embodiment, the UDM may delete various subscription data except for subscription management subscription data from the UDM regarding the corresponding Ambient IoT devices. In one embodiment, the UDM may transition the subscription state of the corresponding Ambient IoT devices stored in the UDM to SUB-UNSUBSCRIBED.

[0161] In step 604, if an AMF and SMF suitable for performing the TASK have been determined, the UDM may request the AMF and SMF to delete information that was pre-configured for performing the TASK.

[0162] In steps 605 and 606, the UDM can send the results of the Ambient IoT Unsubscription request to the AF. If the Ambient IoT devices' unsubscription request is accepted, the AF can transition the Subscription State of the corresponding Ambient IoT devices it stores to SUB-UNSUBSCRIBED. In addition, the AF can delete the related information received from the network for performing the TASK.

[0163] FIG. 7 illustrates a BSS (Business Support System)-based Ambient IoT device subscription procedure according to one embodiment of the present disclosure.

[0164] BSS stands for Business Support System, which refers to the system that telecommunication service providers use to conduct business operations targeting customers.

[0165] The procedure illustrated in FIG. 7 is identical to the procedure illustrated in FIG. 5, except that the operations of AF and UDM in the procedure illustrated in FIG. 5 are performed via BSS. That is, the operations of AF, BSS, and UDM in step 700 of FIG. 7 can be performed identically to or corresponding to the operations of AF, NEF, UMD, and PCF / UDR in steps 501 to 503 of FIG. 5. Thereafter, the operations of AF, NEF, UDM, and AMF / SMF in steps 701 to 702 of FIG. 7 can be performed identically to or corresponding to the operations of AF, NEF, UDM, and AMF / SMF in steps 504 to 506 of FIG. 5.

[0166] FIG. 8 is a diagram illustrating the configuration of a network entity according to one embodiment of the present disclosure.

[0167] FIG. 8 is a diagram illustrating the configuration of a network entity according to an embodiment of the present disclosure.

[0168] A network entity according to one embodiment of the present disclosure may include a processor (820) that controls the overall operation of the network entity, a transceiver (800) including a transmitter and a receiver, and a memory (810). 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. 8.

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

[0170] According to one embodiment of the present disclosure, the processor (820) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (820), the memory (810), and the transceiver (800) 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 (820) and the transceiver (800) can be electrically connected. In addition, the processor (820) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

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

[0172] When the network entity illustrated in FIG. 8 is a UDM entity, the at least one processor may be configured to receive a subscription request message for at least one terminal from an application function (AF) entity. The at least one processor may store subscription information of the at least one terminal based on the subscription request message for the at least one terminal. The at least one processor may be configured to transmit a response message to the subscription request message to the AF entity. In one embodiment, the subscription request message may include information about a task performed by the at least one terminal.

[0173] In one embodiment, the at least one processor may be configured to assign authentication information to the AF entity based on the subscription request message for the at least one terminal. In one embodiment, the at least one processor may be configured to assign a credential to the at least one terminal. In one embodiment, the subscription information of the at least one terminal may be determined based on SLA contract information and network policy information. In one embodiment, the at least one processor may be configured to transition the subscription status of the at least one terminal from 'unsubscription' to 'subscription'. In one embodiment, the at least one processor may be configured to determine an AMF and an SMF based on information about a task performed by the at least one terminal, and to pre-configure the AMF and the SMF with information necessary for the task performed by the at least one terminal. In one embodiment, the subscription request message may include at least one of an identifier (ID) of the AF entity, an ID of the at least one terminal, and an ID for a task performed by the at least one terminal. In one embodiment, the at least one terminal may include an ambient Internet of Things (IoT) terminal.

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

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

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

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

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

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

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

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

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

Claims

1. In a method of UDM (unified data management) in a wireless communication system, A step of receiving a subscription request message for at least one ambient IoT (internet of things) terminal from an AF (application function); A step of storing subscription information of at least one surrounding IoT terminal based on the subscription request message for the at least one surrounding IoT terminal; and A step of transmitting a response message to the above subscription request message to the AF; A method characterized in that the subscription information includes at least one of subscription management subscription information, access and mobility subscription information, and session management subscription information.

2. In paragraph 1, the access and mobility subscription information is: A method characterized in that it includes at least one of an identifier of the AF, an identifier for the usage of the at least one peripheral IoT terminal, a list of IDs of the at least one peripheral IoT terminal, and an ID of a preset SMF (session management function).

3. In paragraph 1, the session management subscription information is: A method characterized in that it includes at least one of an identifier of the AF, an identifier for the usage of the at least one peripheral IoT terminal, a list of IDs of the at least one peripheral IoT terminal, an ID of a network exposure function (NEF) for NIDD (non-IP (internet protocol) data delivery), and the NIDD information.

4. In paragraph 1, A method characterized in that the above subscription request message includes information about a task performed by at least one surrounding IoT terminal.

5. In paragraph 1, A method characterized in that it further comprises a step of assigning authentication information to the AF based on the subscription request message for the at least one surrounding IoT terminal.

6. In paragraph 1, the subscription information of at least one surrounding IoT terminal is: A method characterized in that it is determined based on SLA (service level agreement) contract information and network policy information.

7. In paragraph 1, A method characterized in that it further comprises a step of transitioning the subscription status of the at least one surrounding IoT terminal from unsubscription to subscription in response to the subscription request message.

8. In paragraph 1, A step of determining an access and mobility management function (AMF) and a session management function (SMF) based on information about a task performed by at least one surrounding IoT terminal; and A method characterized in that it further comprises a step of pre-configuring information necessary for a task performed by at least one peripheral IoT terminal to the AMF and SMF.

9. In paragraph 1, the subscription request message, A method characterized in that it includes at least one of an ID (identifier) ​​of the AF entity, an ID of the at least one peripheral IoT terminal, and an ID for a task performed by the at least one peripheral IoT terminal.

10. In the wireless communication system, in the UDM (unified data management) entity, Transmitter and receiver; and At least one processor; comprising: Receive a subscription request message for at least one ambient IoT (internet of things) terminal from an AF (application function) entity, Based on the subscription request message for the at least one peripheral IoT terminal, storing subscription information of the at least one peripheral IoT terminal, and configured to transmit a response message to the above subscription request message to the above AF entity, A UDM entity characterized in that the subscription information includes at least one of subscription management subscription information, access and mobility subscription information, and session management subscription information.

11. In paragraph 10, the access and mobility subscription information is: A UDM entity characterized in that it includes at least one of an identifier of the AF, an identifier for the usage of the at least one peripheral IoT terminal, a list of IDs of the at least one peripheral IoT terminal, and an ID of a preset SMF (session management function).

12. In paragraph 10, the session management subscription information is: A UDM entity characterized in that it includes at least one of the identifier of the AF, an identifier for the usage of the at least one peripheral IoT terminal, a list of IDs of the at least one peripheral IoT terminal, an ID of a network exposure function (NEF) for NIDD (non-IP (internet protocol) data delivery), and the NIDD information.

13. In paragraph 10, A UDM entity, characterized in that the above subscription request message includes information about a task performed by at least one surrounding IoT terminal.

14. In the 10th paragraph, the at least one processor, A UDM entity configured to assign authentication information to the AF entity based on the subscription request message for the at least one surrounding IoT terminal.

15. In paragraph 10, the subscription information of at least one surrounding IoT terminal is: A UDM entity characterized by being determined based on SLA (service level agreement) contract information and network policy information.

Images