Method and apparatus for performing network registration and data transmission for ultra-power-saving device in wireless communication system

Abstract

The present invention relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present invention provides an operation method of an access and mobility management function (AMF) for managing a plurality of ambient IoT devices in a wireless communication system. The operation method of an AMF may be configured to comprise the steps of: receiving a registration request for a group including a plurality of ambient IoT devices from an application function (AF); selecting an AUSF for authenticating the plurality of ambient IoT devices and performing authentication on the plurality of ambient IoT devices through the selected AUSF; performing an AM policy association establishment procedure through a policy control function (PCF); and performing a UE policy association establishment procedure for the plurality of ambient IoT devices through the PCF.

Description

Method and device for performing network registration and data transmission for ultra-low power devices in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for registering a device with very low power consumption and very low price to a network and transmitting data therethrough.

[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 and apparatus capable of effectively registering a device that does not use battery power or operates at low power to a network in a wireless communication system.

[0009] The present disclosure aims to provide an effective data transmission method and device for a device that does not use battery power or operates at low power in a wireless communication system.

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

[0011] According to one embodiment of the present invention, an operation method of an access and mobility management function (AMF) for managing a plurality of Ambient IoT devices in a wireless communication system is disclosed. The operation method of the AMF may include the steps of: receiving a registration request for a group including a plurality of Ambient IoT devices from an application function (AF); selecting an AUSF for authentication of the plurality of Ambient IoT devices and performing authentication on the plurality of Ambient IoT devices through the selected AUSF; performing an AM policy association establishment procedure through a policy control function (PCF); and performing a UE policy association establishment procedure for the plurality of Ambient IoT devices through the PCF.

[0012] According to one embodiment of the present invention, the plurality of Ambient IoT devices can be distinguished through one of a group ID, a device type ID, a connection type ID, a use case ID, or a unique device ID and the ID of the AF.

[0013] According to one embodiment of the present invention, the operating method of the AMF may further include the steps of: receiving a request message for establishing a shared PDU (protocol data unit) session from at least one of the plurality of Ambient IoT devices; checking whether a shared PDU session has been created for the Ambient IoT device that has transmitted the request message; and, if the shared PDU session has not been created for the Ambient IoT device that has transmitted the request message, selecting a session management function (SMF) capable of supporting a shared PDU session and transmitting a shared PDU session establishment request message to the selected SMF.

[0014] According to one embodiment of the present invention, the operating method of the AMF may further include, when a shared PDU session for the Ambient IoT device that transmitted the request message is created, a step of transmitting a rejection message including information about the created shared PDU session to the Ambient IoT device that transmitted the request message.

[0015] Verification of whether a shared PDU session has been created for the Ambient IoT device that transmitted the above request message can be performed based on the AF ID, group ID, and PDU session ID included in the above request message.

[0016] According to one embodiment of the present invention, the operating method of the AMF may further include a step of broadcasting information about the shared PDU session established through a RAN node when the shared PDU session is established.

[0017] According to one embodiment of the present invention, the method of operating the AMF may further include the steps of: receiving a request message for establishing a shared PDU (protocol data unit) session from at least one of the plurality of Ambient IoT devices; and, if the AMF does not support the shared PDU session, transmitting the request message to an AMF that supports the shared PDU session.

[0018] According to another embodiment of the present invention, an access and mobility management function (AMF) for managing a plurality of Ambient IoT devices in a wireless communication system is disclosed. The AMF includes a transceiver; and a control unit, wherein the control unit is configured to receive, from an application function (AF), a registration request for a group including a plurality of Ambient IoT devices, select an AUSF for authentication of the plurality of Ambient IoT devices, perform authentication of the plurality of Ambient IoT devices through the selected AUSF, perform an AM policy association establishment procedure through a policy control function (PCF), and perform a UE policy association establishment procedure for the plurality of Ambient IoT devices through the PCF.

[0019] One embodiment of the present invention discloses a method for effectively registering a plurality of devices that do not use battery power or operate at low power levels to a network.

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

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

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

[0023] FIG. 2 illustrates an example of a scenario in which an Ambient IoT (Internet of Things) device is used in a communication system according to an embodiment of the present disclosure.

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

[0025] FIG. 4a and FIG. 4b illustrate a network registration procedure of a terminal according to an embodiment of the present disclosure.

[0026] FIG. 5 illustrates an example of a data transmission method of an Ambient IoT device according to an embodiment of the present disclosure.

[0027] FIG. 6a and FIG. 6b illustrate a procedure for an Ambient IoT device to request creation of a Shared PDU (Protocol Data Unit) Session according to an embodiment of the present disclosure.

[0028] FIG. 7 illustrates a procedure for creating a connection between a UPF (User Plane Function) and an AF (Application Function) (3rd Party Service Provider) according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0044] 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 inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

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

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

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

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

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

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

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

