Method for determining aiot reader

Abstract

One disclosure of the present specification provides a method. The method comprises the steps of: receiving, by an AIOTF, an AIoT request from an AF, wherein the AIoT request comprises information about a target AIoT device, and the last known reader for the target AIoT device is a first reader; and on the basis of the AIoT request, determining, by the AIOTF, the first reader and a second reader as AIoT readers for the target AIoT device.

Description

AIOT Leader Decision Method

[0001] This specification relates to mobile communication.

[0002] 3GPP (3rd generation partnership project) LTE (long-term evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

[0004] NR targets a single technical framework that covers all deployment scenarios, usage scenarios, and requirements, including eMBB (enhanced mobile broadband), mMTC (massive machine type communications), and URLLC (ultra-reliable and low latency communications). NR must inherently be forward compatible.

[0005] The core network determines additional AIOT leaders along with the last known AIOT leader for the target AIOT device of the AIoT request.

[0006] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0007] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0008] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0009] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0010] FIG. 5 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0011] Figure 6 is an example diagram showing the topology 1 of an A-IoT device.

[0012] Figure 7 is an example diagram showing the topology2 of an A-IoT device.

[0013] FIG. 8 shows a flowchart of a first example of a first embodiment according to the disclosure of the present specification.

[0014] FIG. 9 shows a flowchart of a second example of a first embodiment according to the disclosure of the present specification.

[0015] FIG. 10 shows a flowchart of the first example of the second embodiment according to the disclosure of the present specification.

[0016] FIG. 11 shows a flowchart of a second example of a second embodiment according to the disclosure of the present specification.

[0017] FIG. 12 shows a flowchart of a third example of a second embodiment according to the disclosure of the present specification.

[0018] FIG. 13 illustrates a first example of the AIOTF procedure for the disclosure of the present specification.

[0019] FIG. 14 illustrates a second example of the AIOTF procedure for the disclosure of the present specification.

[0020] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

[0021] For convenience of explanation, the implementation of this specification is described primarily in relation to 3GPP-based wireless communication systems. However, the technical characteristics of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to 3GPP-based wireless communication systems may be applied to other mobile communication systems.

[0022] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0023] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0024] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0025] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0026] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0027] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0028] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0029] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0030] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0031] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0032] The 5G usage scenario shown in FIG. 1 is merely an example, and the technical features of this specification may be applied to other 5G usage scenarios not shown in FIG. 1.

[0033] The three main requirements categories for 5G are (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable and low latency communications (URLLC) category.

[0034] Referring to FIG. 1, the communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of the network of the communication system (1), but the implementation of the present specification is not limited to a 5G system and may be applied to future communication systems beyond a 5G system.

[0035] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0036] Wireless devices (100a to 100f) represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs) and head-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0037] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (personal digital assistant), a PMP (portable multimedia player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

[0038] For example, a UAV can be an aircraft that is not on board and is navigated by radio control signals.

[0039] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in a real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in a real world. For example, a holographic device may include a device for implementing a 360-degree stereoscopic image by recording and playing back stereoscopic information using the phenomenon of light interference that occurs when two laser lights called holograms meet.

[0040] For example, a public safety device may include an image relay device or an image device that can be worn on a user's body.

[0041] For example, MTC devices and IoT devices may be devices that do not require direct human intervention or operation. For instance, MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0042] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, a (in vitro) diagnostic device, a hearing aid, or a surgical device.

[0043] For example, a security device may be a device installed to prevent potential risks and maintain safety. For example, a security device may be a camera, closed-circuit TV (CCTV), a recorder, or a black box.

[0044] For example, a fintech device may be a device capable of providing financial services such as mobile payments. For example, a fintech device may include a payment device or a POS system.

[0045] For example, a weather / environment device may include a device for monitoring or predicting the weather / environment.

[0046] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0047] Wireless communication / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and base station (200) and / or between base station (200). Here, the wireless communication / connections can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D (device-to-device) communication), and communication between base stations (150c) (e.g., relay, IAB (integrated access and backhaul)). Through the wireless communication / connections (150a, 150b, 150c), wireless devices (100a to 100f) and base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) may transmit / receive signals through various physical channels. To this end, based on various proposals in this specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0048] AI refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems within the realm of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0049] A robot can refer to a machine that automatically processes or operates given tasks based on its own capabilities. In particular, a robot equipped with the ability to perceive its environment, make independent judgments, and perform actions can be called an intelligent robot. Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, propellers, etc., in their drive units, enabling them to drive on the ground or fly in the air.

[0050] Autonomous driving refers to technology that drives itself, and an autonomous vehicle refers to a vehicle that drives without user intervention or with minimal user intervention. For example, autonomous driving can include technologies such as maintaining the driving lane, automatically adjusting speed like adaptive cruise control, driving automatically along a predetermined route, and automatically setting a route and driving once a destination is set. The term "vehicle" encompasses vehicles equipped solely with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped solely with electric motors; it can include not only automobiles but also trains and motorcycles. An autonomous vehicle can be viewed as a robot equipped with autonomous driving capabilities.

[0051] Augmented Reality is a collective term for VR, AR, and MR. VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR technology in that it displays real-world and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual and real objects in MR technology are used as equal entities.

[0052] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0053] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change. For example, the two types of frequency ranges (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as millimeter wave (mmW).

[0054] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

[0055] As described above, the numerical values ​​of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0056] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

[0057] Here, the wireless communication technology implemented in the wireless device of this specification may include LTE, NR, and 6G, as well as narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth, and / or LPWAN for low-power communication, and is not limited to the names mentioned above. For example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0058] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0059] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

[0060] The first wireless device (100) may include at least one transceiver such as a transceiver (106), at least one processing chip such as a processing chip (101), and / or one or more antennas (108).

[0061] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

[0062] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0063] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

[0064] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). Each transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (radio frequency) unit. In this specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0065] The second wireless device (200) may include at least one transceiver such as a transceiver (206), at least one processing chip such as a processing chip (201), and / or one or more antennas (208).

[0066] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be placed outside the processing chip (201).

[0067] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0068] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements instruction code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0069] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and transmit and / or receive a wireless signal through one or more antennas (208). Each transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0070] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (media access control) layer, a RLC (radio link control) layer, a PDCP (packet data convergence protocol) layer, a RRC (radio resource control) layer, and an SDAP (service data adaptation protocol) layer). One or more processors (102, 202) may generate one or more PDUs (protocol data units), one or more SDUs (service data units), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0071] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors.

[0072] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may consist of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0073] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0074] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0075] One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0076] Although not illustrated in FIG. 2, the wireless device (100, 200) may include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

[0077] In an implementation of this specification, the UE may operate as a transmitting device in the uplink (UL; uplink) and as a receiving device in the downlink (DL; downlink). In an implementation of this specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released to the first wireless device (100) may be configured to perform UE operations according to an implementation of this specification or to control a transceiver (106) to perform UE operations according to an implementation of this specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of this specification or to control a transceiver (206) to perform base station operations according to an implementation of this specification.

[0078] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0079] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0080] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0081] The UE (100) includes a processor (102), memory (104), transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0082] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Layers of a wireless interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits, and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0083] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

[0084] A transceiver (106) is coupled to operate with a processor (102) and transmits and / or receives a wireless signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a wireless frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a wireless signal.

[0085] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0086] The display (143) outputs the result processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0087] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

