Device and method for selecting UE reader and network function entity for connecting to ambient IoT device in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate, and an operation method of an access and mobility management function (AMF) entity in a wireless communication system according to an embodiment of the present disclosure may comprise the steps of: receiving, from a network exposure function (NEF) entity, an ambient Internet of things (IoT) request message including an application function (AF) identification (ID), a task ID, a tracking area (TA) ID, a user equipment (UE) ID, and an IoT device ID; selecting a gnodeB (gNB) on the basis of the request message and a predetermined priority for information included in the request message; and transmitting the request message to the selected gNB. The predetermined priority may have a higher priority in the order of pre-provided information, the AF ID, the task ID, the TA ID, the UE ID, and the IoT device ID.

Description

Device and method for selecting a UE reader and a network function entity for connecting to an ambient IoT device in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for providing services by connecting to an ultra-low power device in 3GPP 5GS (5G System).

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

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

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

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The present disclosure aims to provide an apparatus and method for selecting a UE reader and a network function entity to provide services by connecting to an ultra-low power device in a wireless communication system, more specifically in 3GPP 5GS (5G System).

[0009] A method of operation of an Access and Mobility Management Function (AMF) entity in a wireless communication system according to an embodiment of the present disclosure may include: receiving an ambient IoT (AIoT) request message from a Network Exposure Function (NEF) entity that includes an Application Function (AF) ID (identification), a task ID, a Tracking Area (TA) ID, a user equipment (UE) ID, and an Internet of Things (IoT) device ID; selecting a gnodeB (gNB) based on a predetermined priority for the request message and the information included in the request message; and transmitting the request message to the selected gNB. The predetermined priority may have a higher priority in the order of the previously provided information, the AF ID, the task ID, the TA ID, the UE ID, and the IoT device ID.

[0010] The operation of selecting the gNB may include: the operation of transmitting the request message to a plurality of gNBs including the gNB; the operation of receiving a response message from at least one gNB among the plurality of gNBs; and the operation of selecting the gNB based on the response message.

[0011] The above request message may be transmitted to at least one UE associated with the UE ID through the gNB. The at least one UE may be selected by the gNB based on the request message and the predetermined priority.

[0012] The above request message may be transmitted to at least one IoT device associated with the IoT device ID through the at least one UE. The at least one IoT device may be selected by the at least one UE based on the request message and the predetermined priority.

[0013] The above operation method may further include: receiving a response message from at least one IoT device; and transmitting the response message to the NEF.

[0014] The operation of transmitting the above response message to the NEF may include, in the case where there are multiple response messages, aggregating multiple response messages based on the priority associated with the response messages or selecting one response message among the multiple response messages. The response message transmitted to the NEF may be the aggregated response message or the selected single response message.

[0015] The above response message may be transmitted from the at least one IoT device to at least one UE. The at least one UE may be selected by the at least one IoT device based on the response message and the priority associated with the response message.

[0016] The above response message may be transmitted from the at least one UE to at least one gNB. The at least one gNB may be selected by the at least one UE based on the response message and the priority associated with the response message.

[0017] The above response message may be transmitted from the at least one gNB. The destination of the response message may be selected by the at least one gNB based on the response message and the priority associated with the response message.

[0018] The above response message can be transmitted to AF via the above NEF.

[0019] In a wireless communication system according to an embodiment of the present disclosure, an Access and Mobility Management Function (AMF) entity may include: a transceiver; and a processor electrically connected to the transceiver. The processor may perform the operation of receiving an ambient IoT (AIoT) request message from a Network Exposure Function (NEF) entity, the AIoT request message including an Application Function (AF) ID (identification), a task ID, a Tracking Area (TA) ID, a user equipment (UE) ID, and an Internet of Things (IoT) device ID; the operation of selecting a gnodeB (gNB) based on a predetermined priority for the request message and the information included in the request message; and the operation of transmitting the request message to the selected gNB. The predetermined priority may have a higher priority in the order of the previously provided information, the AF ID, the task ID, the TA ID, the UE ID, and the IoT device ID.

[0020] The processor may further perform the operation of transmitting the request message to a plurality of gNBs including the gNB; the operation of receiving a response message from at least one gNB among the plurality of gNBs; and the operation of selecting the gNB based on the response message.

[0021] The above request message may be transmitted to at least one UE associated with the UE ID through the gNB. The at least one UE may be selected by the gNB based on the request message and the predetermined priority.

[0022] The above request message may be transmitted to at least one IoT device associated with the IoT device ID through the at least one UE. The at least one IoT device may be selected by the at least one UE based on the request message and the predetermined priority.

[0023] The processor may further perform the operation of receiving a response message from at least one IoT device; and the operation of transmitting the response message to the NEF.

[0024] If there are multiple response messages, the processor may further perform the operation of aggregating multiple response messages based on the priority associated with the response messages, or selecting one of the multiple response messages. The response message transmitted to the NEF may be the aggregated response message or the selected single response message.

[0025] The above response message may be transmitted from the at least one IoT device to at least one UE. The at least one UE may be selected by the at least one IoT device based on the response message and the priority associated with the response message.

[0026] The above response message may be transmitted from the at least one UE to at least one gNB. The at least one gNB may be selected by the at least one UE based on the response message and the priority associated with the response message.

[0027] The above response message may be transmitted from the at least one gNB. The destination of the response message may be selected by the at least one gNB based on the response message and the priority associated with the response message.

[0028] The above response message can be transmitted to AF via the above NEF.

[0029] According to the apparatus and method of the embodiment of the present disclosure, communication efficiency can be increased through the apparatus and method of selecting a UE reader and a network function entity to provide services by connecting to an ultra-low power device in 3GPP 5GS (5G System).

[0030] FIG. 1 is a block diagram of a terminal or user equipment (100) according to one embodiment of the present disclosure.

[0031] FIG. 2 is a block diagram of a base station (200) according to one embodiment of the present disclosure.

[0032] FIG. 3 is a block diagram of a network entity (300) that performs network functions according to one embodiment of the present disclosure.

[0033] FIG. 4 is a flowchart illustrating a message flow for providing services by connecting to an ultra-low power device using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0034] FIGS. 5A and 5B are flowcharts illustrating the flow of a method for selecting a UE Reader and a Network Function to provide services by connecting to an ultra-low power device using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0035] FIGS. 6a and 6b are flowcharts illustrating the message flow of an AIOT Request for connecting to an ultra-low power device and providing services using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0036] FIGS. 7a and 7b are flowcharts illustrating the message flow of an AIOT Request for connecting to an ultra-low power device and providing services using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0037] FIGS. 8a and 8b are flowcharts illustrating the message flow of an AIOT Response for providing services by connecting to an ultra-low power device using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0038] FIGS. 9a and 9b are flowcharts illustrating the message flow of an AIOT Response for providing services by connecting to an ultra-low power device using a UE Reader in a 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0039] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0040] While various details have been described for the purpose of facilitating understanding in describing the embodiments, it will be understood that some aspects of the present disclosure may be practiced without including all such details. Furthermore, various modifications and alternatives are possible regarding the details presented herein, and all of these should be considered to be included within the scope of the present disclosure. Meanwhile, descriptions of technical content that are widely known in the art and may unnecessarily obscure the understanding of the present disclosure may be appropriately omitted, and such omitted descriptions should also be understood to be included within the scope of the present disclosure.

[0041] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0042] The advantages and features of the present disclosure, and the methods for achieving them, will become clear through the embodiments described below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments presented below and may be implemented in various forms. Other features, aspects, and advantages disclosed in the present disclosure will become more clear through the following description of the present disclosure. The following embodiments are merely illustrative to aid in understanding the present disclosure and should not be interpreted in any way as limiting the scope or spirit of the present disclosure. Rather, the present disclosure includes all modifications, changes, and alternatives made within the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Identical or similar components throughout the disclosure are assigned identical or similar reference numerals. Furthermore, terms described below are defined with consideration of their function in the present disclosure and may be used differently depending on the user, operator, or convention. Accordingly, the definitions of terms should be interpreted based on the content of the entire present disclosure.

[0043] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0044] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0045] As used in the embodiments of the present disclosure, the term “part / module” refers to a software or hardware component such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part / module” performs certain roles. However, the term including “part / module” is not limited to software or hardware. The “part / module” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, by example, the “part / module” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts / modules' may be combined into a smaller number of components and 'parts / modules' or further separated into additional components and 'parts / modules'. In addition, the components and 'parts / modules' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Furthermore, in the embodiments, the 'parts / modules' may include one or more processors.

[0046] The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0047] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors may be a circuitry that performs processing, and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor, a microcontroller, a digital signal processor, an FPGA, an ASIC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry. The single processor or combination of processors described above can control the overall operation of an electronic device by executing instructions, such as an operating system, that can be stored in memory. Additionally, the processor or combination of processors can execute other processes or programs residing in memory (e.g., processes related to the present disclosure).

[0048] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0049] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed individually or collectively by one or more processors of an electronic device. Alternatively, said software may be a computer program (or product) that includes instructions that operate an electronic device to perform a method according to the present disclosure when executed individually or collectively by one or more processors of an electronic device.

[0050] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing an apparatus or method according to any one of the claims of the present disclosure, and a non-transient machine-readable storage medium storing such program.