[0052] The present invention provides an effective network registration method, a data transmission method, and a device therefor for a device that does not use battery power or operates at low power in a wireless communication system.

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

[0054] Referring to FIG. 1, a 5G system (5G network) may include at least one of the network entities (NE) or network functions (NF) described below. Of course, the present invention is not limited to the illustration of FIG. 1, and the 5G system may include more or fewer network entities or network functions than those illustrated in FIG. 1.

[0055] According to one embodiment of the present disclosure, (R)AN ((Radio) Access Network) is an entity that performs radio 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.

[0056] According to one embodiment of the present disclosure, a terminal may include a UE (User Equipment), an NG UE (Next Generation UE), an MS (Mobile Station), a cellular phone, a smartphone, a computer, an IoT (Internet of Things) device, or a multimedia system capable of performing a communication function.

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

[0058] According to one embodiment of the present disclosure, as wireless communication systems evolve from 4G systems to 5G systems, a new core network (CN) called Next Generation Core (NG Core) or 5G Core Network (5GC) has been defined. The new core network can be implemented as a network function (NF) by virtualizing all existing network entities (NEs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource, and is not limited to the above examples.

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

[0060] According to one embodiment of the present disclosure, an Access and Mobility Management Function (AMF) may be a network function that manages access and mobility of a terminal (UE). For example, the AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0061] According to one embodiment of the present disclosure, a Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a User Equipment (UE). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining a tunnel between a User Plane Function (UPF) and a RAN required for this, selecting and controlling a User Plane (UP), controlling traffic processing in the UPF, and controlling the collection of charging data.

[0062] According to one embodiment of the present disclosure, a Policy Control Function (PCF) may be a network function that applies a mobile communication service provider's service policy, charging policy, and policy for PDU Session to a terminal.

[0063] According to one embodiment of the present disclosure, Unified Data Management (UDM) may be a network function that stores subscriber information. For example, UDM may 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.

[0064] According to one embodiment of the present disclosure, the Network Exposure Function (NEF) may be a function that provides information about a terminal to a server outside the 5G network. Furthermore, the NEF may provide the function of providing information necessary for services to the 5G network and storing it in a Unified Data Repository (UDR).

[0065] According to one embodiment of the present disclosure, a User Plane Function (UPF) may be a function that acts as a gateway to transmit user data (PDU) to a Data Network (DN). More specifically, the UPF may perform a data processing function so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF 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.

[0066] According to one embodiment of the present disclosure, a Network Repository Function (NRF) can perform a function of storing profiles of NFs and discovering NFs.

[0067] According to one embodiment of the present disclosure, an Authentication Server Function (AUSF) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0068] According to one embodiment of the present disclosure, the Network Slice Selection Function (NSSF) can perform a function of selecting a Network Slice Instance provided to a terminal.

[0069] According to one embodiment of the present disclosure, the Network Data Analytics Function (NWDAF) collects data from multiple NFs (NFs) for the purpose of efficiently operating the 5GC network. The collected data is analyzed using a machine learning (ML) model, and the analyzed results are provided back to the NFs, thereby helping each NF provide efficient network services.

[0070] According to one embodiment of the present disclosure, an Application Function (AF) can communicate with a network operator so that an external server (Application Server) can utilize network services provided by the network operator. The AF can be divided into an internal AF and an external AF depending on the deployment entity. An internal AF deployed by a network operator can directly communicate with NFs within the network operator. An AF deployed by a service provider (3rd Party Service Provider) must go through an NEF to communicate with NFs within the network operator.

[0071] According to one embodiment of the present disclosure, a DN (Data Network) may be a data network through which a terminal transmits and receives data in order to use a network operator's service or a third-party service.

[0072] According to one embodiment of the present disclosure, a 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 an IoT device is referred to as an ambient IoT device (or simply Ambient IoT).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] - N14: Reference point between two AMFs

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

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

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

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

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

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

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

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

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

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

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

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

[0100] - Nnascf: Service-based interface by Nnsacf

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

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

