Method and apparatus for controlling terminal

Abstract

Provided are a method and apparatus for controlling a terminal in a wireless communication system. Specifically, a base station receives information indicating a terminal that can operate as a reader for ambient Internet of things (IoT) devices. In addition, a core network node that provides ambient IoT services is selected on the basis of the information indicating the terminal. Subsequently, at least one of authentication information and authorization information for the ambient IoT service is received from the selected core network node.

Description

Terminal control method and device

[0001] This specification relates to wireless communications applicable to 5G NR, 5G-Advanced and 6G.

[0002] As more and more communication devices demand ever-increasing communication traffic, the need for next-generation 5G systems, which offer enhanced wireless broadband communication capabilities over existing LTE systems, is growing. This next-generation 5G system, known as NewRAT, differentiates communication scenarios into Enhanced Mobile BroadBand (eMBB), Ultra-reliability and low-latency communication (URLLC), and Massive Machine-Type Communications (mMTC).

[0003] Here, eMBB is a next-generation mobile communication scenario with characteristics such as High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate; URLLC is a next-generation mobile communication scenario with characteristics such as Ultra Reliable, Ultra Low Latency, and Ultra High Availability (e.g., V2X, Emergency Service, and Remote Control); and mMTC is a next-generation mobile communication scenario with characteristics such as Low Cost, Low Energy, Short Packet, and Massive Connectivity (e.g., Internet of Things (IoT)).

[0004] An object of the present specification is to provide a control method and device for a terminal that performs communication with an ambient IoT device that provides ultra-low complexity and ultra-low power in a wireless communication system.

[0005] One embodiment of the present specification provides a method for receiving, in a wireless communication system, information indicating a terminal capable of acting as a reader for an ambient Internet of Things (IoT) device, a core network node providing an ambient IoT service based on the information indicating the terminal. Thereafter, the method provides for receiving at least one of authentication information and authorization information for the ambient IoT service from the selected core network node.

[0006] In addition, one embodiment of the present specification provides a wireless communication system comprising at least one processor, and at least one memory storing instructions and being operably electrically connected to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: receiving information indicating a terminal capable of operating as a reader for an ambient IoT (Internet of Things) device; and selecting a core network node providing an ambient IoT service based on the information indicating the terminal. Thereafter, a base station is provided that receives at least one of authentication information and authorization information for the ambient IoT service from the selected core network node.

[0007] The base station can store at least one of authentication information and authorization information for the ambient IoT service received from the core network node in the context of the terminal.

[0008] Additionally, the base station may instruct the terminal on at least one of authentication information and authorization information for the ambient IoT service received from the core network node, and on whether to authenticate or grant authorization.

[0009] Meanwhile, at least one of authentication information and authorization information for the ambient IoT service may be received from the core network node via an initial context setup request message. Here, the initial context setup request message may include parameter information for the terminal to communicate with the RD (Reader Device) link with the ambient IoT device. The above parameter information may include at least one of RD link QoS (Quality of Service) indicator information, latency information, positioning accuracy information, connection density information, device density information, maximum message size information, maximum bit rate information, range information, maximum distance information, device power consumption information, delay budget information, power budget information, repetition count information, repetition cycle information, retransmission count information, validity time information, and device type information.

[0010] On the other hand, the base station may receive a UE context modification request message or a path switch request acknowledge message, wherein the UE context modification request message or the path switch request acknowledge message may include information indicating that authorization for the ambient IoT service is not granted. Based on the received information indicating that authorization is not granted, the base station may perform at least one of releasing an RD (Reader Device) link communication, deactivating the ambient IoT device, and prohibiting the terminal from accessing the ambient IoT service.

[0011] On the other hand, when the terminal is handed over, the base station may include at least one of authentication information and authorization information for the ambient IoT service received from the core network node in a handover request message and transmit it to the target base station.

[0012] According to the disclosure of this specification, it is possible to effectively control a terminal that performs communication with an ambient IoT device that provides ultra-low complexity and ultra-low power in a wireless communication system.

[0013] Figure 1 is a diagram illustrating a wireless communication system.

[0014] Figure 2 illustrates the structure of a radio frame used in NR.

[0015] Figures 3a to 3c are exemplary diagrams showing exemplary architectures for wireless communication services.

[0016] Figure 4 illustrates the slot structure of an NR frame.

[0017] Figure 5 illustrates an example of subframe types in NR.

[0018] Figure 6 illustrates the structure of a self-contained slot.

[0019] Figures 7a to 7c illustrate examples of connectivity topologies for ambient IoT networks and devices.

[0020] Figure 8 is a flowchart illustrating an operation method of a base station according to one embodiment of the present specification.

[0021] Figure 9 illustrates a device according to one embodiment of the present specification.

[0022] Fig. 10 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0023] Figure 11 shows a block diagram of a processor in which the disclosure of this specification is implemented.

[0024] FIG. 12 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 9 or the transmitter / receiver unit of the device illustrated in FIG. 10.

[0025] It should be noted that the technical terms used in this specification are used merely to describe specific embodiments and are not intended to limit the contents of this specification. In addition, unless specifically defined otherwise herein, the technical terms used in this specification should be interpreted as having a meaning generally understood by those skilled in the art to which this specification pertains, and should not be interpreted in an excessively broad or narrow sense. In addition, if a technical term used in this specification is an incorrect technical term that does not accurately express the contents and ideas of this specification, it should be replaced with a technical term that can be correctly understood by a person skilled in the art. In addition, general terms used in this specification should be interpreted according to their dictionary definitions or according to the preceding and following context, and should not be interpreted in an excessively narrow sense.

[0026] Additionally, the singular expressions used herein include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "consist of" or "have" should not be construed to necessarily include all of the components or steps described in the specification, and should be construed to mean that some of the components or steps may not be included, or that additional components or steps may be included.

[0027] Additionally, terms including ordinal numbers, such as "first" and "second," used herein may be used to describe various components, but these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, a first component could be referred to as a second component, and similarly, a second component could also be referred to as a first component.

[0028] When a component is referred to as being connected or connected to another component, it may be directly connected or connected to that other component, but there may also be other components intervening. Conversely, when a component is referred to as being directly connected or connected to another component, it should be understood that there are no other components intervening.

[0029] Hereinafter, embodiments will be described in detail with reference to the attached drawings. Regardless of the drawing numbers, identical or similar components will be given the same reference numbers and redundant descriptions thereof will be omitted. In addition, when describing the contents of this specification, if a detailed description of a related known technology is judged to obscure the gist of this specification, the detailed description thereof will be omitted. In addition, it should be noted that the attached drawings are only intended to make the contents and ideas of this specification easily understandable, and should not be construed as limiting the contents and ideas of this specification by the attached drawings. The contents and ideas of this specification should be construed to extend to all changes, equivalents, and substitutes other than the attached drawings.

[0030] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

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

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

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

[0034] Additionally, parentheses used in this specification may mean “for example.” Specifically, when “control information (PDCCH)” is indicated, “PDCCH (Physical Downlink Control Channel)” may be suggested as an example of “control information.” In other words, “control information” in this specification is not limited to “PDCCH,” and “PDDCH” may be suggested as an example of “control information.” Additionally, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be suggested as an example of “control information.”

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

[0036] Although the attached drawing illustrates a UE (User Equipment) as an example, the illustrated UE may also be referred to as a terminal, ME (Mobile Equipment), etc. In addition, the UE may be a portable device such as a laptop, mobile phone, PDA, smart phone, multimedia device, etc., or a non-portable device such as a PC or vehicle-mounted device.

[0037] Hereinafter, the term "UE" is used as an example of a device capable of wireless communication (e.g., a wireless communication device, a wireless device, or a wireless device). The operations performed by the UE can be performed by any device capable of wireless communication. A device capable of wireless communication may also be referred to as a wireless communication device, a wireless device, or a wireless device.

[0038] The term base station used below generally refers to a fixed station that communicates with wireless devices, and can be used as a comprehensive term that includes eNodeB (evolved-NodeB), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point, gNB (Next generation NodeB), RRH (remote radio head), TP (transmission point), RP (reception point), relay, etc.

[0039] Although this specification describes embodiments using LTE systems, LTE-A systems, and NR systems, these embodiments may be applied to any communication system falling within the above definitions.

[0040] Wireless Communication System

[0041] Building on the success of LTE (long term evolution) / LTE-Advanced (LTE-A) for 4th generation mobile communications, commercialization of the next generation, or 5th generation (so-called 5G) mobile communications, and follow-up research are also ongoing.

[0042] The International Telecommunication Union (ITU) defines 5G mobile communications as providing data transfer speeds of up to 20 Gbps and a perceived transmission speed of at least 100 Mbps everywhere. Its official name is "IMT-2020."

[0043] ITU proposes three usage scenarios: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications).

[0044] URLLC addresses usage scenarios that require high reliability and low latency. For example, services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (e.g., sub-1ms). Current 4G (LTE) latency is statistically 21-43ms (best 10%) and 33-75ms (median). This is insufficient to support services requiring sub-1ms latency. Next, eMBB usage scenarios address usage scenarios that require mobile ultra-wideband.

[0045] In other words, the 5th generation mobile communication system can support higher capacity than the current 4G LTE, increase the density of mobile broadband users, and support D2D (Device to Device), high reliability, and MTC (Machine-type communication). 5G research and development also aims for lower latency and lower battery consumption than 4G mobile communication systems to better implement the Internet of Things. For this 5G mobile communication, a new radio access technology (New RAT or NR) may be proposed.