[0051] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0052] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0053] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0054] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0055] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0056] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0057] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0058] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0059] Furthermore, throughout this disclosure, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, elements, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or substantially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same size measured or applied in different situations, or they may represent different sizes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the disclosure and claims.

[0060] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0061] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0062] Furthermore, expressions such as "if" and "in case that" as described in the present disclosure or claims may be interpreted, depending on the context, as meaning "when or upon," "in response to," "based on," or "according to," and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes for these expressions, provided that they do not impair the technical features of the present disclosure. Furthermore, if a method step (e.g., a step of transmitting a signal) is performed in relation to such terms (e.g., "in case that" or similar expressions) in accordance with the disclosure of the present specification, this may be interpreted as the method step being performed in response to a prior determination that a specific element has a specific state (e.g., bit length exceeding X).

[0063] For example, physical layer signaling may be referred to as L1 (Layer 1) signaling and may include downlink control information (DCI). Additionally, upper layer signaling may include at least one of a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (Layer 3) signaling. However, upper layer signaling is not limited to the above examples.

[0064] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0065] Additionally, the phrase “transmitting a message containing A and B” as described in the present disclosure may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0066] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0067] In the embodiments described in this disclosure, terms or components included in the disclosure may be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the context presented for convenience of explanation, and the disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.

[0068] The drawings or flowcharts described in this disclosure illustrate exemplary methods that may be implemented according to the principles of this disclosure, and various modifications may be made to the methods illustrated in the flowcharts of this disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0069] Additionally, the process of the flowchart can be performed by an electronic device, and one or more steps of the flowchart can be implemented by one or more processors that execute instructions to perform specific functions.

[0070] The methods and apparatus proposed in the embodiments of the present disclosure may be disclosed together with drawings including flowcharts to illustrate exemplary methods that may be implemented according to the principles of the present disclosure. Such flowcharts may include different branches and / or sub-branches. It should be understood that the principles of the present disclosure are not limited to combinations of all branches and sub-branches disclosed in the embodiments, and may consist of at least one individual branch or individual sub-branch, in particular only a single branch or a single sub-branch.

[0071] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0072] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.

[0073] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in similar technical specifications of standardization organizations such as 3GPP (3rd generation partnership project) Technical Specifications (TS) or ETSI (European Telecommunications Standards Institute).

[0074] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.

[0075] The terminal may include at least one of user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, tablet, wearable device, Internet of Things (IoT) device, or other device / system capable of performing communication functions.

[0076] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0077] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) 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, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0078] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0079] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, …, or RRC), MAC CE, NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0080] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI, a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0081] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0082] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.

[0083] For the convenience of the following explanation, the present invention uses terms and names defined in the 5GS and NR specifications, which are the most recent standards defined by the 3GPP (The 3rd Generation Partnership Project) among currently existing communication standards. However, the present invention is not limited by the above terms and names and can be applied in the same way to wireless communication networks conforming to other standards. In particular, the present invention can be applied to 3GPP 5GS / NR (5th generation mobile communication standard).

[0084] 3GPP 5GS (5G System) can provide services by connecting ultra-low power devices. To this end, a device wirelessly connected to an ultra-low power device is called a Reader. A BS Reader, in which a base station performs the Reader function, may be used, or a UE Reader, in which a wireless terminal (UE) performs the Reader role, may be used. Among these, in the method of using a UE Reader, a method for selecting multiple UE Readers and Network Functions is required. For example, Ambient IoT (AIoT) can be used.

[0085] Ambient IoT is a portmanteau of "Ambient" and "Internet of Things," and can be used in a communication environment that refers to an ecosystem of numerous objects, all connected to a wireless sensor network using low-cost, self-driving sensor nodes. Applications of Ambient IoT include making food and pharmaceutical supply chains more efficient and sustainable, preventing counterfeiting, and providing data necessary for advanced transportation and smart city initiatives.

[0086] FIG. 1 is a block diagram of a terminal or user equipment (100) according to one embodiment of the present disclosure.

[0087] The terminal (100) is an electronic device capable of wireless communication and may have various form factors. Examples of the terminal may include at least one of a user device (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or other devices / systems capable of performing wireless communication with a base station (BS) and / or other terminals via a wireless channel.

[0088] Referring to FIG. 1, the terminal (100) may include at least one transceiver (101) (hereinafter, transceiver), at least one processor (102) (hereinafter, processor), and at least one memory (103) (hereinafter, memory). The transceiver (101), processor (102), and memory (103) of the terminal (100) may be operated according to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure. However, the components of the terminal (100) are not limited to the examples of components shown in FIG. 1. In other embodiments, the terminal (100) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (101), processor (102), or memory (103) may be integrated into a single component.

[0089] The transceiver (101) may be a basic communication circuit or communication circuitry that enables the terminal (100) to perform wireless communication with a node or entity of a network. For example, the transceiver (101) may enable the terminal (100) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the transceiver (101) may be 3G (3rd generation), 4G (4th generation), LTE (long-term evolution), 5G (5th generation), NR (new radio), 6G (6th It can support at least one of various cellular wireless communication technologies including generation), and the various cellular wireless communication technologies supported by the transceiver (101) may include all subsequent evolved generations of wireless communication.

[0090] According to one embodiment, the terminal (100) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (100) supports NR-DC (NR Dual Connectivity), the terminal (100) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (100) supports short-range wireless communication, the terminal (100) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, IEEE (institute of electrical and electronics engineer) 802.11-2016 standard or modifications thereof such as 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0091] According to one embodiment, the transceiver (101) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (101) may be configured to include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (101) may output the signal received via the wireless channel to a processor (102) and transmit the signal output from the processor (102) via the wireless channel.

[0092] A processor (102) can control the overall operation of a terminal (100) according to an embodiment of the present disclosure. The processor (102) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may execute various data processing operations. The processor (102) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (103) individually, collectively, or in any combination. Additionally, the processor (102) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0093] The processor (102) is electrically, operatively, and / or communicatively coupled to the transceiver (101) so as to control the transceiver (101).

[0094] The processor (102) may include at least one processor (or, processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (102) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (102) may be included in one chip (or, IC), and another part of the processor (102) may be included in a separate chip (or, IC). Alternatively, at least one processor may be included in other components, e.g., a transceiver (101) or a memory (103).

[0095] The processor (102) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (102) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (102) may control other components of the terminal (100) to perform various operations by executing computer programs, code, or instructions stored in memory (103).

[0096] Memory (103) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (103) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0097] The memory (103) can be electrically, operatively, and / or communicatively coupled to the processor (102) and can be accessed by the processor (102).

[0098] A computer program, code, or instruction that can be executed by a processor (102) may be stored in the memory (103). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (102) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (102) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (103).

[0099] According to one embodiment of the present disclosure, the operation of the terminal (100) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (103), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0100] FIG. 2 is a block diagram of a base station (200) according to one embodiment of the present disclosure.

[0101] The base station (200) can perform wireless communication with at least one terminal within the area of ​​the base station (200) via a wireless channel. The base station (200) can perform communication with a node or entity of the network via wired or wireless communication.

[0102] Referring to FIG. 2, a base station (200) may include at least one transceiver (201) (hereinafter, transceiver), at least one processor (202) (hereinafter, processor), and at least one memory (203) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (201), processor (202), and memory (203) of the base station (200) may be operated. However, the components of the base station (200) are not limited to the examples of components shown in FIG. 2. In other embodiments, the base station (200) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (201), processor (202), or memory (203) may be integrated into a single component.

[0103] The transceiver (201) may be a communication circuit or communication circuitry that enables the base station (200) to perform wireless communication with a node or entity of the network. For example, the transceiver (201) may enable the base station (200) to transmit and receive signals to and from a terminal (100) via cellular wireless communication or to transmit and receive signals to and from another network entity via wireless communication. For example, the transceiver (201) may be 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation) Various cellular wireless communication technologies, including (generation), etc., can be supported, and the various cellular wireless communication technologies supported by the transceiver (201) may include all subsequent evolved generations of wireless communication. According to one embodiment, the transceiver (201) may include various circuit structures used to transmit and receive signals to and from a terminal via a wireless channel. The signals may include control information and data. For example, the transceiver (201) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (201) may output the signal received via the wireless channel to a processor (202) and transmit the signal output from the processor (202) via the wireless channel.

[0104] Meanwhile, according to one embodiment of the present disclosure, a base station (200) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (200) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (200) performs wired communication, the base station (200) may include a separate network interface for wired communication in addition to the transceiver (201). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0105] The processor (202) can control the overall operation of the base station (200) according to an embodiment of the present disclosure. The processor (202) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (202) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (203) individually, collectively, or in any combination. Additionally, the processor (202) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0106] The processor (202) is electrically, operatively, and / or communicatively coupled to the transceiver (201) so as to control the transceiver (201).

[0107] The processor (202) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (202) may be included in one chip (or IC), and another part of the processor (202) may be included in a separate chip (or IC). Alternatively, at least one processor may be included in other components, such as a transceiver (201) or memory (203).

[0108] The processor (202) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (202) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (202) may control other components of the base station (200) to perform various operations by executing computer programs, codes, and instructions stored in memory (203).

[0109] Memory (203) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (203) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0110] The memory (203) can be electrically, operatively, and / or communicatively coupled to the processor (202) and can be accessed by the processor (202).

[0111] A computer program, code, or instruction that can be executed by a processor (202) may be stored in the memory (203). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (202) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (202) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (203).