[0103] According to one embodiment of the present disclosure, an Ambient IoT device may refer to a device that does not have a battery or has very limited energy storage capabilities, and also has very limited communication and computing capabilities. The present disclosure proposes an efficient data registration method for Ambient IoT devices having the aforementioned characteristics.

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

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

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

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

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

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

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

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

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

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

[0114] 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)

[0115] Table 1 - Ambient IoT Device Types

[0116] In addition, in the present disclosure, Ambient IoT devices can 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 four types of connection topologies are also possible. In other words, a single Ambient IoT device can operate by utilizing multiple types of connection topologies.

[0117] 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)

[0118] Table 2 - Ambient IoT Device Connectivity Topology

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

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

[0121] Referring to Figure 2, the Korea Forest Service or the National Fire Agency can deploy millions of Ambient IoT devices on mountains for early detection of forest fires. In this case, the number of Ambient IoT devices is large, and the deployment area is vast, making human access difficult. Therefore, Ambient IoT devices are often deployed by air. For the reasons mentioned above, maintenance (e.g., battery replacement of Ambient IoT devices, replacement of defective parts, etc.) of deployed Ambient IoT devices may be impossible. Once deployed, Ambient IoT devices can operate and perform their tasks for as little as 10 years or as long as 20 years. Therefore, it is important for Ambient IoT devices to operate with minimal battery consumption. In the scenario of Figure 2, the Ambient IoT devices deployed can monitor fires around the mountain. Among the Ambient IoT devices, at least one Ambient IoT device that detects a fire transmits information notifying of the occurrence of a fire to an 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, such as a fire department server in the example of FIG. 2) 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 of the occurrence of a fire, and the information notifying of the occurrence of a fire and / or data related to the information generated based on the monitoring results of at least some of the Ambient IoT devices can be transmitted to a 3rd party server (AF).Although the example in Fig. 2 illustrates a scenario where a fire breaks out in a mountain, Ambient IoT devices can also 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.

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

[0123] Referring to FIG. 3, devices operating according to the 3GPP standard can use the SUPI (Subscription Permanent Identifier) / IMSI (International Mobile Subscriber Identity), which is the identification information contained in the USIM chip, as the ID of the corresponding device. However, Ambient IoT devices cannot use USIM chips, or there are too many of them, making it impossible for mobile carriers to assign a unique ID to each device. Accordingly, FIG. 3 illustrates an embodiment related to the ID of Ambient IoT devices.

[0124] 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. These Ambient IoT devices may be grouped according to their tasks. For example, they may be grouped based on the 3rd party provider of the AF that communicates with the Ambient IoT devices. For example, the 3rd party provider may group the Ambient IoT devices based on various criteria such as region, purpose, or an arbitrarily determined number. 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 may be grouped based on a specific Use Case or task scenario. The embodiment of FIG. 3 illustrates one example of a Device ID for an Ambient IoT device, and various other values ​​may be used as the Device ID of an Ambient IoT device.

[0125] In this embodiment, the definitions for 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's server. Of course, the present invention is not limited to the example below.

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

[0127] - Enterprise ID: This can indicate the company to which a third-party provider belongs. When performing work using multiple third-party servers, the Enterprise ID can be used to group all Ambient IoT devices belonging to the company.

[0128] - AF ID: The AF ID can be an ID that distinguishes a third-party provider / server. All Ambient IoT devices performing a single task or all Ambient IoT devices communicating with a single AF can be distinguished through the AF ID.

[0129] - Group ID: Because the number of Ambient IoT devices is large, grouping them is necessary for control. A Group ID can be used for this purpose. Grouping Ambient IoT devices can be based on various classification criteria, such as their purpose, capabilities, and status.

[0130] - 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. The Device Type ID is an ID that indicates the device type. Ambient IoT devices can also be grouped by Device Type using the Device Type ID.

[0131] - Connectivity Type ID: Ambient IoT devices can be classified into Topology 1 (T1), Topology 2 (T2), Topology 3 (T3), Topology 4 (T4), etc., as in the example of [Table 2] above, depending on their ability to communicate with networks and terminals and their connection topology. Connectivity Type ID can be an ID that indicates such connection topology. Ambient IoT devices can also be grouped by Connectivity Type using Connectivity Type ID.

[0132] - Use Case Specific ID: The Use Case Specific ID may be 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 may be 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 can send only a notification that a forest fire has occurred without separately transmitting the location of the forest fire as data, and a 3rd party provider can identify the location of the Ambient IoT device with only the ID of the Ambient IoT device. This is one embodiment, and the Use Case Specific ID may be utilized in various other Use Cases.

