Communication based on IoT

Abstract

A method is provided in the present disclosure. The method may comprise the steps of: transmitting, to a network entity, a setup request message related to an interface between a device and the network entity; and receiving a setup response message from the network entity.

Description

IOT-based communication

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] Communication based on Ambient IoT (AIoT) is being discussed. However, conventional technology presents a problem: AIoT-based communication cannot be performed effectively and / or accurately.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include the steps of transmitting a setup request message related to an interface between a device and a network entity to the network entity; and receiving a setup response message from the network entity.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method is provided. The method may include: receiving a setup request message related to an interface between a base station and a network entity from the base station; transmitting a setup response message to the base station; receiving a first service response message from the base station; and generating location information of at least one area based on an area index of at least one area in which the response was received.

[0009] According to one embodiment, a device implementing the method is provided.

[0010] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0011] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0012] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0013] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0014] FIGS. 5A to 5E illustrate examples of RACH procedures applicable to one embodiment of the present disclosure.

[0015] Figures 6a and 6b illustrate examples of topologies related to Ambient IoT.

[0016] Figures 7a and 7b illustrate an example of a procedure according to the first example of the disclosure of the present specification.

[0017] FIG. 8 illustrates an example of a leader of a base station according to one embodiment of the disclosure of the present specification.

[0018] Figures 9a to 9c illustrate an example of a procedure according to the second example of the disclosure of the present specification.

[0019] FIG. 10 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

[0020] The following techniques, devices, and systems can 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 Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using 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 using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0021] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features 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 a 3GPP-based wireless communication system can 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] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0024] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can 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 identically to “at least one of A and B.”

[0026] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0027] Additionally, parentheses used herein 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 individually described in 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 operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

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

[0031] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

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

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

[0034] Referring to FIG. 1, a 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 a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

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

[0036] The 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. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) 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., smart watches 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 personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, 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 a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0038] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via 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) can communicate with each other via the base station (200) / network (300), but can 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., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0039] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection 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 base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of the various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0040] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

[0042] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0043] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0044] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0045] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by 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 above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0046] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0047] 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 case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

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

[0049] 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 alternatively, the memory (104) may be located external to the processing chip (101).

[0050] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0051] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0052] 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) to transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

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

[0054] 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 located external to the processing chip (201).

[0055] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0056] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0057] 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 may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0058] 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 physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Service Data Adaptation Protocol (SDAP) layer). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0059] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The 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 the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0060] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can 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) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0061] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, 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 operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0062] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via 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) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0063] Although not illustrated in FIG. 2, the wireless device (100, 200) may further 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., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0064] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below 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 in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0065] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0066] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

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

[0068] The UE (100) includes a processor (102), memory (104), a 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).

[0069] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or 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 flowcharts disclosed herein. A layer of a radio 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 processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0070] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

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

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

[0073] The display (143) outputs the results 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).

[0074] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

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

[0076] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0077] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0078] - AUSF (Authentication Server Function)

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

[0080] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0081] - USDF (Unstructured Data Storage Function)

[0082] - NEF (Network Exposure Function)

[0083] - I-NEF (Intermediate NEF)

[0084] - NRF (Network Repository Function)

[0085] - NSSF (Network Slice Selection Function)

[0086] - PCF (Policy Control Function)

[0087] - SMF (Session Management Function)

[0088] - UDM (Unified Data Management)

[0089] - UDR (Unified Data Repository)

[0090] - UPF (User Plane Function)

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

[0092] - AF (Application Function)

[0093] - UE (User Equipment)

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

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

[0096] - NWDAF (Network Data Analytics Function)

[0097] - CHF (CHarging Function)

[0098] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

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

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

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

[0102] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0103] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

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

[0105] The 5G system architecture includes the following benchmarks:

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

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

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

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

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

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

[0112] The following benchmarks illustrate the interactions that exist between NF services in NF.

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

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

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

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

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

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

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

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

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

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

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

[0124] In some cases, two NFs may need to be interconnected to serve a UE.

[0125] <Random Access Channel (RACH) 절차>

[0126] FIGS. 5A to 5E illustrate examples of RACH procedures applicable to one embodiment of the present disclosure.

[0127] Referring to FIGS. 5A to 5E, a RACH procedure according to an embodiment of the present disclosure is described. The embodiments of FIGS. 5A to 5E may be combined with various embodiments of the present disclosure.

[0128] In one embodiment of the present disclosure, when RF requirements (e.g., Tx RF performance requirements and / or Rx RF performance requirements) are described, the UE can satisfy these RF requirements. For example, the UE can be tested to satisfy the RF requirements (e.g., Tx RF performance requirements and / or Rx RF performance requirements) according to one embodiment of the present disclosure. In one embodiment of the present disclosure, a UE that satisfies these RF requirements can perform a RACH procedure. When the UE transmits a message, data, signaling, etc. to the gNB, the UE satisfies the Tx RF performance requirements described in the first embodiment of the present specification. When the UE receives a message, data, signaling, etc. from the gNB, the UE satisfies the Rx RF performance requirement described in the first embodiment of the present specification.

[0129] To connect a UE to a 5G network, the UE and the 5G network must be synchronized in both uplink and downlink. Downlink synchronization occurs when the UE successfully decodes the SSB transmitted by the gNB. To establish uplink synchronization and RRC connection, the UE must perform a RACH random access procedure.

[0130] Two types of random access procedures are supported: a four-step Random Access (RA) type using MSG1 and a two-step RA type using MSGA.

[0131] Two types of RA procedures can support Contention Based Random Access (CBRA) and Contention Free Random Access (CFRA), as shown in Figures 5a to 5e below, respectively. The UE can select the random access type when initiating a random access procedure depending on network settings.

[0132] Referring to FIGS. 5a and 5c, a four-step RA type using MSG1 is described.

[0133] MSG1 of the 4-step RA type includes a preamble of the PRACH. The UE transmits MSG1. After transmitting MSG1, the UE monitors the network for a response within a set period of time.

[0134] For the CBRA example of FIG. 5a, when the UE receives a random access response (MSG2) from the gNB, the UE can transmit MSG3 using the UL grant scheduled by the response message. The UE can then monitor contention resolution. If contention resolution is not successful after (re)transmitting MSG3, the UE performs MSG1 transmission again.

[0135] For the CFRA example in Figure 5c, a dedicated preamble for MSG1 transmission is allocated by the network. The gNB transmits the RA preamble allocation to the UE. The UE transmits MSG1, which includes a random access preamble, to the gNB. Upon receiving a random access response from the network, the UE terminates the random access procedure.

[0136] Referring to Figures 5b, 5d, and 5e, a two-step RA type is described. The MSGA of the two-step RA type includes a random access preamble of the PRACH and a PUSCH payload. After the UE transmits the MSGA, the UE monitors the network's response within a configured window.

[0137] For CBRA according to the example of Fig. 5b, if the UE successfully resolves the contention after receiving a network response (e.g., MSGB), the UE terminates the random access procedure. If a fallback indication is received within the MSGB, the UE performs MSG3 transmission using the UL grant reserved in the fallback indication, as shown in Fig. 5e, and monitors contention resolution. If the contention resolution is not successful after the MSG3 (re)transmission, the UE performs MSGA transmission again.

[0138] For CFRA according to the example of FIG. 5d, the UE can receive an RA preamble allocation and a PUSCH allocation from the gNB. Then, dedicated preamble and PUSCH resources can be configured for MSGA transmission. The UE transmits the MSGA. When the UE receives a network response, the UE terminates the random access procedure.

[0139] If the random access procedure of type 2 RA is not completed after several MSGA transmissions, the UE may be configured to transition to CBRA of type 4 RA.

[0140] Ambient IoT refers to Internet of Things (IoT) technology that operates on low power and continuously collects and transmits data in the ambient environment. Existing IoT systems often require batteries or wired power. Ambient IoT utilizes technologies such as energy harvesting and backscattering to enable devices to operate for extended periods without power supply.

[0141] For example, energy harvesting can refer to a technology in which a device collects small amounts of energy from the ambient environment and converts it into electricity. Backscattering, for example, can refer to a technology in which a device transmits data using the principle of radio wave reflection (backscattering).

[0142] Ambient IoT can be used in a variety of applications, including smart packaging, logistics management, environmental monitoring, and healthcare.