[0088] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0089] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0090] 5GC (5G Core) may include various components, and FIG. 5 includes some of them, such as AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0091] The UE (100) is connected to the data network via the UPF (440) through the NG-RAN (Next Generation Radio Access Network) including the gNB (20).

[0092] The UE (100) can also receive data services through untrusted non-3GPP access, such as a WLAN (Wireless Local Area Network). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0093] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G systems. When the UE (100) is connected to non-3GPP access (e.g., WiFi referred to as IEEE 801.11), the UE (100) can be connected to the 5G system through the N3IWF (490). The N3IWF (490) performs control signing with the AMF (410) and connects to the UPF (440) via the N3 interface for data transmission.

[0094] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform the function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform the function of handling mobility in an idle state.

[0095] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communication.

[0096] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains the data path between the gNB (20) and the SMF (420). Additionally, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform the function of handling PDUs. For mobility within the NG-RAN (Next Generation Radio Access Network defined in 3GPP Release-15 or later), packets can be routed through the UPF. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined prior to 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0097] The illustrated PCF (430) is a node that controls the operator's policy.

[0098] The illustrated AF (450) is a server for providing various services to the UE (100).

[0099] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home subscriber Server) of 4th generation mobile communication. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0100] The illustrated SMF (420) can perform the function of assigning the IP (Internet Protocol) address of the UE. Also, the SMF (420) can control the PDU (protocol data unit) session.

[0101] For reference, the reference numerals for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

[0102] Fifth-generation mobile communication supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban environments, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0103] FIG. 5 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0104] The 5G system (5GS) structure consists of the following network functions (NF).

[0105] - AUSF (Authentication Server Function)

[0106] - AMF (Access and Mobility Management Function)

[0107] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0108] - USDF (Unstructured Data Storage Function)

[0109] - NEF (Network Exposure Function)

[0110] - I-NEF (Intermediate NEF)

[0111] - NRF (Network Repository Function)

[0112] - NSSF (Network Slice Selection Function)

[0113] - PCF (Policy Control Function)

[0114] - SMF (Session Management Function)

[0115] - UDM (Unified Data Management)

[0116] - UDR (Unified Data Repository)

[0117] - UPF (User Plane Function)

[0118] - UCMF (UE radio Capability Management Function)

[0119] - AF (Application Function)

[0120] - UE (User Equipment)

[0121] - (R)AN ((Radio) Access Network)

[0122] - 5G-EIR (5G-Equipment Identity Register)

[0123] - NWDAF (Network Data Analytics Function)

[0124] - CHF (CHarging Function)

[0125] In addition, the following network functions may be considered.

[0126] - N3IWF (Non-3GPP InterWorking Function)

[0127] - TNGF (Trusted Non-3GPP Gateway Function)

[0128] - W-AGF (Wireline Access Gateway Function)

[0129] Figure 5 shows the 5G system structure in a non-roaming case using a reference point representation that shows how various network functions interact with each other.

[0130] In Fig. 5, for clarity of the point-to-point diagram, UDSF, NEF, and NRF are not described. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0131] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in FIG. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in FIG. 4.

[0132] The 5G system structure includes the following reference points.

[0133] - N1: Reference point between UE and AMF.

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

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

[0136] - N4: Reference point between SMF and UPF.

[0137] - N6: Reference point between the UPF and the data network.

[0138] - N9: Reference point between two UPFs.

[0139] The following reference points show the interactions that exist between the NF services of NF.

[0140] - N5: Reference point between PCF and AF.

[0141] - N7: Reference point between SMF and PCF.

[0142] - N8: Reference point between UDM and AMF.

[0143] - N10: Reference point between UDM and SMF.

[0144] - N11: Reference point between AMF and SMF.

[0145] - N12: Reference point between AMF and AUSF.

[0146] - N13: Reference point between UDM and AUSF.

[0147] - N14: Reference point between two AMFs.

[0148] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF of the visited network for roaming scenarios.

[0149] - N16: Reference point between two SMFs (in the case of roaming, between the SMF of the visited network and the SMF of the home network)

[0150] - N22: Reference point between AMF and NSSF.

[0151] In some cases, two NFs may need to be connected to each other to service the UE.

[0152] <A-IoT (Ambient Internet of Things)>

[0153] A-IoT (Ambient Internet of Things) refers to low-cost, low-power IoT devices powered by ambient energy. This overcomes the limitations of existing IoT technology and can be applied to various fields such as distribution, logistics, and smart factories.

[0154] A-IoT can refer to ultra-low power IoT devices that operate by consuming significantly less power than existing IoT devices (or by utilizing energy such as ambient light, heat, and radio waves without a battery).

[0155] In this specification, the terms UE and terminal are used interchangeably.

[0156] An intermediate node (or A-IoT leader, base station) can transmit a CW (continuous wave) / DL (downlink) signal to an A-IoT device. The A-IoT device can transition from an inactive state to an active state by means of the CW / DL signal. The activated A-IoT device can reflect the CW / DL signal by including data within it. Through this, A-IoT operation can be performed.

[0157] In this specification, the CW (continuous wave) / DL (downlink) signal may be a signal transmitted to an A-IoT device for A-IoT operation.

[0158] In this specification, the CW (continuous wave) / DL (downlink) signal may refer to an A-IoT signal.

[0159] 1. A-IoT Topology

[0160] The topology of A-IoT can be broadly divided into two types as follows.

[0161] Figure 6 is an example diagram showing the topology 1 of an A-IoT device.

[0162] Topology 1 (T1) means that the A-IoT device and the BS (base station) communicate directly.

[0163] Figure 7 is an example diagram showing the topology2 of an A-IoT device.

[0164] Topology 2 (T2) means that there is an intermediate node between the A-IoT device and the base station.

[0165] Intermediate nodes may include relays, IAB nodes (integrated access and backhaul), UEs, repeaters, etc.

[0166] Topology 1 is a topology where the BS (Base Station) acts as the reader. (BS - AIOT device)

[0167] In Topology 1, the BS reader can perform an inventory operation to find AIoT devices and interact with AIoT devices, such as command operations (e.g., read, write).

[0168] Topology 2 is a topology where an intermediate node (e.g., UE) acts as the leader. (BS - Intermediate Node - AIOT Device)

[0169] In Topology 2, the intermediate node leader (intermediate node) can perform inventory operations to find AIoT devices and interact with AIoT devices, such as command operations (e.g., read, write).

[0170] For Topology 1, AIOTF can select AIOT RAN nodes and optionally a list of base station (BS) leaders.

[0171] For topology 2, AIOTF can select a UE leader (e.g., a candidate or final UE leader) and provide the list of selected UE leaders to the RAN.

[0172] AIOTF can locally store and manage information related to AIoT devices (also known as device context information). This information may include the AIoT device's permanent ID, last known reader information, and the like. The last known reader information can be used by AIOTF to select a service reader to deliver messages to a specific AIoT device.

[0173] AF can send AIOT-related requests to the AIOT core network.

[0174] The A-IoT CN (core network of AIoT) receives AIoT-related requests from the AF (Application Function), performs a series of procedures, and can transmit a response (e.g., result of performing AIoT-related requests) to the AF based on the results obtained / received from the A-IoT device(s).

[0175] However, regarding the time required for AF to make AIoT-related requests to the core network and receive responses / results, there may be latency-related requirements.

[0176] For example, after the AF sends an AIoT-related request to the core network, the AF may want to receive a response / result regarding the request within a specific time.