[0133] - Unique Device ID: The Unique Device ID can be 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 number within a specific range of Unique Device IDs, or they can replace the Unique Device ID 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.

[0134] The above examples illustrate examples of elements that constitute the Device ID of an Ambient IoT device, 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, various components can be used to configure a Group ID for grouping Ambient IoT devices. In addition, various components not mentioned in this embodiment can be added according to the purpose of use or function of the Ambient IoT device. Among each component, at least the AF ID and the Unique Device ID can be included in the Device ID of the Ambient IoT device.

[0135] In this disclosure, a network registration method considering the characteristics of the above-described Ambient IoT device is proposed.

[0136] FIG. 4a and FIG. 4b illustrate a network registration procedure of a terminal according to an embodiment of the present disclosure.

[0137] In one embodiment, steps not described below may be performed identically or similarly to a general terminal network registration procedure, rather than an Ambient IoT device.

[0138] In step 1, the terminal can transmit a Registration Request message to the base station (R)AN. Ambient IoT devices can be composed of millions to tens of millions of devices depending on the purpose of use. As such, since Ambient IoT devices are typically deployed in the millions or more, it may be realistically difficult for each device to individually perform the registration procedure like a general terminal. In this disclosure, 3 rd We propose group registration through a Party Service Provider (AF) or using a representative terminal. Group registration can divide devices into groups in various ways depending on the purpose of use of the devices, and this disclosure is not limited thereto. This disclosure includes 3 rd Although described based on group registration through a Party Service Provider (AF), group registration using other devices such as a representative terminal or user terminal may also be included. Furthermore, in this disclosure, it may be assumed that one AF is responsible for one group of Ambient IoT Devices.

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

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

[0141] 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​is a type of terminal ID and is an abbreviated form of 5G-GUTI (5G Globally Unique Temporary Identifier). 5G-S-TMSI consists of an AMF Set ID, an AMF Pointer, and a 5G-TMSI, and is used in wireless signaling procedures. A 5G-TMSI can identify a single AF within an AMF(s).

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

[0143] A Public Land Mobile Network (PLMN) ID is the mobile operator's ID. It consists of a Mobile Country Code (MCC) and a Mobile Network Code (MNC).

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

[0145] The Establishment Cause value indicates the purpose for which the terminal requested the creation of an RRC (Radio Resource Control) connection. In the present disclosure, it can be set to “Group Initial Registration,” which means group registration.

[0146] If the terminal is part of a Mobile Base Station Relay (MBSR) node, the AN parameter must include the MBSR Indication.

[0147] The Registration type value indicates the purpose for which the terminal requests registration. The Registration type value may be set to one of the following values: Initial Registration, Mobility Registration Update, Periodic Registration Update, Emergency Registration, Disaster Roaming Initial Registration, or Disaster Roaming Mobility Registration Update. In the present disclosure, the Registration type may be set to “Group Initial Registration,” which means group registration.

[0148] SUCI (Subscription Concealed Identifier) ​​is a form of terminal ID that includes a concealed SUPI (Subscription Permanent Identifier) ​​value for the purpose of preventing leakage of the SUPI value. In the present disclosure, the network may allocate a SUPI to an AF, thereby concealing the AF's SUPI value, or may conceal a general AF ID value.

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

[0150] PEI (Permanent Equipment Identifier) ​​identifies ME (Mobile Equipment). If the terminal supports at least one 3GPP access technology (i.e., NG-RAN, E-UTRAN, UTRAN, or GERAN), the PEI format must be set to IMEI (International Mobile Equipment Identity) or IMEISV (International Mobile Equipment Identity-Software Version). In the present disclosure, the PEI value of the AF may be transmitted by allocating a PEI to the AF in the network, or this value may be omitted in the case of Group Initial Registration.

[0151] The last visited TAI (Tracking Area Identity) indicates the TAI value the terminal last visited. This value is used by the AMF to determine the terminal's RA (Registration Area). This value may be omitted in the case of Group Initial Registration.

[0152] Security parameters values ​​are used for terminal authentication and integrity protection.

[0153] This message may contain a list of device ID(s). This value may represent a list of device IDs registered by Group Initial Registration.

[0154] In step 2-3, the NG-RAN, which is a base station, can confirm or identify that the Establishment cause value in the AN parameter is “Group Initial Registration”, select an AMF that supports Group Initial Registration, and transmit a Registration Request message to the selected AMF.