[0143] For reference, in the disclosure of this specification, the terms Ambient IoT and AIoT may be used interchangeably. An AIoT device may refer to a device that supports operations based on Ambient IoT.

[0144] Technologies are being developed to support terminals that transmit data by harvesting energy through methods such as harvesting and backscattering. There is a need to obtain location information from AIoT devices with the utmost accuracy and transmit it to the network.

[0145] Architectural support for ambient power-enabled IoT devices is being studied.

[0146] Methods to support AIoT devices can be studied with the following examples:

[0147] - Architecture to support Ambient IoT, including security support for Ambient IoT devices or groups of Ambient IoT devices, including security support, device identity verification, device operation, and service security.

[0148] - Identification, subscription, registration, and connection management for supporting Ambient IoT devices. For example, research may be conducted to determine whether subscription management, registration management, and / or connection management are required, and if so, to identify the necessary state machines, procedures, and functions, taking into account the functions and characteristics of Ambient IoT devices. For example, research may be conducted to determine whether and how reachability and paging are applied to Ambient IoT devices, considering the functions and characteristics of Ambient IoT devices, and if so, what impact they have. Research may also be conducted on methods for identifying Ambient IoT devices or groups of devices, and on the format of identifiers.

[0149] Ambient IoT services. For example, research may be conducted on methods for supporting the transmission of information about ambient IoT services and related system functions. Research may also be conducted on ambient IoT services and methods enabled for exposure to AF.

[0150] Additionally, potential solutions for determining the location of Ambient IoT devices need to be discussed. In this case, methods for transmitting location information to the core network without affecting existing specifications or with minimal impact on existing specifications could also be discussed.

[0151] Referring to Figures 6a and 6b, examples of connectivity topologies for Ambient IoT networks and devices defined in TR 38.848 V18.0.0 are described. Note that in Topology 2 of Figure 6b, a UE may also act as an intermediate node.

[0152] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0153] Figures 6a and 6b illustrate examples of topologies related to Ambient IoT.

[0154] Fig. 6a shows an example of topology 1, and Fig. 6b shows an example of topology 2. In Figs. 6a and 6b, BS may mean a base station.

[0155] Referring to Fig. 6a, an example of topology 1 is described. In topology 1, the base station can communicate directly with the Ambient IoT device.

[0156] In Topology 1, Ambient IoT devices can communicate directly and bidirectionally with a base station. Communication between the base station and Ambient IoT devices may include Ambient IoT device data and / or signaling. In this topology, the base station transmitting signals to Ambient IoT devices and the base station receiving signals from Ambient IoT devices may be different.

[0157] For reference, in various examples of the disclosure of this specification, Ambient IoT devices may also be referred to as Ambient devices.

[0158] In topology 2 according to the example of FIG. 6b, the Ambient IoT device can indirectly communicate with the base station.

[0159] In Topology 2, Ambient IoT devices can communicate bidirectionally with an intermediate node between the device and the base station. In this topology, the intermediate node can be an Ambient IoT-enabled relay, IAB node, UE, repeater, etc. The intermediate node can transmit Ambient IoT data and / or signals between the BS and the Ambient IoT devices.

[0160] However, conventional technology presents a challenge: Ambient IoT (AIoT) devices cannot communicate effectively and / or accurately. For example, the RAN needs to acquire location information from Ambient IoT (AIoT) devices with the utmost accuracy and transmit it to the network.

[0161] For example, however, because AIoT devices must have low device complexity, there is a problem that it is difficult for AIoT devices to determine their current location information on their own or transmit it to the network.

[0162] For example, to provide effective AIoT services, a method is needed to obtain location information of AIoT devices and notify the network (e.g., base station, AF, etc.).

[0163] For reference, in the disclosure of this specification, a Reader may be a device capable of receiving a signal from an AIoT device or transmitting a signal to an AIoT device.

[0164] For example, there is a need for a method in which an A-RAN (i.e., Topology 1) or UE (i.e., Topology 2) with a Reader can obtain the location information of an AIoT Device as accurately as possible and then report that information to the network, and the network then reports this to the AF.

[0165] For example, because AIoT devices must have low device complexity, it may be difficult for AIoT devices to independently determine their current location information or transmit it to the network. For example, a method is needed in which an A-RAN (e.g., Topology 1 in Figure 6a) or a UE (e.g., Topology 2 in Figure 6b) with a reader can obtain the location information of an AIoT device as accurately as possible and then report the location information to the network, which then reports this information to the AF.

[0166] According to one embodiment of the disclosure of this specification, for Topology 1, a base station may include a Reader. For example, a base station may include one or more Readers associated with an area smaller than a cell. A base station with a Reader may be referred to as an A-RAN (Ambient IoT RAN or Ambient RAN).

[0167] A base station with a reader (e.g., A-RAN: Amibient RAN) can set up an NG or NG-like (NG') interface with the AIoTF that manages AIoT devices.

[0168] For reference, in the disclosure of this specification, NG refers to the interface between the 5G core network and the 5G base station. NG-like (NG') may refer to an interface between the base station and the AIoTF (or AMF), similar to the NG interface. NG-like (NG') may be identical to the NG interface, or a new interface different from the NG interface may be used.

[0169] When setting up an interface, a base station can also transmit location information for each reader's area of ​​responsibility, along with zoning / coordinate information. For example, A-RAN can divide the area covered by each reader into multiple zones or areas and then transmit coordinate information and index values ​​for each zone or area to AIoTF.

[0170] Based on the received information, AIoTF can convert the area that is the target of the AIoT Service operation (e.g., Inventory, Command) received from AF into an Area index or Zone index and transmit it to A-RAN.

[0171] Additionally, the A-RAN can perform AIoT service operations for the area corresponding to the area index or zone index. Afterwards, the A-RAN can transmit the response sent by the AIoT Device, along with the area index or zone index where the response was received, to the AIoTF. Based on the received information, the AIoTF can identify the area or zone where the AIoT Device sent the response, and can then convert this information into geographical information and transmit it to the AF.

[0172] According to one embodiment of the disclosure of this specification, for Topology 2, a UE with a Reader can perform a registration procedure with the network. The UE can transmit location information for the areas covered by individual Readers, along with information zoning / coordinates thereof, to AIoTF. Based on the received information, AIoTF can perform conversion between geographical location information and area index.

[0173] According to one embodiment of the disclosure of the present specification, the Reader may not immediately forward a response to an AIoT service operation from an AIoT Device to the AIoTF whenever it receives the response, but may forward the response after a certain period of time and / or when certain conditions are met. For example, the A-RAN (i.e., Topology 1) or the UE (i.e., Topology 2) may collect responses from the AIoT Device over a certain period of time and forward them to the AIoTF.

[0174] For reference, businesses can access AIoTF via AF. When businesses transmit coordinate information, such as GPS, to AIoTF, AIoT can replace the coordinate information with information related to AIoT-related readers.

[0175] An operation of measuring / collecting location information of an AIoT Device in units of area or zone and transmitting it to a network according to one embodiment of the disclosure of the present specification is composed of a combination of one or more operations / configurations / steps described below.

[0176] In various examples of the disclosure of this specification, an area or zone unit may be smaller in size than a cell.

[0177] In this specification, UE (User Equipment) and terminal may be used as terms with the same meaning.

[0178] In this specification, the terms “Subscriber” and “User” may be used interchangeably.

[0179] In this specification, the terms network, Core Network (CN), 5G CN, 3GPP network, and 3GPP system may be used interchangeably.

[0180] In this specification, terms such as zone, area, region, sector, area, region, and locality may be used with the same meaning.

[0181] In this specification, AIoTF (AIoT Function) is a network function or functionality that supports Ambient IoT.

[0182] For reference, AIoT may be co-located with or supported by a conventional NF (e.g., AMF, NEF, UPF, etc.), or may exist in a standalone form. Furthermore, the name of AIoTF disclosed in this specification is merely an example, and AIoTF may be called by various names (e.g., AIoT NF, AIoT GW, etc.).

[0183] In this specification, A-RAN can be interpreted as a base station, RAN, Base Station, RAN node, etc. having reader function.

[0184] In this specification, the NG or NG-like (NG') interface may be an N2 or N2 like (N2') interface, an N3 or N3 like (N3') interface, an N2 / N3 or N2 / N3 like (N2' / N3') interface. Alternatively, a new interface name may be defined for the interface between the A-RAN and the Core Network.

[0185] For some or all of the service operations between Core NFs described in the various examples of the disclosure of this specification, new service operations may be defined and used. In addition, for some or all of the NG messages between AMF and NG-RAN described in the disclosure of this specification, new NG messages may be defined and used. In addition, for some or all of the RRC messages between NG-RAN and UE described in the disclosure of this specification, new RRC messages may be defined and used.

[0186] Any of the steps described in the various examples of the disclosure herein may be performed concurrently / in parallel or in an alternate order.

[0187] The names of indication or parameter information suggested in various examples of the disclosure of this specification are merely examples, and for the procedures / purposes / methods suggested in the disclosure of this specification, the names below may be interpreted as being replaced with other names.

[0188] The first and second examples of the disclosure of the present specification described below may be combined with each other or applied independently.

[0189] 1. First example of disclosure of this specification

[0190] In the first example of the disclosure of this specification, an example of a procedure for supporting an AIoT device based on topology 1 is described.

[0191] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0192] Figures 7a and 7b illustrate an example of a procedure according to the first example of the disclosure of the present specification.

[0193] The examples in FIG. 7a and FIG. 7b are examples of the overall procedure for supporting AIoT devices in topology 1.

[0194] For reference, in the examples of FIGS. 7a and 7b, the messages transmitted in steps 1a, 1b, 6, and 9 may be NG messages based on the NG interface or NG' (NG-like) messages based on the NG' (NG-like) interface.

[0195] In the examples of FIGS. 7A and 7B, the A-RAN may include one or more Readers. For example, the A-RAN may be connected to one or more Readers.

[0196] Step 1: In Step 1a, an A-RAN with one or more readers can send a SETUP REQUEST message to AIoTF. The SETUP REQUEST message may include, for example, a Supported Area Index.

[0197] For example, A-RAN can initiate the setup process for an NG interface or NG-like (i.e., NG') interface with AIoTF by sending a SETUP REQUEST message.

[0198] A-RAN may include one or more of the following information for each Reader in the SETUP REQUEST message:

[0199] - Reader ID

[0200] - Location information for the area covered by the Reader:

[0201] i)Geographical location information;

[0202] ii) TAI, cell ID information; and / or