[0177] AIOTF may store last known reader information for AIoT devices.

[0178] In order to transmit a message to the above AIoT device (e.g., to transmit messages such as inventory, read, write, disable, etc. to the AIoT device), the AIOTF may provide the base station with last known reader information as AIoT reader information.

[0179] Then, the base station may have the provided AIoT reader (e.g., the last known reader) transmit the message to the AIoT device. At this time, the base station may include / be equipped with the AIoT reader (e.g., the last known reader).

[0180] Having the last known leader (the AIoT leader that last interacted with the AIoT device) perform interaction with the AIoT device again may have advantages in terms of resource efficiency. For example, wireless resources can be saved by having one AIoT leader send messages to the AIoT device instead of having multiple AIoT leaders send messages to the AIoT device.

[0181] The AIoT device may move out of the communication range of the last known reader. In this case, after attempting to reach the last known reader, message transmission must be attempted through another AIoT reader. In this scenario, a delay may occur.

[0182] In relation to the aforementioned delay, an efficient AIoT service support plan is needed that takes into account AIoT-related latency requirements.

[0183] In this specification, the terms UE (User Equipment) and terminal are used interchangeably.

[0184] In this specification, Ambient IoT, AIoT, A-IoT, etc. are used interchangeably.

[0185] In this specification, the terms AIoT RAN node, AIoT RAN, base station, etc. are used interchangeably.

[0186] In this specification, base station, A-IoT-enabled gNB, AIoT RAN node, AIoT RAN, AIoT RAN node function, AIoT RAN function, etc. are used interchangeably in description.

[0187] The method proposed in this specification assumes Topology 1, in which the AIoT leader is a leader in the form of belonging to a base station.

[0188] In this specification, terms such as AIoT reader, AIoT RAN reader, BS reader, BS type reader, reader, base station reader, etc. are used interchangeably.

[0189] In this specification, information regarding AIoT devices, context regarding AIoT devices, etc. are described in combination.

[0190] In this specification, AIoT procedures, AIoT service procedures, AIoT service operations, AIoT operations, etc. are described interchangeably.

[0191] In this specification, the terms AF (Application Function), AS (Application Server), ASP (Application Service Provider) server, AIoT server, etc., are used interchangeably.

[0192] In this specification, types of AIoT services may be, for example, Inventory, Command, Read, Write, Disable, Permanently (or Permanent) Disable, Temporarily (or Temporary) Disable, Enable, etc. Instead of viewing Command itself as a type of AIoT service, all types of AIoT services, excluding Inventory, may be considered as types of Command.

[0193] The method proposed in this specification can be applied to various AIoT services (e.g., Sensor, Tracking, Positioning, etc.) in addition to the types of AIoT services described above.

[0194] In this specification, terms such as AIoT-related requests, AIoT service requests, and AIoT requests are used interchangeably.

[0195] In this specification, AIoT-related requests may include inventory requests, command requests, read requests, write requests, inactive requests, permanently (or Permanent) inactive requests, temporary (or Temporary) inactive requests, active requests, etc. In this specification, AIoT-related requests may also include requests in the form of combinations of the aforementioned types of requests.

[0196] In this specification, AIoT-related latency requirements (or AIoT-related latency requirements or AIoT-related latency requirements) may refer to the AIoT service completion time, the time taken to provide a response / result to an AIoT request, the time required to provide a response / result to an AIoT request, the AIoT request execution completion time, the AIoT request execution deadline, and the AIoT service-related period (period, etc.). Here, the response may be interpreted not merely as providing an ACK to indicate that the AIoT-related request has been successfully received, but as processing the AIoT-related request and providing / notifying the result thereof.

[0197] The last known reader in this specification may be an AIoT reader that last interacted with the target AIoT device.

[0198] The AIOT reader in this specification may be a base station. Alternatively, the AIOT reader in this specification may be one that is included in or supported by a base station. In this specification, one base station (or AIoT RAN node) may include or support one or more AIOT readers.

[0199] The AIoT reader of this specification can serve a target AIoT device.

[0200] The methods proposed in this specification may consist of a combination of one or more operations, configurations, or steps described below. The proposed methods may be performed or used in combination or complementarily.

[0201] I. First Embodiment: Determining whether AIOTF provides additional AIoT leader information to the base station in addition to the last known leader

[0202] 1. First example of the first embodiment

[0203] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0204] FIG. 8 shows a flowchart of a first example of a first embodiment according to the disclosure of the present specification.

[0205] Figure 8 illustrates the AIoT service processing procedure in an AIoT architecture where a base station (AIoT RAN) and an AIOTF are connected via a direct interface.

[0206] Figure 8 illustrates and explains that the AIoT service procedure is for a command, but the proposed content can be applied to all AIoT service procedures.

[0207] The first embodiment assumes the following:

[0208] - Prior to this procedure (e.g., prior to step 1), an AIoT procedure has been performed on the target AIoT device (or multiple target AIoT devices). Accordingly, the core network (e.g., AIOTF or other NF) stores information (e.g., the last known reader) regarding the target AIoT device (or multiple target AIoT devices).

[0209] 1) Step 1

[0210] AF can transmit AIoT service requests to the core network.

[0211] Here, although it is illustrated that AF directly transmits the AIoT service request to AIOTF, AF may transmit the AIoT service request to NEF, and NEF may transmit the AIoT service request to AIOTF.

[0212] The above AIoT service request may include information related to the requested AIoT service. For example, the above AIoT service request may include information such as the type of the requested service and target AIoT device(s).

[0213] The above AIoT service request may include at least one of the following:

[0214] - AIoT service related information: Service type (e.g., inventory or command (read or write))

[0215] - Information to be used for AIoT leader selection: Target area information

[0216] - Information related to the target AIoT device: One or more of the AIoT device ID or filtering information that can be used to connect multiple AIoT devices

[0217] - Information to be used for resource allocation: Approximate number of AIoT devices, approximate D2R (Device to Reader) message size

[0218] In addition, the above AIoT service request may include the AIoT service completion time.

[0219] For example, the AIoT service completion time may be expressed as a specific time (in units such as msec, sec, etc.) from the time AF transmitted the request. For example, the AIoT service completion time may be expressed as the time when the AIoT service is to be completed (e.g., January 6, 2026, 2:29 PM). The AIoT service completion time may be expressed in various other forms.

[0220] The above AIoT service request may include the type of service being requested. The type of service being requested may be a command (e.g., command, read, write, disable, etc.).

[0221] AIOTF (and / or NEF) may also perform authentication / verification for the above AIoT service request.

[0222] 2) Step 2

[0223] AIOTF can send a response to the above AIoT service request to AF. This may also be sent to AF via NEF.

[0224] Step 2 may be omitted.

[0225] 3) Step 3

[0226] AIOTF can check whether information about the target AIoT device(s) is stored.

[0227] Information about the target AIoT device(s) may be stored in AIOTF. Alternatively, AIOTF may obtain information about the target AIoT device(s) stored in another NF.

[0228] Since an AIoT procedure was performed on the target AIoT device (or multiple target AIoT devices) prior to this procedure (e.g., prior to step 1), the core network stores information about the target AIoT device (or multiple target AIoT devices) (e.g., information about the last known leader). Therefore, AIOTF can verify information about the target AIoT device (or multiple target AIoT devices) (e.g., information about the last known leader).

[0229] AIOTF can send a command request (a command-related AIoT service request message) to a base station (AIoT RAN node). The base station may be a base station that supports / includes the last known leader.