[0112] According to one embodiment of the present disclosure, the operation of a base station (200) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (203), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.

[0113] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.

[0114] FIG. 3 is a block diagram of a network entity (300) that performs network functions according to one embodiment of the present disclosure.

[0115] A network entity (300) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (300).

[0116] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.

[0117] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0118] Referring to FIG. 3, a network entity (300) may include at least one network interface (301), at least one processor (302) (hereinafter referred to as processor), and at least one memory (303) (hereinafter referred to as memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (300), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 3. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.

[0119] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (301), processor (302), and memory (303) of the network entity (300) may be operated. However, the components of the network entity (300) are not limited to the examples of components shown in FIG. 3. In other embodiments, the network entity (300) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (301), processor (302), or memory (303) may be implemented as a single component.

[0120] The network interface (301) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or other network entities. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (301) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (301) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (301) may be referred to as a communication circuitry, a network interface circuitry, or a communication interface circuitry.

[0121] The processor (302) may control the overall operation of the network entity (300) according to an embodiment of the present disclosure. In one embodiment, the processor (302) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (302) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (303) individually, collectively, or in any combination. Additionally, the processor (302) may include a single-core processor or a multi-core processor, and in a specific implementation method, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (302) may not necessarily be composed of physical hardware when the network function (300) is implemented in an instance form according to another embodiment.

[0122] According to one embodiment, the processor (302) is electrically, operatively, and / or communicatively coupled to the network interface (301) so as to control the network interface (301).

[0123] The processor (302) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (302) may be included in one chip (or IC), and another part of the processor (302) may be included in a separate chip (or IC). Alternatively, at least one processor may be included in other components, such as a network interface (301) or memory (303).

[0124] The processor (302) may perform or control the operation of a network entity (300) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (302) may control the operation of the network entity (300) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (302) may control other components of the network entity (300) to perform various operations by executing computer programs, code, or instructions stored in memory (303).

[0125] Memory (303) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (303) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0126] According to one embodiment, the memory (303) may be electrically, operatively, and / or communicatively coupled to the processor (302) and may be accessed by the processor (302).

[0127] A computer program, code, or instruction that can be executed by a processor (302) may be stored in the memory (303). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (302) may be stored in a single memory or separated and distributed across two or more memories. The processor (302) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (303).

[0128] According to one embodiment of the present disclosure, the operation of a network entity (300) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (303), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.

[0129] FIG. 4 is a flowchart illustrating a message flow for providing services by connecting to an ultra-low power device using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0130] Referring to FIG. 4, in step S101, AF (700) can send an IoT service request message (AF request) to AIoTF (600) via NEF (600). The AF request message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. Inventory may be a service that identifies the devices responsible for the service. Command may be a service that requests a specific operation, such as Read or Write, from the target device.

[0131] In step S102, the AIoTF (600) can send an AIoT Request message to the AMF (1). The AIoT Request message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. The AIoTF (600) can select the necessary AMF from among multiple AMFs (1, 2).

[0132] In step S103, at least one of AMF1 (1) or AMF2 (2) may send an AIoT Request message to at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22). The AIoT Request message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. At least one of AMF1 (1) or AMF (2) may select a required gNB from among a plurality of gNBs (11, 12, 21, 22).

[0133] In step S104, at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) may send an AIoT Request message to at least one of the UE Readers UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), or UE222 (222). The AIoT Request message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. At least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) can select the required UE Reader from among a plurality of UE Readers (111, 112, 121, 122, 211, 212, 221, 222).

[0134] In step S105, at least one of the UE Readers UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), or UE222 (222) is Device1111 (1111), Device1112 (1112), Device1121 (1121), Device1122 (1122), Device1211 (1211), Device1212 (1212), Device1221 (1221), Device1222 (1222), Device2111 (2111), Device2112 (2112), Device2121 (2121), Device2122 (2122), Device2211 (2211), Device2212 (2212), Device2211 (2211), Device2212 (2212), An AIoT Request message may be sent to at least one of Device2221 (2221) or Device2222 (2222). The AIoT Request message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. At least one of the UE Readers UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), or UE222 (222) can select the necessary device from a plurality of devices (1111, 1112, 1121, 1122, 1211, 1212, 1221, 1222, 2111, 2112, 2121, 2122, 2211, 2212, 2221, 2222).

[0135] In step S106, at least one of Device1111(1111), Device1112(1112), Device1121(1121), Device1122(1122), Device1211(1211), Device1212(1212), Device1221(1221), Device1222(1222), Device2111(2111), Device2112(2112), Device2121(2121), Device2122(2122), Device2211(2211), Device2212(2212), Device2221(2221), or Device2222(2222) is a UE Reader UE111(111), UE112(112), UE121(121), UE122(122), UE211(211), UE212(212), UE211(211), UE212(212), UE211(211), UE212(212), An AIoT Response message may be sent to at least one of UE221 (221) or UE222 (222). The AIoT Response message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command.At least one of Device 1111 (1111), Device 1112 (1112), Device 1121 (1121), Device 1122 (1122), Device 1211 (1211), Device 1212 (1212), Device 1221 (1221), Device 1222 (1222), Device 2111 (2111), Device 2112 (2112), Device 2121 (2121), Device 2122 (2122), Device 2211 (2211), Device 2212 (2212), Device 2221 (2221), or Device 2222 (2222) can select a required UE Reader from among a plurality of UE Readers (111, 112, 121, 122, 211, 212, 221, 222). And, when at least one of the plurality of UE Readers (111, 112, 121, 122, 211, 212, 221, 222) receives a response message from at least one of the plurality of Devices (1111, 1112, 1121, 1122, 1211, 1212, 1221, 1222, 2111, 2112, 2121, 2122, 2211, 2212, 2221, 2222), at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) can select or aggregate the response message.

[0136] In step S107, at least one of the UE Readers UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), or UE222 (222) may send an AIoT Response message to at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22). The AIoT Response message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. At least one of the UE Readers UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), or UE222 (222) can select the necessary gNB from among a plurality of gNBs (11, 12, 21, 22). And, when at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) receives a response message from at least one of a plurality of UE Readers (111, 112, 121, 122, 211, 212, 221, 222), at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) can select or aggregate the response message.

[0137] In step S108, at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) may send an AIoT Response message to at least one of AMF1 (1) or AMF2 (2). The AIoT Response message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. At least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) may select the necessary AMF from among a plurality of AMFs (1, 2). And, if at least one of AMF1 (1) or AMF (2) receives a response message from one of the multiple gNBs (11, 12, 21, 22), AMF1 (1) or AMF (2) can select or aggregate the response message.

[0138] In step S109, at least one of AMF1 (1) or AMF2 (2) may transmit an AIoT Response message to the AIoTF (600). The AIoT Response message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. At least one of AMF1 (1) or AMF2 (2) may select the necessary AIoTF from among the plurality of AIoTFs (600). And, when the AIoTF (600) receives response messages from the plurality of AMFs (1, 2), the AIoTF (600) may select or aggregate the response messages.

[0139] In step S110, the AIoTF / NEF (600) can send an AIoT Response message to the AF (700). The AIoT Response message may include Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), Inventory, or Command. The AIoTF / NEF (600) can select the necessary AF from among multiple AFs. And, if the AF (700) receives response messages from multiple AIOTF / NEFs, the AF (700) can select or aggregate the response messages.

[0140] FIGS. 5A and 5B are flowcharts illustrating the flow of a method for selecting a UE Reader and a Network Function to provide services by connecting to an ultra-low power device using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0141] Referring to FIG. 5a, at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF can receive an Inventory Request message (S211). At least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF can check whether a Context such as Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID) associated with the Inventory Request message is stored (S212). If at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF has the corresponding Context stored, it may select the UE Reader or NF that is next in line to receive according to the Context and deliver the Inventory Request message (S213). If at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF has the corresponding Context not stored, it may deliver the Inventory Request message to all capable UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF (S214).

[0142] Referring to FIG. 5b, at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF can transmit an Inventory Response message (S221). At least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF can check whether the context associated with the Inventory Response message, such as Device IDs, UE IDs, Validity Time Condition, Location Condition, Task ID (or Session ID, Service ID, Transaction ID), etc., is stored (S222). If at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF has the corresponding Context stored, it may select the UE Reader or NF that is next in line to receive according to the Context and deliver the Inventory Response message (S223). If at least one of the UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF has the corresponding Context not stored, it may deliver the Inventory Response message to all UE Readers (111, 112, 121, 122, 211, 212, 221, 222) or NF that can receive (S224).

[0143] FIGS. 6a and 6b are flowcharts illustrating the message flow of an AIOT Request for connecting to an ultra-low power device and providing services using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0144] Referring to FIG. 6a and FIG. 6b, a 3GPP 5GS (5G System) according to an embodiment of the present disclosure may include a plurality of Devices (e.g., Device 1 (100-1), Device 2 (100-1)), a plurality of UE Readers (e.g., UE 1 (200-1), UE 2 (200-2)), a plurality of Base Stations (e.g., gNB1 (300-1) to gNBm (300-m)), a plurality of AMFs (e.g., AMF1 (400-1) to AMFn (400-n)), UDM1 / UDR1 (500), NEF / AIoTF (600), and AF (700). According to the embodiments of the present disclosure, there may be multiple AIoTFs (600) responsible for AIoT functions, but for convenience of explanation in FIG. 6a and FIG. 6b, it is assumed that the number of AIoTFs (600) connected to one AF (700) is set to one in advance in the AF (700) or NEF (600), but the embodiments of the present disclosure are not limited thereto.