[0155] In steps 8-9, AMF can perform terminal authentication by selecting AUSF for terminal authentication.

[0156] In steps 13-14, the AMF can select a UDM to retrieve terminal subscriber information (i.e., Access and Mobility Subscription data for a group of devices). The AMF can select a UDM based on the AF ID to retrieve subscriber information for a group of devices. Group terminal subscriber information (i.e., Access and Mobility Subscription data for a group of devices) can also be stored in the AF.

[0157] AMF can register group terminal subscriber information in UDM by sending the Nudm_UECM_Registration message to UDM. This subscriber information can be identified by an AF ID. Subscriber information can also include the following information: the number of devices, the type of devices, and a list of tasks.

[0158] In step 16, the AMF can perform a Group AM Policy Association Establishment with the PCF. This message may include the AF ID. Additionally, it may include a “Group AM Policy indication” to indicate the Group AM Policy Association.

[0159] In step 21b, the AMF can perform Group UE Policy Association Establishment with the PCF. The message that the AMF sends to the PCF to perform Group UE Policy Association Establishment may include the AF ID. Additionally, the AMF may include a “Group UE Policy indication” in the message that it sends to the PCF to indicate the Group UE Policy Association.

[0160] FIG. 5 illustrates an example of a data transmission method of an Ambient IoT device according to an embodiment of the present disclosure.

[0161] In this disclosure, a data transmission method considering the characteristics of the above-described Ambient IoT device is proposed.

[0162] Referring to FIG. 5, tens to millions of Ambient IoT devices can be deployed depending on the intended use. It may not be possible for all devices to create a PDU Session and communicate over a network like existing devices. Therefore, in the present disclosure, a group composed of multiple Ambient IoT devices can be defined. In addition, devices belonging to each group can transmit data by sharing a single PDU Session (e.g., a Shared PDU Session). For example, in an embodiment of the present disclosure, a single PDU Session shared by multiple Ambient IoT devices belonging to a group may be referred to as a Shared PDU Session.

[0163] In Fig. 5, all Ambient IoT devices can be divided into two groups. Each group can create Shared PDU Session #1 and Shared PDU Session #2. When data to be transmitted to the network occurs, the Ambient IoT devices belonging to each group can transmit the data using the created Shared PDU Session. Alternatively, if the created Shared PDU Session does not exist, a Shared PDU Session can be created and the data can be transmitted to the network.

[0164] FIG. 6A and FIG. 6B illustrate a procedure for an Ambient IoT device to request creation of a Shared PDU Session according to an embodiment of the present disclosure.

[0165] Referring to FIGS. 6A and 6B, in step 1, a terminal may transmit a PDU Session Establishment Request message to the network to request establishment of a Shared PDU Session. The Request Type of the PDU Session Establishment Request message may be set to “Shared Initial Request.” The PDU Session ID may be set to a pre-configured value for the group. Other parameter values ​​for the PDU Session creation request (e.g., including at least one of S-NSSAI, DNN, SSC mode, or 5GSM Capability) may be pre-configured in the network (e.g., including at least one of AMF, SMF, or UDM). Other values ​​may also be pre-configured in the network, but may be set to the following values. For example, the PDU Session Type may be set to the Unstructured PDU Session type. For example, the Always-on PDU Session Requested value may be set according to the TASK performed by the terminals. The PDU Session Establishment Request message may include at least one of the AF ID and Group ID.

[0166] In Step 2, if the AMF does not support Shared PDU Session, it can retransmit the terminal's request to another AMF that does support Shared PDU Session. If the AMF that received the terminal's request from an AMF that does not support Shared PDU Session supports the Shared PDU Session function, it can decide whether to grant the terminal's request based on the terminal's subscription information (e.g., Access and Mobility Subscription data) received from the UDM.

[0167] An AMF (e.g., an AMF that supports Shared PDU Sessions) can check whether a Shared PDU Session has already been created for the group by checking the AF ID, Group ID, and PDU Session ID. If a Shared PDU Session for the group has already been created, the AMF can reject the terminal's request. In this case, the rejection message can include a reason for rejection (e.g., "Shared PDU Session is established"). Of course, the above example is not limited.

[0168] Therefore, when a Shared PDU Session is initially created for a group, the results can be broadcast to all terminals in the group. Therefore, terminals in the group can transmit data using the pre-created Shared PDU Session without triggering the Shared PDU Session creation procedure.