[0230] At this time, the AIOTF may provide support information to the base station (AIoT RAN node) along with a command request (a command-related AIoT service request message). Alternatively, the command request (a command-related AIoT service request message) may include support information.

[0231] Based on the information received from AF, AIOTF can determine the support information to provide to the base station.

[0232] The support information included in (or transmitted together with) the above command request (command-related AIoT service request message) may include one or more of the following information:

[0233] - AIoT service types (e.g., Inventory, Command)

[0234] - Optionally, number of AIoT devices based on AF request (approximate value)

[0235] - Optionally, D2R message size based on AF request (approximate value)

[0236] A command request (a command-related AIoT service request message) may include the last known reader information for a specific target AIoT device (e.g., identification information of the AIoT reader).

[0237] The AIOTF may include information about other AIOT leader(s) in the above command request (along with / instead of the last known leader information for a specific target AIOT device). Whether the AIOTF includes information about other AIOT leader(s) may be determined based on various information. For example, whether the AIOTF includes information about other AIOT leader(s) may be determined based on at least one of the information in a) to e) below (or information in a combined form):

[0238] - a) AIoT service completion time provided by AF (or AIoT service completion time set in AIOTF if AF does not provide AIoT service completion time): The AIoT service completion time set in AIOTF may also be set per type of AIoT service.

[0239] For example, if the AIoT service completion time is short, the AIOTF may decide to include information on other AIoT leader(s) (additionally or instead) in addition to the last known leader for the target AIoT device (if such information exists).

[0240] - b) Time / period when the last AIoT procedure was performed on the target AIoT device: This information may be stored in the information regarding the AIoT device.

[0241] For example, if the time / date when the last AIoT procedure was performed on the target AIoT device is old, the AIOTF may decide to include information on other AIoT leader(s) (additionally / instead of) in addition to the last known leader for the target AIoT device (if such information exists).

[0242] - c) Time taken to receive a response / result for an AIoT service request for the target AIoT device (average value and / or maximum value): This information may be stored in the information regarding the AIoT device.

[0243] For example, if the time taken is insufficient compared to the AIoT service completion time of a) above, the AIOTF may decide to include information on other AIoT leader(s) (additionally / instead of) in addition to the last known leader for the target AIoT device (if such information exists).

[0244] - d) Time taken to receive a response / result for an AIoT service request, including not only the target AIoT device but also other AIoT devices (average value and / or longest value): This information may be stored in the information regarding the AIoT device.

[0245] - e) AIOTF local configuration / policy

[0246] The above command request (command-related AIoT service request message) may include the AIoT service completion time.

[0247] Determining whether AIOTF includes information about other AIOT leader(s) in the above command request (along with / instead of the last known leader information for a specific target AIOT device) can be interpreted as ultimately selecting / determining AIoT leader(s) or determining AIoT leader information to provide to the AIoT RAN node.

[0248] In addition to the last known leader, other AIoT leader(s) selected / determined (or instead) may correspond to one or more of the following:

[0249] - AIoT leader(s) located in adjacent / neighboring positions to the last known leader

[0250] - AIoT leader(s) serving around the last known leader's service / serving area

[0251] - Other AIoT leader(s) supported / included by the AIoT RAN node that supports / includes the last known leader

[0252] - AIoT leader(s) supported / included by the AIoT RAN node that supports / includes the last known leader and the neighboring AIoT RAN node

[0253] Based on location information of each AIoT leader, service / serving area information of each AIoT leader, location information of base stations (AIOT RAN nodes) supporting / containing AIoT leaders, and / or service / serving area information of base stations (AIOT RAN nodes) supporting / containing AIoT leaders, AIOTF can select / determine AIoT leader(s) adjacent / neighbored to the last known leader.

[0254] Including information about other AIoT leader(s) in addition to the last known leader in a command request (command-related AIoT service request message) transmitted by the AIOTF to a base station may mean that the AIOTF transmits the said command request to a base station that supports / includes each of all AIoT leaders (e.g., the last known leader and other AIoT leader(s)), including information about the AIoT leader(s) supported / included by that base station.

[0255] For example, the AIoT leaders selected / determined by AIOTF may be as follows:

[0256] - The last known leader (AIoT Leader A) and AIoT Leader B supported / included by Base Station #1 (AIoT RAN node #1)

[0257] - AIoT Leader C supported / included by Base Station #2 (AIoT RAN node #2)

[0258] In this case, AIOTF may transmit a command request to Base Station #1 containing information about AIoT Leader A and AIoT Leader B. And, AIOTF may transmit a command request to Base Station #2 containing information about AIoT Leader C.

[0259] 4) Step 4

[0260] A base station (AIoT RAN node) that receives a command request (command-related AIoT service request message) from AIOTF can have the AIoT leader(s) included in the command request perform a command procedure.

[0261] A base station (or AIoT reader(s) supported / included by the base station) can perform a command procedure with a target AIoT device.

[0262] Although only one AIoT device is shown in FIG. 8, if there are multiple target AIoT devices, step 4 can be performed for multiple target AIoT devices.

[0263] 5) Step 5

[0264] The base station (AIOT RAN node) can transmit a command response (command-related AIoT service response message) to the AIOTF based on the result of the command procedure performed with the target AIoT device.

[0265] For example, the base station may transmit a command response (command-related AIoT service response message) containing the result of the command procedure performed in step 4 to the AIOTF.

[0266] 6) Step 6

[0267] Based on the command response received from the base station, the AIOTF can notify the AF of the result regarding the AIoT service request. This may also be transmitted to the AF via the NEF.

[0268] If there are multiple target AIoT devices, the message in step 3 may include information about the multiple AIoT devices. Additionally, the message in step 6 may include information about results for all of the multiple AIoT devices.

[0269] 2. Second example of the first embodiment

[0270] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0271] FIG. 9 shows a flowchart of a second example of a first embodiment according to the disclosure of the present specification.

[0272] Figure 9 shows the AIoT service processing procedure in an AIoT architecture where a base station (AIoT RAN) and an AIOTF are connected via an AMF (e.g., indirectly connected).

[0273] Figure 9 illustrates and explains that the AIoT service procedure is for a command, but the proposed content can be applied to all AIoT service procedures.

[0274] The procedure illustrated / described in Fig. 9 can be understood as identical to the procedure illustrated / described in Fig. 8, except that message exchange between the AIOTF and the AIoT RAN node takes place through the AMF.

[0275] In the first embodiment (e.g., the first example of the first embodiment, the second example of the first embodiment), the AIOTF may determine whether to provide information on additional AIoT leaders to base stations (AIoT RAN nodes)(s) in addition to the last known leader. However, if there is information on the last known base station (last known AIoT RAN node) instead of the last known leader information for the target AIoT device, the AIOTF may select / determine additional base stations (AIoT RAN nodes)(s) in addition to the last known AIoT RAN node, taking into account the latency-related requirements of the AIoT, to request the execution of an AIoT procedure.

[0276] Alternatively, even if there is no last known leader information (and / or last known base station (last known AIOT RAN node) information) for the target AIoT device, the AIOTF may select / determine an AIoT leader(s) (or base station(s)) in consideration of the AIoT latency-related requirements to request the execution of an AIoT procedure.

[0277] For the selection / determination of the aforementioned AIoT leader(s) (or base station(s)) and the execution of AIoT procedures, the procedures / descriptions of the first embodiment (e.g., the first example of the first embodiment, the second example of the first embodiment) may be utilized / extended.