[0145] At least one of Device1 (100-1) or Device2 (100-1) may be substantially identical or similar to at least one of Device1111 (1111), Device1112 (1112), Device1121 (1121), Device1122 (1122), Device1211 (1211), Device1212 (1212), Device1221 (1221), Device1222 (1222), Device2111 (2111), Device2112 (2112), Device2121 (2121), Device2122 (2122), Device2211 (2211), Device2212 (2212), Device2221 (2221), or Device2222 (2222) of FIG. 4.

[0146] At least one of UE1 (200-1) or UE2 (200-2) may be substantially identical or similar to at least one of UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), or UE222 (222) of FIG. 4.

[0147] gNB1 (300-1) to gNBm (300-m) may be substantially identical or similar to at least one of gNB11 (11), gNB12 (12), gNB21 (21), or gNB22 (22) of FIG. 4.

[0148] At least one of AMF1 (400-1) to AMFn (400-n) may be substantially identical or similar to at least one of AMF1 (1) or AMF2 (2) of FIG. 4.

[0149] NEF / AIoTF (600) may be substantially the same or similar to NEF / AIoTF (600) of FIG. 4.

[0150] AF (700) may be substantially the same or similar to AF (700) of FIG. 4.

[0151] In steps S300a and S300b, UE1 (200-1) and UE2 (200-2) can perform registration with the Network in advance. In step S300a, UE1 (200-1) can send a Registration Request message to UDM1 / UDR1 (500). In step S300b, UE2 (200-2) can send a Registration Request message to UDM1 / UDR1 (500). The Registration Request message may include AIoT UE Reader Capability and UE Reader Indication. UDM1 / UDR1 (500) can send the Registration Request message received from UE1 (200-1) and UE2 (200-2) to AMF1 (400-1). AMF1 (400-1) can receive the Registration Request message from UDM1 / UDR1 (500). AMF1 (400-1) can receive subscription information from UDM1 / UDR1 (500). AMF1 (400-1) can check whether the AIoT UE Reader Subscription is stored in UE1 (200-1) and UE2 (200-2). If AMF1 (400-1) confirms that the AIoT UE Reader Subscription is stored in UE1 (200-1) and UE2 (200-2), it can transmit the AIoT UE Reader Subscription to be stored in UDM1 / UDR1 (500) and AMF1 (400-1). AMF1 (400-1) can transmit a message to UE1 (200-1) and UE2 (200-2) allowing them to operate as UE Readers.

[0152] In step S300d, AF (700) can select AIoTF / NEF based on available information such as Device ID, UE ID, Location (Geographical), and Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0153] Info priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > Location > UE ID > Device ID. For example, AF (700) can select NEF / AIoTF (600) based on the available information and the priority.

[0154] In step S300c prior to step S300d, AF (700) can check available areas in advance by sending an inquiry message (AIoT service area query) to inquire about AIoT service availability area information provided by the Network and receiving a response message (AIoT service area response) to the inquiry message.

[0155] For example, AF (700) can send an inquiry message (AIoT Service Area Query) to NEF / AIoTF (600) to inquire about AIoT service area information provided by the Network. NEF / AIoTF (600) can receive an inquiry message (AIoT Service Area Query) from AF (700) to inquire about AIoT service area information provided by the Network. NEF / AIoTF (600) can send a response message to AF (700) regarding the inquiry message. AF (700) can receive a response message regarding the inquiry message from NEF / AIoTF (600). AF (700) can identify the AIoT service area based on the response message received from NEF / AIoTF (600).

[0156] AF (700) may not be able to confirm the selection of an AIoTF / NEF due to insufficient information for selecting an AIoTF / NEF, or may decide to select an AIoTF / NEF later. AF (700) may send an AIoT Request message to a plurality of selectable AIoTF / NEFs, including AIoTF / NEF (600). AF (700) may receive an AIoT Response message transmitted from at least one of the plurality of AIoTF / NEFs. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0157] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0158] For example, AF (700) can select NEF / AIoTF (600) based on information included in the AIoT Response message and the priority of said information.

[0159] In step S301, AF (700) can send an AF request message to NEF / AIoTF (600). NEF / AIoTF (600) can receive an AF request message from AF (700).

[0160] In step S301-1, NEF / AIoTF (600) can select AMF 1 (400-1) based on the AF request message.

[0161] In step S301-2, NEF / AIoTF (600) may send a UDM subscribe message to UDM1 / UDR1 (500) requesting notification of the AMFs where the corresponding Locations (TA IDs) and corresponding UE Readers (UEs with UE capability and UE Subscription) are located. UDM1 / UDR1 (500) may receive a UDM subscribe message from NEF / AIoTF (600) requesting notification of the AMFs where the corresponding Locations (TA IDs) and corresponding UE Readers (UEs with UE capability and UE Subscription) are located.

[0162] In step S301-3, UDM1 / UDR1 (500) may send a UDM subscribe message to AMF1 (400-1) requesting notification of the location change when a location change of the corresponding UE occurs. AMF1 (400-1) may receive a UDM subscribe message from UDM1 / UDR1 (500) requesting notification when a location change of the corresponding UE occurs.

[0163] In step S301-4, AMF1 (400-1) can generate a notify message based on a UDM subscribe message requesting notification of the corresponding Location (TA ID) and the corresponding UE Reader (UEs with UE capability and UE Subscription).

[0164] In step S301-5, AMF1 (400-1) can send a notification message to UDM1 / UDR1 (500). UDM1 / UDR1 (500) can receive a notification message from AMF1 (400-1). UDM1 / UDR1 (500) can send a notification message to NEF / AIoTF (600). NEF / AIoTF (600) can receive a notification message from UDM1 / UDR1 (500).

[0165] In step S301-6, NEF / AIoTF (600) can determine the corresponding UE and the corresponding AMF based on the notification message. NEF / AIoTF (600) can determine to map the determined UE Reader to a Task ID (or Session ID, Service ID, Transaction ID).

[0166] In step S302, the AIoTF / NEF (600) can select an AMF based on available information such as Device ID, UE ID, Location (TA ID (or cell ID / gNB ID)), Task ID (or Session ID, Service ID, Transaction ID). The AIoTF / NEF (600) can convert the Geographical Location information received from the AF (700) into Location information assigned by the Network, such as a TA (tracking area) ID (or cell ID / gNB ID). The information priority of the available information may be as follows.

[0167] Info priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0168] For example, AIoTF / NEF (600) can select AMF1 (400-1) based on the available information and the priority.

[0169] AIoTF / NEF (600) may not be able to confirm the selection of an AMF due to insufficient information for selecting an AMF, or may decide to select an AMF later. AIoTF / NEF (600) may send an AIoT Request message to selectable AMF1 (400-1) to AMFn (400-n). AIoTF / NEF (600) may receive an AIoT Response message from at least one AMF among AMF1 (400-1) to AMFn (400-n). AIoTF / NEF (600) may select AMF1 (400-1) based on the information included in the AIoT Response message. The priority of the information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0170] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0171] For example, AIoTF / NEF (600) can select AMF1 (400-1) based on information included in the AIoT Response message and the priority of said information.

[0172] In step S302-1, AMF1 (400-1) can select a gNB based on available information such as Device ID, UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0173] Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0174] For example, AMF1 (400-1) can select gNB1 (300-1) based on the available information and the priority.

[0175] AMF1 (400-1) can send an AIoT request message to gNB1 (300-1). gNB1 (300-1) can receive an AIoT request message from AMF1 (400-1).

[0176] If the selected gNB rejects the request according to the AIoT request message due to a lack of resources or inability to connect to the corresponding UE, the gNB may be excluded from the selection candidates.

[0177] AMF1(400-1) may not be able to confirm a choice due to insufficient information, or may decide to make a choice later.

[0178] In step S303, AMF1 (400-1) can send an AIoT Request message to selectable gNB1 (300-1) to gNBm (300-m). AMF1 (400-1) can receive an AIoT Response message sent from at least one of gNB1 (300-1) to gNBm (300-m). The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0179] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0180] For example, AMF1 (400-1) can select gNB1 (300-1) based on information included in the AIoT Response message and the priority of said information.

[0181] In step S303-1, gNB1 (300-1) can select a UE Reader based on available information such as Device ID, UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0182] Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0183] For example, gNB1 (300-1) can select UE1 (200-1) as the UE Reader based on the available information and the priority.

[0184] gNB1(300-1) may not be able to confirm the selection of a UE Reader due to a lack of information for selecting a UE Reader, or may decide to select a UE Reader later.

[0185] In step S304, gNB1 (300-1) can transmit an AIoT Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 1). gNB1 (300-1) can receive an AIoT Response message from at least one of the UE Readers. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0186] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0187] For example, gNB1 (300-1) can select UE1 (200-1) as the UE Reader based on the information included in the AIoT Response message and the priority above.

[0188] If gNB1(300-1) fails to send an AIoT Request message to at least one of the UE Readers due to reasons such as resource shortage, the UE Reader that did not receive the AIoT Request message may be excluded from the selection candidates.

[0189] In step S304-1, UE 1 (200-1), a UE reader, can select at least one device (100-1, 100-2) based on available information such as Device ID, Location (TA ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection Info Priority) may be as follows.