[0046] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges (FR1, 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” and can be called millimeter wave (mmW).

[0047] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0048] The numerical value of the frequency range of the NR system can be changed. For example, FR1 can include a band from 410 MHz to 7125 MHz, as shown in Table 1. That is, FR1 can 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 can include unlicensed bands. Unlicensed bands can be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0049] Meanwhile, 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), physical multicast channel (PMCH), physical control format indicator channel (PCFICH), physical downlink control channel (PDCCH), and physical hybrid ARQ indicator channel (PHICH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, is a signal with a special predefined waveform known to the gNB and the UE. For example, cell specific RS, UE-specific RS (UE-RS), positioning RS (PRS), and channel state information RS (CSI-RS) are defined as downlink reference signals. The 3GPP LTE / LTE-A standard defines uplink physical channels corresponding to resource elements carrying information originating from higher layers, and uplink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers.For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

[0050] In this specification, PDCCH (Physical Downlink Control CHannel) / PCFICH (Physical Control Format Indicator CHannel) / PHICH ((Physical Hybrid automatic retransmit request Indicator CHannel) / PDSCH (Physical Downlink Shared CHannel) mean a set of time-frequency resources or a set of resource elements that carry DCI (Downlink Control Information) / CFI (Control Format Indicator) / downlink ACK / NACK (ACKnowlegement / Negative ACK) / downlink data, respectively. In addition, PUCCH (Physical Uplink Control CHannel) / PUSCH (Physical Uplink Shared CHannel) / PRACH (Physical Random Access CHannel) mean a set of time-frequency resources or a set of resource elements that carry UCI (Uplink Control Information) / uplink data / random access signals, respectively.

[0051] Figure 1 is a diagram illustrating a wireless communication system.

[0052] As can be seen from FIG. 1, the wireless communication system includes at least one base station (BS). The BS is divided into a gNodeB (or gNB) (20a) and an eNodeB (or eNB) (20b). The gNB (20a) supports 5th generation mobile communications. The eNB (20b) supports 4th generation mobile communications, i.e., long term evolution (LTE).

[0053] Each base station (20a and 20b) provides communication services for a specific geographic area (commonly referred to as a cell) (20-1, 20-2, 20-3). The cell may be further divided into multiple areas (referred to as sectors).

[0054] A UE (user equipment) typically belongs to a single cell, and the cell to which the UE belongs is called a serving cell. The base station that provides communication services for the serving cell is called a serving base station (BS). Since the wireless communication system is a cellular system, there are other cells adjacent to the serving cell. These other cells adjacent to the serving cell are called neighbor cells. The base station that provides communication services to the neighbor cell is called a neighbor BS. The serving cell and neighbor cells are determined relative to the UE.

[0055] Hereinafter, downlink refers to communication from a base station (20) to a UE (10), and uplink refers to communication from a UE (10) to a base station (20). In downlink, the transmitter may be part of the base station (20), and the receiver may be part of the UE (10). In uplink, the transmitter may be part of the UE (10), and the receiver may be part of the base station (20).

[0056] Meanwhile, wireless communication systems can be broadly divided into frequency division duplex (FDD) and time division duplex (TDD). In FDD, uplink and downlink transmissions occupy different frequency bands and occur at different times. In TDD, uplink and downlink transmissions occupy the same frequency band but occur at different times. The channel response in TDD is essentially reciprocal, meaning that the downlink and uplink channel responses are nearly identical in a given frequency range. Therefore, in TDD-based wireless communication systems, the downlink channel response can be derived from the uplink channel response, which is advantageous. In TDD, uplink and downlink transmissions are time-divided across the entire frequency band, so downlink transmission by the base station and uplink transmission by the UE cannot be performed simultaneously. In TDD systems, where uplink and downlink transmissions are divided into subframes, uplink and downlink transmissions are performed in different subframes.

[0057] Figure 2 illustrates the structure of a radio frame used in NR.

[0058] In NR, uplink and downlink transmissions are structured as frames. A radio frame is 10ms long and is defined by two 5ms half-frames (HF). Each half-frame is defined by five 1ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols, depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 symbols. When an extended CP is used, each slot contains 12 symbols. Here, the symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or DFT-s-OFDM symbols).

[0059] Support for various numerologies

[0060] In NR systems, multiple numerologies may be provided to terminals as wireless communication technologies advance. For example, an SCS of 15 kHz supports a wide area in traditional cellular bands. An SCS of 30 kHz / 60 kHz supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0061] The above numerology can be defined by the cycle prefix (CP) length and subcarrier spacing (SCS). A single cell can provide multiple numerologies to a terminal. When the numerology index is represented by μ, each subcarrier spacing and the corresponding CP length can be as shown in the table below.

[0062] μ△f=2 μ 15 [kHz]CP015 General 130 General 260 General, Extended 3120 General 4240 General 5480 General 6960 General

[0063] For general CP, when the index of the numerology is represented by μ, the number of OFDM symbols per slot (N slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) is as shown in the table below.

[0064] μ△f=2 μ 15 [kHz]N slot symb N frame,μ slot N subframe,μ slot 015141011301420226014404312014808424014160165480143203269601464064

[0065] For extended CP, when the index of the numerology is represented by μ, the number of OFDM symbols per slot (N slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) is as shown in the table below.

[0066] μSCS (15*2 u )N slot symb N frame,μ slot N subframe,μslot 260KHz (u=2)12404

[0067] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0068] Figures 3a to 3c are exemplary diagrams showing exemplary architectures for wireless communication services.

[0069] Referring to FIG. 3a, the UE is connected to an LTE / LTE-A-based cell and an NR-based cell in a DC (dual connectivity) manner.

[0070] The above NR-based cell is connected to the core network for existing 4th generation mobile communication, i.e. Evolved Packet Core (EPC).

[0071] Referring to FIG. 3b, unlike FIG. 3a, the LTE / LTE-A-based cell is connected to a core network for 5th generation mobile communication, i.e., a 5G core network.

[0072] A service method based on an architecture as illustrated in Figures 3a and 3b above is called NSA (non-standalone).

[0073] Referring to Figure 3c, the UE is connected only to NR-based cells. A service method based on this architecture is called SA (standalone).

[0074] Meanwhile, in the above NR, it may be considered that reception from the base station utilizes a downlink subframe, and transmission to the base station utilizes an uplink subframe. This method can be applied to paired and unpaired spectrums. A pair of spectrums means that two carrier spectrums are included for downlink and uplink operations. For example, in a pair of spectrums, one carrier may include a downlink band and an uplink band that are paired with each other.

[0075] Figure 4 illustrates the slot structure of an NR frame.

[0076] A slot contains multiple symbols in the time domain. For example, in the case of a normal CP, one slot contains 14 symbols, but in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical, P)RBs in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A terminal can be configured with up to N (e.g., 4) BWPs in the downlink and uplink, respectively. Downlink or uplink transmission is performed through an activated BWP, and at a given time, only one BWP among the BWPs configured for the terminal can be activated. In the resource grid, each element is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0077] Figure 5 illustrates an example of subframe types in NR.

[0078] The transmission time interval (TTI) illustrated in FIG. 5 may be referred to as a subframe or slot for NR (or new RAT). The subframe (or slot) of FIG. 5 may be used in a TDD system of NR (or new RAT) to minimize data transmission delay. As illustrated in FIG. 5, a subframe (or slot) includes 14 symbols. The symbols in the front of the subframe (or slot) may be used for a downlink (DL) control channel, and the symbols in the back of the subframe (or slot) may be used for an uplink (UL) control channel. The remaining symbols may be used for DL ​​data transmission or UL data transmission. According to this subframe (or slot) structure, downlink transmission and uplink transmission may be sequentially performed in one subframe (or slot). Therefore, downlink data may be received within a subframe (or slot), and an uplink acknowledgment (ACK / NACK) may be transmitted within the subframe (or slot).

[0079] The structure of these subframes (or slots) can be called self-contained subframes (or slots).

[0080] Specifically, the first N symbols in a slot are used to transmit a DL control channel (hereinafter, DL control region), and the last M symbols in the slot can be used to transmit a UL control channel (hereinafter, UL control region). N and M are each integers greater than or equal to 0. A resource region (hereinafter, data region) between the DL control region and the UL control region can be used for DL ​​data transmission or UL data transmission. For example, a physical downlink control channel (PDCCH) can be transmitted in the DL control region, and a physical downlink shared channel (PDSCH) can be transmitted in the DL data region. A physical uplink control channel (PUCCH) can be transmitted in the UL control region, and a physical uplink shared channel (PUSCH) can be transmitted in the UL data region.

[0081] Using this subframe (or slot) structure has the advantage of minimizing the final data transmission latency by reducing the time required to retransmit data that has experienced reception errors. In this self-contained subframe (or slot) structure, a time gap may be required during the transition from transmit mode to receive mode or from receive mode to transmit mode. To this end, some OFDM symbols during the transition from DL to UL in the subframe structure can be designated as a guard period (GP).

[0082] Figure 6 illustrates the structure of a self-contained slot.