[0169] AMF can select an SMF capable of supporting a Shared PDU Session. SMF selection can be done using NRF, but information about the SMF for a given terminal group can also be pre-configured in AMF.

[0170] In step 3, the AMF may send an Nsmf_PDUSession_CreateSMFContext Request message to the selected SMF. The Nsmf_PDUSession_CreateSMFContext Request message may include at least one of a Group ID or a PDU Session ID. The Request Type may be set to “Shared Initial Request”. The SM context value for the Shared PDU Session may be pre-configured in the SMF. Alternatively, the SM context value for the Shared PDU Session may be pre-configured in the UDM, and the SMF may receive the SM context value from the UDM.

[0171] The pre-configured SM context value may include at least one of the following values. For example, the pre-configured SM context value may include at least one of S-NSSAI, DNN, SSC mode, 5GSM Capability, PDU Session Type (for example, it may be set to Unstructured PDU Session type), or Always-on PDU Session Requested (for example, it may be set according to TASK of the terminal). The pre-configured SM context value may also include other values ​​as needed in addition to the examples described above.

[0172] In Step 4, the SMF can retrieve subscriber information (e.g., Session Management subscription data) from the UDM. The SMF can request subscriber information from the UDM using the AF ID and Group ID. Some of the subscriber information may be pre-configured in the SMF.

[0173] In step 5, SMF can send an Nsmf_PDUSession_CreateSMFContext Response message to AMF.

[0174] In step 6, the authentication / authorization procedure of the PDU Session can be performed.

[0175] In step 7a, the SMF can select the PCF.

[0176] Step 7b may perform SM Policy Association Establishment or SM Policy Association Modification initiated by the SMF. The SMF may select a PCF using the AF ID and Group ID. Additionally, the SMF may receive SM Policy Information for a Shared PDU Session from the PCF.

[0177] In step 8, SMF can select a UPF that can support Shared PDU Session and Unstructured PDU Session types.

[0178] In step 9, the SMF may initiate SM Policy Association Modification. However, if it was already initiated in step 7b, step 9 may be omitted.

[0179] In step 10a, the SMF can send the N4 rules for the Shared PDU Session and Unstructured PDU Session types to the UPF. The SMF can assign an IPv6 prefix for N6 Point-to-Point (PtP) tunneling. For the N6 PtP tunnel, the SMF can send the IP address of the AF (e.g., a 3rd Party Service Provider) to the UPF. In step 10b, the SMF can receive a response from the UPF to the transmission of the N4 rules for the Shared PDU Session and Unstructured PDU Session types.

[0180] In step 11, the SMF can send a Shared PDU Session Indication to the AMF. The AMF can mark the PDU Session as a Shared PDU Session. The AMF can then send information about the marked shared PDU Session to the SMF.

[0181] In step 12, the AMF may transmit an N2 PDU Session Request message to the base station. The N2 PDU Session Request message may include information about the marked Shared PDU Session.

[0182] In step 13, the terminal may receive a PDU Session Establishment Accept message from the base station. The PDU Session Establishment Accept message may include a Shared PDU session Accepted Indication.

[0183] In step 14, the base station may transmit an N2 PDU Session Response message to the AMF in response to the N2 PDU Session Request message. Afterwards, the terminal may transmit the first uplink data to the UPF.

[0184] In step 15, AMF may send a PDUSession_UpdateSMContext Request message to SMF to request an update of the SM Context.

[0185] In step 16a, SMF may send an N4 Session Modification Request message containing N4 rules to UPF.

[0186] In step 16b, UPF may receive an N4 Session Modification Response message in response to the transmission of N4 rules to SMF.

[0187] At step 16c, a registration procedure between SMF and UDM can be performed.

[0188] In step 17, SMF may send a PDUSession_UpdateSMContext Response message to AMF in response to the request to update the SM Context in step 15.

[0189] In step 18, SMF can notify SM Context status to AMF.

[0190] In step 19, SMF can transmit IPv6 Address Configuration to the terminal via UPF.

[0191] At step 20, SMF can initiate SM Policy Association Modification.

[0192] An unsubscription procedure may be performed at step 21.

[0193] Of course, the above examples are not limiting. Therefore, at least one action in the above-described procedure may be omitted, or a new action may be added and organically combined with the above-described actions.

[0194] FIG. 7 illustrates a procedure for creating a connection between a UPF and an AF (3rd Party Service Provider) according to an embodiment of the present disclosure.