[0203] iii) External area information (e.g., warehouse #1, warehouse #2, address information, etc.).

[0204] - When the area handled by the Reader is divided into multiple areas or zones, the coordinate information of the area or zone and the corresponding area index or zone index. If the A-RAN provides the AIoTF with the geographical location information handled by the Reader, the AIoTF can configure this information and provide it to the A-RAN. For example, based on the geographical location information handled by the Reader and the corresponding area index, the A-RAN can transmit the ID and area index of the reader to which the A-IoT device sent a response to the AIoTF. Then, the AIoTF can convert the area index received from the A-RAN into geographical location information and transmit it to the AF, or perform the opposite operation. For example, the opposite operation can include an operation in which, when the AF transmits geographical location information to the AIoTF, the AIoTF generates area index information based on the geographical location information, and the A-IoT transmits the area index information to the A-RAN.

[0205] The above geographical location information and coordinate information may be, for example, various types of information defined in TS 23.032 V18.1.0 "Universal Geographical Area Description (GAD)". This may be applied throughout this specification.

[0206] Area index and / or zone index information may indicate area indices and / or zone indices related to areas shared by more than one Reader, rather than areas solely managed by a single Reader. For example, as illustrated in the example of FIG. 8, multiple areas may be assigned to multiple Readers.

[0207] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0208] FIG. 8 illustrates an example of a leader of a base station according to one embodiment of the disclosure of the present specification.

[0209] Referring to the example in Figure 8, Leader A can be in charge of areas 1 and 2. Leader B can be in charge of areas 3 and 4. Leader C can be in charge of areas 1 and 3. Leader D can be in charge of areas 2 and 4.

[0210] For example, Area 1 may be covered by both Leader A and Leader C.

[0211] Referring again to FIGS. 7a and 7b, a procedure according to the first example of the disclosure of the present specification will be described.

[0212] AIoTF can store information related to the Reader received from the A-RAN. When AIoTF receives a request for AIoT Service operation from the AF via the NEF, AIoTF can utilize the information related to the Reader received from the A-RAN.

[0213] In step 1b, AIoTF completes the NG (or NG') Setup process by sending a setup response message (e.g., NG SETUP RESPONSE message or NG' SETUP RESPONSE message) to A-RAN.

[0214] For reference, A-RAN may be configured with a CU-DU split architecture. In this case, the Reader may belong to the DU. In this case, the DU may transmit information about the Reader managed by the DU to the CU during the process of setting up the F1 interface or F1-like (i.e., F1') interface. The CU may collect the Reader information from the DU and transmit it back to the AIoTF as in Step 1. Alternatively, if the Reader belongs to the CU, the CU may pre-transmit the information necessary for signaling transmission for energy harvesting to the DU so that the AIoT Device can perform energy harvesting through the F1 (or F1') setup process or other F1 (or F1') signaling. In addition, to support the case where the AIoT Device sends a response to the Inventory Request message, the CU may pre-transmit to the DU the configuration information necessary for the DU to receive the response and / or the information necessary for the DU to transmit the response to the CU.

[0215] For reference, in FIGS. 7a and 7b, it is assumed that the A-RAN is directly connected to the AIoTF, or that the AMF and the AIoTF are co-located, or that the AMF has the functions of the AIoTF (e.g., the operation of the AIoTF in FIG. 7 may be the operation of the AMF), but this is only an example. The example in FIG. 7 can also be applied to a situation where the A-RAN is connected to the AIoTF through the AMF. In this case, the AMF may separately transmit the information related to the Reader received in Step 1 (e.g., Supported area index) to the AIoTF.

[0216] Step 2: AMF can send a request message related to AIoT service (e.g., Nnef_AIoT_Service Request message) to NEF.

[0217] For example, AF can request AIoT service for specific AIoT Device(s) and / or AIoT Device(s) located in a specific region by sending Nnef_AIoT_Service Request message to NEF. Nnef_AIoT_Service Request message can include area information, device information, and information related to service operation.

[0218] For example, the Nnef_AIoT_Service Request message may contain some or all of the following:

[0219] - AIoT service operation to be requested (e.g., Inventory, Command)

[0220] - Assistance information for service operations. For example, assistance information may include one or more of the following:

[0221] i) Information on whether to perform a new Service operation;

[0222] ii) Allowed age information (e.g., information about how long ago information obtained can be sent instead of performing a new service); and / or

[0223] iii) An indication requesting already stored information instead of a new service operation.

[0224] - List of Reader IDs that will perform AIoT service operations

[0225] - List of AIoT Device IDs that are the target of AIoT service

[0226] - Information about the area where you want to provide AIoT service (e.g. area info):

[0227] i) Geographical location information;

[0228] ii) TAI, cell id; and / or