[0083] In an NR system, a frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and a UL control channel can all be included within a single slot. For example, the first N symbols within a slot can be used to transmit a DL control channel (hereinafter, referred to as a DL control region), and the last M symbols within a slot can be used to transmit a UL control channel (hereinafter, referred to as a UL control region). N and M are each integers greater than or equal to 0. The resource region (hereinafter, referred to as a data region) between the DL control region and the UL control region can be used for DL ​​data transmission or UL data transmission. As an example, the following configuration can be considered. Each section is listed in chronological order.

[0084] 1. DL only configuration

[0085] 2. UL only configuration

[0086] 3. Mixed UL-DL configuration

[0087] - DL area + GP (Guard Period) + UL control area

[0088] - DL control area + GP + UL area

[0089] DL area: (i) DL data area, (ii) DL control area + DL data area

[0090] UL domain: (i) UL data domain, (ii) UL data domain + UL control domain

[0091] In the DL control region, a PDCCH can be transmitted, and in the DL data region, a PDSCH can be transmitted. In the UL control region, a PUCCH can be transmitted, and in the UL data region, a PUSCH can be transmitted. In the PDCCH, downlink control information (DCI), for example, DL data scheduling information, UL data scheduling information, etc., can be transmitted. In the PUCCH, uplink control information (UCI), for example, ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, SR (Scheduling Request), etc., can be transmitted. GP provides a time gap when a base station and a terminal switch from transmission mode to reception mode or when switching from reception mode to transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0092] Figures 7a to 7c illustrate examples of connectivity topologies for ambient IoT networks and devices.

[0093] The ambient Internet of Things (AIO) is an IoT device powered by energy harvesting. It has no battery or limited energy storage capability (e.g., using a capacitor), and its energy is provided by harvesting energy from radio waves, light, motion, heat, or other suitable sources. Energy harvesting can be continuous or incidental (e.g., from vibration). Therefore, AIO devices cannot be assumed to always have power to transmit and receive data. Ambient IoT devices need to be designed to have lower complexity, smaller size, reduced capabilities, and lower power consumption than previously defined 3GPP IoT devices (e.g., Narrowband Internet of Things (NB-IoT) / enhanced Machine-Type Communication (eMTC) devices). Ambient IoT devices can be designed to have a long lifespan of 10 years or more without maintenance. This can be used to replace existing 3GPP IoT devices or to support various use cases (e.g., inventory, sensors, positioning, commands) that existing 3GPP IoT devices cannot support. Connectivity topologies such as those shown in FIGS. 7a to 7c can be defined for ambient IoT networks and devices. In all these topologies, the ambient IoT devices can be provided with carrier waves from other nodes within or outside the topology. The links in each topology can be bidirectional or unidirectional. In FIG. 7a, the ambient IoT devices communicate directly and bidirectionally with a base station (BS).The base station is a node that provides the function of a radio network (RAN) according to the separation of functions from a core network (CN) in a mobile communication network, and represents a node that provides a radio network function such as radio resource control for ambient IoT devices (e.g., RAN node function: A function that contains, e.g., the control of the A-IoT radio resources used towards the A-IoT device). The base station may be referred to as a reader, which is a counterpart node for a tag such as an ambient IoT device. For the convenience of explanation, the node is referred to as a base station hereinafter. This is for the convenience of explanation and may be referred to by any other name such as AIoT RAN node, AIoT RAN Reader, AIoT base station, or AIoT BS Reader. Communication between the base station and the ambient IoT device includes ambient IoT data and / or signaling. The base station transmitting to the ambient IoT device and the base station receiving from the ambient IoT device may be the same base station or different base stations.

[0094] Meanwhile, referring to FIG. 7b, the ambient IoT device transmits data / signals to the base station and receives data / signals from an assisting node / assisting terminal. Alternatively, the ambient IoT device receives data / signals from the base station and transmits data / signals to the assisting node / terminal. Alternatively, the ambient IoT device receives data / signals from an assisting node connected to the base station via a wireless interface (Uu) and transmits data / signals to the assisting node. The assisting node may be referred to as a terminal reader, which is a counterpart node for a tag such as the ambient IoT device. For convenience of explanation, a node connected to the base station via a wireless interface (Uu) is referred to as an assisting node hereinafter. This is for convenience of explanation and may be referred to by any other name, such as AIoT Assisting UE, UE connected / associated with AIoT enabled RAN, AIoT UE reader, etc. In this topology, auxiliary nodes / terminals can be relays, IABs (Integrated Access Backhauls), UEs (User Equipment), repeaters, etc., capable of providing ambient IoT functions / services. In Fig. 7c, the ambient IoT device communicates bidirectionally with the UE (e.g., a general terminal). Communication between the UE and the ambient IoT device includes ambient IoT data and / or signaling.

[0095] As mentioned above, although connectivity topology types for ambient IoT networks and devices have been defined, a specific base station control method for providing communication of ambient IoT devices that supports lower complexity, smaller size, reduced capabilities, and lower power consumption compared to existing 3GPP LPWA (Low-Power Wide-Area) IoT has not been provided.

[0096] To address these issues, the present invention proposes a method and device for providing communication for ambient IoT devices that supports lower complexity, smaller size, reduced capabilities, and lower power consumption compared to existing 3GPP LPWA IoT. For example, the present invention proposes a method and device for controlling an assisting node / UE that operates as a reader for an ambient IoT device.

[0097] Hereinafter, a data transmission and reception method based on 5GS (Fifth Generation System) / NR technology will be described in detail. However, this is for convenience of explanation, and the present invention can be applied to any system or wireless access technology (for example, 6G). The embodiments described in the present invention may refer to information elements and operation contents specified in the NR / 5GS standard (for example, TS 38.321, which is an NR MAC standard, TS 38.331, which is an NR RRC standard, TS 23.501, which is a system architecture standard, etc.). Even if the terminal operation contents related to the definition of the corresponding information element are not described in this specification, the corresponding contents specified in the standard specification, which is a known technology, may be included in the present invention.

[0098] Any function described below may be defined as an individual terminal capability (UE radio capability or UE Core network capability) and transmitted by the terminal to a base station / core network entity (e.g., AMF (Access and Mobility Management Function) / SMF (Session Management Function) / AIoTNF (Ambient IoT Network Function)) through corresponding signaling. Alternatively, any function may be combined / combined and defined as a corresponding terminal capability and transmitted by the terminal to a base station / core network entity through corresponding signaling.

[0099] For convenience of explanation, the ambient IoT device may be expressed as an ambient IoT terminal, IoT device, IoT terminal, or terminal hereinafter.

[0100] Ambient IoT devices can be defined and categorized into at least one device type / category based on at least one capability (or a combination of capabilities) they support. For example, based on energy storage capacity, devices can be categorized into devices with no storage at all, devices with a storage capacity of a specific value (up to E1 Joules), and devices with a storage capacity of another specific value (up to E2 Joules, where E2 > E1). Other examples include devices with no energy storage and no independent signal generation / amplification (e.g., backscatter transmission) (referred to as Device A for convenience of description below), devices with energy storage and no independent signal generation (e.g., backscatter transmission) (referred to as Device B for convenience of description below), where Device B's use of stored energy may include amplification of reflected signals), and devices with energy storage and independent signal generation (e.g., active RF components for transmission) (referred to as Device C for convenience of description below).As another example, a device can be classified into a device having ~1 μW peak power consumption, energy storage, and no amplification in both DL and UL within the device, whose uplink transmission is backscattered on an externally provided carrier wave (referred to as Device 1 below for convenience of description), a device having ≤ a few hundred μW peak power consumption, energy storage, and amplification possible in both DL and UL within the device, whose uplink transmission is backscattered on an externally provided carrier wave (referred to as Device 2a below for convenience of description), and a device having ≤ a few hundred μW peak power consumption, energy storage, and amplification possible in both DL and UL within the device, whose uplink transmission is internally generated by the device (referred to as Device 2b below for convenience of description).

[0101] The base station / AIoTNF may transmit / instruct the terminal / auxiliary terminal via an RRC / NAS message (or MAC Control Element) information indicating permission / support / configuration of any function or any combination of functions described below. For example, this may be instructed to the terminal / auxiliary terminal prior to or simultaneously with the configuration / application of the function / auxiliary terminal. The RRC / NAS message may be broadcast via system information. Alternatively, it may be instructed to the terminal / auxiliary terminal via a dedicated RRC / NAS message.

[0102] The base station / AIoTNF can transmit / instruct the terminal / auxiliary terminal via MAC / RRC / NAS messages information to restrict any of the functions described below. For example, the prohibit timer for the corresponding function can be instructed. The prohibit timer can be started / restarted before or when the corresponding function is initiated. While the timer is running, the terminal / auxiliary terminal can be restricted / controlled to prevent the initiation / execution of the corresponding function.

[0103] The functions described below may be performed individually and independently. Alternatively, the functions described below may be arbitrarily combined and performed, and this is also clearly included within the scope of the present invention.

[0104] Any information described below may be traffic characteristic information (e.g., expected value / average, deviation, standard deviation minimum, maximum, etc.) statistically / empirically obtained / calculated / derived from a terminal / network. Accordingly, any information included in this specification may represent at least one of the average (expected value) / minimum / maximum / standard deviation values. This is for convenience of explanation, and all information in this specification may be used as statistical information. Alternatively, it may be information pre-configured in the terminal / network or provisioned through OAM (Operations, Administration, and Maintenance) / application server / application function / UDM (Unified Data Management).