[0190] Selection Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0191] For example, UE 1 (200-1) can select Device1 (100-1) based on the available information and the priority.

[0192] UE1 (200-1) may not be able to confirm the selection of a device because there is insufficient information to select a device, or may decide to select a device later.

[0193] In step S305, UE1 (200-1) can send an AIoT Request message to a plurality of selectable devices including Device1 (100-1) and Device2 (100-2) of FIG. 1 (e.g., Device1111 (1111), Device1112 (1112), Device1121 (1121), Device1122 (1122), Device1211 (1211), Device1212 (1212), Device1221 (1221), Device1222 (1222), Device2111 (2111), Device2112 (2112), Device2121 (2121), Device2122 (2122), Device2211 (2211), Device2212 (2212), Device2221 (2221), and Device2222 (2222)). UE1 (200-1) can receive an AIoT Response message transmitted from at least one of multiple devices. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0194] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0195] For example, UE1 (200-1) can select Device1 (100-1) and Device2 (100-2) based on information included in the AIoT Response message and the priority of said information.

[0196] FIGS. 6a and 6b illustrate a case where UE1 (200-1), a UE Reader, transmits a Request message to Device1 (100-1) and Device2 (100-2) in step S305 for convenience of explanation, but the embodiments of the present disclosure are not limited thereto.

[0197] FIGS. 7a and 7b are flowcharts illustrating the message flow of an AIOT Request for connecting to an ultra-low power device and providing services using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0198] Referring to FIGS. 7a and 7b, a 3GPP 5GS (5G System) according to an embodiment of the present disclosure may include a plurality of Devices (e.g., Device 1 (100-1), Device 2 (100-2), a plurality of UE Readers (e.g., UE 1 (200-1), UE 2 (200-2), a plurality of Base Stations (e.g., gNB1 (300-1) to gNBm (300-m)), a plurality of AMFs (e.g., AMF1 (400-1) to AMFn (400-n)), UDM1 / DUR1 (500), NEF / AIoTF (600), and AF (700). Although there may also be a plurality of AIoTFs (600) responsible for AIoT functions, FIGS. 7a and 7b indicate that the number of AIoTFs (600) connected to one AF (700) is predetermined as one AF (700) or It is assumed that it is set in NEF(600), but embodiments of the present disclosure are not limited thereto.

[0199] In steps S400a and S400b, UE1 (200-1) and UE2 (200-2) may perform registration for the Network in advance. In step S400a, UE1 (200-1) may send a Registration Request message to UDM1 / UDR1 (500). In step S400b, UE2 (200-2) may send a Registration Request message to UDM1 / UDR1 (500). The Registration Request message may include AIoT UE Reader Capability and UE Reader Indication. UDM1 / UDR1 (500) may send the Registration Request message received from UE1 (200-1) and UE2 (200-2) to AMF1 (400-1). AMF1 (400-1) may receive the Registration Request message from UDM1 / UDR1 (500). AMF1 (400-1) can receive subscription information from UDM1 / UDR1 (500). AMF1 (400-1) can check whether the AIoT UE Reader Subscription is stored in UE1 (200-1) and UE2 (200-2). If AMF1 (400-1) confirms that the AIoT UE Reader Subscription is stored in UE1 (200-1) and UE2 (200-2), it can transmit the AIoT UE Reader Subscription to be stored in UDM1 / UDR1 (500) and AMF1 (400-1). AMF1 (400-1) can transmit a message to UE1 (200-1) and UE2 (200-2) allowing them to operate as UE Readers.

[0200] In step S400d, AF (700) can select AIoTF / NEF based on available information such as Device ID, UE ID, Location (Geographical), Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0201] Info priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > Location > UE ID > Device ID

[0202] For example, AF (700) can select AIoTF / NEF (600) based on the available information and the priority of the information.

[0203] In step S400c prior to step S400d, AF (700) can check available areas in advance by sending an inquiry message (AIoT service area query) to inquire about AIoT service availability area information provided by the Network and receiving a response message (AIoT service area response) to the inquiry message.

[0204] For example, AF (700) can send an inquiry message (AIoT Service Area Query) to NEF / AIoTF (600) to inquire about AIoT service area information provided by the Network. NEF / AIoTF (600) can receive an inquiry message (AIoT Service Area Query) from AF (700) to inquire about AIoT service area information provided by the Network. NEF / AIoTF (600) can send a response message to AF (700) regarding the inquiry message. AF (700) can receive a response message regarding the inquiry message from NEF / AIoTF (600). AF (700) can identify the AIoT service area based on the response message received from NEF / AIoTF (600).

[0205] AF (700) may not be able to confirm the selection of an AIoTF / NEF due to insufficient information for selecting an AIoTF / NEF, or may decide to select an AIoTF / NEF later. AF (700) may send an AIoT Request message to a plurality of selectable AIoTF / NEFs, including AIoTF / NEF (600). AF (700) may receive an AIoT Response message transmitted from at least one of the plurality of AIoTF / NEFs. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0206] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0207] For example, AF (700) can select AIoTF / NEF (600) based on information included in the AIoT Response message and the priority of said information.

[0208] In step S401, AF (700) can send an AF request message to the selected NEF / AIoTF (600). NEF / AIoTF (600) can receive an AF request message from AF (700).

[0209] In step S401-1, NEF / AIoTF (600) can select AMF 1 (400-1) based on the AF request message.

[0210] In step S401-2, AIoTF / NEF (600) may send a UDM subscribe message to UDR1 / UDM1 (500) requesting notification of the corresponding Locations (TA IDs) and the AMFs where the corresponding UE Readers (UEs with UE capability and UE Subscription) are located. UDM1 / UDR1 (500) may receive a UDM subscribe message from NEF / AIoTF (600) requesting notification of the corresponding Locations (TA IDs) and the AMFs where the corresponding UE Readers (UEs with UE capability and UE Subscription) are located.

[0211] In step S401-3, UDM1 / UDR1 (500) may send a UDM subscribe message to AMF1 (400-1) requesting notification of the location change when a location change of the corresponding UE occurs. AMF1 (400-1) may receive a UDM subscribe message from UDM1 / UDR1 (500) requesting notification of the location change when a location change of the corresponding UE occurs.

[0212] In step S401-4, AMF1 (400-1) can generate a notify message based on a UDM subscribe message requesting notification of the corresponding Location (TA ID) and the corresponding UE Reader (UEs with UE capability and UE Subscription).

[0213] In step S401-5, AMF1 (400-1) can send a notification message to UDM1 / UDR1 (500). UDM1 / UDR1 (500) can receive a notification message from AMF1 (400-1). UDM1 / UDR1 (500) can send a notification message to NEF / AIoTF (600). NEF / AIoTF (600) can receive a notification message from UDM1 / UDR1 (500).

[0214] In step S401-6, NEF / AIoTF (600) can determine the corresponding UE and the corresponding AMF based on the notification message. NEF / AIoTF (600) can determine to map the determined UE Reader to a Task ID (or Session ID, Service ID, Transaction ID).

[0215] In step S402, the AIoTF / NEF (600) can select an AMF based on available information such as Device ID, UE ID, Location (TA ID (or cell ID / gNB ID)), Task ID (or Session ID, Service ID, Transaction ID). The AIoTF / NEF (600) can convert the Geographical Location information received from the AF (700) into Location information assigned by the Network, such as a TA (tracking area) ID (or cell ID / gNB ID). The information priority of the available information may be as follows.

[0216] Info priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0217] For example, AIoTF / NEF (600) can select AMF1 (400-1) based on the available information and the info priority.

[0218] AIoTF / NEF (600) may not be able to confirm the selection of an AMF due to insufficient information for selecting an AMF, or may decide to select an AMF later. AIoTF / NEF (600) may send an AIoT Request message to selectable AMF1 (400-1) to AMFn (400-n). AIoTF / NEF (600) may receive an AIoT Response message sent from at least one of AMF1 (400-1) to AMFn (400-n). The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0219] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0220] For example, AIoTF / NEF (600) can select AMF1 (400-1) based on information included in the AIoT Response message and the priority of said information.

[0221] In step S402-1, AMF1 (400-1) can select a gNB based on available information such as Device ID, UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0222] Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0223] For example, AMF1 (400-1) can select a gNB based on the available information and the priority. AMF1 (400-1) can send an AIoT request message to the selected gNB. The selected gNB can receive an AIoT request message from AMF1 (400-1).

[0224] If the selected gNB rejects the request according to the AIoT request message due to a lack of resources or inability to connect to the corresponding UE, the gNB may be excluded from the selection candidates.

[0225] AMF1(400-1) may not be able to confirm the selection of gNB due to a lack of information to select gNB, or may decide to select gNB later.

[0226] In step S403, AMF1 (400-1) can send an AIoT Request message to selectable gNB1 (300-1) to gNBm (300-m). AMF1 (400-1) can receive an AIoT Response message sent from at least one of gNB1 (300-1) to gNBm (300-m). The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0227] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0228] For example, AMF1 (400-1) can select gNB1 (300-1) based on the information included in the AIoT Response message and the priority above.

[0229] In step S403-1, gNB1 (300-1) can select a UE Reader based on available information such as Device ID, UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0230] Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0231] For example, gNB1 (300-1) can select a UE Reader based on the available information and the priority.