[0229] iii) External area information (e.g., warehouse #1, warehouse #2, address information, etc.).

[0230] Additionally, for the parameters included in the Nnef_AIoT_Service Request message, please refer to TR 23.700-13 V0.2.0.

[0231] Step 3: NEF can perform authorization for the AIoT Service Request sent by AF in Step 2.

[0232] Step 4: NEF can send a service request message (e.g., Naiot_Service Request) to AIoTF. The service request message can include one or more of area information, device information, and / or information related to service operation.

[0233] For example, the NEF may select an AIoTF to perform a request for an AIoT service operation received from the AF based on (pre-)configuration information and / or assistance from other NFs (e.g., NRF, UDM). The NEF may also select an AIoTF based on domain information about the AIoT service provided by the AF and domain information for which the AIoTF is responsible. The NEF may know the domain information for which the AIoTF is responsible based on what the AIoTF has registered with the NRF. Alternatively, the operator may have preset the domain information for which the AIoTF is responsible to the NEF.

[0234] NEF can send a Naiotf_Service Request message to the selected AIoTF. The Naiotf_Service Request message can include information received from the AF in Step 2. At this time, external information (e.g., Reader ID, AIoT Device ID) can be mapped / converted to internal information and used.

[0235] The AF may have allowed information already stored to be transmitted (e.g., if age information was provided via the assist information for the service operation in step 2). In this case, the NEF may retrieve information related to the AIoT Device(s) stored by the selected AIoTF from the UDM before transmitting the Naiotf_Service Request message to the AIoTF. For example, during the past process of performing the operation according to the example of FIG. 7 or the operation according to the example of FIG. 8 for the AIoT Device(s), information related to the AIoT device(s) may be stored in the UDM through Step 13 of FIGS. 7a and 7b or Step 20 of FIGS. 9a to 9c. Based on the information acquired from the UDM, the NEF may decide whether to transmit the Naiotf_Service Request message to the AIoTF or to transmit the information acquired from the UDM to the AF. If the NEF decides to respond based on the information stored in the UDM, steps 4 to 11 and step 13 may be skipped. Therefore, NEF may immediately transmit a Response message according to Step 12 for the Request message received in Step 2. In this case, the Step 12 message may be in the form of a Request message, a Report message, or a Notify message.

[0236] Step 5: AIoTF can discover (or select) A-RAN and translate (or translate) area information into area index.

[0237] For example, AIoTF may select the A-RAN(s) to perform the AIoT service operation based on the information received in Step 4 and / or subscription data for the AIoT Device stored in the UDM and / or mapping information between the AIoT Device and the Reader (previously stored in AIoTF through a previous AIoT service operation).

[0238] For example, if AIoTF receives Reader ID(s) and / or AIoT Device ID(s) in Step 4, AIoTF may select the A-RAN(s) to which the Reader ID(s) and / or AIoT Device(s) belong (or are associated).

[0239] For example, if AIoTF receives Area info in Step 4, AIoTF may select the A-RAN(s) whose Reader's serving area belongs to the Area info.

[0240] For example, if the AIoTF does not have information to select a specific A-RAN(s), it may decide to perform the AIoT service operation requested in Step 4 on all A-RANs connected to the AIoTF. In this case, the AIoTF may perform the AIoT service operation sequentially on all A-RANs or simultaneously on all A-RANs.

[0241] AIoTF can retrieve information from the UDM. For example, the information retrieved from the UDM may include mapping information between AIoT devices and readers, and / or subscriber information for AIoT devices.

[0242] For example, when AIoTF retrieves information from UDM, it can also retrieve information about AIoT Devices to determine whether to perform a new service operation or respond with NEF based on the information stored in UDM. If AIoTF decides to respond based on the information stored in UDM, AIoTF can skip steps 5 to 10 and step 13. In this case, AIoTF can directly send a Response message in step 11 for the Request message received in step 4. In this case, the message in step 11 can be in the form of a Request message, a Report message, or a Notify message.

[0243] Additionally, AIoTF can convert the Area info information received in Step 4 into the form of an Area index based on the Area index value received from A-RAN in Step 1.

[0244] Step 6: AIoTF can send a service request message (e.g., AIoT Service Request) to A-RAN. The service request message may include, for example, a target area index, device information, and information related to the service operation.

[0245] AIoTF can request AIoT service operation for a specific region (or area) and / or AIoT Device(s) by transmitting an NG (or NG') AIoT SERVICE REQUEST message to the A-RAN(s) selected in Step 5. At this time, AIoTF can also transmit the information received in Step 4 and / or the Area index list obtained in Step 5. At this time, AIoTF can transmit information related to the conditions under which the A-RAN will transmit AIoT Device information to the A-RAN. For example, the information related to the conditions under which the AIoT Device information will be transmitted can include one or more of the following information: immediate, periodic, timer-based (in which case timer information can also be included in the service request message), whether aggregation of AIoT device information is needed (e.g., whether aggregation is needed or not), and a condition for transmitting information when a response is received for all AIoT Devices that are the target of the AIoT service. Information related to the conditions for transmitting AIoT Device information may be information provided by AF in step 2 or information configured based on information provided by AF.

[0246] Step 7: A-RAN can perform AIoT service operations for AIoT devices.

[0247] For example, based on the information received in Step 6, the A-RAN can perform service operations for a specific area index and / or a specific AIoT Device. At this time, the A-RAN can perform service operations for AIoT Devices through one or more Readers, if necessary. For example, if the Area Index is an area jointly managed by one or more Readers, the A-RAN can use one or more Readers to perform service operations.

[0248] Step 8: The AIoT Device can send a response message containing the device ID to the A-RAN.

[0249] For example, an AIoT Device can respond to a Reader within the A-RAN with a Response message including its Device ID. Depending on the AIoT service operation requested in Step 7, the AIoT Device may include additional information in the Response message. For example, the following description may apply to additional information transmitted by the AIoT Device. For example, if the AF requests a "Read" operation of the AIoT Device while transmitting a command message, the AIoT Device may include additional information stored in the Response message (e.g., results measured by the AIoT Device as a sensor about the surrounding environment, etc.).

[0250] For reference, in the disclosure of this specification, communication between an AIoT device and a reader can be performed as in the following example. The reader can transmit an A-IoT paging message to the AIoT device. The A-IoT paging message can be transmitted based on a service request received by the reader. Optionally, an A-IoT random access procedure can be performed between the AIoT device and the reader. The AIoT device can transmit D2R (Device to Reader) data to the reader. For example, the AIoT device can transmit its ID to the reader. For example, the reader can transmit R2D (Reader to Device) data (e.g., a command related to an AIoT service operation) to the AIoT device. For example, the AIoT device can transmit D2R data (e.g., a response related to an AIoT service operation) to the reader.

[0251] For reference, in Step 7, the A-RAN sequentially transmits backscattering signals to the zones or areas located within each Reader, and in Step 8, it may also receive responses from AIoT Devices through the Reader. In this case, the A-RAN can determine that an AIoT Device is located in a zone or area within the Reader.

[0252] Step 9: The A-RAN may send a service response message (e.g., an AIoT service response) to the AIoTF. The service response message may include an area index, device ID, and information related to the service operation.

[0253] For example, the A-RAN can forward the response of the AIoT Device received in Step 8 to the AIoTF by sending an NG (or NG') AIoT SERVICE RESPONSE or NOTIFY message to the AIoTF. For example, the A-RAN can perform authentication on the AIoT Device(s) that sent the response, and then include only the responses of the AIoT Devices that passed the authentication in the response message transmitted to the AIoTF.

[0254] For reference, the A-RAN may also include one or more of the following information related to the Reader that received the AIoT Device's response within the NG (or NG') AIoT SERVICE RESPONSE message:

[0255] - Reader ID; and / or

[0256] - Zone index or Area index where the AIoT Device sent a response within the area covered by the Reader.

[0257] For example, the A-RAN may collect all responses from AIoT Device(s) received through the Reader(s) over a certain period of time, then forward them to the AIoTF and ignore any responses from AIoT Device(s) received thereafter. Alternatively, the A-RAN may periodically report the collected responses from AIoT Device(s) to the AIoTF at specific periods within a certain period of time. Alternatively, the A-RAN may immediately forward the responses from AIoT Device(s) received to the AIoTF via an NG (or NG') AIoT SERVICE RESPONSE or NOTIFY message. The time at which the A-RAN collects responses from AIoT Device(s) and / or the pattern (or condition) for reporting them to the AIoTF may be pre-configured in the A-RAN, or the A-RAN may be pre-configured by the AIoTF in Step 1. Alternatively, through Step 6, the A-RAN may receive configuration from the AF or AIoTF regarding the time at which the A-RAN collects responses from the AIoT Device(s) and / or the pattern (or condition) at which it reports these to the AIoTF.

[0258] For reference, the A-RAN may be configured with a CU-DU split architecture, and the Reader may belong to the DU. In this case, the DU can collect responses from AIoT Device(s) for a certain period of time and forward them to the CU. The CU can collect responses from AIoT Device(s) from each DU for a certain period of time and then forward them to the AIoTF. In this case, the time at which the DU collects responses from AIoT Device(s) and / or the pattern in which it reports them to the CU may be pre-configured in the DU, or may be configured in advance by the AIoTF and / or the CU in Step 1. Alternatively, the time at which the DU collects responses from AIoT Device(s) and / or the pattern in which it reports them to the CU may be configured from the AF or AIoTF through the CU in Step 6.

[0259] Alternatively, if the Reader belongs to a CU, the CU may collect responses from AIoT Device(s) received through the DU over a period of time and forward them to the AIoTF, as in Step 9.

[0260] Step 10: AIoTF can transform the region index.

[0261] AIoTF may also transform information (e.g., area index or zone index) related to AIoT Device(s) contained in a response received from A-RAN.

[0262] For example, AIoTF may convert the location information associated with each AIoT Device(s) included in a response received from A-RAN from the form of an Area index or Zone index into some or all of the following forms. These conversions may also be performed by the NEF:

[0263] - Location information about the AIoT Device(s) that sent the response (i.e. Location info):

[0264] i) Geographical location information;

[0265] ii) TAI and / or Cell ID; and / or

[0266] iii) External area information (e.g., shelf #A in warehouse #1, shelf #C in warehouse #2, address information, etc.).

[0267] Step 11: AIoTF can send a service response message (e.g., Naiotf_Service response) to the UDM. For example, the service response message can include location information, device ID, and information related to the service operation.

[0268] For example, AIoTF can send a Naiotf_Service Response message to NEF, and transmit the current location information of the AIoT Device(s) along with the response from the AIoT Device(s). AIoTF can also perform authentication on the AIoT Device(s) included in the response from A-RAN, and then transmit only the current location information of the AIoT Device(s) that passed the authentication to NEF.

[0269] Step 12: NEF may send a service response message (e.g., Nnef_Service response) to AF. For example, the service response message may include location information, device ID, and information related to the service operation.

[0270] For example, NEF can send the Nnef_AIoT_Service Response message to AF, and convey the current location information of the AIoT Device(s) along with the response of the AIoT Device(s).

[0271] Step 13: AIoTF can update device subscription data (e.g., location information, device ID). For example, AIoTF can store information such as the current location information of AIoT Device(s), the Reader ID to which the AIoT Device(s) responded, the A-RAN ID, the time the AIoT Device responded, and the AIoTF ID in the UDM.

[0272] In the example of FIG. 7, if the A-RAN or the DU of the A-RAN does not receive a response from any AIoT Device within a given time, it may provide AIoTF with information related thereto (e.g., no response received, etc.).

[0273] In the example of FIG. 7, when the A-RAN or the DU of the A-RAN receives a response from an AIoT Device as a result of an AIoT service operation, if the AIoT Device is valid (e.g., belongs to the list of AIoT Devices that are targets of the AIoT service), it can include it in the response (e.g., the response message of step 9).

[0274] In FIG. 7a and FIG. 7b, messages are exchanged between AF and AIoTF through NEF, but AF and AIoTF can also exchange messages directly without going through NEF.

[0275] 2. Second example of disclosure of this specification

[0276] In the second example of the disclosure of this specification, an example of a procedure for supporting an AIoT device based on topology 2 is described.

[0277] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0278] Figures 9a to 9c illustrate an example of a procedure according to the second example of the disclosure of the present specification.