[0105] Typical use cases for ambient IoT include inventory, sensor data collection, asset tracking, and actuator control. Typical use cases for ambient IoT can be supported via mobile networks. Ambient IoT use cases via mobile networks can be defined as ambient IoT services. For example, the primary purpose of an ambient IoT inventory service (e.g., inventory) is to discover which products (e.g., boxes, containers, packages, tools) are present in a specific area. When a request is sent from the network within a specific area, ambient IoT devices attached to these products report identifiers associated with the products, and other information such as status, measurement results, and / or location may be added. Sensor data collection allows ambient IoT devices to connect / bind with sensors. Sensor data transmission can be initiated by the ambient IoT devices. This can be periodically, when the ambient IoT devices are powered on, or triggered by the network. The primary purpose of asset tracking is to determine the location of an item. Ambient IoT devices attached to such items report identifiers associated with the item. These can then be combined with location information. Asset tracking can be initiated by an ambient IoT-enabled assisting node / UE, a base station, a core network entity (e.g., Access and Mobility Management Function (AMF), Session Management Function (SMF), Ambient IoT Network Function (AIoTNF), Network Exposure Function (NEF), or an application server. The location of an ambient IoT device can be located within a specific range of an assisting node / UE / base station. Ambient IoT command services (e.g.,Using actuator control, ambient IoT devices are connected to actuators. Actuator command transmission is generally initiated by the network. Here, AIoTNF (Ambient IoT Network Function) represents a network function / application function / application server for providing ambient IoT services. This is for convenience of explanation and can be changed to any other name. AIoTNF can be implemented as an independent entity, or can be implemented as an entity combined with the AMF within the AMF by being included in the AMF function. A core network control plane entity (e.g., AMF / SMF / AIoTNF) that has an interface with a terminal can connect to an external application server (AS) through a network exposure function (NEF) that provides network function (NF) capabilities and event linkage / exposure. For example, a specific core network control plane entity (e.g., AMF / AIoTNF) can forward data / messages received from ambient IoT devices to AIoTNF / NEF / AS. AIoTNF can perform at least one of the following functions: authentication for an ambient IoT application server / application function, registration for an ambient IoT device, registration for a base station / general terminal / auxiliary terminal that provides wireless connection / access to the ambient IoT device, transmission of an ambient IoT service trigger / request message to a base station / general terminal / auxiliary terminal that provides wireless connection / access to the ambient IoT device at the request of the ambient IoT application server / application function, reception of a service data / confirmation / response message in response to transmission of an ambient IoT service trigger / request message from a base station / general terminal / auxiliary terminal that provides wireless connection / access to the ambient IoT device, transmission of a message received from a base station / general terminal / auxiliary terminal that provides wireless connection / access to the ambient IoT device to the ambient IoT application server / application function, and transmission and reception of an NAS message through an interface with the ambient IoT device.In this way, AIoTNF can request AIoT service from base station / general terminal / auxiliary terminal based on information included in the request (e.g. AIoT service type (inventory, command), AIoT device identifier, message / data size expected to be received from AIoT device according to the service request) according to the request of the corresponding AF, and receive service data / confirmation / response message therefor. AIoTNF can send and receive NAS messages with ambient IoT devices through base station / general terminal / auxiliary terminal. The NAS message can include one or more of ambient IoT device identifier, A-IoT application data, and NAS signaling.

[0106] Ambient IoT devices (e.g., device 1 and device 2a defined above) operate in passive mode to support low complexity and can transmit data using backscattering. As shown in FIGS. 7A to 7C, devices that transmit data to or receive data from ambient IoT devices can be base stations, auxiliary terminals, or general terminals. A device that transmits data to or receives data from ambient IoT devices via a wireless interface can be referred to as a reader. This is for convenience of explanation and can be replaced with any other name. Ambient IoT devices can start / initiate data communication / transmission when triggered / paged / notified by a reader. As described above, the reader can be one of a base station, an auxiliary terminal, or a general terminal.

[0107] When an auxiliary terminal / general terminal operates as a reader, the communication between the base station and the reader can be performed using conventional mobile communication technology. For communication between the reader and the ambient IoT device (for convenience of explanation, this is referred to as RD communication (Reader to / from Device communication) hereinafter. This can refer to both bidirectional communication between the reader and the device, unidirectional communication from the reader to the device, and unidirectional communication from the device to the reader), conventional mobile communication technology can be utilized or the technology can be applied in conjunction with conventional mobile communication technology. For example, transmission from the reader to the device can use an OFDM-based waveform. Meanwhile, for low-complexity device implementation, OOK (On-Off Keying) can be used for OFDM symbol transmission for one OFDM waveform. Line coding such as Manchester encoding or pulse interval encoding can be used. For RD timing acquisition, a timing acquisition signal (e.g., RD ​​preamble) may be included to indicate the start of RD (Reader Device) transmission within the time domain for RD transmission. For DR (Device to Reader) timing acquisition, a timing acquisition signal (e.g., DR preamble) may be included to indicate the start of DR (Device to Reader) transmission within the time domain for DR transmission. RD communication configuration information that the base station indicates to the auxiliary terminal may include information for indicating one of (bidirectional) in-band configuration, guard band configuration, and single band configuration.

[0108] In this specification, the physical channel for RD data transmission is referred to as PRDCH (Physical Reader to Device CHannel), the physical channel for DR data transmission is referred to as PDRCH (Physical Device to Reader CHannel), and the interface / link between the reader and the device is referred to as RD (Reader Device) interface / link. This is for convenience of explanation and may be replaced with any other name. The RD interface / link may represent one or more of a wireless interface between the reader and the device, a bidirectional link between the reader and the device, a unidirectional link from the reader to the device, and a unidirectional link from the device to the reader. For reference, the PC5 interface, which is a wireless interface between terminals, and the side link, which is a link between terminals, represent one or more of a bidirectional link, a unidirectional link between a transmitting terminal and a receiving terminal, and a unidirectional link between a receiving terminal and a transmitting terminal.

[0109] Authentication / authorization of auxiliary terminals that transmit and receive data through the RD interface

[0110] The network can identify / distinguish and process an auxiliary terminal operating as a leader (or a general terminal operating as a leader; for convenience of explanation, an auxiliary terminal operating as a leader is described below, but a general terminal operating as a leader is also included in the scope of the present invention). By transmitting information for instructing the terminal to establish / set up a wireless connection of the terminal, the base station can select a core network node providing the function / service and perform network registration. The base station can receive authentication / authorization information for the function / service (e.g., communication between a leader and a device, RD communication procedure, leader capability, auxiliary terminal capability, Ambient IoT service) from the core network node to the network.

[0111] For example, when a base station providing wireless access to an auxiliary terminal receives an INITIAL CONTEXT SETUP REQUEST message (from a core network node (e.g., AMF)), the base station may receive authentication / authorization information (e.g., authorization status of the assisting UE) for a corresponding function / service (e.g., Ambient IoT Reader, Ambient IoT Reader UE, Ambient IoT assisting node, Inventory service, command / actuator service, asset tracking, or sensor service) and store the information in the corresponding terminal context. For example, a UE reader authorization indication may be received for a terminal acting as a reader. The authentication / authorization information may be provided as a single information element. Alternatively, the authentication / authorization information may be provided as information elements that are differentiated for each function / service. The authentication / authorization information can be used to indicate whether the auxiliary terminal is authenticated / authorized for the corresponding function / service (e.g., AIoT service, allowed area, allowed terminal type (single, multiple, group), coverage). Once the information is set, the base station can consider the auxiliary terminal as authenticated / authorized for the related function / service. The base station can use this for the RD link communication of the terminal (e.g., network-scheduled mode: a mode in which the network dynamically or semi-statically allocates the corresponding radio resources).

[0112] As another example, a base station providing wireless access to an auxiliary terminal may receive parameter information on an RD link / interface when receiving an INITIAL CONTEXT SETUP REQUEST message. The parameter information on the RD link / interface may indicate communication parameters (e.g., RD ​​link QoS indicator, latency, positioning accuracy, connection density, device density, maximum message size, maximum bit rate, range, maximum distance, device power consumption, delay budget, power budget, number of repetitions, repetition period, number of transmissions / retransmissions, validity time, and / or device type, etc.) required for the auxiliary terminal to perform RD link communication with an ambient IoT device. The corresponding parameters may be indicated by respective parameter values ​​or by index values ​​that quantize the corresponding parameter values. For example, the range (or maximum distance) can be mapped to an index value of ~10m (0), ~20m (1), ~30m (2), ~40m (3), and ~50m (4) to indicate the maximum distance between the reader and the device, from 0 to 50m. The base station can receive this information and store it in the corresponding terminal context. The base station can use this for the terminal's RD link communication (e.g., in network-scheduled mode).

[0113] As another example, when the base station receives a UE context modification request message (UE CONTEXT MODIFICATION REQUEST message) including authentication / authorization information (e.g., authorization status of the assisting UE) for a corresponding function / service (e.g., Ambient IoT Reader, Ambient IoT Reader UE, Ambient IoT assisting node, Inventory service, command / actuator service, asset tracking, or sensor service), the base station may update the corresponding information for the corresponding UE. If the corresponding information / sub-information element is received with the authorization set to not authorized, the base station may initiate at least one of releasing the corresponding RD link communication and deactivating the corresponding ambient IoT device. The base station may perform actions to ensure that the corresponding auxiliary terminal no longer has access to the corresponding function / service. The base station may reject an RRC connection / RD communication schedule request from the corresponding auxiliary terminal. The base station may control (e.g., barring) the access of the corresponding auxiliary terminal.

[0114] As another example, the base station may use this when a UE CONTEXT MODIFICATION REQUEST message is received on the RD link / interface to provide parameter information.

[0115] The auxiliary terminal can be mobile. When the auxiliary terminal is mobile, it can maintain authentication / authorization information (e.g., authorization status of the assisting UE) for the aforementioned functions / services (e.g., Ambient IoT Reader, Ambient IoT Reader UE, Ambient IoT assisting node, Inventory service, command / actuator service, asset tracking, or sensor service) to support the service.

[0116] For example, a handover request message transmitted by a source base station to a target base station may include authentication / authorization information (e.g., authorization status of the assisting UE) for the corresponding function / service (e.g., Ambient IoT Reader, Ambient IoT Reader UE, Ambient IoT assisting node, Inventory service, command / actuator service, asset tracking, or sensor service). When the target base station receives the information, it may consider the corresponding auxiliary terminal to be authenticated / authorized for the corresponding function / service. The base station may use this for the RD link communication of the corresponding terminal (e.g., in a network-scheduled mode).

[0117] As another example, a handover request message transmitted by a source base station to a target base station may include parameter information (e.g., RD ​​link QoS indicator, latency, positioning accuracy, connection density, device density, maximum message size, maximum bit rate, range, maximum distance, device power consumption, delay budget, power budget, repetition count, repetition period, transmission / retransmission count, validity time, device type, etc.) on the RD link / interface. The base station can use this for the RD link communication of the corresponding terminal (e.g., in a network scheduled mode).

[0118] As another example, a path switch request acknowledgement message (PATH SWITCH REQUEST ACKNOWLEDGE message) transmitted by a core network node (e.g., AMF) to a (target) base station may include authentication / authorization information (e.g., authorization status of the assisting UE) for the corresponding function / service (e.g., Ambient IoT Reader, Ambient IoT Reader UE, Ambient IoT assisting node, Inventory service, command / actuator service, asset tracking, or sensor service). When the base station receives the information, it may update the information for the corresponding UE. If the information / sub-information element is received with the authorization set to not authorized, the base station may initiate at least one of releasing the corresponding RD link communication and deactivating the corresponding ambient IoT device. The base station may perform actions to ensure that the corresponding auxiliary UE can no longer access the corresponding function / service.

[0119] As another example, a path switch request acknowledgement message (PATH SWITCH REQUEST ACKNOWLEDGE message) transmitted by a core network node (e.g., AMF) to a (target) base station may include parameter information transmitted on the RD link / interface. The base station can use this for RD link communications of the corresponding terminal (e.g., in network scheduled mode).

[0120] Transmission of instruction information of auxiliary terminals that transmit and receive data through the RD interface

[0121] Identification of an auxiliary terminal that provides / controls RD link communication (or an auxiliary terminal that acts as a leader or triggers an ambient IoT device to receive uplink transmissions backscattered from that device) can be performed at the wireless network / base station. This allows selection of an appropriate core network node capable of supporting the auxiliary terminal (e.g., an auxiliary node capable of AMF).

[0122] For example, when an auxiliary terminal attempts to access the network for RD transmission, for example, when establishing a connection with the auxiliary terminal, the auxiliary terminal may transmit information to the serving base station to indicate this. For example, the indication information may be included in any uplink message in the "RRC Setup / establishment" procedure. As another example, the information may be included in the "RRC Setup Complete" message. As another example, the information may be included in the "RRC Resume complete" message. As another example, the information may be included in the "RRC Re-establishment complete" message.

[0123] The serving base station can select an appropriate AMF / AIoTNF for the auxiliary terminal (e.g., an Ambient IoT capable / supporting AMF, an Ambient IoT Reader supporting AMF, an Ambient IoT Reader UE supporting AMF, an Ambient IoT assisting node supporting AMF, an Inventory service capable AMF, or a command / actuator service capable AMF). The AMF / AIoTNF can extract authentication / authorization information for the corresponding function / service of the auxiliary terminal through core network signaling and provide it to the corresponding base station.

[0124] Below, other embodiments of the present invention are described.

[0125] When an auxiliary terminal acts as a reader and communicates with an ambient IoT device, the base station can control communication between the auxiliary terminal and the ambient IoT device. For example, the base station can control wireless resources on the RD interface through signaling with the auxiliary terminal.

[0126] An auxiliary terminal acting as a reader can control the radio resources used for RD link transmission and reception between the reader and devices. For example, one or more of the radio resources used for data transmission from the reader to the device(s) and the radio resources used for data transmission from the device(s) to the reader can be controlled. A resource allocation mode for RD link communication can be defined in the auxiliary terminal.

[0127] For example, an auxiliary terminal can communicate with an ambient IoT device through scheduled resource allocation by a base station.

[0128] In order for an auxiliary terminal acting as a reader to transmit / receive data with an ambient IoT device over an RD link, the auxiliary terminal must be in an RRC connection state. The base station can schedule RD link transmission resources of the auxiliary terminal. The base station can configure / instruct the auxiliary terminal about RD link transmission parameters of the auxiliary terminal. The transmission parameters can be any parameters included in this specification. For example, the base station can configure / instruct the auxiliary terminal about the radio resource configuration to be used in the RD link through a dedicated RRC message (e.g., RRC reconfiguration).

[0129] As another example, an auxiliary terminal can communicate with an ambient IoT device through autonomous resource allocation. The auxiliary terminal can autonomously select its transmission resources from a resource pool.

[0130] In autonomous resource allocation mode, the auxiliary terminal can be in an RRC connection state to transmit / receive data to / from an ambient IoT device. This allows the auxiliary terminal to receive RD link communication requests from the corresponding AMF / AIoTNF / AF via the base station / network to trigger the ambient IoT device, or to transmit data received from the ambient IoT device to the AMF / AIoTNF / AF (Application Function).

[0131] In at least one of the following cases: when the auxiliary terminal goes out of the base station coverage, when the auxiliary terminal detects a radio link failure with the base station, when the auxiliary terminal is in an RRC idle / inactive state, and when the ambient IoT device is in an inactive / unable to transmit or receive state, the auxiliary terminal may restrict communication (or part of its functionality) with the ambient IoT device. For example, the auxiliary terminal may suspend RD link communication. For another example, the auxiliary terminal may restrict transmission to the ambient IoT device but may receive data transmitted by the ambient IoT device. For another example, the auxiliary terminal may store data received from the device by an RD link trigger and suspend transmission to the base station (until it enters an RRC connected state). For another example, the auxiliary terminal may initiate an RRC connection establishment / setup procedure with the base station. For another example, the auxiliary terminal may resume RD link communication when it enters an RRC connected state. As another example, the auxiliary terminal may be configured to perform RD link communication only when it is in an RRC connection state. As another example, the auxiliary terminal may consider the radio resources to be valid during the validity period of the radio resource configuration to be used in the RD link received from the base station in the RRC connection state. When the base station receives information to instruct to release the radio resource configuration or when the validity period of the radio resource configuration expires (e.g., when the timer expires, the timer may be started when the auxiliary terminal receives / configures / applies the radio resource configuration or when the auxiliary terminal transitions to an RRC idle / inactive state), the auxiliary terminal may consider the radio resources to be invalid. Even when the auxiliary terminal is in an RRC idle / inactive state, the auxiliary terminal may be configured to perform RD link communication while the radio resources are valid.

[0132] A capability can be defined to support communication between an auxiliary terminal and an ambient IoT device when out of base station coverage. An auxiliary terminal supporting the capability can transmit / receive data with an ambient IoT device and store the data even when out of base station coverage. A terminal with the capability can have transmission resources and transmission parameters for RD link communication pre-configured in the auxiliary terminal. Alternatively, the transmission resources and transmission parameters can be indicated and stored from the base station / OAM / AIoTSF / AF during an RRC connection state. When the auxiliary terminal enters coverage, the auxiliary terminal can transmit the stored data to the network (e.g., the base station / AIoTSF / AMF / AF).

[0133] As another example, information for configuring scheduled resource allocation and / or autonomous resource allocation on the RD link can be configured in the auxiliary terminal via an RRC message (e.g., an RRC reconfiguration message). The information can include at least one of an RD-RNTI (Radio Network Temporary Identifier) ​​(or an RD-RNTI list), RD link scheduling information, periodic BSR timer information, and retransmission BSR timer information. Here, the RD-RNTI represents a unique terminal identifier used for RD link communication scheduling (at the base station). This is for convenience of explanation and can be replaced with any other name. Here, the RD link scheduling information includes a start time / subframe / slot / symbol (for RD link communication), a start time / subframe / slot / symbol offset (for RD link communication), a start time / subframe / slot / symbol based on a specific reference time (e.g., RD / DR preamble) (for RD link communication), a start time / subframe / slot / symbol offset based on a specific reference time (for RD link communication), a duration (for RD link communication), a transmission opportunity (for RD link), a transmission cycle (for RD link), an available time slot, a range of available time slots, a maximum number of time slots, an associated uplink / downlink start time / subframe / slot / symbol for indicating an RD link start time, a start time / subframe / slot / symbol offset, RD link frequency domain information, RD link subchannel number / index, RD link frequency offset, and RD link MCS (Modulation and Coding) Scheme), RD link transmission block size / transmission data size, communication range / Range, location information, priority, RD link transmission / retransmission count, and (RD link communication) validity period / time.In this way, RD link scheduling information may include one or more of time domain radio resource information, frequency domain radio resource information, and valid time information for the corresponding radio resource used on the interface between the device and the reader.

[0134] A base station can transmit DCI (or scheduling grant) for the RD link schedule of an auxiliary terminal to the auxiliary terminal. Information for the RD link scheduling of the auxiliary terminal can be transmitted from the base station in a (specific) DCI format that is CRC (cyclic redundancy check) scrambled by the RD-RNTI.

[0135] As another example, to configure autonomous resource allocation on the RD link, the RD link resource pool, the RD link resource pool identifier, the start time / subframe / slot / symbol (for RD link communication), the start time / subframe / slot / symbol offset (for RD link communication), the start time / subframe / slot / symbol relative to a specific reference time (for RD link communication), the start time / subframe / slot / symbol offset relative to a specific reference time (for RD link communication), the duration (for RD link communication), the transmission opportunity (occasion), the transmission period (for RD link), the available time slot, the available time slot range, the maximum number of time slots, the associated uplink / downlink start time / subframe / slot / symbol for indicating the RD link start time, the start time / subframe / slot / symbol offset, the RD link frequency domain information, the RD link subchannel number / index, the DR link frequency offset, the RD link MCS, At least one of information among RD link transmission block size / transmission data size, communication range / Range, location information, priority, RD link transmission / retransmission count, (RD link communication) validity period / time, RD link subchannel size indicating minimum granularity in frequency domain for RD link sensing, RD link sensing subchannel index / index list, and RD link time window / window start / window duration for sensing (or channel busy ratio measurement) can be configured in the auxiliary terminal through RRC.

[0136] As another example, when an auxiliary terminal receives a message to trigger / request an ambient IoT service from a network (e.g., a base station / AIoTSF / AMF / AF), the auxiliary terminal can transmit the corresponding service trigger / paging / notification to the ambient IoT device. The auxiliary terminal can receive confirmation / response / additional data for the corresponding service trigger / paging / notification from the ambient IoT device and transmit the same to the network (e.g., a base station / AIoTSF / AMF / AF).

[0137] When a base station receives a message to trigger / request an ambient IoT service from a network (e.g., AIoTSF / AMF / AF) and instructs the auxiliary terminal with the message (or information included in the message), the message used may be a downlink RRC message.

[0138] For example, the base station may transmit the message (or the information included in the message) using a UEInformationRequest RRC message. As another example, the base station may transmit the message (or the information included in the message) using a DLInformationTransfer RRC message. As another example, the base station may transmit the message (or the information included in the message) using an RRCreconfiguration RRC message. As another example, the message (or the information included in the message) may be transmitted via a newly defined downlink RRC message that is distinct from the UEInformationRequest RRC message or the DLInformationTransfer RRC message. As another example, the UEInformationRequest RRC message or the DLInformationTransfer RRC message or the new RRC message may contain the message (or the information included in the message) via a Non-Access Stratum (NAS) container.

[0139] As another example, when the auxiliary terminal receives confirmation / response / additional data for the service trigger / paging / notification from the ambient IoT device, the auxiliary terminal can include the information in the UEInformationResponse RRC message and transmit it. As another example, when the auxiliary terminal receives confirmation / response / additional data for the service trigger / paging / notification from the ambient IoT device, the auxiliary terminal can include the information in the ULInformationTransfer RRC message and transmit it. As another example, the base station can use the RRCreconfigurationcomplete RRC message to transmit the message (or the information included in the message). As another example, it can be transmitted through a newly defined downlink RRC message that is distinct from the UEInformationResponse RRC message or the ULInformationTransfer RRC message. As another example, the UEInformationResponse RRC message or the ULInformationTransfer RRC message or a new RRC message can include the message (or the information included in the message) through an NAS container.

[0140] As another example, when a base station receives a message from a network (e.g., AIoTSF / AMF / AF) to trigger / request an ambient IoT service and instructs the auxiliary terminal with the message (or information included in the message), the base station may transmit at least one of the information for configuring the aforementioned scheduled resource allocation and / or autonomous resource allocation via a downlink RRC message.

[0141] As another example, when a base station receives a message to trigger / request an ambient IoT service from a network (e.g., AIoTSF / AMF / AF), the base station can instruct the auxiliary terminal via L2 (layer 2, e.g., MAC CE) / L1 (layer 1, e.g., DCI / PDCCH) signaling with the message (or at least one piece of information included in the message).

[0142] As another example, a message for a base station to trigger / request an ambient IoT service from a network (e.g., AIoTSF / AMF / AF) may include at least one piece of information included in the information for configuring the aforementioned scheduled resource allocation and / or autonomous resource allocation.

[0143] A MAC entity can transmit RD link data using a specific terminal identifier indicated / configured by the base station / network.

[0144] For example, the identifier may be an RNTI (e.g., RD-RNTI) for dynamically scheduled RD link transmissions. The identifier may be configured in the auxiliary terminal via RRC as RNTI / C(Cell)-RNTI indication information for monitoring base station / network scheduling for RD link transmissions.

[0145] As another example, the identifier may be information for uniquely identifying the terminal (or multiple terminals, or a group of terminals) in the network / PLMN (Public Land Mobile Network).

[0146] As another example, the identifier could be an identifier uniquely identified by the owner of the ambient IoT device.

[0147] As another example, the identifier may be an identifier that is uniquely identified / assigned by the PLMN / operator.

[0148] As another example, the identifier may be configured / indicated to the auxiliary terminal by the base station via RRC / L2 (e.g., MAC CE) / L1 (e.g., DCI / PDCCH) signaling.

[0149] As another example, the identifier may be indicated as an auxiliary terminal by AIoTSF / AF / AMF.

[0150] As another example, when an RD link grant is received on the PDCCH for the RD-RNTI of the MAC entity, the MAC entity may use the received RD link grant to determine at least one of transmission resources and transmission parameters for initial transmission / retransmission of the MAC PDU. The RD link grant may include at least one piece of information included in the information for configuring the scheduled resource allocation and / or autonomous resource allocation described above.

[0151] For another example, the base station can instruct / configure a semi-persistent RD link grant to the auxiliary terminal via a configured grant via RRC. For example, the base station can configure / instruct the auxiliary terminal about the RD link scheduling information to be used in the RD link via a dedicated RRC message (e.g., RRC reconfiguration). RD link scheduling information includes: start time / subframe / slot / symbol (for RD link communication), start time / subframe / slot / symbol offset (for RD link communication), start time / subframe / slot / symbol based on a specific reference time (e.g., RD / DR preamble) (for RD link communication), start time / subframe / slot / symbol offset based on a specific reference time (for RD link communication), duration (for RD link communication), transmission opportunity (for RD link), transmission cycle (for RD link), available time slot, available time slot range, maximum number of time slots, associated uplink / downlink start time / subframe / slot / symbol for indicating RD link start time, start time / subframe / slot / symbol offset, RD link frequency domain information, RD link subchannel number / index, RD link frequency offset, RD link MCS (Modulation and Coding Scheme), The RD link scheduling information may include at least one of the following: RD link transmission block size / transmission data size, communication range / Range, location information, priority, RD link transmission / retransmission count, and (RD link communication) validity period / time. In this way, the RD link scheduling information may include one or more of the time domain radio resource information, frequency domain radio resource information, and validity time information for the corresponding radio resource used on the interface between the device and the reader.

[0152] The auxiliary terminal can request resource allocation from the base station for RD link transmission. In other words, the auxiliary terminal can request RD link scheduling from the base station for RD link transmission. The auxiliary terminal can indicate the request information to the base station. The request information can be indicated via RRC / L2 (e.g., MAC CE) / L1 (e.g., UCI / PUCCH) signaling.

[0153] When an auxiliary terminal receives a message from a network (e.g., a base station / AIoTSF / AMF / AF) to trigger / request an ambient IoT service, the auxiliary terminal can instruct the base station with the corresponding request information. The auxiliary terminal can instruct the base station with the corresponding request information based on an ambient IoT service trigger received from a higher layer.

[0154] For example, the request information can be transmitted to the base station via an existing RRC message (e.g., UE information Response, UE assistant message). To this end, the UE Information Request message can be instructed to the auxiliary terminal by including at least one of RD link transmission resources, RD link transmission parameter information, information for configuring the aforementioned scheduled resource allocation and / or autonomous resource allocation, and allowance / support / instruction information for RD link transmission configuration, A-IoT service type, ambient IoT device identifier, (estimated) number of ambient IoT devices, and (estimated) message size transmitted from the device to the leader. As another example, the request information can be transmitted via a new RRC message (e.g., RD / DR link UE assistant message) that is distinct from an existing RRC message (e.g., UE information Response). The RRC message can be a one-way RRC message transmitted from the terminal to the base station without receiving the RRC message requested from the terminal to the base station. Alternatively, the RRC message may be a response RRC message transmitted by the terminal to the base station in response to the request RRC message when the base station receives an RRC message requesting the terminal, the RRC message including at least one of information for configuring RD link transmission resources, RD link transmission parameter information, the aforementioned scheduled resource allocation and / or autonomous resource allocation, and permission / support / instruction information for configuring RD link transmission, an A-IoT service type, an ambient IoT device identifier, the (estimated) number of ambient IoT devices, and a message size transmitted from the (estimated) devices to the leader. The base station may instruct the terminal to send an RRC reconfiguration message including dedicated configuration information to the secondary terminal.The RRC reconfiguration message may include at least one of information for configuring RD link transmission resources, RD link transmission parameter information, and the aforementioned scheduled resource allocation and / or autonomous resource allocation.

[0155] As another example, the request information may be transmitted to the base station via a MAC CE. The MAC CE may include information for requesting at least one piece of information included in the RD link transmission resources, RD link transmission parameter information, and information for configuring the aforementioned scheduled resource allocation and / or autonomous resource allocation.

[0156] As another example, the request information may be transmitted to the base station via UCI / SR / PUCCH. The UCI / SR / PUCCH may include information for requesting at least one piece of information included in RD link transmission resources, RD link transmission parameter information, and information for configuring the aforementioned scheduled resource allocation and / or autonomous resource allocation.

[0157] RD link grants can be received dynamically on the PDCCH.

[0158] As another example, the RD link grant can be semi-statically configured by RRC. Alternatively, the RD link transmission resources / grants can be autonomously selected by the MAC entity.

[0159] As another example, if a MAC entity is configured by RRC to transmit using a resource pool, the MAC entity can select the corresponding RD link transmission resource (e.g., PRDCH parameter, Carrier Wave (CW) parameter). For example, it can randomly select the corresponding resource among the configured resources (e.g., time / frequency / code resources / resource set). For the corresponding RD link transmission occasion, the MAC entity can select the corresponding transmission block size / MCS, if configured.

[0160] As another example, an auxiliary terminal can use a Scheduling Request (SR) to request RD link resources (or resource allocation).

[0161] As another example, a scheduling request may be used by an auxiliary terminal to inform a serving base station of information about RD link data to be transmitted to an ambient IoT device within a MAC entity (e.g., whether data has been received from a higher layer, the corresponding data buffer, volume, the corresponding AIoT-service type (e.g., inventory and / or command), the corresponding message type, the corresponding device type, the RD link transmission parameters, and QoS parameters for RD link data processing, etc.).

[0162] As another example, a scheduling request may be used when triggered by RD link buffer status reporting to inform the serving base station about the RD link data buffer / volume within the MAC entity.

[0163] As another example, the priority of the triggered SR can be set to have a higher value than the priority of other general logical channels of the auxiliary terminal (for example, a logical channel associated with a DRB (Data Radion Bearer)).

[0164] As another example, the priority of the triggered SR may be set to have a lower value than the priority of another general logical channel of the auxiliary terminal (e.g., a logical channel associated with a Signaling Radio Bearer (SRB)).

[0165] As another example, when the RD link grant has accepted all pending data available for transmission within the RD link, all pending SR(s) (triggered according to the RD link BSR procedure) may be canceled, and the corresponding SR prohibit timer (sr-ProhibitTimer) may be stopped.

[0166] A reporting procedure may be defined to notify the serving base station of information related to RD link data to be transmitted to an ambient IoT device (e.g., whether data has been received from a higher layer, the corresponding data buffer, volume, corresponding message type, corresponding device type, RD link transmission parameters, and QoS parameters for RD link data processing, etc.). For convenience of explanation, this is hereinafter referred to as RD link BSR (Buffer Status Report). This is for convenience of explanation only and may be changed to any other name (e.g., RD ​​link DTT (Device-Terminated Triggered) request reporting, RD link scheduling request, or RD link command reporting, etc.).

[0167] An RD Link BSR can be triggered when any of the events described below occur.

[0168] For example, it could be triggered when RD link data becomes available (or is received, buffered) to the MAC entity.

[0169] As another example, the MAC entity could be triggered when a new command / message becomes available for transmission on the RD link (or is received, buffered).

[0170] Another example could be triggered when the retransmission BSR timer expires to control that reporting.

[0171] As another example, the retransmission BSR timer to control the reporting may be triggered when the timer expires and any RD link data / command / message is available / present.

[0172] Another example could be when uplink resources are allocated and the padding BSR is triggered and the number of remaining padding bits is greater than the size of the RD link BSR MAC CE plus its subheader.

[0173] As another example, the MAC entity may start or restart the retransmission BSR timer when uplink shared channel (UL-SCH) resources are available for a new transmission and, as a result of logical channel priorities, the UL-SCH resources can accommodate the RD link BSR MAC CE plus its subheader.

[0174] As another example, the MAC entity may start or restart the retransmission BSR timer when it receives an RD link grant for new data / message / command transmission on the RD link.

[0175] As another example, the RD Link BSR may include at least one of ambient IoT device identifier information (or index information for the identifier), buffer size information, ambient IoT data / comment / message type information, and logical channel / logical channel group identifier information mapped to the ambient IoT data / comment / message type. The information may be configured in the auxiliary terminal via RRC.

[0176] Figure 8 is a flowchart illustrating an operation method of a base station according to one embodiment of the present specification.

[0177] Referring to FIG. 8, a base station receives information indicating a terminal capable of operating as a reader for an ambient IoT (Internet of Things) device (S801). An auxiliary terminal operating as a reader or a general terminal operating as a reader can transmit the corresponding indication information to the base station. Based on the received information indicating a terminal capable of operating as a reader, the base station selects a core network node that provides an ambient IoT service (S802). The base station performs network registration for the terminal with the selected core network node. Through this, at least one of authentication information and authorization information for the ambient IoT service is received from the selected core network node (S803).

[0178] The base station can store at least one of authentication information and authorization information for the ambient IoT service received from the core network node in the context of the terminal.

[0179] Additionally, the base station may instruct the terminal on at least one of authentication information and authorization information for the ambient IoT service received from the core network node, and on whether to authenticate or grant authorization.

[0180] Meanwhile, at least one of authentication information and authorization information for the ambient IoT service may be received from the core network node via an initial context setup request message. Here, the initial context setup request message may include parameter information for the terminal to communicate with the RD (Reader Device) link with the ambient IoT device. The above parameter information may include at least one of RD link QoS (Quality of Service) indicator information, latency information, positioning accuracy information, connection density information, device density information, maximum message size information, maximum bit rate information, range information, maximum distance information, device power consumption information, delay budget information, power budget information, repetition count information, repetition cycle information, retransmission count information, validity time information, and device type information.

[0181] On the other hand, the base station may receive a UE context modification request message or a path switch request acknowledge message, wherein the UE context modification request message or the path switch request acknowledge message may include information indicating that authorization for the ambient IoT service is not granted. Based on the received information indicating that authorization is not granted, the base station may perform at least one of releasing an RD (Reader Device) link communication, deactivating the ambient IoT device, and prohibiting the terminal from accessing the ambient IoT service.

[0182] On the other hand, when the terminal is handed over, the base station may include at least one of authentication information and authorization information for the ambient IoT service received from the core network node in a handover request message and transmit it to the target base station.

[0183] The disclosures of this specification, as described so far, can be implemented through various means. For example, the disclosures of this specification can be implemented through hardware, firmware, software, or a combination thereof. Specifically, the disclosures will be described below with reference to the drawings.

[0184] Figure 9 illustrates a device according to one embodiment of the present specification.

[0185] Referring to FIG. 9, the wireless communication system may include a first device (100a) and a second device (100b).

[0186] The first device (100a) may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) 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 climate / environmental device, a device related to 5G services, or any other device related to the 4th industrial revolution field.