[0232] gNB1(300-1) may not be able to confirm the selection of a UE Reader due to a lack of information for selecting a UE Reader, or may decide to select a UE Reader later.

[0233] In step S404, gNB1 (300-1) can transmit an AIoT Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 1). gNB1 (300-1) can receive an AIoT Response message transmitted from at least one of the UE Readers. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0234] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0235] For example, gNB1 (300-1) can select UE1 (200-1) as the UE Reader based on the information included in the AIoT Response message and the priority above.

[0236] If gNB1(300-1) fails to send an AIoT Request message to at least one of the UE Readers due to reasons such as resource shortage, the UE Reader that did not receive the AIoT Request message may be excluded from the selection candidates.

[0237] In step 404-1, UE1 (200-1), a UE reader, can select a Device based on available information such as Device ID, Location (TA ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection Info Priority) may be as follows.

[0238] Selection Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0239] For example, UE1 (200-1) can select Device1 (100-1) and Device2 (100-2) based on the available information and the priority.

[0240] UE1 (200-1) may not be able to confirm the selection of a device because there is insufficient information to select a device, or may decide to select a device later. UE1 (200-1) can send an AIoT Request message to a plurality of selectable devices including Device1 (100-1) and Device2 (100-2) of FIG. 1 (e.g., Device1111 (1111), Device1112 (1112), Device1121 (1121), Device1122 (1122), Device1211 (1211), Device1212 (1212), Device1221 (1221), Device1222 (1222), Device2111 (2111), Device2112 (2112), Device2121 (2121), Device2122 (2122), Device2211 (2211), Device2212 (2212), Device2221 (2221), and Device2222 (2222)). UE1 (200-1) can receive an AIoT Response message transmitted from at least one of a plurality of devices. UE1 (200-1) can select at least one of the plurality of devices based on information included in the AIoT Response message. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0241] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0242] For example, UE1 (200-1) can select Device1 (100-1) and Device2 (100-2) based on the information included in the AIoT Response message and the priority.

[0243] FIGS. 7a and 7b illustrate an embodiment in which UE1 (200-1), a UE Reader, simultaneously transmits an AIoT Request message to Device1 (100-1) and Device2 (200-2).

[0244] In step S402a, the AIoTF / NEF (600) can select an AMF based on available information such as Device ID, UE ID, Location (TA ID (or cell ID / gNB ID)), Task ID (or Session ID, Service ID, Transaction ID). The AIoTF / NEF (600) can convert the Geographical Location information received from the AF (700) into Location information assigned by the Network, such as a TA (tracking area) ID (or cell ID / gNB ID). The priority of the available information may be as follows.

[0245] Info priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0246] For example, AIoTF / NEF (600) can select AMFn (400-n) based on the available information and the priority.

[0247] AIoTF / NEF (600) may not be able to confirm the selection of an AMF due to insufficient information for selecting an AMF, or may decide to select an AMF later. AIoTF / NEF (600) may send an AIoT Request message to selectable AMF1 (400-1) to AMFn (400-n). AIoTF / NEF (600) may receive an AIoT Response message sent from at least one of AMF1 (400-1) to AMFn (400-n). The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0248] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0249] For example, AIoTF / NEF (600) can select AMFn (400-n) based on information included in the AIoT Response message and the priority of said information.

[0250] In step S402-1a, AMFn (400-n) can select a gNB based on available information such as Device ID, UE ID, TA ID (or cell ID / gNB ID), Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0251] Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0252] For example, AMFn (400-n) can select gNBm (300-m) based on the available information and the priority.

[0253] AMFn (400-n) may not be able to confirm the selection of gNB due to insufficient information for selecting gNB, or may decide to select gNB later. AMFn (400-n) may send an AIoT Request message to selectable gNB1 (300-1) to gNBm (300-m). AMFn (400-n) may receive an AIoT Response message transmitted from at least one of gNB1 (300-1) to gNBm (300-m). The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0254] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0255] For example, AMFn (400-n) can select gNBm (300-m) based on information included in the AIoT Response message and the priority of said information.

[0256] In step S403-1a, gNBm (300-m) can select a UE Reader based on available information such as Device ID, UE ID, TA ID (or cell ID / gNB ID), Task ID (or Session ID, Service ID, Transaction ID). The information priority of the available information may be as follows.

[0257] Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0258] For example, gNBm(300-m) can select a UE Reader based on the available information and the priority.

[0259] gNBm(300-m) may not be able to confirm the selection of a UE Reader due to a lack of information for selecting a UE Reader, or may decide to select a UE Reader later.

[0260] In step S404a, gNBm (300-m) can transmit an AIoT Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 4). gNBm (300-m) can receive an AIoT Response message transmitted from at least one of the UE Readers. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0261] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0262] For example, gNBm (300-m) can select UE2 (200-2) as the UE Reader based on the information included in the AIoT Response message and the priority.

[0263] In step S404-1a, UE2 (200-2), a UE reader, can select a Device based on available information such as Device ID, Location (TA ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information may be as follows.

[0264] Selection Info Priority: Provisioned Info > AF ID > Task ID (or Session ID, Service ID, Transaction ID) > TA ID (or cell ID / gNB ID) > UE ID > Device ID

[0265] For example, UE2 (200-2) can select a Device based on the available information and the priority.

[0266] UE2 (200-2) may not be able to confirm the selection of a device because there is insufficient information to select a device, or may decide to select a device later. UE2 (200-2) can send an AIoT Request message to a plurality of selectable devices including Device1 (100-1) and Device2 (100-2) of FIG. 1 (e.g., Device1111 (1111), Device1112 (1112), Device1121 (1121), Device1122 (1122), Device1211 (1211), Device1212 (1212), Device1221 (1221), Device1222 (1222), Device2111 (2111), Device2112 (2112), Device2121 (2121), Device2122 (2122), Device2211 (2211), Device2212 (2212), Device2221 (2221), and Device2222 (2222)). UE2 (200-2) can receive an AIoT Response message transmitted from at least one of multiple devices. The priority of information included in the AIoT Response message (Broadcast and Filtering Response) may be as follows.

[0267] Broadcast and Filtering Response: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0268] For example, UE2 (200-2) can select Device1 (100-1) and Device2 (100-2) based on information included in the AIoT Response message and the priority of said information.

[0269] FIGS. 7a and 7b illustrate an embodiment in which UE2 (200-2), a UE Reader, simultaneously transmits an AIoT Request message to Device1 (100-1) and Device2 (100-2), but the embodiments of the present disclosure are not limited thereto.

[0270] FIGS. 8a and 8b are flowcharts illustrating the flow of AIOT Response messages for connecting to an ultra-low power device using a UE Reader in 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0271] Referring to FIGS. 8a and 8b, steps 0 through 4 may be substantially identical or similar to steps S300a through S304 of FIGS. 6a and 6b, or steps S400a through S404a of FIGS. 7a and 7b. Steps S504-1 and S505 of FIG. 8a may be substantially identical or similar to steps S304-1 of FIG. 6a and S305 of FIG. 6b, or steps S404-1 of FIG. 7a and S405 of FIG. 7b. Steps S504-1a and S505a of FIG. 8a may be substantially identical or similar to steps S404-1a and S405a of FIG. 7b.

[0272] Device1 (100-1) and Device2 (100-2) that have received an AIoT Request message can select a UE Reader based on the AIoT Request message.

[0273] In step S505-1, Device1 (100-1) can select a UE reader based on available information such as a stored UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0274] Selection by stored Info Priority: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0275] Device1 (100-1) can select a UE reader based on the available information and the priority.

[0276] Device1 (100-1) may not be able to confirm the selection of a UE reader due to insufficient information for selecting a UE reader, or may decide to select a UE reader later. Device1 (100-1) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 4). Device1 (100-1) may receive a Response message transmitted from at least one of the plurality of UE Readers. Device1 (100-1) may select a UE reader based on information included in the Response message and the priority of said information. Device1 (100-1) can select a UE Reader based on the status information (NF / UE Reader) of the following Response message, prioritizing the above priority.

[0277] NF / UE Reader: filtering by air power (prioritizes received messages with higher signal strength), frequency (prioritizes messages with shorter reception cycles, i.e., the entity sending messages more frequently), first with timer (prioritizes the entity sending the message first within a specific time range)

[0278] For example, Device1 (100-1) can select UE1 (200-1) as a UE reader based on the above status information.

[0279] Device1 (100-1) may not be able to confirm the selection of a UE reader due to insufficient information for selecting a UE reader, or may decide to select a UE reader later. Device1 (100-1) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 4). Device1 (100-1) may receive a Response message transmitted from at least one of the plurality of UE Readers. Device1 (100-1) may select one of the plurality of received Response messages or aggregate the plurality of received Response messages.

[0280] In step S506, Device1 (100-1) can transmit an aggregated or selected AIoT response message to UE1 (200-1), a UE reader. UE1 (200-1) can receive the aggregated or selected AIoT response message from Device1 (100-1).

[0281] In step S505-1a, Device2 (100-2) can select a UE reader based on available information such as a stored UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0282] Selection by stored Info Priority: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0283] Device2 (100-2) can select UE1 (200-1) as a UE reader based on the available information and the priority.

[0284] Device2 (100-2) may not be able to confirm a selection because there is insufficient information to select a UE reader, or it may decide to select a UE reader later. Device2 (100-2) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 4). Device2 (100-2) may select a UE reader based on the priority of information included in a Response message sent from at least one of the UE Readers. Device2 (100-2) can select a UE Reader based on the status information (NF / UE Reader) of the following Response message, prioritizing the above priority.