[0195] Referring to FIG. 7, at step 0, the terminal is performing a Shared PDU Session creation procedure and may perform steps 1 to 10 described above (e.g., steps 1 to 10 of FIG. 6a described above). During the Shared PDU Session creation procedure, the SMF may request an N4 Session Establishment to the UPF. At this time, the SMF may request an N6 PtP tunnel with an AF (e.g., a 3rd Party Service Provider).

[0196] In step 1, the UPF may send a Naf_N6PtPTunnel_Connection Request message to the AF. The Naf_N6PtPTunnel_Connection Request message may include at least one of the following information. For example, the Naf_N6PtPTunnel_Connection Request message may include at least one of the AF ID, Group ID, PtPTunnel ID, PtPTunnel Duration, PtPTunnel Information, or Requested Action. In addition, the Naf_N6PtPTunnel_Connection Request message may include information related to PtP Tunnel creation and a request (Requested Action) requested to the AF.

[0197] In step 2, AF can send the Naf_N6PtPTunnel_Connection Response message to UPF as a response message to UPF's request.

[0198] In step 3, the UPF may send a Nsmf_N6PtPTunnel_CreateContext Request message to the SMF. The Nsmf_N6PtPTunnel_CreateContext Request message may include at least one of the following information. For example, the Nsmf_N6PtPTunnel_CreateContext Request message may include at least one of a UPF ID, an AF ID, a Group ID, a PtPTunnel ID, a PtPTunnel Duration, PtPTunnel Information, or a Requested Action. For example, the Requested Action may be set to any of the following values. Each of the following settings may instruct to perform the corresponding action. Of course, the present invention is not limited to the following examples.

[0199] - Create: Request to create PtPTunnel ID, UPF ID, and N6PtPTunnel Context.

[0200] - Cancel: Request to delete the N6PtPTunnel Context identified by PtPTunnel ID and UPF ID.

[0201] - Update: Request to update the N6PtPTunnel Context identified by PtPTunnel ID and UPF ID.

[0202] In step 4, SMF can send the Nsmf_N6PtPTunnel_CreateContext Response message to UPF.

[0203] In step 5, the terminal performs PDU Session Establishment during the PDU Session setup procedure.

[0204] An Accept message can be received. N6PtPTunnel Information may not be visible to the terminal. N6PtPTunnel Information may be information about the connection between the UPF and AF.

[0205] In step 6, MO (Mobile-Oriented) DATA can be transmitted from the terminal to the AF. The MO data can be transmitted using the created Shared PDU Session. The data transmitted from the terminal is transmitted to the UPF, and the UPF can encapsulate the transmitted MO data using UDP / IPv6. Then, the UPF can transmit the encapsulated MO data to the AF using the N6 PtP Tunnel. The AF, which receives the MO data, can receive the data transmitted by the terminal by decapsulating the received MO data using the PtPTunnel Configuration information identified by the PtPTunnel ID.

[0206] In step 7, MT (Mobile-Terminated) DATA can be transmitted from AF to terminal. AF can encapsulate the data to be transmitted using UDP / IPv6 and then transmit the encapsulated MT data to UPF using N6 PtP Tunnel. UPF that receives MT data can decapsulate the received MT data using PtPTunnel Configuration information identified by PtPTunnel ID. UPF can transmit the decapsulated MT data to terminal using Shared PDU Session.

[0207] Of course, the above examples are not limiting. Therefore, at least one action in the above-described procedure may be omitted, or a new action may be added and organically combined with the above-described actions.

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

[0209] The terminal of FIG. 8 may refer to the terminal described through the embodiments of FIGS. 1 to 7.

[0210] A terminal according to one embodiment of the present disclosure may include a processor (820) that controls the overall operation of the terminal, 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 terminal may include more or fewer components than those illustrated in FIG. 8.

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

[0212] According to one embodiment of the present disclosure, the processor (820) can control the terminal to perform any one of the operations of the above-described embodiments. 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.

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

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

[0215] The base station of FIG. 9 may refer to the RAN node described through the embodiments of FIGS. 1 to 7.

[0216] A network entity according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the network entity, a transceiver (900) including a transmitter and a receiver, and a memory (910). 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. 9.

[0217] According to one embodiment of the present disclosure, the transceiver (900) 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.

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

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

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

[0221] The network entity of FIG. 10 may be one of the network entities described through the embodiments of FIGS. 1 to 7.