[0279] The examples in FIGS. 9a to 9c are examples of the overall procedure for supporting AIoT devices in topology 2.

[0280] In the examples of FIGS. 9A to 9C, the UE may include one or more readers. For example, the UE may be connected to one or more readers.

[0281] Step 1: A UE with one or more readers can initiate the network registration process by sending a Registration Request message to the AMF via the NG-RAN. For example, the Registration Request message may include a supported area index (e.g., a supported area index).

[0282] The UE may include some or all of the following information about each Reader in the Registration Request message. Alternatively, after successfully completing the network registration procedure, the UE may transmit some or all of the following information to AIoTF via AMF in a separate message.

[0283] - Reader ID

[0284] - Location information for the area covered by the Reader:

[0285] i)Geographical location information;

[0286] ii) TAI, cell ID information; and / or

[0287] iii) External area information (e.g., warehouse #1, warehouse #2, address information, etc.)

[0288] - When the area handled by the Reader is divided into multiple areas or zones, the coordinate information of the area or zone and the corresponding area index or zone index. If the UE provides the AIoTF with the geographical location information handled by the Reader, the AIoTF can compose this information and provide it to the UE.

[0289] Area index and / or zone index information may indicate area indices and / or zone indices related to areas shared by more than one Reader, rather than areas solely managed by a single Reader. For example, as illustrated in the example of FIG. 8, multiple areas may be assigned to multiple Readers.

[0290] NOTE: The network can notify the UE via SIB whether it supports AIoT service so that the UE can select a network that supports AIoT service. In addition, the UE can explicitly include a separate indication in the RRC message and / or NAS message when sending a Registration Request message to the network, indicating that it can act as a Reader for AIoT service. Alternatively, the UE can implicitly notify the network that the UE can act as a Reader for AIoT service by including the Reader information from step 1 in the Registration Request message. In addition, the AMF's capability information for AIoT service can be transmitted to the NG-RAN in advance during the NG Setup process so that the NG-RAN can select an AMF that supports AIoT service during the UE's registration process.

[0291] Step 2: AMF can send a registration request message (e.g., Namf_AIoT_Registration request) to AIoTF. The registration request message can include a support area index.

[0292] For example, the AMF may decide to grant a Registration request for the UE. In this case, the AMF may determine a serving AIoTF for the UE based on information pre-configured within the AMF, subscriber data of the UE (e.g., the UE's subscription data), and / or information transmitted by the UE (e.g., information transmitted by the UE in Step 1), and / or with the assistance of the NRF. The AMF may request registration for the UE by sending a Namf_AIoT_Registration Request message to the determined serving AIoTF. The Namf_AIoT_Registration Request message may include information related to the Reader received by the AMF in Step 1. The AIoTF may store the information about the Reader received from the AMF, and may utilize the stored information when a request for an AIoT Service operation is received from the AF via the NEF.

[0293] For reference, in FIGS. 9a to 9c, it is assumed that AMF and AIoTF are not co-located, but the descriptions in FIGS. 9a to 9c are also applicable when AMF and AIoTF are co-located. In this case, Steps 2 to 3 and Step 9 and Step 16 may be omitted.

[0294] For reference, in FIGS. 9A to 9C, it is assumed that all information related to the Reader is pre-configured within the UE, but this is merely an example. For example, AIoTF may configure or update some information about the Reader existing within the UE. For example, through Steps 1 and 2, the UE may transmit each Reader ID and location information (e.g., Geographical location information, TAI, cell ID information, External area information, etc.) for the area covered by the Reader to the AMF, and the AMF may transmit the information received from the UE in Step 2 to the AIoTF. Then, the AIoTF may divide the area covered by each Reader into multiple areas or zones, and then allocate / set the coordinate information of each area or zone and the corresponding area index or zone index and transmit them to the UE through Steps 3 and 4.

[0295] Step 3: AIoTF can send a registration response message to AMF.

[0296] For example, AIoT can complete the registration process for a UE by sending a Namf_AIoT_Registration Response message to AMF.

[0297] Step 4: AMF can send a registration acceptance message to the UE.

[0298] For example, AMF can notify the UE that it has successfully registered with the network by sending a Registration Accept message to the UE.

[0299] Step 5: AF can send a service request message (e.g., Nnef_AIoT_Service Request message) to NEF. The service request message can include, for example, area information, device information, and information related to the service operation.

[0300] An AF can request AIoT services for specific AIoT Device(s) and / or AIoT Device(s) located in a specific region by sending a Nnef_AIoT_Service Request message to the NEF. The Nnef_AIoT_Service Request message may contain some or all of the following:

[0301] - AIoT service operation to be requested (e.g., Inventory, Command)

[0302] - Assistance information for service operations. For example, assistance information may include one or more of the following:

[0303] i) Information on whether to perform a new Service operation;

[0304] ii) Allowed age information (e.g., information about how long ago information obtained can be sent instead of performing a new service); and / or

[0305] iii) An indication requesting already stored information instead of a new service operation.

[0306] - List of Reader IDs that will perform AIoT service operations

[0307] - List of AIoT Device IDs that are the target of AIoT service

[0308] - Information about the area where you want to provide AIoT service (e.g. area info):

[0309] i) Geographical location information;