[0187] The second device (100b) may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) 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 climate / environmental device, a device related to 5G services, or any other device related to the 4th industrial revolution field.

[0188] The first device (100a) may include at least one processor, such as a processor (1020a), at least one memory, such as a memory (1010a), and at least one transceiver, such as a transceiver (1031a). The processor (1020a) may perform the functions, procedures, and / or methods described above. The processor (1020a) may perform one or more protocols. For example, the processor (1020a) may perform one or more layers of a wireless interface protocol. The memory (1010a) may be connected to the processor (1020a) and may store various types of information and / or commands. The transceiver (1031a) may be connected to the processor (1020a) and may be controlled to transmit and receive wireless signals.

[0189] The second device (100b) may include at least one processor, such as a processor (1020b), at least one memory device, such as a memory (1010b), and at least one transceiver, such as a transceiver (1031b). The processor (1020b) may perform the functions, procedures, and / or methods described above. The processor (1020b) may implement one or more protocols. For example, the processor (1020b) may implement one or more layers of a wireless interface protocol. The memory (1010b) may be connected to the processor (1020b) and may store various types of information and / or commands. The transceiver (1031b) may be connected to the processor (1020b) and may be controlled to transmit and receive wireless signals.

[0190] The memory (1010a) and / or the memory (1010b) may be connected internally or externally to the processor (1020a) and / or the processor (1020b), or may be connected to another processor via various technologies such as a wired or wireless connection.