[0278] For example, if the AIoT service completion time is considered short (or compared to a long AIoT service completion time), more AIoT leader(s) (or base station(s)) may be selected / determined. Based on this, AIoT procedures may be performed.

[0279] For example, if there is no last known leader information (and / or last known base station information) for the target AIoT device but the last known location information (e.g., cell information, coordinate information, etc.) of the target AIoT device is known, the AIoT leader(s) (or base station(s)) may be selected / determined by considering such information and the latency-related requirements of AIoT.

[0280] II. Second Embodiment: Determining whether a base station (AIoT RAN node) will have an additional AIoT leader, other than the last known leader, perform an AIoT procedure.

[0281] 1. First example of the second embodiment

[0282] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0283] FIG. 10 shows a flowchart of the first example of the second embodiment according to the disclosure of the present specification.

[0284] FIG. 10 shows the AIoT service processing procedure in an AIoT architecture where the AIoT RAN and AIOTF are connected via a direct interface. FIG. 10 illustrates and explains that the AIoT service procedure is for commands, but the proposed content can be applied to all AIoT service procedures.

[0285] The first example of the second embodiment assumes the following:

[0286] - Prior to this procedure (e.g., prior to step 1), an AIoT procedure has been performed on the target AIoT device (or multiple target AIoT devices). Accordingly, the core network (e.g., AIOTF or other NF) stores information (e.g., the last known reader) regarding the target AIoT device (or multiple target AIoT devices).

[0287] 1-2) Step 1 and Step 2

[0288] The contents of step 1 and step 2 of the first example of the first embodiment may be applied.

[0289] 3) Step 3

[0290] AIOTF can check whether information about the target AIoT device(s) is stored.

[0291] Information about the target AIoT device(s) may be stored in AIOTF. Alternatively, AIOTF may obtain information about the target AIoT device(s) stored in another NF.

[0292] Since an AIoT procedure was performed on the target AIoT device (or multiple target AIoT devices) prior to this procedure (e.g., prior to step 1), the core network stores information about the target AIoT device (or multiple target AIoT devices) (e.g., information about the last known leader). Therefore, AIOTF can verify information about the target AIoT device (or multiple target AIoT devices) (e.g., information about the last known leader).

[0293] AIOTF can send a command request (a command-related AIoT service request message) to a base station (AIoT RAN node). The base station may be a base station that supports / includes the last known leader.

[0294] At this time, the AIOTF may provide support information to the base station (AIoT RAN node) along with a command request (a command-related AIoT service request message). Alternatively, the command request (a command-related AIoT service request message) may include support information.

[0295] Based on the information received from AF, AIOTF can determine the support information to provide to the base station.

[0296] The support information included in (or transmitted together with) the above command request (command-related AIoT service request message) may include one or more of the following information:

[0297] - AIoT service types (e.g., Inventory, Command)

[0298] - Optionally, number of AIoT devices based on AF request (approximate value)

[0299] - Optionally, D2R message size based on AF request (approximate value)

[0300] A command request (a command-related AIoT service request message) may include last known leader information for a specific target AIoT device (e.g., identification information of the AIoT leader). Here, the last known leader information included in the command request may be explicitly or implicitly expressed as the last known leader of the target AIoT device.

[0301] Alternatively, the last known leader information included in the above command request may simply be expressed as AIOT leader information. In this case, the base station (AIoT RAN node) may not recognize that the AIOT leader included in the received information is the 'last known leader'. In this case, the 'last known leader' in the following description may be interpreted as being replaced with the 'AIoT leader provided by AIOTF'.

[0302] The above command request may include the AIoT service completion time. This may be the AIoT service completion time provided by AF, or, if AF has not provided an AIoT service completion time, the AIoT service completion time set in AIOTF.