[0310] ii) External area information (e.g., warehouse #1, warehouse #2, address information, etc.).

[0311] Additionally, for the parameters included in the Nnef_AIoT_Service Request message, please refer to TR 23.700-13 V0.2.0.

[0312] Step 6: NEF can perform authorization for the AIoT Service Request sent by AF in Step 5.

[0313] Step 7: NEF can send a service request message (e.g., Naiot_Service Request) to AIoTF. The service request message can include one or more of area information, device information, and / or information related to service operation.

[0314] For example, the NEF may select an AIoTF to execute a request for an AIoT service operation received from the AF based on (pre-)configuration information and / or assistance from other NFs (e.g., NRF, UDM). The NEF may also select an AIoTF based on domain information about the AIoT service provided by the AF and domain information for which the AIoTF is responsible. The NEF may know the domain information for which the AIoTF is responsible based on what the AIoTF has registered with the NRF. Alternatively, the operator may have preset the domain information for which the AIoTF is responsible to the NEF.

[0315] NEF can send a Naiotf_Service Request message to the selected AIoTF. The Naiotf_Service Request message can include information received from the AF in Step 5. At this time, external information (e.g., Reader ID, AIoT Device ID) can be mapped / converted to internal information and used.

[0316] The AF may have allowed information already stored to be transmitted (e.g., if age information was provided via the assist information for the service operation in step 5). In this case, the NEF may retrieve information related to the AIoT Device(s) stored by the selected AIoTF from the UDM before transmitting the Naiotf_Service Request message to the AIoTF. For example, in the past, during the operation according to the examples of FIGS. 7A and 7B or the operation according to the example of FIG. 8 for the AIoT Device(s), information related to the AIoT device(s) may be stored in the UDM through Step 13 of FIGS. 7A and 7B or Step 20 of FIGS. 9A to 9C. Based on the information acquired from the UDM, the NEF may decide whether to transmit the Naiotf_Service Request message to the AIoT or to transmit the information acquired from the UDM to the AF. If the NEF decides to respond based on the information stored in the UDM, steps 7 to 18 and step 20 may be skipped. Therefore, NEF may immediately transmit a Response message according to Step 19 for the Request message received in Step 2. In this case, the Step 19 message may be in the form of a Request message, a Report message, or a Notify message.

[0317] Step 8: AIoTF can discover (or select) A-RAN and translate (or translate) area information into area index.

[0318] For example, AIoTF can select UE(s) to perform AIoT service operation based on the information received in Step 7 and / or subscription data for AIoT Device stored in UDM and / or mapping information between AIoT Device and Reader (previously stored in AIoT TF through previous AIoT service operation). Based on the selected UE, AIoTF can find UE's serving NG-RAN and serving AMF.

[0319] For example, if AIoTF receives Reader ID(s) and / or AIoT Device ID(s) in Step 7, AIoTF may select the UE to which the Reader ID(s) and / or AIoT Device(s) belong (or are associated).

[0320] For example, if AIoTF receives Area info in Step 7, AIoTF may select a UE whose Reader's serving area belongs to the Area info.

[0321] For example, if there is no information available for AIoTF to select a specific UE, AIoTF may decide to perform the AIoT service operation requested in Step 7 for all UE(s) connected to AIoTF. In this case, AIoTF may perform the AIoT service operation sequentially for all UEs or perform the AIoT service operation simultaneously for all UEs.

[0322] AIoTF can retrieve information from the UDM. For example, the information retrieved from the UDM may include mapping information between AIoT devices and readers, and / or subscriber information for AIoT devices.

[0323] For example, when AIoTF retrieves information from UDM, it can also retrieve information about AIoT Devices to determine whether to perform a new service operation or respond with NEF based on the information stored in UDM. If AIoTF decides to respond based on the information stored in UDM, AIoTF can skip steps 8 to 17 and step 20. In this case, AIoTF can also transmit directly in the Response message (e.g., the message in step 18) to the Request message received in step 7. In this case, the message in step 18 can be in the form of a Request message, a Report message, or a Notify message.

[0324] Additionally, AIoTF can convert the Area info information received in Step 7 into the form of an Area index based on the Area index value received from the UE in Step 1.

[0325] Step 9: AIoTF may send a service request message (e.g., Namf_AIoT_Service Request message) to AMF. The service request message may include one or more of the following information: target area index, device information, and / or information related to service operation.

[0326] At this time, AIoTF can transmit information related to the conditions under which A-RAN will transmit AIoT Device information to AMF. For example, information related to the conditions under which AIoT Device information will be transmitted may include one or more of the following: immediate, periodic, timer-based (in which case timer information may also be included in the service request message), whether aggregation of AIoT device information is needed (e.g., whether aggregation is needed or not), and conditions under which information is transmitted when a response is received from all AIoT Devices that are targets of the AIoT service. Information related to the conditions under which AIoT Device information will be transmitted may be information provided by AF in step 5 or information configured based on information provided by AF.

[0327] Step 10: The AMF may send a service request message (e.g., an AIoT SERVICE REQUEST message) to the NG-RAN. The service request message may include one or more of the following information: a target area index, device information, and / or information related to service operation.

[0328] The AMF can request AIoT service operation for a specific region and / or AIoT Device(s) by transmitting an NG (or NG') AIoT SERVICE REQUEST message to the serving NG-RAN(s) of the UE(s) selected in Step 8. At this time, the AMF can also forward the information received in Step 9 to the NG-RAN. At this time, the AMF can also transmit the information received in Step 9, for example, information related to conditions for transmitting AIoT Device information, to the serving NG-RAN. For example, the information related to conditions for transmitting AIoT Device information can include one or more of the following information: immediate, periodic, timer-based (in which case timer information can also be included in the service request message), whether aggregation of AIoT device information is needed (e.g., whether aggregation is needed or not), and a condition for transmitting information when a response is received for all AIoT Devices that are targets of the AIoT service.

[0329] For reference, the interface between NG-RAN and AMF may be reused as is, or the interface may be expanded with functions to support AIoT service operations. Alternatively, a new NG interface designed solely to support AIoT service operations may be used.

[0330] Step 11: The NG-RAN may transmit an AIoT service request message to the UE. For example, the service request message may include one or more of the following information: a target area index, device information, and / or information related to service operation.

[0331] The NG-RAN can request AIoT service operation for a specific region and / or AIoT Device(s) by transmitting an AIoT Service Request message to the UE(s) selected in Step 8. At this time, the NG-RAN can also transmit the information received in Step 10 to the UE. At this time, the NG-RAN can also transmit the information received in Step 9, for example, information related to conditions for transmitting AIoT Device information, to the UE. For example, the information related to conditions for transmitting AIoT Device information may include one or more of the following information: immediate, periodic, timer-based (in which case timer information may also be included in the service request message), whether aggregation of AIoT device information is needed (e.g., whether aggregation is needed or not), and conditions for transmitting information when a response is received for all AIoT Devices that are targets of the AIoT service.

[0332] For reference, in FIGS. 9a to 9c, the NG-RAN requests AIoT service operation to the UE(s) through an RRC message, but the NG-RAN may also request AIoT service operation through a NAS message.

[0333] Step 12: The UE can perform AIoT service operations for the AIoT device.

[0334] For example, based on the information received in Step 11, the UE can perform a service operation for a specific area index and / or a specific AIoT Device. At this time, the UE can perform the service operation for the AIoT Device through one or more Readers, if necessary. For example, if the Area index is an area jointly managed by one or more Readers, the UE can perform the service operation using one or more Readers.

[0335] Step 13: The AIoT Device can send a response message containing the device ID to the UE.

[0336] For example, an AIoT Device can respond to a Reader within the UE with a Response message that includes its Device ID. Depending on the AIoT service operation requested in Step 12, the AIoT Device may also include additional information in the Response message.

[0337] For reference, in Step 12, the UE sequentially transmits a backscattering signal to the zones or areas located within each Reader, and when a response from the AIoT Device is received through the Reader in Step 13, it can be known that the AIoT Device is located in the zone or area within the Reader.

[0338] Step 14: The UE may send a service response message (e.g., an AIoT service response) to the AIoTF. The service response message may include an area index, a device ID, and information related to the service operation.

[0339] For example, the UE can forward the response of the AIoT Device received in Step 13 to the AIoTF by sending an AIoT SERVICE RESPONSE message to the NG-RAN. For example, the UE can perform authentication on the AIoT Device(s) that sent the response, and then include only the responses of the AIoT Devices that passed the authentication in the response message transmitted to the NG-RAN.

[0340] The UE may include one or more of the following information related to the Reader that received the response from the AIoT Device in the AIoT SERVICE RESPONSE message:

[0341] - Reader ID;

[0342] - Zone index or Area index to which the AIoT Device sent a response within the area covered by the Reader; and / or

[0343] - Location information of the UE (e.g., coordinate information, etc.).

[0344] For example, the UE may receive responses from AIoT Device(s) through Reader(s) for a certain period of time, then collate them all and forward them to AIoTF via NG-RAN, and ignore any responses from AIoT Device(s) received thereafter. Alternatively, the UE may periodically report the responses from AIoT Device(s) collected up to that point to AIoTF via NG-RAN at specific periods within a certain period of time. Alternatively, the UE may immediately forward an AIoT SERVICE RESPONSE message to AIoTF via NG-RAN whenever it receives a response from AIoT Device(s). The time at which the UE collates responses from AIoT Device(s) and / or the pattern (or condition) for reporting them to AIoTF via NG-RAN may be configured in advance in the UE, or the UE may be configured in advance from AIoTF in Steps 3 and 4. Alternatively, through Steps 9 to 11, the UE may receive configuration from AF or AIoTF, such as the time at which the UE collects responses from AIoT Device(s) and / or the pattern (or condition) for reporting them to AIoTF.

[0345] Step 15: The NG-RAN may send an AIoT service response message to the AMF. The AIoT service response message may include one or more of the following information: an area index, a device ID, and information related to the service operation.

[0346] For example, the NG-RAN can transmit the response of the AIoT Device received in Step 14 to the AMF by transmitting an NG (or NG') AIoT SERVICE RESPONSE or NOTIFY message. As in Step 14, the NG-RAN can also collect responses of AIoT Device(s) from each UE at a certain time and / or according to a certain pattern and transmit them to the AMF. Information such as the time and / or pattern for collecting responses of AIoT Device(s) may be pre-configured in the NG-RAN, or may be pre-configured from the AIoTF in Steps 3 and 4. Alternatively, the NG-RAN can receive information such as the time and / or pattern for collecting responses of AIoT Device(s) from the AF or AIoTF through Steps 9 and 10. The NG-RAN can perform authentication on the AIoT Device(s) included in the response from the UE, and then include only the responses of the AIoT Devices that passed the authentication in the response transmitted to the AMF.

[0347] Step 16: AMF may send a service response message (e.g., Namf_AIoT_Service Response message) to AIoTF. The service response message may include one or more of the following information: a region index, a device ID, and information related to the service operation.

[0348] For example, the AMF can transmit the response of the AIoT Device received in Step 15 to the AIoTF by sending the Namf_AIoT_Service Response message. As in Step 14, the AMF can also collect responses of the AIoT Device(s) from each UE at a certain time and / or according to a certain pattern and transmit them to the AIoTF. Information such as the time and / or pattern for collecting responses of the AIoT Device(s) may be pre-configured in the AMF, or may be pre-configured from the AIoTF in Step 3. Alternatively, the AMF may receive information such as the time and / or pattern for collecting responses of the AIoT Device(s) from the AF or the AIoTF in Step 9. The AMF may perform authentication on the AIoT Device(s) included in the response from the NG-RAN, and then include only the responses of the AIoT Devices that passed the authentication in the response to / AIoTF.

[0349] Step 17: AIoTF can transform the region index.

[0350] AIoTF may also transform information related to AIoT Device(s) contained in the response received from AMF (e.g., area index or zone index).

[0351] For example, AIoTF may convert the location information associated with each AIoT Device(s) included in a response received from AMF from the form of an Area index or Zone index into some or all of the following forms. These conversions may also be performed by NEF:

[0352] - Location information about the AIoT Device(s) that sent the response (i.e. Location info):

[0353] i) Geographical location information;

[0354] ii) TAI and / or Cell ID; and / or

[0355] iii) External area information (e.g., shelf #A in warehouse #1, shelf #C in warehouse #2, address information, etc.).

[0356] Step 18: AIoTF can send a service response message (e.g., Naiotf_Service response) to the UDM. For example, the service response message can include one or more of the following information: location information, device ID, and information related to the service operation.

[0357] For example, AIoTF can send a Naiotf_Service Response message to NEF, and transmit the current location information of the AIoT Device(s) along with the response from the AIoT Device(s). AIoTF can also perform authentication on the AIoT Device(s) included in the response from AMF, and then transmit only the current location information of the AIoT Device(s) that passed the authentication to NEF.

[0358] Step 19: NEF may send a service response message (e.g., Nnef_Service response) to AF. For example, the service response message may include location information, device ID, and information related to the service operation.

[0359] For example, NEF can send the Nnef_AIoT_Service Response message to AF, and convey the current location information of the AIoT Device(s) along with the response of the AIoT Device(s).

[0360] Step 20: AIoTF can update device subscription data (e.g., location information, device ID). For example, AIoTF can store information such as the current location information of AIoT Device(s), the Reader ID to which the AIoT Device(s) responded, the A-RAN ID, the time the AIoT Device responded, and the AIoTF ID in the UDM.

[0361] In the examples of FIGS. 9A to 9C, if the UE does not receive a response from any AIoT Device within a given time, the UE may provide AIoTF with information related thereto (e.g., failure to receive a response, etc.) through the serving NG-RAN and the serving AMF.

[0362] In the examples of FIGS. 9A to 9C, when the UE receives a response from an AIoT Device as a result of an AIoT service operation, if the AIoT Device is valid (e.g., belongs to the list of AIoT Devices that are targets of the AIoT service), the UE may include the response from the AIoT Device in the response transmitted to the NG-RAN.

[0363] In Figures 9a to 9c, messages are exchanged between AF and AIoTF via NEF, but this is merely an example. For example, AF and AIoTF can also exchange messages directly without going through NEF.

[0364] Hereinafter, with reference to the example of FIG. 10, an example of a procedure according to various examples of the disclosure of the present specification will be described. The description with reference to FIG. 10 below may be based on the description according to the disclosure of the present specification, including the first example of the disclosure of the present specification and / or the second example of the disclosure of the present specification.

[0365] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0366] FIG. 10 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