[0191] The first device (100a) and / or the second device (100b) may have one or more antennas. For example, the antenna (1036a) and / or the antenna (1036b) may be configured to transmit and receive wireless signals.

[0192] Fig. 10 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0193] In particular, FIG. 10 is a drawing illustrating the device of FIG. 9 in more detail.

[0194] The device includes a memory (1010), a processor (1020), a transceiver (1031), a power management module (1091), a battery (1092), a display (1041), an input unit (1053), a speaker (1042), and a microphone (1052), a subscriber identification module (SIM) card, and one or more antennas.

[0195] The processor (1020) may be configured to implement the proposed functions, procedures, and / or methods described herein. Layers of a radio interface protocol may be implemented in the processor (1020). The processor (1020) may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor (1020) may be an application processor (AP). The processor (1020) may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of the processor (1020) may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, a KIRINTM series processor manufactured by HiSilicon®, or a corresponding next-generation processor.

[0196] The power management module (1091) manages power to the processor (1020) and / or the transceiver (1031). The battery (1092) supplies power to the power management module (1091). The display (1041) outputs the results processed by the processor (1020). The input unit (1053) receives input to be used by the processor (1020). The input unit (1053) can be displayed on the display (1041). A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and its associated keys, which are used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0197] The memory (1010) is operably coupled to the processor (1020) and stores various information for operating the processor (610). The memory (1010) may include a read-only memory (ROM), a random access memory (RAM), flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiment is implemented in software, the techniques described herein may be implemented as modules (e.g., procedures, functions, etc.) that perform the functions described herein. The modules may be stored in the memory (1010) and executed by the processor (1020). The memory (1010) may be implemented within the processor (1020). Alternatively, the memory (1010) may be implemented external to the processor (1020) and communicatively connected to the processor (1020) via various means known in the art.