[0303] Below, the operations performed by the base station (AIoT RAN node #1) that received the message of step 3 after the message of step 3 is transmitted and before step 4 (and / or step 5) are described.

[0304] A base station (AIoT RAN node #1) that receives a command request from the AIOTF may determine whether to have an additional (or substitute) AIoT leader, other than the last known leader, perform an AIoT procedure. This decision may be made based on various information. For example, this decision may be made based on at least one (or a combination of) of the information in A) through F) below:

[0305] - A) AIoT service completion time provided by AIOTF (or AIoT service completion time set in the base station (AIoT RAN node #1) if AIOTF did not provide an AIoT service completion time)

[0306] The AIoT service completion time set in the base station (AIoT RAN node #1) may also be set for each type of AIoT service.

[0307] For example, if the AIoT service completion time is short, the base station (AIoT RAN node #1) may decide to have another AIoT leader perform the AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device.

[0308] - B) Time / period when the last AIoT procedure was performed on the target AIoT device: This information may be stored in the information about the target AIoT device stored / managed by the base station (AIoT RAN node #1) or may be provided by AIOTF.

[0309] For example, if the time / period when the last AIoT procedure was performed on the target AIoT device is old, the base station (AIoT RAN node #1) may decide to have another AIoT leader perform the AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device.

[0310] - C) Time taken to receive a response / result to an AIoT service request for a target AIoT device (average value and / or maximum value): This information may be stored in the information about the target AIoT device stored / managed by the base station (AIoT RAN node #1) or may be provided by AIOTF.

[0311] For example, if the time taken is insufficient compared to the AIoT service completion time of A), the base station (AIoT RAN node #1) may decide to have another AIoT leader perform the AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device.

[0312] - D) Time taken to receive a response / result for an AIoT service request, including not only the target AIoT device but also other AIoT devices (average value and / or maximum value): This information may be stored in the information about the target AIoT device stored / managed by the base station (AIoT RAN node #1) or may be provided by the AIOTF.

[0313] - E) Instruction information for the AIOTF to determine whether to have an additional (or substitute) AIoT leader, other than the last known leader, perform the AIoT procedure to the base station (AIoT RAN node #1): This information may be included in the Step 3 message.

[0314] - F) Local configuration / policy of base station (AIoT RAN node#1)

[0315] The decision by the base station (AIoT RAN node #1) to have another AIoT leader perform an AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device can be explained as ultimately selecting / determining the AIoT leader(s).

[0316] The decision by a base station (AIoT RAN node #1) to have another AIoT leader perform an AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device may be interpreted as selecting / determining another base station (AIoT RAN node(s)). Here, the other base station may be a base station that supports / includes the selected / determined AIoT leader(s).

[0317] In addition to the last known leader, other AIoT leader(s) selected / determined (or instead) may correspond to one or more of the following:

[0318] - AIoT leader(s) located in adjacent / neighboring positions to the last known leader

[0319] - AIoT leader(s) serving around the last known leader's service / serving area

[0320] - Other AIoT leader(s) supported / included by the base station (AIoT RAN node) that supports / includes the last known leader

[0321] - The base station (AIoT RAN node) supporting / containing the last known leader and the AIoT leader(s) supported / containing by other neighboring base stations (AIoT RAN nodes)

[0322] The base station can select / determine AIOT leader(s) adjacent to / neighboring with the last known leader based on one or more of the following information:

[0323] - Location information of the AIoT reader supported / included by the above base station

[0324] - Service / serving area information of the AIoT reader supported / included by the above base station

[0325] - Service / serving area information of AIoT leader(s) supported / included by other neighboring base stations

[0326] If the above base station does not know the service / serving area information of the AIoT leader(s) supported / included by the neighboring base station (AIoT RAN node), only the neighboring base station (AIoT RAN node)(s) may be selected / determined, and the neighboring base station (AIoT RAN node)(s) may select / determine the AIoT leader(s).

[0327] In the case where there are multiple target AIoT devices, the decision by the base station (AIoT RAN node #1) to have another AIoT leader perform an AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device can be understood as a decision for all target AIoT devices.

[0328] 4) Step 4

[0329] If a base station (AIoT RAN node #1) decides to have other AIoT leader(s) perform an AIoT procedure in addition to (or instead of) the last known leader for the target AIoT device, and another base station (AIoT RAN node #2) supports / includes said other AIoT leader(s), the base station (AIoT RAN node #1) may transmit the command request of step 3 to said other base station (AIoT RAN node #2).

[0330] A base station (AIoT RAN node #1) may transmit to another base station (AIoT RAN node #2) one or more of the information from i) to v) in response to the command request:

[0331] - i) Last known reader's service / serving area information and / or location information

[0332] - ii) If the base station (AIoT RAN node #1) selects / determines other AIoT leader(s), information on the AIoT leader(s) supported / included by the other base station (AIoT RAN node #2) among the selected / determined AIoT leader(s)

[0333] - iii) AIOTF information: This may be AIOTF information to which another base station (AIoT RAN node #2) sends the result / response of an AIoT procedure. For example, another base station (AIoT RAN node #2) may transmit the result of an AIOT command procedure to the AIOTF corresponding to the AIOTF information.

[0334] iv) Information included in the command request (Command-related AIoT service request message) sent by AIOTF: Refer to step 3. This information may be included when forwarding the request message sent by AIOTF to the base station (AIoT RAN node #1) as is, or it may be included separately when forwarding the request message.

[0335] In Figure 10, only AIoT RAN node #2 is shown as another base station. However, if another base station (AIoT RAN node) also needs to participate in the AIoT procedure, step 4 can be performed on that base station (e.g., AIoT RAN node #3, etc.).

[0336] 5) Step 5

[0337] The base station (AIoT RAN node #1) may have the selected / determined AIoT leader(s) perform a command procedure. The selected / determined AIoT leader may be only the last known leader, or additionally (or instead) other AIoT leader(s) supported / included by the base station (AIoT RAN node #1).

[0338] Although only one AIoT device is shown in FIG. 10, if there are multiple target AIoT devices, step 5 can be performed for multiple target AIoT devices.

[0339] Step 4 and Step 5 may be performed in parallel, or Step 5 may be performed before Step 4.

[0340] 6) Step 6

[0341] Based on a message received from a base station (AIoT RAN node #1) and information contained in the message, another base station (AIoT RAN node #2) may have the selected / determined AIoT leader(s) perform a command procedure.

[0342] Based on the information in i) and / or ii) described in step 4 above, another base station (AIoT RAN node #2) can select / determine the AIoT leader(s) to perform the command procedure.

[0343] 7) Step 7

[0344] The base station (AIoT RAN node #1) can transmit a command response (command-related AIoT service response message) to the AIOTF based on the result of a command procedure performed by the AIoT leader(s).

[0345] For example, the base station may transmit a command response (command-related AIoT service response message) containing the result of the command procedure performed in step 5 to the AIOTF.

[0346] The base station (AIoT RAN node #1) may include information indicating that it has forwarded a command request to another base station (e.g., AIoT RAN node #2) in the command response. The information may also include information regarding which base station (AIoT RAN node)(s) the command request was forwarded to (e.g., identification information of the AIoT RAN node(s).

[0347] 8) Step 8

[0348] Another base station (AIoT RAN node #2) can send a command response (command-related AIoT service response message) to the AIOTF based on the result of the command procedure by the AIoT leader(s).

[0349] 9) Step 9

[0350] Based on the command response (command-related AIoT service response message) received from the base station (AIoT RAN node)(s), the AIOTF may notify the AF of the result of the AIoT service request. This may also be transmitted to the AF via the NEF.

[0351] If there are multiple target AIoT devices, the step 3 message may include information about the multiple AIoT devices. And, the step 9 message may include information about the results for all AIoT devices.

[0352] 2. Second example of the second embodiment

[0353] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0354] FIG. 11 shows a flowchart of a second example of a second embodiment according to the disclosure of the present specification.

[0355] Figure 11 shows the AIoT service processing procedure in an AIoT architecture where a base station (AIoT RAN) and an AIOTF are connected via an AMF (e.g., indirectly connected).

[0356] Figure 11 illustrates and explains that the AIoT service procedure is for a command, but the proposed content can be applied to all AIoT service procedures.

[0357] The procedure illustrated / described in Fig. 11 can be understood as identical to the procedure illustrated / described in Fig. 10, except that the message exchange between the AIOTF and the base station (AIoT RAN node) takes place through the AMF.

[0358] 3. Third example of the second embodiment

[0359] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0360] FIG. 12 shows a flowchart of a third example of a second embodiment according to the disclosure of the present specification.

[0361] Figure 12 shows the AIoT service processing procedure in an AIoT architecture where a base station (AIoT RAN) and an AIOTF are connected via an AMF (e.g., indirectly connected).

[0362] Figure 12 illustrates and explains that the AIoT service procedure is for a command, but the proposed content can be applied to all AIoT service procedures.

[0363] The procedure illustrated / described in FIG. 12 may be applied differently from the procedure illustrated / described in FIG. 10 as follows:

[0364] - When a base station (AIoT RAN node #1) transmits a command request (a command-related AIoT service request message) to another base station (AIoT RAN node #2), the command request may be transmitted via an AMF rather than a directly connected interface (Step 4a and Step 4b). To this end, the base station (AIoT RAN node #1) may transmit information about the other base station (AIoT RAN node #2) to the AMF. For example, the message in step 4a may include information about the other base station (AIoT RAN node #2). Based on this, the AMF can recognize the target of the message in step 4b.

[0365] Other than that, the same procedure as illustrated / described in FIG. 10 can be applied to FIG. 12.

[0366] In Fig. 12, the base station (AIoT RAN node #1) selects another base station (AIoT RAN node #2) and notifies the AIOTF, but it is also possible for the AIOTF to directly select another base station (AIoT RAN node #2) in Step 3 without the help of the base station (AIoT RAN node #1) and transmit a command request.

[0367] For example, after performing base station (AIoT RAN node) selection in AIOTF, it is also possible to entrust the selection / decision of the AIoT leader to the selected base station (AIoT RAN node).

[0368] In the second embodiment (e.g., the first example of the second embodiment, the second example of the second embodiment, and the third example of the second embodiment), the base station (AIoT RAN node) determined whether to have an additional AIoT leader, other than the last known leader, perform the AIoT procedure. However, even if there is no information on the last known leader for the target AIoT device, the base station (AIoT RAN node) may select / determine additional other base station (AIoT RAN node)(s) or AIoT leader(s) in consideration of AIoT latency-related requirements to request the performance of the AIoT procedure.

[0369] For the selection / determination of the other base station (AIoT RAN node)(s) (or AIoT leader(s)) mentioned above and the execution of AIoT procedures, the procedures / descriptions of the second embodiment (e.g., the first example of the second embodiment, the second example of the second embodiment, the third example of the second embodiment) may be utilized / extended.

[0370] For example, if the AIoT service completion time is considered short (in contrast to a long AIoT service completion time), the base station may select / determine more AIoT leader(s) and / or base station(s) (AIoT RAN node) to perform the AIoT procedure.

[0371] If there is no information on the last known leader for the target AIOT device, the base station may select / determine AIoT leader(s) and / or base station (AIoT RAN node)(s) based on (if possible) the last known location information (e.g., cell information, coordinate information, etc.) of the target AIOT device and the latency-related requirements of AIoT to perform the AIoT procedure.

[0372] III. Third Embodiment: Method by which AIOTF provides priority information to base station (AIoT RAN node)(s)

[0373] AIOTF can transmit a command request (command-related AIoT service request message) to a base station (AIoT RAN node) by including priority information.

[0374] AIOTF can determine priority by combining the following information:

[0375] - Priority information and / or service type information included by AF in the AIoT request message

[0376] - Priority information set in AIOTF by AF

[0377] - Priority information set in AIOTF by service type

[0378] - Priority information set in AIOTF by combination of AF and service type

[0379] - AIoT service completion time. For example, if the AIoT service completion time is short, AIOTF can set the priority high, and if the service completion time is long, AIOTF can set the priority low.

[0380] - The number of AIoT procedures currently being performed by AIoT leaders (or AIoT RAN nodes) that have not yet received a response / result, and the priority information assigned to each procedure

[0381] When a base station (AIoT RAN node) performs paging for AIoT device(s) through AIoT leader(s) based on priority information provided by AIOTF, the base station (AIoT RAN node) can process requests with higher priority first.

[0382] Alternatively, based on priority information provided by AIOTF, AIoT leader(s) can process high-priority requests first when performing paging for AIoT device(s).

[0383] For example, AIoT leader(s) can prioritize scheduling paging for high-priority requests. This can reduce response times for AIoT device(s). Additionally, the frequency used and paging repetitions can be performed differently depending on the priority.

[0384] In Step 4 of FIGS. 10 and 11, the base station (AIoT RAN node #1) may also transmit the priority information to another base station (AIoT RAN node #2).

[0385] IV. Fourth Embodiment: AIOTF provides information from other AIoT reader(s) instead of the last known reader to AIoT RAN node(s)

[0386] Basically, the procedure of the fourth embodiment can be performed as described in the first embodiment.

[0387] According to the fourth embodiment, the AIOTF may perform one or more of the following operations:

[0388] - Even if the last known leader is stored in the context for the target AIoT device (the target AIoT device requested by AF), the AIOTF may decide to select alternative (other) AIoT leader(s) in place of that leader (the last known leader). If the selection of alternative AIoT leader(s) is decided, the AIOTF may provide information about the alternative AIoT leader(s) to the base station (AIoT RAN node)(s).

[0389] As described above, in order to perform AIOT procedures with the target AIOT device, the AIOTF may decide to select alternative AIoT leader(s) in place of the last known leader. This decision may be based on one or more of the following information / reasons. However, the above decision may be based on various information / reasons, not limited to the information / reasons below:

[0390] - The last known AIoT reader is not available.

[0391] - The last known AIoT reader is disabled.

[0392] - The Last known AIoT reader is overloaded in performing AIoT reader operations.

[0393] - AIOTF local configuration / policy

[0394] Through the disclosure of this specification, AIoT services can be supported by taking into account the latency-related requirements of AIoT.

[0395] According to the disclosure of the present specification, the following operations may be performed:

[0396] - AIOTF may receive an AIoT service request from AF. The request may include the AIoT service completion time.

[0397] - AIOTF may select / determine AIoT leader(s) for the target AIoT device. This may involve selecting / determining other AIoT leader(s) along with (or in place of) the last known leader information for the target AIoT device if such information is available or exists. When making such selections / determinies, the AIoT service completion time may be considered.

[0398] - AIOTF may enable the selected / determined AIoT leader(s) to perform an AIoT service request. This may involve sending a message related to the AIoT service request to a base station (AIoT RAN node)(s) that supports / includes the AIoT leader(s).

[0399] - AIOTF can receive the results of performing AIoT service requests from base stations (AIoT RAN nodes).

[0400] - AIOTF can provide / notify AF of the results of AIoT service request execution.

[0401] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0402] FIG. 13 illustrates a first example of the AIOTF procedure for the disclosure of the present specification.

[0403] 1. AIOTF (Ambient Internet of Things Function) can receive AIOT requests from AF (Application Function).

[0404] The above AIOT request may include information about the target AIOT device.

[0405] The last known reader for the above target AIOT device may be the first reader.

[0406] 2. Based on the above AIoT request, the above AIOTF can determine the first leader and the second leader as AIoT leaders for the target AIoT device.

[0407] Based on the above decision, the AIOTF can transmit a first command request with the target AIOT device to a base station including the first leader.

[0408] Based on the above decision, the AIOTF can transmit a second command request with the target AIOT device to a base station including the second leader.

[0409] The above first command request and the above second command request can be transmitted through the AMF (Access and Mobility management Function).

[0410] The above AIOT request may include at least one of i) an AIOT service type, ii) a target area, or iii) time information on when the AIoT service must be completed.

[0411] The first reader mentioned above may be the AIOT reader that last performed an interaction with the target AIOT device.

[0412] The second leader may correspond to at least one of i) a leader located at a position adjacent to the first leader, ii) a leader serving around the serving area of ​​the first leader, iii) another leader included in a base station including the first leader, or iv) a leader included in a base station adjacent to the base station including the first leader.

[0413] The step of the AIOTF determining the first leader and the second leader may be performed based on at least one of: i) location information of one or more leaders, ii) serving area information of one or more leaders, or iii) information related to a base station including one or more leaders.