[0285] NF / UE Reader: filtering by air power (prioritizes received messages with higher signal strength), frequency (prioritizes messages with shorter reception cycles, i.e., the entity sending messages more frequently), first with timer (prioritizes the entity sending the message first within a specific time range)

[0286] Device2 (100-2) may not be able to confirm the selection of a UE reader due to insufficient information for selecting a UE reader, or may decide to select a UE reader later. Device2 (100-2) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 4). Device2 (100-2) may receive a Response message transmitted from at least one of the plurality of UE Readers. Device2 (100-2) may select one of the plurality of Response messages or aggregate the plurality of Response messages.

[0287] In step S506a, Device2 (100-2) can transmit the aggregated or selected AIoT response message to UE1 (200-1). UE1 (200-1) can receive the aggregated or selected AIoT response message from Device2 (100-2).

[0288] In step S506-1, UE1 (200-1), which is a UE Reader, can select a gNB based on available information such as a stored gNB ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0289] Selection by stored Info Priority: gNB ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0290] UE1 (200-1) can select gNB based on the available information and the priority of the available information. For example, UE1 (200-1) can select gNB1 (300-1).

[0291] When UE1 (200-1) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0292] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0293] UE1 (200-1) can perform an operation for aggregating or selecting multiple AIoT Response messages based on the above priority.

[0294] In step S507, UE1 (200-1) can transmit an aggregated or selected AIoT response message to gNB1 (300-1). gNB1 (300-1) can receive an aggregated or selected AIoT response message from UE1 (200-1).

[0295] FIG. 5 illustrates an embodiment in which UE1 (200-1), a UE Reader, aggregates or selects an AIoT Response message received from Device1 (100-1) in step S506 and a Response message received from Device2 (100-2) in step S506a, and transmits one AIoT Response message to gNB1 (300-1), but the embodiments of the present disclosure are not limited thereto.

[0296] In step S507-1, gNB1 (300-1) can select an AMF based on available information such as TA ID (or cell ID / gNB ID) and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0297] Selection by stored Info Priority: AMF ID, TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0298] gNB1 (300-1) can select an AMF based on the available information and the priority of the available information. For example, gNB1 (300-1) can select an AMF1 (400-1).

[0299] When gNB1 (300-1) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority order for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows: Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0300] gNB1(300-1) can perform aggregation or selection operations on the plurality of AIoT Response messages based on the above priority.

[0301] In step S508, gNB1 (300-1) can transmit an aggregated or selected AIoT response message to AMF1 (400-1). AMF1 (400-1) can receive an aggregated or selected AIoT response message from gNB1 (300-1).

[0302] In step S508-1, AMF1 (400-1) can select AIoTF / NEF based on available information such as Device ID, UE ID, Location (TA ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0303] Selection by stored Info Priority: Provisioned Info > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0304] AMF1 (400-1) can select AIoTF / NEF based on the available information and the priority. For example, AMF1 (400-1) can select AIoTF / NEF1 (600).

[0305] When AMF1 (400-1) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0306] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0307] AMF1 (400-1) can perform an operation for aggregating or selecting the plurality of AIoT Response messages based on the above priority.

[0308] In step S509, AMF1 (400-1) can transmit an aggregated or selected AIoT response message to AIoTF / NEF1 (600). AIoTF / NEF1 (600) can receive the aggregated or selected AIoT response message from AMF1 (400-1).

[0309] In step S509-1, the AIoTF / NEF (600) can select an AF based on available information such as Device ID, UE ID, Location (Geographical), Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0310] Selection by stored Info Priority: Provisioned Info > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0311] For example, AIoTF / NEF (600) can select AF (700) based on the available information and the priority.

[0312] When the AIoTF / NEF (600) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0313] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0314] AIoTF / NEF (600) can perform an operation for aggregating or selecting the plurality of AIoT Response messages based on the above priority.

[0315] In step S510, the AIoTF / NEF (600) can send aggregated or selected AIoT Response messages to the AF (700). The AF (700) can receive aggregated or selected AIoT Response messages from the AIoTF / NEF (600).

[0316] FIGS. 9a and 9b are flowcharts illustrating the message flow of an AIoT Response for providing services by connecting to an ultra-low power device using a UE Reader in a 3GPP 5GS (5G System) according to an embodiment of the present disclosure.

[0317] Referring to FIGS. 9a and 9b, steps 0 through 4 may be substantially identical or similar to steps S300a through S304 of FIGS. 6a and 6b, or steps S400a through S404a of FIGS. 7a and 7b. Steps S604-1 and S605 of FIG. 9a may be substantially identical or similar to steps S304-1 and S305 of FIG. 6b, or steps S404-1 and S405 of FIG. 7b. Steps S604-1a and S605a of FIG. 9a may be substantially identical or similar to steps S404-1a and S405a of FIG. 7b.

[0318] In step S605-1, Device1 (100-1) can select a UE reader based on available information such as a stored UE ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0319] Selection by stored Info Priority: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0320] Device1 (100-1) can select a UE reader based on the available information and the priority.

[0321] Device1 (100-1) may not be able to confirm the selection of a UE reader due to insufficient information to select a UE reader, or may decide to select a UE reader later. Device1 (100-1) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 4). Device1 (100-1) may receive a Response message transmitted from at least one of the plurality of UE Readers. Device1 (100-1) may select a UE Reader based on information included in the Response message and the priority of said information. Device1 (100-1) may select a UE Reader based on the following state information (NF / UE Reader) of a Response message, prioritizing the above priority. NF / UE Reader: filtering by air power (prioritizing the one with the highest received signal strength of the received message), frequency (prioritizing the one with the shortest received period of the received message, i.e., the entity that transmits messages more frequently), first w / timer (prioritizing the entity that sent the message first based on a certain time range).

[0322] For example, Device1 (100-1) can select UE1 (200-1) and UE2 (200-1) as UE readers based on the above status information.

[0323] Device1 (100-1) may not be able to confirm the selection of a UE reader due to insufficient information for selecting a UE reader, or may decide to select a UE reader later. Device1 (100-1) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 1). Device1 (100-1) may receive a Response message transmitted from at least one of the plurality of UE Readers. Device1 (100-1) may select or aggregate one of the received plurality of Response messages.

[0324] In step S606, Device1 (100-1) can transmit aggregated or selected AIoT response messages to UE readers UE1 (200-1) and UE2 (200-2). UE1 (200-1) can receive aggregated or selected AIoT response messages from Device1 (100-1). UE2 (200-2) can receive aggregated or selected AIoT response messages from Device1 (100-1).

[0325] In step S605-1a, Device2 (100-2) can select a UE reader based on available information such as a stored UE ID, TA ID (or cell ID / gNB ID), Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information may be as follows.

[0326] Selection by stored Info Priority: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0327] Device2 (100-2) can select UE1 (200-1) and UE2 (200-2) as UE readers based on the available information and the priority.

[0328] Device2 (100-2) may not be able to confirm a selection because it lacks sufficient information to select a UE reader, or it may decide to select a UE reader later. Device2 (100-2) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 1). Later, Device2 (100-2) may select a UE reader based on the priority of information included in a Response message sent from at least one of the UE Readers. Device2 (100-2) can select a UE Reader based on the status information (NF / UE Reader) of the following Response message, prioritizing the above priority.

[0329] NF / UE Reader: filtering by air power (prioritizes received messages with higher signal strength), frequency (prioritizes messages with shorter reception cycles, i.e., the entity sending messages more frequently), first with timer (prioritizes the entity sending the message first within a specific time range)

[0330] Device2 (100-2) may not be able to confirm the selection of a UE reader due to insufficient information for selecting a UE reader, or may decide to select a UE reader later. Device2 (100-2) may send a Request message to a plurality of selectable UE Readers including UE1 (200-1) and UE2 (200-2) (e.g., UE111 (111), UE112 (112), UE121 (121), UE122 (122), UE211 (211), UE212 (212), UE221 (221), and UE222 (222) of FIG. 1). Device2 (100-2) may receive a Response message transmitted from at least one of the plurality of UE Readers. Device2 (100-2) may select one of the plurality of Response messages or aggregate the plurality of Response messages.

[0331] In step S606a, Device2 (100-2) may transmit the aggregated or selected AIoT response message to UE1 (200-1) and UE2 (200-2). UE1 (200-1) may receive the aggregated or selected AIoT response message from Device2 (100-2). UE2 (200-2) may receive the aggregated or selected AIoT response message from Device2 (100-2).

[0332] In step S606-1, UE1 (200-1), a UE Reader, can select a gNB based on available information such as a stored gNB ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information may be as follows.

[0333] Selection by stored Info Priority: gNB ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0334] UE1 (200-1) can select gNB based on the available information and the priority of the available information. For example, UE1 (200-1) can select gNB1 (300-1).

[0335] When UE1 (200-1) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0336] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0337] UE1 (200-1) can perform an operation for aggregating or selecting multiple AIoT Response messages based on the above priority.

[0338] In step S607, UE1 (200-1) can send an aggregated or selected AIoT response message to gNB1 (300-1). gNB1 (300-1) can receive an aggregated or selected AIoT response message from UE1 (200-1).