[0198] The transceiver (1031) is operably coupled to the processor (1020) and transmits and / or receives a radio signal. The transceiver (1031) includes a transmitter and a receiver. The transceiver (1031) may include baseband circuitry for processing a radio frequency signal. The transceiver controls one or more antennas to transmit and / or receive a radio signal. The processor (1020) transmits command information to the transceiver (1031) to initiate communication, for example, to transmit a radio signal constituting voice communication data. The antenna functions to transmit and receive radio signals. Upon receiving a radio signal, the transceiver (1031) may transmit the signal to the processor (1020) for processing and convert the signal to baseband. The processed signal may be converted into audible or readable information output through the speaker (1042).

[0199] The speaker (1042) outputs sound-related results processed by the processor (1020). The microphone (1052) receives sound-related input to be used by the processor (1020).

[0200] A user inputs command information, such as a phone number, for example, by pressing (or touching) a button on an input unit (1053) or by voice activation using a microphone (1052). The processor (1020) receives this command information and processes it to perform an appropriate function, such as dialing a phone number. Operational data can be extracted from a SIM card or memory (1010). In addition, the processor (1020) can display command information or operation information on a display (1041) for the user's recognition and convenience.

[0201] Figure 11 shows a block diagram of a processor in which the disclosure of this specification is implemented.