[0414] Based on the first command request, the AIOTF can receive a first result of a command procedure with the target AIOT device from a base station including the first leader.

[0415] Based on the second command request, the AIOTF can receive a second result of a command procedure with the target AIOT device from a base station including the second leader.

[0416] The above AIOTF can transmit the response to the above AIOT request to the above AF.

[0417] The above response may include the above first result and the above second result.

[0418] The first reader and the second reader may be a base station or a reader included in a base station.

[0419] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0420] FIG. 14 illustrates a second example of the AIOTF procedure for the disclosure of the present specification.

[0421] 1. AIOTF can receive AIOT requests from AF.

[0422] The above AIOT request may include information about the target AIOT device.

[0423] The last known reader for the above target AIOT device may be the first reader.

[0424] 2. Based on the above AIoT request, the above AIOTF may determine a second leader as an AIoT leader for the target AIoT device in place of the first leader.

[0425] Based on the above decision, the AIOTF can transmit a second command request with the target AIOT device to a base station including the second leader.

[0426] The above second command request can be transmitted via AMF.

[0427] The above AIOT request may include at least one of i) an AIOT service type, ii) a target area, or iii) time information on when the AIoT service must be completed.

[0428] The first reader mentioned above may be the AIOT reader that last performed an interaction with the target AIOT device.

[0429] The second leader may correspond to at least one of i) a leader located at a position adjacent to the first leader, ii) a leader serving around the serving area of ​​the first leader, iii) another leader included in a base station including the first leader, or iv) a leader included in a base station adjacent to the base station including the first leader.

[0430] The step of the AIOTF determining the second leader may be performed based on at least one of: i) location information of one or more leaders, ii) serving area information of one or more leaders, or iii) information related to a base station including one or more leaders.

[0431] Based on the second command request, the AIOTF can receive a second result of a command procedure with the target AIOT device from a base station including the second leader.