[0222] A network entity according to one embodiment of the present disclosure may include a processor (1020) that controls the overall operation of the network entity, a transceiver (1000) including a transmitter and a receiver, and a memory (1010). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than the configuration illustrated in FIG. 10.

[0223] According to one embodiment of the present disclosure, the transceiver (1000) 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.

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

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

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

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

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

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

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

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

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

[0233] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the scope of the claims. In other words, it will be apparent to those skilled in the art 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.

[0234] 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 operating an AMF (access and mobility management function) for managing multiple Ambient IoT devices in a wireless communication system, A step of receiving a registration request for a group including multiple Ambient IoT devices from an AF (application function); A step of selecting an AUSF for authentication of the plurality of Ambient IoT devices and performing authentication on the plurality of Ambient IoT devices through the selected AUSF; A step of performing the AM policy association establishment procedure through PCF (policy control function); and A method comprising the step of performing a UE policy association establishment procedure for the plurality of Ambient IoT devices through the PCF.

2. In paragraph 1, A method wherein the above plurality of Ambient IoT devices are distinguished through one of a group ID, a device type ID, a connection type ID, a use case ID, or a unique device ID and the ID of the AF.

3. In paragraph 1, A step of receiving a request message for establishing a shared PDU (protocol data unit) session from at least one of the plurality of Ambient IoT devices; A step for checking whether a shared PDU session has been created for the Ambient IoT device that transmitted the above request message; and A method further comprising the step of selecting a session management function (SMF) capable of supporting a shared PDU session and transmitting a shared PDU session establishment request message to the selected SMF, if a shared PDU session for the Ambient IoT device that transmitted the request message has not been created.

4. In paragraph 3, A method further comprising the step of transmitting a rejection message including information about the created shared PDU session to the Ambient IoT device that transmitted the request message, if a shared PDU session for the Ambient IoT device that transmitted the request message has been created.

5. In paragraph 3, A method wherein the verification of whether a shared PDU session has been created for an Ambient IoT device that transmitted the above request message is performed based on the AF ID, group ID, and PDU session ID included in the above request message.

6. In paragraph 3, A method further comprising the step of broadcasting information about the established shared PDU session through a RAN node when the shared PDU session is established.

7. In paragraph 1, A step of receiving a request message for establishing a shared PDU (protocol data unit) session from at least one of the plurality of Ambient IoT devices; and A method further comprising the step of transmitting the request message to an AMF that supports shared PDU sessions, if the AMF does not support shared PDU sessions.

8. In the AMF (access and mobility management function) that manages multiple Ambient IoT devices in a wireless communication system, Transmitter and receiver; and Includes a control unit, The above control unit, Receive a registration request for a group including multiple Ambient IoT devices from AF (application function), Selecting an AUSF for authentication of the above multiple Ambient IoT devices, and performing authentication on the above multiple Ambient IoT devices through the selected AUSF, Perform AM policy association establishment procedure through PCF (policy control function). AMF, which is set to perform a UE policy association establishment procedure for the plurality of Ambient IoT devices through the PCF.

9. In paragraph 8, The above multiple Ambient IoT devices are distinguished through an ID of one of a group ID, a device type ID, a connection type ID, a use case ID or a unique device ID and an ID of the AF.

10. In paragraph 8, The above control unit, Receive a request message for establishing a shared PDU (protocol data unit) session from at least one of the plurality of Ambient IoT devices, Check whether a shared PDU session has been created for the Ambient IoT device that sent the above request message. If a shared PDU session is not created for the Ambient IoT device that sent the above request message, AMF is further configured to select a session management function (SMF) that can support a shared PDU session and transmit a shared PDU session establishment request message to the selected SMF.

11. In paragraph 10, The above control unit, AMF is further configured to transmit a rejection message including information about the created shared PDU session to the Ambient IoT device that transmitted the request message, if a shared PDU session for the Ambient IoT device that transmitted the request message is created.

12. In paragraph 10, Verification of whether a shared PDU session has been created for the Ambient IoT device that sent the above request message is performed based on the AF ID, group ID, and PDU session ID included in the above request message.

13. In paragraph 10, The above control unit, AMF, which is further configured to broadcast information about the established shared PDU session through RAN nodes when the above shared PDU session is established.

14. In paragraph 8, The above control unit, Receive a request message for establishing a shared PDU (protocol data unit) session from at least one of the plurality of Ambient IoT devices, AMF, which is further configured to send the request message to an AMF that supports shared PDU sessions, if the above AMF does not support shared PDU sessions.

Images