[0202] As can be seen from FIG. 11, the processor (1020) implementing the disclosure of the present specification may include multiple circuits to implement the proposed functions, procedures, and / or methods described herein. For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3). Furthermore, although not shown, the processor (1020) may include more circuits. Each circuit may include multiple transistors.

[0203] The above processor (1020) may be called an application-specific integrated circuit (ASIC) or an application processor (AP), and may include at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphics processing unit (GPU).

[0204] FIG. 12 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 9 or the transmitter / receiver unit of the device illustrated in FIG. 10.

[0205] Referring to FIG. 12, the transceiver (1031) includes a transmitter (1031-1) and a receiver (1031-2). The transmitter (1031-1) includes a Discrete Fourier Transform (DFT) unit (1031-11), a subcarrier mapper (1031-12), an IFFT unit (1031-13), a CP insertion unit (1031-14), and a wireless transmitter (1031-15). The transmitter (1031-1) may further include a modulator. In addition, for example, the transmitter may further include a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown), and a layer permutator (not shown), which may be arranged before the DFT unit (1031-11). That is, in order to prevent an increase in PAPR (peak-to-average power ratio), the transmitter (1031-1) first passes the information through a DFT (1031-11) before mapping the signal to a subcarrier. The signal spread (or precoded in the same sense) by the DFT unit (1031-11) is mapped to a subcarrier through a subcarrier mapper (1031-12) and then passes through an IFFT (Inverse Fast Fourier Transform) unit (1031-13) to be converted into a signal on the time axis.

[0206] The DFT unit (1031-11) performs DFT on the input symbols and outputs complex-valued symbols. For example, if Ntx symbols are input (where Ntx is a natural number), the DFT size is Ntx. The DFT unit (1031-11) may be called a transform precoder. The subcarrier mapper (1031-12) maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper (1031-12) may be called a resource element mapper. The IFFT unit (1031-13) performs IFFT on the input symbols and outputs a baseband signal for data, which is a time-domain signal. The CP insertion unit (1031-14) copies a portion of the rear portion of the baseband signal for data and inserts it into the front portion of the baseband signal for data. CP insertion prevents ISI (Inter-Symbol Interference) and ICI (Inter-Carrier Interference), thereby maintaining orthogonality even in multipath channels.

[0207] On the other hand, the receiver (1031-2) includes a wireless reception unit (1031-21), a CP removal unit (1031-22), an FFT unit (1031-23), and an equalization unit (1031-24). The wireless reception unit (1031-21), the CP removal unit (1031-22), and the FFT unit (1031-23) of the receiver (1031-2) perform the inverse functions of the wireless transmission unit (1031-15), the CP insertion unit (1031-14), and the IFF unit (1031-13) of the transmitter (1031-1). The receiver (1031-2) may further include a demodulator.

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

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

[0210] 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 and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In a method of operating a base station in a wireless communication system, A step of receiving information indicating a terminal capable of acting as a reader for an ambient IoT (Internet of Things) device; A step of selecting a core network node that provides an ambient IoT service based on information indicating the terminal; and A method comprising the step of receiving at least one of authentication information and authorization information for the ambient IoT service from a permanent core network node.

2. In paragraph 1, A method further comprising a step of storing at least one of the authentication information and the authorization information in the context of the terminal.

3. In paragraph 1, A method further comprising a step of indicating to the terminal at least one of authentication information and authorization information based on at least one of the authentication information and authorization information.

4. In paragraph 1, A method wherein at least one of the authentication information and the authorization information is received via an initial context setup request message.

5. In paragraph 4, A method in which the initial context setup request message includes parameter information for RD (Reader Device) link communication between the terminal and the ambient IoT device.

6. In paragraph 5, A method wherein the parameter information includes at least one of RD link QoS (Quality of Service) indicator information, latency information, positioning accuracy information, connection density information, device density information, maximum message size information, maximum bit rate information, range information, maximum distance information, device power consumption information, delay budget information, power budget information, repetition count information, repetition cycle information, retransmission count information, validity time information, and device type information.

7. In paragraph 4, Further comprising a step of receiving a UE context modification request message or a path switch request acknowledge message, A method wherein the terminal context modification request message or the path switch request confirmation message includes information that authorization for the ambient IoT service is not granted.

8. In paragraph 7, A method further comprising, based on the above-mentioned non-authorization information, performing at least one of: releasing the RD (Reader Device) link communication, deactivating the ambient IoT device, and prohibiting the terminal from accessing the ambient IoT service.

9. In paragraph 1, A method further comprising the step of including at least one of the authentication information and the authorization information in a handover request message and transmitting the handover request message to a target base station during a handover of the terminal.

10. As a base station in a wireless communication system, at least one processor; and At least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor are: A step of receiving information indicating a terminal capable of acting as a reader for an ambient IoT (Internet of Things) device; A step of selecting a core network node that provides an ambient IoT service based on information indicating the terminal; and A base station comprising a step of receiving at least one of authentication information and authorization information for the ambient IoT service from a permanent core network node.

11. In paragraph 10, Based on the above instruction being executed by the at least one processor, the operations performed are: A base station further comprising a step of storing at least one of the authentication information and the authorization information in the context of the auxiliary terminal.

12. In paragraph 10, Based on the above instruction being executed by the at least one processor, the operations performed are: A base station further comprising a step of indicating to the terminal at least one of authentication information and authorization information.

13. In paragraph 10, A base station, wherein at least one of the authentication information and the authorization information is received via an initial context setup request message.

14. In paragraph 13, The base station, wherein the initial context setup request message includes parameter information for RD (Reader Device) link communication between the terminal and the ambient IoT device.

15. In paragraph 14, A base station, wherein the parameter information includes at least one of RD link QoS (Quality of Service) indicator information, latency information, positioning accuracy information, connection density information, device density information, maximum message size information, maximum bit rate information, range information, maximum distance information, device power consumption information, delay budget information, power budget information, repetition count information, repetition cycle information, retransmission count information, validity time information, and device type information.

16. In paragraph 13, Based on the above instruction being executed by the at least one processor, the operations performed are: Further comprising a step of receiving a UE context modification request message or a path switch request acknowledge message, A base station, wherein the terminal context modification request message or the path switch request confirmation message includes information that authorization for the ambient IoT service is not granted.

17. In paragraph 16, Based on the above instruction being executed by the at least one processor, the operations performed are: A base station further comprising, based on the above-mentioned non-authorization information, a step of performing at least one of: releasing the RD (Reader Device) link communication, deactivating the ambient IoT device, and prohibiting the terminal from accessing the ambient IoT service.

18. In paragraph 10, Based on the above instruction being executed by the at least one processor, the operations performed are: A base station further comprising a step of including at least one of the authentication information and the authorization information in a handover request message and transmitting the handover request message to a target base station during a handover of the terminal.

Images