[0432] The above AIOTF can transmit the response to the above AIOT request to the above AF.

[0433] The above response may include the above second result.

[0434] The first reader and the second reader may be a base station or a reader included in a base station.

[0435] The step of the AIOTF determining the second leader may be performed based on at least one of: i) the first leader is not available, ii) the first leader is disabled, or iii) the first leader is overloaded.

[0436] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0437] For example, the device may include a processor, a transceiver, and memory.

[0438] For example, the processor can be configured to be operablely coupled with memory and the processor.

[0439] The operation performed by the above processor may include: a step in which an Ambient Internet of Things Function (AIOTF) receives an AIOT request from an Application Function (AF); and a step in which the AIOT request includes information about a target AIOT device, the last known reader for the target AIOT device is a first reader, and based on the AIOT request, the AIOTF determines the first reader and the second reader as AIOT readers for the target AIOT device.

[0440] Hereinafter, a processor of a device for providing communication according to some embodiments of the present specification will be described.

[0441] The operation performed by the above processor may include the step of an AIOTF (Ambient Internet of Things Function) receiving an AIOT request from an AF (Application Function); and the step of the AIOT request including information about a target AIOT device, the last known reader for the target AIOT device being a first reader, and based on the AIOT request, the AIOTF determining the first reader and the second reader as AIOT readers for the target AIOT device.

[0442] Hereinafter, a non-volatile computer-readable medium storing one or more instructions for providing mobile communication according to some embodiments of the present specification will be described.

[0443] According to some embodiments of the present disclosure, the technical features of the present disclosure may be directly implemented in hardware, software executed by a processor, or a combination of both. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0444] In some examples, storage media are coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. In other examples, the processor and storage media can reside as separate components.

[0445] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0446] For example, non-volatile computer-readable media may include RAM (Random Access Memory) such as SDRAM (Synchronization Dynamic Random Access Memory), ROM (Read-Only Memory), and NVRAM (Non-Volatile Random Access Memory); read-only memory (EEPROM); flash memory; magnetic or optical data storage media; or other media that can be used to store instructions or data structures. Non-volatile computer-readable media may also include combinations of the above.

[0447] Additionally, the method described herein may be realized at least partially by a computer-readable communication medium that transmits or transmits code in the form of instructions or data structures and can be accessed, read, and / or executed by a computer.

[0448] According to some embodiments of the present disclosure, a non-transient computer-readable medium stores one or more instructions thereon. The stored one or more instructions can be executed by a processor of a base station.

[0449] One or more stored commands may include the step of an AIOTF (Ambient Internet of Things Function) receiving an AIOT request from an AF (Application Function); and the step of the AIOT request including information about a target AIOT device, the last known reader for the target AIOT device being a first reader, and based on the AIOT request, the AIOTF determining the first reader and the second reader as AIOT readers for the target AIOT device.

[0450] This specification may have various effects.

[0451] For example, efficient AIOT procedures can be performed.

[0452] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0453] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

1. As a method, A step in which an AIOTF (Ambient Internet of Things Function) receives an AIOT request from an AF (Application Function); and The above AIOT request includes information about the target AIOT device, and The last known reader for the above target AIOT device is the first reader, and A method comprising the step of determining the first leader and the second leader as AIOT leaders for the target AIOT device based on the above AIoT request.

2. In Paragraph 1, Based on the above decision, the AIOTF transmits a first command request with the target AIOT device to a base station including the first leader; and A method further comprising the step of, based on the above decision, the AIOTF transmitting a second command request with the target AIOT device to a base station including the second leader.

3. In Paragraph 2, A method in which the above-mentioned first command request and the above-mentioned second command request are transmitted through an AMF (Access and Mobility management Function).

4. In any one of paragraphs 1 through 3, A method in which the above AIOT request includes at least one of i) an AIOT service type, ii) a target area, or iii) time information on when the AIoT service must be completed.

5. In any one of paragraphs 1 through 4, A method in which the first leader is an AIOT leader that last performed an interaction with the target AIOT device.

6. In any one of paragraphs 1 through 5, A method in which the second leader is at least one of i) a leader located adjacent to the first leader, ii) a leader serving around the serving area of ​​the first leader, iii) another leader included in a base station including the first leader, or iv) a leader included in a base station adjacent to the base station including the first leader.

7. In any one of paragraphs 1 through 6, The step of the AIOTF determining the first leader and the second leader is performed based on at least one of: i) location information of one or more leaders, ii) serving area information of one or more leaders, or iii) information related to a base station including one or more leaders.

8. In any one of paragraphs 1 through 7, Based on the first command request, the AIOTF receives a first result of a command procedure with the target AIOT device from a base station including the first reader; Based on the second command request, the AIOTF receives a second result of a command procedure with the target AIOT device from a base station including the second leader; and The above AIOTF further includes the step of transmitting a response to the AIOT request to the AF, and The above response is a method including the above first result and the above second result.

9. In any one of paragraphs 1 through 10, A method in which the first leader and the second leader are a base station or a leader included in a base station.

10. As a method, A step in which AIOTF receives an AIOT request from AF; and The above AIOT request includes information about the target AIOT device, and The last known reader for the above target AIOT device is the first reader, and A method comprising the step of determining a second leader in place of the first leader as an AIOT leader for the target AIOT device based on the above AIoT request.

11. In Paragraph 10, A method further comprising the step of, based on the above decision, the AIOTF transmitting a second command request with the target AIOT device to a base station including the second leader.

12. In Paragraph 11, The above second command request is transmitted via AMF.

13. In any one of paragraphs 10 through 12, A method in which the above AIOT request includes at least one of i) an AIOT service type, ii) a target area, or iii) time information on when the AIoT service must be completed.

14. In any one of paragraphs 10 through 13, A method in which the first leader is an AIOT leader that last performed an interaction with the target AIOT device.

15. In any one of paragraphs 10 through 14, A method in which the second leader is at least one of i) a leader located adjacent to the first leader, ii) a leader serving around the serving area of ​​the first leader, iii) another leader included in a base station including the first leader, or iv) a leader included in a base station adjacent to the base station including the first leader.

16. In any one of paragraphs 10 through 15, The step of the AIOTF determining the second leader is performed based on at least one of: i) location information of one or more leaders, ii) serving area information of one or more leaders, or iii) information related to a base station including one or more leaders.

17. In any one of paragraphs 10 through 16, Based on the second command request, the AIOTF receives a second result of a command procedure with the target AIOT device from a base station including the second leader; and The above AIOTF further includes the step of transmitting a response to the AIOT request to the AF, and The above response is a method including the above second result.

18. In any one of paragraphs 10 through 17, A method in which the first leader and the second leader are a base station or a leader included in a base station.

19. In any one of paragraphs 10 through 18, A method in which the step of the AIOTF determining the second reader is performed based on at least one of: i) the first reader is not available, ii) the first reader is disabled, or iii) the first reader is overloaded.

20. As an AIOTF performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is an AIOTF, which is a method according to any one of claims 1 to 19.

21. As an apparatus in mobile communication, At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and An apparatus in which the operation performed based on the execution of the above instruction by the at least one processor is a method according to any one of claims 1 to 19.

22. A non-volatile computer-readable storage medium that records instructions, A non-volatile computer-readable storage medium in which, when the above instructions are executed by one or more processors, the operation that causes the one or more processors to perform is a method according to any one of claims 1 to 19.

Images