[0367] For reference, the procedure illustrated in FIG. 10 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 10.

[0368] For example, with respect to the example of FIG. 10, the operations described in the examples of FIGS. 1 to 9c may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 10, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0369] For reference, the device of the example of FIG. 10 may be a base station according to the first example of the disclosure of this specification, or may be a UE according to the second example of the disclosure of this specification.

[0370] In the example of Fig. 10, the network entity can be AIoTF or AMF.

[0371] Hereinafter, the example of FIG. 10 will be described focusing on the example of the device of FIG. 10 being a base station, but this is merely an example. For example, if the device of FIG. 10 is a UE, the operation according to the second example of the disclosure of the present specification described above with reference to FIGS. 9A to 9C may be performed. If the device of FIG. 10 is a UE, the UE may communicate with the base station, and the base station may communicate with the network entity of FIG. 10.

[0372] Below, an example of a procedure performed when the device is a base station (e.g., NG-RAN, A-RAN, etc.) is described.

[0373] In step (S1001), the device can transmit a setup request message to a network entity.

[0374] For example, a setup request message may be a setup request message related to an interface between a device and a network entity.

[0375] For example, the setup request message may include information related to one or more Ambient Internet on Things (AIoT) readers included in the device.

[0376] For example, information related to one or more AIoT readers may include one or more of an ID of the one or more AIoT readers, an area index related to the one or more AIoT readers, and / or location information related to the one or more AIoT readers.

[0377] In step (S1002), the network entity may transmit a setup response message to the device.

[0378] Before step (S1003) is performed, the device can perform an AIoT service operation for the AIoT device.

[0379] In step (S1003), the AIoT device can transmit a response to the device.

[0380] For example, a device may receive responses related to AIoT service operations from one or more AIoT devices. In the example of FIG. 10, one AIoT device is shown, but this is merely an example, and the device may receive responses from one or more AIoT devices.

[0381] For example, a device may receive a service request message related to an AIoT service operation from a network entity.

[0382] In step (S1004), the device can transmit a service response message to the network entity.

[0383] Before step (S1004) is performed, the network entity may receive a service request message from a network entity related to network exposure or a network entity related to an application. Based on the received service request message, the network entity may transmit a service request message related to an AIoT service operation to a device (e.g., a base station).