[0339] In step S606-1a, UE2 (200-2), a UE Reader, can select a gNB based on available information such as a stored gNB ID, TA ID (or cell ID / gNB ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information may be as follows.

[0340] Selection by stored Info Priority: gNB ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0341] UE2 (200-2) can select gNB based on the available information and the priority of the available information. For example, UE2 (200-2) can select gNBm (300-m).

[0342] When UE2 (200-2) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages may be as follows.

[0343] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0344] UE2 (200-2) can perform an operation for aggregating or selecting multiple AIoT Response messages based on the above priority.

[0345] In step S607a, UE2 (200-2) can send an aggregated or selected AIoT response message to gNBm (300-m). gNBm (300-m) can receive an aggregated or selected AIoT response message from UE2 (200-2).

[0346] In step S607-1, gNB1 (300-1) can select an AMF based on available information such as TA ID (or cell ID / gNB ID) and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0347] Selection by stored Info Priority: AMF ID, TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0348] gNB1 (300-1) can select an AMF based on the available information and the priority of the available information. For example, gNB1 (300-1) can select an AMF1 (400-1).

[0349] When gNB1 (300-1) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority order for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows: Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0350] gNB1(300-1) can perform aggregation or selection operations on the plurality of AIoT Response messages based on the above priority.

[0351] In step S608, gNB1 (300-1) can transmit an aggregated or selected AIoT response message to AMF1 (400-1). AMF1 (400-1) can receive an aggregated or selected AIoT response message from gNB1 (300-1).

[0352] In step S607-1a, gNBm (300-m) can select an AMF based on available information such as TA ID (or cell ID / gNB ID) and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0353] Selection by stored Info Priority: AMF ID, TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0354] gNBm (300-m) can select an AMF based on the available information and the priority of the available information. For example, gNBm (300-m) can select an AMFn (400-n).

[0355] When gNBm (300-m) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0356] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0357] gNBm(300-m) can perform aggregation or selection operations on the plurality of AIoT Response messages based on the above priority.

[0358] In step S608a, gNBm (300-m) can send an aggregated or selected AIoT response message to AMFn (400-n). AMFn (400-n) can receive the aggregated or selected AIoT response message from gNBm (300-m).

[0359] In step S608-1, AMF1 (400-1) can select AIoTF / NEF based on available information such as Device ID, UE ID, Location (TA ID), and Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0360] Selection by stored Info Priority: Provisioned Info > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0361] AMF1 (400-1) can select AIoTF / NEF based on the available information and the priority. For example, AMF1 (400-1) can select AIoTF / NEF1 (600).

[0362] When AMF1 (400-1) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0363] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0364] AMF1 (400-1) can perform an operation for aggregating or selecting the plurality of AIoT Response messages based on the above priority.

[0365] In step S609, AMF1 (400-1) can transmit an aggregated or selected AIoT response message to AIoTF / NEF (600). AIoTF / NEF (600) can receive an aggregated or selected AIoT response message from AMF1 (400-1).

[0366] In step S608-1a, AMFn (400-n) can select available information such as Device ID, UE ID, Location (TA ID), and Task ID (or Session ID, Service ID, Transaction ID) based on AIoTF / NEF. The priority of the available information (Selection by stored Info Priority) may be as follows.

[0367] Selection by stored Info Priority: Provisioned Info > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0368] AMFn (400-n) can select AIoTF / NEF based on the available information and the priority. For example, AMFn (400-n) can select AIoTF / NEF (600).

[0369] When AMFn (400-n) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0370] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)

[0371] AMFn (400-n) can perform an operation for aggregating or selecting the plurality of AIoT Response messages based on the above priority.

[0372] In step S609a, AMFn (400-n) can transmit aggregated or selected AIoT response messages to AIoTF / NEF (600). AIoTF / NEF (600) can receive aggregated or selected AIoT response messages from AMFn (400-n).

[0373] In step S609-1, the AIoTF / NEF (600) can select an AF based on available information such as Device ID, UE ID, Location (Geographical), Task ID (or Session ID, Service ID, Transaction ID). The priority of the available information (Selection by stored Info Priority) may be as follows.

[0374] Selection by stored Info Priority: Provisioned Info > Task ID (or Session ID, Service ID, Transaction ID) > AF ID

[0375] For example, AIoTF / NEF (600) can select AF (700) based on the available information and the priority.

[0376] When the AIoTF / NEF (600) receives multiple AIoT Response messages, it may aggregate the multiple AIoT Response messages or select one of the multiple AIoT Response messages. The priority for aggregating or selecting the multiple AIoT Response messages (Aggregation, Selection among responses from Devices) may be as follows.

[0377] Aggregation, Selection among responses from Devices: Device ID > UE ID > TA ID (or cell ID / gNB ID) > Task ID (or Session ID, Service ID, Transaction ID)]

[0378] AIoTF / NEF (600) can perform an operation for aggregating or selecting the plurality of AIoT Response messages based on the above priority.

[0379] In step S610, the AIoTF / NEF (600) can send aggregated or selected AIoT Response messages to the AF (700). The AF (700) can receive aggregated or selected AIoT Response messages from the AIoTF / NEF (600).

[0380] FIG. 6 illustrates an embodiment in which AIoTF / NEF (600) aggregates or selects an AIoT Response message received from AMF1 (400-1) in step S609 and an AIoT Response message received from AMFm (400-m) in step S609a, and transmits one AIoT Response message to AF (700) in step S610, but various embodiments of the present disclosure are not limited thereto.

[0381] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. In a method of operation of an Access and Mobility Management Function (AMF) entity in a wireless communication system, An operation of receiving an AIoT (ambient IoT) request message from a NEF (Network Exposure Function) entity that includes an AF (Application Function) ID (identification), a task ID, a TA (Tracking Area) ID, a UE (user equipment) ID, and an IoT (Internet of Things) device ID; An operation to select a gNB (gnodeB) based on a predetermined priority for the above request message and the information included in the above request message; and It includes the operation of sending the request message to the selected gNB, and The above-determined priority is a method having a higher priority in the order of the previously provided information, the AF ID, business ID, TA ID, UE ID, and IoT device ID.

2. In Paragraph 1, The operation of selecting the above gNB is, The operation of transmitting the request message to a plurality of gNBs including the above gNB; The operation of receiving a response message from at least one gNB among the plurality of gNBs; and A method comprising the operation of selecting the gNB based on the above response message.

3. In Paragraph 1, The above request message is transmitted to at least one UE associated with the UE ID via the above gNB, and A method in which at least one UE is selected by the gNB based on the request message and the predetermined priority.

4. In Paragraph 3, The above request message is transmitted to at least one IoT device associated with the IoT device ID through the above at least one UE, and A method in which at least one IoT device is selected by at least one UE based on the request message and the predetermined priority.

5. In Paragraph 4, The operation of receiving a response message from at least one IoT device; and A method comprising the action of transmitting the above response message to the above NEF.

6. In Paragraph 5, The operation of sending the above response message to the above NEF is, If there are multiple response messages, the operation includes aggregating the multiple response messages based on the priority associated with the response messages, or selecting one of the multiple response messages. A method in which the response message transmitted to the above NEF is either the aggregated response message or the selected single response message.

7. In Paragraph 5, The above response message is transmitted from at least one IoT device to at least one UE, and A method in which at least one UE is selected by at least one IoT device based on the response message and the priority associated with the response message.

8. In Paragraph 7, The above response message is transmitted from at least one UE to at least one gNB, and A method in which at least one gNB is selected by at least one UE based on the response message and the priority associated with the response message.

9. In Paragraph 8, The above response message is transmitted from the above at least one gNB, and A method in which the destination of the above response message is selected by the at least one gNB based on the above response message and the priority associated with the above response message.

10. In Paragraph 9, The above response message is transmitted to AF via the above NEF, a method.

11. In an Access and Mobility Management Function (AMF) entity in a wireless communication system, Transmitter / receiver; and A processor electrically connected to the above-mentioned transmitter and receiver; including The above processor is, An operation of receiving an AIoT (ambient IoT) request message from a NEF (Network Exposure Function) entity that includes an AF (Application Function) ID (identification), a task ID, a TA (Tracking Area) ID, a UE (user equipment) ID, and an IoT (Internet of Things) device ID; An operation to select a gNB (gnodeB) based on a predetermined priority for the above request message and the information included in the above request message; and Perform the operation of sending the request message to the selected gNB, and The above predetermined priority is an AMF entity having a higher priority in the order of the pre-provided information, the AF ID, business ID, TA ID, UE ID, and IoT device ID.

12. In Paragraph 11, The above processor is, The operation of transmitting the request message to a plurality of gNBs including the above gNB; The operation of receiving a response message from at least one gNB among the plurality of gNBs; and An AMF entity that further performs the operation of selecting the gNB based on the above response message.

13. In Paragraph 12, The above request message is transmitted to at least one UE associated with the UE ID via the above gNB, and The above at least one UE is an AMF entity selected by the gNB based on the request message and the predetermined priority.

14. In Paragraph 13, The above request message is transmitted to at least one IoT device associated with the IoT device ID through the above at least one UE, and The above at least one IoT device is an AMF entity selected by the above at least one UE based on the above request message and the above predetermined priority.

15. In Paragraph 14, The operation of receiving a response message from at least one IoT device; and An AMF entity comprising the operation of transmitting the above response message to the above NEF.

Images