[0384] For example, the service response message may include the response received in step (S1003). For example, if the device receives multiple responses in step (S1003), the service response message may include some or all of the multiple responses.

[0385] For example, a service response message may include information related to at least one AIoT leader that received a response from one or more AIoT devices, among one or more AIoT leaders.

[0386] For example, information related to at least one AIoT leader may include a leader ID of the at least one AIoT leader, an area index of at least one area from among one or more areas related to the at least one AIoT leader that received the response from the at least one AIoT device.

[0387] For example, a service response message may be used by a network entity to generate location information of said at least one area based on an area index of said at least one area.

[0388] For example, a service response message may include a response related to an AIoT service operation received by the base station from one or more AIoT devices and information related to at least one AIoT leader that received the response among one or more AIoT leaders. The network entity may generate location information of at least one area based on an area index of at least one area in which the response was received.

[0389] For example, as described with reference to the example of FIG. 8, when a response from an AIoT device is received in an area jointly managed by two or more AIoT readers, the location of the AIoT device can be derived more accurately. For example, there may be two or more AIoT readers that have received a response from a first AIoT device among one or more AIoT devices. The location of the first AIoT device can be derived based on the response being received from the first AIoT device in a common area among one or more areas managed by the first AIoT reader and one or more areas managed by the second AIoT reader among the two or more AIoT readers.

[0390] For example, the location information of at least one area may be information based on one or more of geographic location information, Tracking Area Identity (TAI), cell ID, or area information.

[0391] For example, a network entity may send a service response message containing location information of at least one area to a network entity associated with the network exposure or to a network entity associated with the application.

[0392] According to one embodiment of the disclosure of the present specification, the AIoTF can measure the current location of the AIoT Device in an area unit smaller than a Cell and notify the AF.

[0393] For example, the UE or RAN to which the Reader belongs can transmit information zoning / coordinates of the area covered by the Reader to the AIoTF.

[0394] For example, AIoT can request an AIoT service operation for an AIoT Device located in a specific area or coordinates from a UE or RAN based on an AF request.

[0395] For example, after a UE or RAN performs an AIoT service operation in response to an AIoTF request, it may transmit information about the area in which it received a response from the AIoT Device to the AIoTF.

[0396] For example, AIoTF can convert information about the area in which a response is received from an AIoT Device into geographical information and transmit it to AF.

[0397] This specification may have various effects.

[0398] For example, the current location of an AIoT device can be effectively and / or accurately measured in units of area or zone smaller than a cell. The AIoTF can transmit geographical location information to the AF. Congestion can also be avoided by having the base station or reader collect responses from AIoT devices for a certain period of time or until a certain condition is met and then forward them to the AIoTF.

[0399] For example, AIoTF can measure the current location of an AIoT Device in an area or zone unit smaller than a cell without the help of the AIoT Device. AIoTF can convert the current location of the AIoT Device into geographical location information and transmit it to AF. Since the Reader collects the responses of the AIoT Device for a certain period of time and then transmits them to AIoTF, congestion situations that may occur in the Uu section (for Topology 2) and / or the NG (or NG') section (for Topology 1&2) can be prevented.

[0400] The effects that can be achieved through the specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects 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.

[0401] For reference, the operation of the terminal (e.g., UE, remote UE, relay UE, etc.) described in this specification can be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal (e.g., UE, remote UE, relay UE, etc.) can be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal (e.g., UE, remote UE, relay UE, etc.) described in this specification can be processed by one or more processors (102 or 202). The operation of the terminal described in this specification can be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a terminal (e.g., UE) described in the disclosure of this specification.

[0402] In addition, commands for performing operations of a terminal (e.g., UE, AIoT device, etc.) described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform operations of a terminal (e.g., UE, remote UE, relay UE, etc.) described in the disclosure of this specification.

[0403] For reference, the operations of a network node (e.g., AIoTF, AMF, SMF, UPF, PCF, NEF, UDM, DN, AF, etc.) or a base station (e.g., NG-RAN, gNB, gNB-DU, gNB-CU, DU, CU, CU-UP, CU-CP, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operations of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operations of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0404] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

[0405] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0406] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0407] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A step of transmitting a setup request message related to an interface between a device and a network entity to the network entity; and comprising the step of receiving a setup response message from the network entity; The setup request message includes information related to one or more Ambient Internet on Things (AIoT) readers included in the device, A step of receiving a response related to an AIoT service operation from one or more AIoT devices; A method further comprising the step of transmitting a service response message including the above response to the network entity.

2. In paragraph 1, A method wherein the information related to the one or more AIoT readers includes one or more of an ID of the one or more AIoT readers, an area index related to the one or more AIoT readers, and / or location information related to the one or more AIoT readers.

3. In paragraph 1 or 2, A method further comprising the step of receiving a service request message related to the AIoT service operation from the network entity.

4. In any one of paragraphs 1 to 3, A method further comprising a step of performing the AIoT service operation for the AIoT device.

5. In any one of paragraphs 1 to 4, The above service response message is, Among the one or more AIoT readers, information related to at least one AIoT leader that received the response from the one or more AIoT devices, A method wherein the information related to the at least one AIoT reader includes a leader ID of the at least one AIoT reader, an area index of at least one area from among one or more areas related to the at least one AIoT reader that received the response from the at least one AIoT device.

6. In any one of paragraphs 1 to 5, A method wherein the service response message is used by the network entity to generate location information of the at least one area based on an area index of the at least one area.

7. In any one of paragraphs 1 to 6, There are two or more AIoT readers that have received a response from a first AIoT device among the above one or more AIoT devices, A method in which the location of the first AIoT device is derived based on a response received from the first AIoT device in a common area among one or more areas managed by the first AIoT leader and one or more areas managed by the second AIoT leader among the two or more AIoT readers.

8. In any one of paragraphs 1 to 7, A method wherein the location information of at least one area is information based on one or more of geographic location information, Tracking Area Identity (TAI), cell ID, or area information.

9. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 1 to 7.

10. One or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 1 to 7.

11. A non-transitory computer-readable storage medium that records commands, A CRM wherein the above instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 7.

12. A step of receiving a setup request message related to the interface between the base station and the network entity from the base station; The setup request message includes information related to one or more Ambient Internet on Things (AIoT) readers included in the base station; A step of transmitting a setup response message to the base station; A step of receiving a first service response message from the base station, The first service response message includes a response related to an AIoT service operation received by the base station from one or more AIoT devices and information related to at least one AIoT leader that received the response among the one or more AIoT leaders; and A method comprising the step of generating location information of at least one area based on an area index of at least one area in which the response is received.

13. In paragraph 12, The above first service response message is, Among the one or more AIoT readers, information related to at least one AIoT leader that received the response from the one or more AIoT devices, A method wherein the information related to the at least one AIoT leader includes a leader ID of the at least one AIoT leader, an area index of at least one area from which the response was received from the at least one AIoT device among one or more areas related to the at least one AIoT leader.

14. In paragraph 12 or 13, A method wherein the information related to the one or more AIoT readers includes one or more of an ID of the one or more AIoT readers, an area index related to the one or more AIoT readers, and / or location information related to the one or more AIoT readers.

15. In any one of paragraphs 12 to 14, A step of receiving a second service request message from a network entity or an application related to network exposure; A step of transmitting a first service request message related to the AIoT service operation to the base station based on the second service request message being received; and A method further comprising the step of transmitting a second service response message including location information of at least one area to a network entity related to the network exposure or a network entity related to the application.

16. In any one of paragraphs 12 to 15, A method wherein the information related to the at least one AIoT leader includes a leader ID of the at least one AIoT leader, an area index of at least one area from which the response was received from the at least one AIoT device among one or more areas related to the at least one AIoT leader.

17. In any one of paragraphs 12 to 16, There are two or more AIoT readers that have received a response from a first AIoT device among the above one or more AIoT devices, A method in which the location of the first AIoT device is derived based on a response received from the first AIoT device in a common area among one or more areas managed by the first AIoT leader and one or more areas managed by the second AIoT leader among the two or more AIoT readers.

18. In any one of paragraphs 12 to 17, A method wherein the location information of at least one area is information based on one or more of geographic location information, Tracking Area Identity (TAI), cell ID, or area information.

19. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 12 to 18.

Images