Signaling method and apparatus

Abstract

A signaling method and apparatus in a wireless communication system are provided. This terminal receives, from a base station, a first radio resource control (RRC) message including a first ambient Internet of Things (AIoT) parameter for an inventory request and, after receiving the first RRC message, performs an inventory procedure through an AIoT wireless interface. In addition, after performing the inventory procedure, the terminal transmits a second RRC message to the base station in response to the first RRC message, wherein the second RRC message includes a second A-IoT parameter for a response to and / or a report on the inventory request.

Description

Signaling method and device

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

[0002] As the times change and more communication devices demand larger communication traffic, there is a demand for next-generation 5G systems, which are wireless broadband communication systems that are improved over existing LTE systems. In these next-generation 5G systems, referred to as NewRAT, communication scenarios are classified 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 characterized by high spectrum efficiency, high user experience data rate, and high peak data rate; URLLC is a next-generation mobile communication scenario characterized by ultra-reliability, ultra-low latency, and ultra-high availability (e.g., V2X, emergency service, remote control); and mMTC is a next-generation mobile communication scenario characterized by low cost, low energy, short packet, and massive connectivity (e.g., Internet of Things (IoT)).

[0004] One disclosure of this specification aims to provide a signaling method and apparatus for supporting data communication of a 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 in which, in a wireless communication system, a terminal receives a first Radio Resource Control (RRC) message from a base station that includes a first Ambient Internet of Things (AIoT) parameter for an inventory request, and after receiving the first RRC message, performs an inventory procedure through an AIoT wireless interface. Additionally, after performing the inventory procedure, the terminal transmits a second RRC message to the base station in response to the first RRC message, wherein the second RRC message includes a second A-IoT parameter for at least one of a response to and a report regarding the inventory request.

[0006] Additionally, one embodiment of the present specification provides a wireless communication system comprising at least one processor and at least one memory that stores instructions and is operabably electrically connected to at least one processor, and based on instructions being executed by at least one processor, an operation performed is: receiving a first Radio Resource Control (RRC) message from a base station that includes a first Ambient Internet of Things (AIoT) parameter for an inventory request, and after receiving the first RRC message, performing an inventory procedure through an AIoT wireless interface. Additionally, after performing the inventory procedure, a second RRC message is transmitted to the base station in response to the first RRC message, wherein the second RRC message includes a second A-IoT parameter for at least one of a response to and a report for the inventory request, and the terminal provides

[0007] The first AIoT parameter information may include at least one of AIoT device identification information, security parameter information, information for terminal reader selection, information regarding the number of target AIoT devices, and information regarding the size of the D2R (Device to Reader) response message according to the inventory request. Here, the first AIoT parameter information may be stored by an RRC entity.

[0008] The above AIoT device identification information may include either permanent AIoT device identification information or identification information that has been security-processed with respect to the permanent AIoT device identification information. Here, the security parameter information may be random parameter information used to generate the security-processed identification information.

[0009] Meanwhile, the first RRC message may be received via a specific signaling radio bearer (SRB), and the second RRC message may be transmitted via the specific signaling radio bearer (SRB). Here, the specific SRB may be an SRB type distinct from the existing SRB1, SRB2, SRB3, SRB4, and SRB5, and may be configured by the base station after Access Stratum (AS) security is activated. Additionally, the specific SRB may be configured with a lower priority compared to the existing SRB0 and SRB1.

[0010] According to the disclosure of the present specification, signaling between a terminal and a base station can be effectively controlled to support data communication of a device providing ultra-low complexity and ultra-low power in a wireless communication system.

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

[0012] Figure 2 illustrates the structure of a wireless frame used in NR.

[0013] FIGS. 3a to 3c are exemplary diagrams illustrating exemplary architectures for wireless communication services.

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

[0015] Figure 5 illustrates an example of a subframe type in NR.

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

[0017] FIGS. 7a and 7b show examples of connectivity topologies for ambient Internet of Things (A-IoT) networks and devices.

[0018] Figure 8 shows an example of a procedure for an A-IoT inventory service.

[0019] Figure 9 shows an example of an Access Stratum (AS) procedure between an A-IoT device and a reader.

[0020] FIG. 10 is a flowchart illustrating a method of operation of a terminal according to one embodiment of the present specification.

[0021] FIG. 11 shows an apparatus according to one embodiment of the present specification.

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

[0023] FIG. 13 shows a block diagram of a processor in which the disclosure of the present specification is implemented.

[0024] FIG. 14 is a block diagram showing in detail the transceiver of the first device shown in FIG. 11 or the transceiver of the device shown in FIG. 12.

[0025] It should be noted that technical terms used in this specification are used merely to describe specific embodiments and are not intended to limit the content of this specification. Furthermore, unless specifically defined otherwise in this specification, technical terms used in this specification should be interpreted in the sense generally understood by those skilled in the art to which this disclosure pertains, and should not be interpreted in an overly broad or overly narrow sense. Additionally, if a technical term used in this specification is an incorrect technical term that fails to accurately express the content and concept of this specification, it should be understood as being replaced by a technical term that can be correctly understood by those skilled in the art. Moreover, general terms used in this specification should be interpreted according to their prior definitions or the context, and should not be interpreted in an overly narrow sense.

[0026] Additionally, singular expressions used in this specification include plural expressions unless the context clearly indicates otherwise. In this application, terms such as "composed of" or "have" should not be interpreted as necessarily including all of the various components or steps described in the specification, and should be interpreted as meaning that some of the components or steps may be omitted or additional components or steps may be included.

[0027] Additionally, terms including ordinal numbers, such as first, second, etc., used herein may be used to describe various components, but said components shall not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the rights, the first component may be named the second component, and similarly, the second component may be named the first component.

[0028] When it is stated that a component is connected to or coupled with another component, it may be directly connected to or coupled with that other component, or there may be other components in between. On the other hand, when it is stated that a component is directly connected to or directly coupled with another component, it should be understood that there are no other components in between.

[0029] Hereinafter, embodiments will be described in detail with reference to the attached drawings. Identical or similar components regardless of drawing symbols are assigned the same reference number, and redundant descriptions thereof will be omitted. Furthermore, in describing the contents of this specification, if it is determined that a detailed description of related prior art may obscure the gist of this specification, such detailed description will be omitted. Additionally, it should be noted that the attached drawings are intended only to facilitate understanding of the contents and concepts of this specification, and should not be interpreted as limiting the contents and concepts of this specification. The contents and concepts of this specification should be interpreted as extending to all modifications, equivalents, and substitutions in addition to the attached drawings.

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

[0031] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “A and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B or C.”

[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 as synonymous with “at least one of A and B.”

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

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

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

[0036] In the attached drawings, User Equipment (UE) is illustrated as an example, but the illustrated UE may also be referred to by terms such as Terminal or Mobile Equipment (ME). Furthermore, the UE may be a portable device such as a laptop, mobile phone, PDA, smartphone, multimedia device, etc., or a non-portable device such as a PC or vehicle-mounted device.

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

[0038] The term "base station" as used below generally refers to a fixed station that communicates with wireless devices, and can be used as a comprehensive term including 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] This specification describes embodiments using LTE systems, LTE-A systems and NR systems, but these embodiments may be applied to any communication system corresponding to 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 communication, commercialization and subsequent research for the next generation, namely 5th generation (so-called 5G) mobile communication, are also continuing.

[0042] Fifth-generation mobile communication, as defined by the International Telecommunication Union (ITU), refers to providing data transmission speeds of up to 20 Gbps and a perceived transmission speed of at least 100 Mbps anywhere. It is officially referred to as 'IMT-2020'.

[0043] The ITU presents three major usage scenarios, such as eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications).

[0044] URLLC concerns use scenarios requiring 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., latency of 1ms or less). Currently, the latency of 4G (LTE) is statistically 21-43ms (best 10%) and 33-75ms (median). This is insufficient to support services requiring latency of 1ms or less. Next, eMBB use scenarios concern use scenarios requiring mobile ultra-broadband.

[0045] In other words, 5th generation mobile communication systems support higher capacity than current 4G LTE, increase the density of mobile broadband users, and can support D2D (Device to Device), high stability, 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. New radio access technology (New RAT or NR) may be proposed for such 5G mobile communication.

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

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

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

[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 used by the physical layer but not carrying information originating from upper layers. For example, 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, refers to a signal of a specific waveform that is known to both 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 that carry information originating from upper layers, and uplink physical signals corresponding to resource elements used by the physical layer but that do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and physical random access channel (PRACH) are defined as uplink physical channels, and the demodulation reference signal (DMRS) for uplink control / data signals and the 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) each refers to a set of time-frequency resources or a set of resource elements carrying DCI (Downlink Control Information) / CFI (Control Format Indicator) / downlink ACK / NACK (ACKnowlegement / Negative ACK) / downlink data. Additionally, PUCCH (Physical Uplink Control Channel) / PUSCH (Physical Uplink Shared Channel) / PRACH (Physical Random Access Channel) each refers to a set of time-frequency resources or a set of resource elements carrying UCI (Uplink Control Information) / uplink data / random access signals.

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

[0052] As can be seen with reference to 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 communication. The eNB (20b) supports 4th generation mobile communication, i.e., LTE (Long Term Evolution).

[0053] Each base station (20a and 20b) provides communication services for a specific geographical area (generally called a cell) (20-1, 20-2, 20-3). A cell can be further divided into multiple areas (called sectors).

[0054] User Equipment (UE) typically belongs to a single cell, and the cell to which the UE belongs is called the serving cell. The base station that provides communication services to the serving cell is called the serving base station (serving BS). Since the wireless communication system is a cellular system, there exists another cell adjacent to the serving cell. The other cell adjacent to the serving cell is called the neighbor cell. The base station that provides communication services to the neighbor cell is called the neighbor base station (neighbor BS). The serving cell and neighbor cells are determined relatively to the UE.

[0055] In the following, the downlink refers to communication from the base station (20) to the UE (10), and the uplink refers to communication from the UE (10) to the base station (20). In the downlink, the transmitter may be part of the base station (20) and the receiver may be part of the UE (10). In the 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 classified into Frequency Division Duplex (FDD) and Time Division Duplex (TDD) methods. In the FDD method, uplink and downlink transmissions occupy different frequency bands. In the TDD method, uplink and downlink transmissions occupy the same frequency band and occur at different times. The channel response in the TDD method is practically reciprocal. This means that the downlink channel response and the uplink channel response are nearly identical within a given frequency range. Therefore, in a wireless communication system based on TDD, there is an advantage in that the downlink channel response can be derived from the uplink channel response. In the TDD method, since the entire frequency band is time-divided for uplink and downlink transmissions, downlink transmission by the base station and uplink transmission by the UE cannot be performed simultaneously. In a TDD system where uplink and downlink transmissions are separated by subframes, uplink and downlink transmissions are performed in different subframes.

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

[0058] In NR, uplink and downlink transmissions consist of frames. A radio frame has a length of 10 ms and is defined as two 5 ms half-frames (HF). A half-frame is defined as five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots within 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 standard 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) or SC-FDMA symbols (or DFT-s-OFDM symbols).

[0059] Support for various numerologies

[0060] In NR systems, as wireless communication technology develops, multiple numerologies may be provided to the terminal. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

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

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

[0063] For a standard CP, when the numerology index is denoted 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 numerology index is denoted 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, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) composed of the same number of symbols can be configured differently among the merged cells.

[0068] FIGS. 3a to 3c are exemplary diagrams illustrating 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, namely the EPC (Evolved Packet Core).

[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, that is, a 5G core network.

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

[0073] Referring to Fig. 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 spectra and unpaired spectra. A paired spectrum means that it includes two carrier spectra for downlink and uplink operations. For example, in a paired spectrum, 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 standard CP, one slot contains 14 symbols, whereas in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) 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 may be configured with up to N (e.g., 4) BWPs in both the downlink and uplink. Downlink or uplink transmission is performed through an active BWP, and at a given time, only one of the BWPs configured for the terminal may be active. In the resource grid, each element is referred to as a Resource Element (RE), and a single complex symbol may be mapped to it.

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

[0078] The transmission time interval (TTI) illustrated in Fig. 5 can be referred to as a subframe or slot for NR (or new RAT). The subframe (or slot) of Fig. 5 can be used in the TDD system of NR (or new RAT) to minimize data transmission delay. As illustrated in Fig. 5, the subframe (or slot) contains 14 symbols. The symbols at the beginning of the subframe (or slot) can be used for the downlink (DL) control channel, and the symbols at the end of the subframe (or slot) can be used for the uplink (UL) control channel. The remaining symbols can be used for DL ​​data transmission or UL data transmission. According to this subframe (or slot) structure, downlink transmission and uplink transmission can proceed sequentially within a single subframe (or slot). Thus, downlink data can be received within the subframe (or slot), and uplink acknowledgments (ACK / NACK) can be transmitted within that subframe (or slot).

[0079] The structure of such a subframe (or slot) can be called a self-contained subframe (or slot).

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

[0081] Using such a subframe (or slot) structure has the advantage of reducing the time required to retransmit data that has received errors, thereby minimizing the waiting time for final data transmission. In such a 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 may be set 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-complete structure in which a DL control channel, DL or UL data, a UL control channel, etc., can all be included within a single slot. For example, the first N symbols within the slot are used to transmit a DL control channel (hereinafter referred to as the DL control area), and the last M symbols within the slot may be used to transmit a UL control channel (hereinafter referred to as the UL control area). N and M are each integers greater than or equal to 0. The resource area (hereinafter referred to as the data area) located between the DL control area and the UL control area may be used for transmitting DL data or for transmitting UL data. 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 Area: (i) UL Data Area, (ii) UL Data Area + UL Control Area

[0091] PDCCH can be transmitted in the DL control area, and PDSCH can be transmitted in the DL data area. PUCCH can be transmitted in the UL control area, and PUSCH can be transmitted in the UL data area. Downlink Control Information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted in PDCCH. Uplink Control Information (UCI), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, Channel State Information (CSI), and Scheduling Request (SR), can be transmitted in PUCCH. GP provides a time gap during the process in which the base station and the terminal switch from transmit mode to receive mode, or from receive mode to transmit mode. Within a subframe, some symbols at the point of transition from DL to UL can be set as GP.

[0092] FIGS. 7a and 7b show examples of connectivity topologies for ambient Internet of Things (A-IoT / AIoT) networks and devices.

[0093] An Ambient IoT (or ambient power-enabled Internet of Things, A-IoT / AIoT) device is an IoT device powered by energy harvesting, which has no battery or possesses limited energy storage capability (e.g., the use of capacitors). For the sake of convenience of explanation, AIoT devices may be referred to as "devices" below. This is for the sake of convenience of explanation and may be changed to any other name. Energy is provided through the energy harvesting of radio waves, light, motion, heat, or other suitable power sources. Energy harvesting may be continuous or may occur incidentally (e.g., by vibration). Therefore, it cannot be assumed that an AIoT device always possesses power for data transmission and reception. AIoT devices need to be designed to have lower complexity, smaller size, reduced capacity, and lower power consumption than previously defined 3GPP IoT terminals / devices (e.g., NB-IoT (Narrowband Internet of Things) / eMTC (enhanced Machine Type Communication) devices). AIoT devices can be designed to have a long lifespan of more than 10 years without maintenance. This allows them to be used as replacements for existing 3GPP IoT devices or to support various use cases (e.g., inventory, sensors, positioning, commands) that existing 3GPP IoT devices cannot support. Functions and procedures to support Ambient IoT use cases can be defined as AIoT services (e.g., inventory services, command services).For example, the primary purpose of the inventory service is to search for what goods (e.g., boxes, containers, packages, tools) are present in a specific area. When a request is transmitted from a network within a specific area, AIoT devices attached to these goods report identifiers associated with the goods, and other information such as status, measurement results, and / or location may be added by AIoT devices and / or AIoT RAN (Radio Access Network) / Readers. Through the inventory service, AIoT devices within a certain range of a specific reader can be discovered / tracked. The command service represents a procedure for executing commands on AIoT devices within a specific area. Such commands may include read, write, disable, and / or enable services as follows.

[0094] - Read: Request to read information from an AIoT device

[0095] - Write: Request to write information to an AIoT device

[0096] - Disable: A request to permanently or temporarily disable the RF transmission function of an AIoT device.

[0097] -Enable: Request to enable a temporarily disabled AIoT Device

[0098] A connectivity topology such as that shown in FIGS. 7a and 7b can be defined for ambient IoT networks and devices. In FIG. 7a, BS represents the Ambient IoT Radio Access Network (RAN). The AIoT RAN represents a node that performs a specific function for AIoT (e.g., RAN node function: A function that contains, e.g., the control of the AIoT radio resources used towards the AIoT device) as part of the functional separation between the radio network (RAN) and the core network (CN). The AIoT RAN can service one or more AIoT readers. An AIoT reader represents a reader that terminates the AIoT device and the AIoT protocol. For convenience of explanation, the node may be referred to as the AIoT RAN (or AIoT reader) below. This is for the convenience of explanation and may be referred to by any other name, such as AIoT RAN reader, AIoT base station, or AIoT BS reader.

[0099] In all these topologies, carriers may be provided to the AIoT device from other nodes inside or outside the topology. The links in each topology may be bidirectional or unidirectional. In FIG. 7a, the AIoT device communicates directly and bidirectionally with the base station. Communication between the base station and the AIoT device may include AIoT data and / or signaling. The base station transmitting to the AIoT device and the base station receiving from the AIoT device may be the same base station or different base stations.

[0100] In FIG. 7b, bidirectional communication is performed between the AIoT device and the AIoT RAN through an intermediate node, an assisting node, and an assisting UE. In this topology, the intermediate node, the assisting node, and the assisting UE can be a relay, an IAB (Integrated Access and Backhaul), a UE, a repeater, etc., capable of ambient IoT functions / services. For convenience of explanation, the node is referred to as a UE reader below. This is for convenience of explanation and may be referred to by any other name, such as UE connected / associated with AIoT enabled RAN, AIoT enabled RAN / reader, AIoT reader, or AIoT UE reader.

[0101] Figure 8 shows an example of a procedure for an A-IoT inventory service.

[0102] Referring to FIG. 8, a procedure for an AIoT inventory service is described below.

[0103] 1a. The A-IoT CN sends an Inventory request message to the A-IoT RAN node.

[0104] 1b. The A-IoT RAN node allocates and coordinates the usage of A-IoT radio resources.

[0105] 2. The A-IoT RAN node sends an inventory response message to the A-IoT CN.

[0106] 3. The A-IoT RAN node performs the inventory procedure towards the A-IoT device(s) over the A-IoT radio interface.

[0107] 4a / 4b. After receiving the inventory result from the A-IoT device(s), the A-IoT RAN node may send one or multiple inventory reports to the A-IoT CN, including the received inventory result.

[0108] Figure 9 shows an example of an Access Stratum (AS) procedure between an A-IoT device and a reader.

[0109] Referring to FIG. 9, the overall Access Stratum (AS) procedure between an ambient IoT (A-IoT) device and a reader is described below.

[0110] Step A: A-IoT Paging (S901)

[0111] Based on the service request, the reader sends the A-IoT paging message indicating the device(s) that need to respond. Here, the A-IoT paging message can be used interchangeably with the initial trigger message.

[0112] Step B: D2R (Device-to-Reader) (Device ID) data transmission (S902~S903)

[0113] An A-IoT device triggered by paging performs the device ID transmission to the reader either via the A-IoT random access procedure or without using the A-IoT random access procedure. Subsequently, D2R data is transmitted to the reader.

[0114] Step C1: R2D (Reader-to-Device) data transfer (S904)

[0115] Perform possible R2D data transmission. (For example, for sending the command)

[0116] Step C2: D2R data transmission (S905)

[0117] Perform possible D2R data transmission. (For example, the corresponding response to the command)

[0118] As such, although a high-level procedure for providing inventory services or command services was defined in a topology like Fig. 7b, a specific signaling method between a UE leader (A-IoT enabled UE) and a base station (AIoT enabled gNB) for supporting the AIoT service was not provided, so the AIoT service could not be effectively implemented.

[0119] In providing AIoT technology to support lower complexity, smaller size, reduced capacity, and lower power consumption compared to existing 3GPP LPWA (Low-Power Wide-Area) IoT, specific signaling methods between a UE leader (A-IoT enabled UE) and a base station (AIoT enabled gNB) for supporting AIoT services are not provided.

[0120] The present invention, devised to solve these problems, proposes a method and apparatus for effectively providing signaling between a UE reader (A-IoT enabled UE) and a base station (AIoT enabled gNB) by considering AIoT characteristics. Additionally, the present invention proposes a method for configuring wireless resources of the terminal.

[0121] Hereinafter, a method for transmitting and receiving data based on 5GS (Fifth Generation System) / NR technology will be described in detail. However, this is for the convenience of explanation, and the present invention may also be applied through any system or wireless access technology (e.g., 6G). The embodiments described in the present invention may refer to information elements and operation details specified in NR / 5GS standards (e.g., NR MAC standard TS 38.321, NR RRC standard TS 38.331, system structure standard TS 23.501, etc.). Even if the definition of the relevant information elements and related terminal operation details are not described in this specification, the relevant details specified in known standard standards may be included in the present invention.

[0122] 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)) via the corresponding signaling. Alternatively, any functions may be combined / combined to be defined as the corresponding terminal capability and transmitted by the terminal to a base station / core network entity via the corresponding signaling. Here, AIoTF (Ambient IoT Function or Ambient IoT Network Function) represents a network function for providing management and control of AIoT services and AIoT operations. For the convenience of explanation, this may be changed to any other name. AIoTF can select an AIoT RAN node (or UE reader). AIoTF can receive AIoT service requests from application functions / application servers and trigger AIoT RAN / reader (or AIoT UE reader) to perform AIoT service operations with AIoT devices. AIoTF can collect the results of AIoT service operations from AIoT RAN nodes (or AIoT UE readers) and transmit them to application functions / application servers.

[0123] Ambient IoT devices may be defined by being classified into at least one device type / category according to at least one supported capability (or a combination of at least one capability). For example, based on energy storage capacity, they may be classified into devices with no storage space, 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, E2 > E1). As another example, they may be classified into a device without energy storage and without independent signal generation / amplification (e.g., backscatter transmission) (hereinafter referred to as Device A for convenience of explanation), a device with an energy storage device and without independent signal generation (e.g., backscatter transmission) (hereinafter referred to as Device B for convenience of explanation), the use of stored energy in Device B may include amplification of reflected signals, and a device with an energy storage device and independent signal generation (e.g., active RF components for transmission) (hereinafter referred to as Device C for convenience of explanation).As another example, the device may be classified into a device having ~1 μW peak power consumption, energy storage, and no amplification in both the DL and UL within the device, and whose uplink transmission is backscattered on an externally provided carrier wave (hereinafter referred to as Device 1 for convenience of explanation), a device having ≤ a few hundred μW peak power consumption, energy storage, and whose uplink transmission is backscattered on an externally provided carrier wave, and whose uplink transmission is capable of amplification in both the DL and UL within the device (hereinafter referred to as Device 2a for convenience of explanation), and a device having ≤ a few hundred μW peak power consumption, energy storage, and whose uplink transmission is generated internally by the device, and whose uplink transmission is capable of amplification in both the DL and UL within the device (hereinafter referred to as Device 2b for convenience of explanation).

[0124] An AIoT RAN / reader / base station / UE-reader or AIoTF may transmit / instruct / configure information / messages to an AIoT device to instruct the enable / activation / allow / support / configuration of any function or combination of functions described below. For example, this may be transmitted from the AIoTF to the AIoT device via an AIoT NAS message / container. Alternatively, it may be transmitted from the AIoT RAN / reader / base station / UE-reader to the AIoT device via a dedicated MAC PDU.

[0125] An AIoT RAN / reader / base station / UE-reader or AIoTF may transmit / instruct / configure information / messages to an AIoT device to disable / deactivate / restrict / control any function or combination of functions described below. For example, it may instruct a prohibit / suspend / deactivate timer for the operation of the relevant function. The timer may be started / restarted with the initiation of the relevant function or before and after the initiation of the relevant function. While the timer is running, the device may disable / deactivate / restrict / control the relevant function to prevent it from being initiated / executed.

[0126] The embodiments and functions described below may be performed individually and independently. Alternatively, the embodiments and functions described below may be performed in any combination or combination, and it is obvious that this is also included within the scope of the present invention.

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

[0128] In the following description, the physical channel for R2D (Reader to Device) data transmission is referred to as PRDCH (Physical Reader to Device CHannel), the physical channel for D2R (Device to Reader) 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 interface / link (e.g., AIoT Radio interface). This is for the convenience of explanation and may be replaced with any other name. In the following, RD / DR link resource / scheduling information includes: start time / subframe / slot / symbol / reference time / arbitrary AIoT device unit time (for RD / DR link communication); start time / subframe / slot / symbol / reference time / arbitrary AIoT device unit time offset (for RD / DR link communication); start time / subframe / slot / symbol based on a specific reference time / point in time (e.g., reception of R2D data, start of reception of R2D data, end of reception of R2D data, or a specific reference time of the serving base station / cell servicing the said reader); start time / subframe / slot / symbol offset based on a specific reference time (for RD / DR link communication); duration (RD / DR link communication); transmission occlusion (RD / DR link); transmission period (RD / DR link); available time slot; available time slot range; and maximum time slot. It may include at least one of the following information: uplink / downlink start time / subframe / slot / symbol of an associated base station / auxiliary terminal for indicating the RD link start time, start time / subframe / slot / symbol offset, RD link frequency domain information, RD link subchannel number / index, DR link frequency offset, RD / DR link MCS, RD / DR link transmission block size, communication range / Range, location information, priority, number of RD / DR link retransmissions, (RD / DR link communication) validity period / time and validity criteria.

[0129] Storage of relevant AIoT wireless interface parameters and / or AIoT service request context during the signaling process between the UE reader and the base station

[0130] As shown in Fig. 8, 1a, a core network (e.g., AIoTF) can transmit an AIoT service request (e.g., inventory or command) to a base station (AIoT enabled gNB). The service request can be transmitted via a service-based interface between the AIoTF and the AMF. The service request can be transmitted via NGAP (NG Application Protocol) messages between the AMF and the base station (AIoT enabled gNB).

[0131] The base station may allocate AIoT wireless resources. The base station may transmit information regarding the AIoT wireless resources allocated by the base station to any neighboring base station. The AIoT wireless resources / resource information may include configured AIoT grant / resource configuration information.

[0132] A UE reader (AIoT-enabled UE) can receive a Radio Resource Control (RRC) message from a base station directing a corresponding AIoT service request (e.g., inventory or command).

[0133] When a UE reader receives an RRC message from a base station directing a corresponding AIoT service request (e.g., inventory or command), the UE reader can store information related to the AIoT service request contained in the RRC message in the corresponding terminal variable.

[0134] For example, a UE reader can store the relevant information from an RRC layer / entity in an RRC terminal variable.

[0135] As another example, the UE reader can store the relevant information in the AIoT context (or AIoT device context) (at the RRC layer / entity, the RRC upper layer, or the AIoT UE reader control protocol layer / entity).

[0136] As another example, the information may include AIoT wireless interface parameters and / or AIoT service request information / context for one or more AIoT device(s).

[0137] The AIoT wireless interface parameters and / or AIoT service request context may include at least one of the following: AIoT device identification information, security parameters, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), information for selecting an AIoT RAN / reader (or UE reader), the expected / expected / estimated number of target AIoT devices for the service, and the expected / expected / estimated size of the D2R response message for the service request. The AIoT wireless interface parameters and / or AIoT service request context may include at least one of dedicated AIoT grants / resources, configured AIoT grants / resource configuration information, and QoS / wireless resource / transmission parameters (e.g., QoS indicator, latency, positioning accuracy, connection density, device density, maximum message size, maximum bit rate, range, maximum distance, device power consumption, latency budget, power budget, number of repetitions, repetition period, number of retransmissions, valid time / valid period / valid period (of the relevant AIoT grants / resources), valid time / valid period / valid period device type (of the relevant AIoT service request), etc.).

[0138] The UE reader can send an RRC message to the base station instructing it to respond to or confirm the corresponding AIoT service request (e.g., inventory or command).

[0139] The RRC message may include at least one of the following: AIoT device identification information, security parameters, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), and capability information regarding the AIoT function / service of the terminal.

[0140] Signaling information between the core network and the UE reader

[0141] A core network (e.g., AIoTF) can transmit user plane data (or AIoT UE reader control messages) that direct an AIoT service request (e.g., inventory or command) to a UE reader (AIoT enabled UE).

[0142] The UE reader can store information related to the corresponding AIoT service request in the corresponding AIoT context (or AIoT device context) (at the RRC layer / entity, RRC upper layer, or AIoT UE reader control protocol layer / entity). Information related to AIoT service requests includes AIoT device identification information, security parameters, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), information for selecting an AIoT RAN / reader (or UE reader), the expected / estimated / projected number of target AIoT devices for the service, the expected / estimated / projected size of the D2R response message for the service request, assistance information for configuring dedicated AIoT grants / resources, assistance information for configuring configured AIoT grants / resources, and QoS / radio resource / transmission parameters (e.g., QoS indicator, latency, positioning accuracy, connection density, device density, maximum message size, maximum bit rate, range, maximum distance, device power consumption, latency budget, power budget, number of iterations, iteration period, number of retransmissions, validity period / validity time (of the relevant AIoT grant / resource), validity period / validity time (of the relevant AIoT service request), and device type. It may include at least one piece of information among etc.

[0143] A UE reader may transmit at least one piece of information received via user plane data from a core network (e.g., AIoTF) to a base station (AIoT enabled gNB). Through such information, the UE reader may transmit dedicated AIoT grants / resources for R2D / D2R message / data transmission / reception with the relevant AIoT device(s) via the AIoT wireless interface, and assistance information for requesting configured AIoT grants / resources. Such information may be indicated via RRC messages / MAC-CE (Medium Access Control-Control Element) / UCI (Uplink Control Information). Upon receiving such information, the base station may configure / instruct / assign dedicated AIoT grants / resources and / or configured AIoT grants / resources to the terminal. Such information may be indicated via RRC messages / MAC-CE / DCI (Downlink Control Information).

[0144] The AIoT UE Leader control protocol layer / entity is a protocol layer / entity located above the PDU (Protocol Data Unit) layer / IP (Internet Protocol) transport layer between the UE Leader and the AIoTF, and enables the transmission of AIoT service request messages / data (e.g., inventory or commands) between the AIoTF and the UE Leader through a PDU session between the UE Leader (AIoT-enabled UE) and the UPF (User Plane Function) that services the UE Leader.

[0145] The corresponding user plane data (or AIoT UE reader control message) can be transmitted via a PDU session between a UE reader (AIoT enabled UE) and a UPF that services the UE reader. To this end, the UE reader can establish a PDU session associated with a specific DNN (Data Network Name) / S-NSSAI (Single-Network Slice Selection Assistance Information). By receiving AIoT service request messages / data transmitted from the core network via the user plane, the UE reader can prevent overhead / overload associated with control plane message processing between the core network and the base station (AIoT enabled gNB) and / or between the base station (AIoT enabled gNB) and the terminal acting as the UE reader.

[0146] Definition of wireless bearer signaling between UE reader and base station

[0147] As shown in Fig. 8, 1a, a core network (e.g., AIoTF) can transmit an AIoT service request (e.g., inventory or command) to a base station (AIoT enabled gNB). The service request can be transmitted via a service-based interface between the AIoTF and the AMF. The service request can be transmitted via an NGAP message between the AMF and the base station (AIoT enabled gNB).

[0148] The base station may allocate AIoT wireless resources. The base station may transmit information regarding the AIoT wireless resources allocated by the base station to any neighboring base station. The AIoT wireless resources / resource information may include configured AIoT grant / resource configuration information.

[0149] A UE reader (AIoT-enabled UE) can receive an RRC message from the base station directing the corresponding AIoT service request (e.g., inventory or command).

[0150] For example, a Signaling Radio Bearer (SRB) can be defined and configured in the UE reader for transmitting an RRC message to instruct an AIoT service request (e.g., inventory or command) and / or an RRC message to instruct a response / acknowledgment to said AIoT service request (e.g., inventory or command). AIoT service requests may be provided to massive AIoT devices. Problems may occur during the data transmission and reception process to the terminal due to an increase in the control plane data (or resulting overload). These characteristics may be taken into account. For example, an SRB with a lower priority than the existing SRB (e.g., SRB0 and / or SRB1) can be defined and used between the UE reader and the base station. That SRB can be configured by the network after (only) AS security activation. The default SRB configuration for that SRB may have a priority value within the corresponding logical channel configuration that is greater than the value (1) for SRB1. The default SRB configuration for the corresponding SRB can have a priority value within the corresponding logical channel configuration that is greater than (or equal to) the value for SRB2 (3).

[0151] A corresponding SRB-based RRC message may be defined. The corresponding RRC message may include information elements / containers for an AIoT service request and / or AIoT wireless interface parameters / information elements / containers for it.

[0152] As another example, one or more existing SRBs (e.g., SRB2, SRB3, SRB4, or SRB5) having a lower priority than existing SRB0 and / or SRB1 may be used to transmit RRC messages to direct an AIoT service request (e.g., inventory or command) and / or RRC messages to direct a response / acknowledgment to said AIoT service request (e.g., inventory or command).

[0153] RRC messages between UE reader and base station

[0154] As another example, an RRC message directing an inventory request can use an RRC reconfiguration message. An RRC message directing a response or acknowledgment to that inventory request can be directed via an RRC reconfiguration complete message. RRC reconfiguration messages are used to modify the RRC connection.

[0155] RRC messages directing command requests may use RRC reconfiguration messages. RRC messages directing a response / acknowledgment to the corresponding inventory request may be directed via RRC reconfiguration completion messages.

[0156] When a base station modifies an RRC connection to a UE leader, it may perform an inventory request and / or response / confirmation by including information elements related to the relevant AIoT service / procedure within an RRC reconfiguration / reconfiguration completion message. For example, the RRC reconfiguration message and / or the RRC reconfiguration completion message may include at least one of the following: AIoT device identification information, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), information for selecting an AIoT RAN / leader, the expected / expected / estimated number of target AIoT devices for the service, and the expected / expected / estimated size of the D2R response message for the service request. And / or the RRC message may include AIoT wireless interface parameters / information elements / containers.

[0157] As another example, RRC messages directing inventory / command requests can use Downlink Information Transfer messages. RRC messages directing responses / acknowledgments to such inventory / command requests can be directed via Uplink Information Transfer messages. DL / UL Information Transfer messages are used to transfer NAS-specific information between the core network and the terminal. Inventory / command requests and / or responses / acknowledgments to them are information transmitted and received between the core network and the UE reader to request, respond to, or acknowledge AIoT service procedures for the AIoT device. In the case of AIoT service procedures, NAS (Non-Access Stratum) layer / protocol operations are performed between the AIoT device and the AIoTF. Therefore, there are no dedicated NAS messages for AIoT service procedures to be transmitted and received between the base station and the UE reader. If the AIoTF is connected to the base station via a direct interface / Service-Based Interface (SBI) (or AIoT reader control protocol), the information included in the RRC message between the base station and the UE reader may be information received via an interface (NxAP) / SBI-based message (or AIoT reader control protocol message) between the AIoTF and the base station for AIoT service procedures. If the AIoTF is connected to the base station via an AMF, the information included in the RRC message between the base station and the UE reader may be information received via an NGAP message between the AMF and the base station for AIoT service procedures. In this way, DL / UL information transfer messages can be used to transmit and receive Nx / NG-related information.The DL / UL information transfer message may include at least one of the following: AIoT device identification information, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), information for selecting an AIoT RAN / reader, the expected / expected / estimated number of target AIoT devices for the service, and the expected / expected / estimated size of the D2R response message for the service request. And / or the RRC message may include AIoT wireless interface parameters / information elements / containers.

[0158] As another example, the message may define new DL RRC messages and UL RRC messages for transmitting and receiving Nx / NG-related information. The RRC message may represent a new message distinct from the aforementioned RRC reconstruction / reconstruction completion and DL / UL information transfer messages. The RRC message may include at least one of the following information: AIoT device identification information, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), information for selecting an AIoT RAN / reader, the expected / expected / estimated number of target AIoT devices for the service, and the expected / expected / estimated size of the D2R response message for the service request. And / or the RRC message may include AIoT wireless interface parameters / information elements / containers.

[0159] As another example, when a UE reader receives user plane data (or an AIoT UE reader control message) directing an AIoT service request (e.g., inventory or command), the UE reader can store information related to the AIoT service request contained in the user plane data in the corresponding terminal variable. The UE reader can set up / store the information in the corresponding AIoT device context.

[0160] The AIoT device context may include at least one of the following: AIoT device identification information, AIoT service type information (e.g., inventory or command (e.g., read, write, enable, disable)), information for selecting an AIoT RAN / reader, the expected / expected / estimated number of target AIoT devices for the service, and the expected / expected / estimated size of a D2R response message for the service request.

[0161] The UE reader can transmit user plane data (or AIoT UE reader control messages) instructing the corresponding core network to respond to / acknowledge the corresponding AIoT service request (e.g., inventory or command).

[0162] When the UE reader transmits user plane data (or AIoT UE reader control message) instructing the response / acknowledgment to the corresponding AIoT service request (e.g., inventory or command) to the corresponding core network, the UE reader can release / remove / delete / discard the corresponding AIoT device context.

[0163] Other embodiments of the present invention will be described below.

[0164] AIoT device identification information may represent AIoT device identification information included in NxAP (or an application protocol above the service-based interface protocol between AIoTF and AIoT RAN or the service-based interface protocol between AIoTF and AIoT RAN / leader) / NGAP messages between AIoTF and AIoT RAN, or AIoT device identification information used in the NAS (Non-Access Stratum) layer / entity of AIoTF and AIoT devices. The information may represent at least one of the following: a full permanent Ambient IoT Device Identifier configured in an AIoT device; a part of an Ambient IoT Device Identifier; a full permanent AIoT Device Identifier that has undergone security processing / verification (e.g., cyphering / encryption, integrity protection, Message Authentication Code, hash function, and / or device authentication); a part of a permanent AIoT Device Identifier that has undergone security processing / verification; a code that is calculated / generated / derived / determined through security processing / verification for the AIoT device (or full / partial permanent AIoT Device Identifier); a code associated with the AIoT device (or full / partial permanent AIoT Device Identifier); and filtering / mask information for determining / extracting AIoT device identification information. The permanent AIoT Device Identifier may be assigned by an operator or a third party. A permanent AIoT device identifier may include a network identifier (for example, MCC (Mobile Country Code) + MNC (Mobile Network Code) and / or NID (Network Identifier)) or one of the information used to identify a third-party operator.A permanent AIoT device identifier may include information used to distinguish different AIoT devices within information used to identify a network identifier (e.g., MCC+MNC and / or NID) or a third-party operator (e.g., EPC (Electronic Product Code) or other local / internal identification information). In any signaling process, one or more AIoT device identification information may be used for a single AIoT device. For example, information used to identify a network identifier (e.g., MCC+MNC and / or NID) or a third-party operator may be used as the first AIoT device identification information, and information used to distinguish different AIoT devices within information used to identify a network identifier (e.g., MCC+MNC and / or NID) or a third-party operator (e.g., EPC (Electronic Product Code), other local / internal identification information) may be used as the second AIoT device identification information. At least one of the first AIoT device identification information and / or the second AIoT device identification information (or at least one of the whole / part of the first AIoT device identification information and the whole / part of the second AIoT device identification information) may be transmitted after security processing / verification. (For example, the first AIoT device identification information (plaintext), the second AIoT device identification information (ciphertext), or vice versa).

[0165] The security parameter may represent at least one of the following information: a key, key identification information, fresh value, counter, token, validation value, random parameter, algorithm, and / or device credential / profile used for security processing / verification (e.g., cyphering / encryption, integrity protection, Message Authentication Code, hash function, device authentication) for a full / partially persistent AIoT device identifier in an AIoTF and / or AIoT device.

[0166] The wireless resources used in the AIoT wireless interface between the AIoT device and the UE reader need to be controlled by the network / base station. For example, to perform AIoT AS procedures / operations between the UE reader and the AIoT device, the UE reader may receive scheduling / wireless resource information from the corresponding base station for transmitting R2D messages to the AIoT device and / or receiving D2R messages from the AIoT device. Using the AIoT wireless resources included in the scheduling / wireless resource information (or by determining / selecting specific / partial scheduling / wireless resources among the scheduling / wireless resource information, or by using scheduling / wireless resources generated / re-generated by such scheduling / wireless resources (or scheduling allocations / grants)), the UE reader and the AIoT device may perform R2D / D2R message / data transmission / reception. A UE reader / AIoT device (or a MAC layer / entity of a UE reader / AIoT device) may direct the corresponding MAC PDU and / or the corresponding scheduling / radio resources to a physical layer / physical layer entity.

[0167] Based on scheduling / radio resource information received from the relevant base station, the R2D message / data transmitted by the UE reader to the AIoT device may include scheduling / radio resource information for the relevant / subsequent R2D message and / or subsequent D2R message(s). For example, such information may be included through control information / fields within PRDCH control information or the MAC PDU included in the PRDCH.

[0168] For the sake of convenience of explanation, information configured, allocated, or directed to schedule PRDCH (R2D message / data) transmission / reception and / or PDRCH (D2R message / data) transmission / reception used by a base station for AIoT AS procedures / operations between a UE reader and AIoT device(s) is referred to as an AIoT grant. This is for the sake of convenience of explanation and may be replaced with any other name such as PRDCH, PDRCH, R2D, D2R allocation, scheduling grant, AIoT interface grant, scheduling information, or radio resource. An AIoT grant may include at least one piece of information among PRDCH / PDRCH / R2D / D2R frequency domain resources (transmission / occupied bandwidth), time domain resources, an ID associated with a device intended for PRDCH / R2D reception (e.g., an AS ID (Access Stratum Identifier)), and a modulation / coding format. Here, the AS ID may be a random ID included in the first D2R message (or AIoT MSG1) or an ID assigned to the device by a reader. The corresponding AS ID may be included in a subsequent R2D message containing such information, so that the device can distinguish and use messages sent to it via the corresponding AS ID.

[0169] AIoT grants / radio resources for a UE leader can be configured, directed, or allocated to the terminal by the base station via dedicated signaling. The UE leader may perform AIoT procedures on the AIoT radio interface between the leader and the device only when the said AIoT grants / radio resources are valid within the corresponding base station cell. For example, the leader may transmit PRDCH (R2D message / data) to the device. The device may transmit D2R message / data to the leader. (The leader may receive D2R message / data from the device.)

[0170] For example, when a terminal receives a dedicated radio resource from a base station, it can use the radio resource to perform an AIoT procedure on the AIoT radio interface between the reader and the device. The base station can allocate / configure / instruct AIoT grant / radio resources to a terminal acting as a UE reader using at least one of RRC signaling, MAC CE, and DCI signaling.

[0171] For example, in response to a request from a UE leader (via RRC / MAC-CE / UCI), the base station may configure / assign AIoT grants / radio resources to the UE leader. And / or based on an AIoT service request from the core network, the base station may configure / assign AIoT radio resources to the UE leader.

[0172] As another example, AIoT grants / radio resources allocated / configured / instructed by a base station to a UE leader for an RRC-connected terminal may have validity period / validation time / valid cycle information for said grants / radio resources. This validity period / validation time / valid cycle information for said AIoT grants / radio resources may be included in the corresponding signaling and indicated together when the base station allocates / configures / instructs said AIoT grants / radio resources to the UE leader via RRC / MAC-CE / DCI.

[0173] As another example, validity period, validity time, and validity cycle information for the relevant AIoT grant / wireless resource can be configured or instructed to the UE reader via RRC. The UE reader can store this information in the corresponding terminal variable.

[0174] When a base station allocates, configures, or directs a radio resource to a UE reader via MAC-CE / DCI, the terminal may perform AIoT procedures on the AIoT radio interface between the reader and the device using the AIoT grant / radio resource for the stored validity period / valid time / valid cycle for the radio resource. The terminal may store the AIoT grant / radio resource in a terminal variable. And / or may start a timer to limit the validity period / valid time / valid cycle for the AIoT grant / radio resource. The terminal may consider the AIoT grant / radio resource to be valid for the validity period / valid time / valid cycle. When the timer expires, the (stored) AIoT grant / radio resource may be released / removed / deleted / discarded.

[0175] A terminal operating as a UE reader may be allocated semi-static AIoT grants / radio resources by a base station on the AIoT wireless interface. For convenience of explanation, semi-static radio resources on the AIoT wireless interface are referred to as configured AIoT resources. This designation is for convenience of explanation and may be replaced with any other name, such as configured AIoT grant or configured AIoT allocation. The configured AIoT resource configuration information may include at least one of the following information as radio parameters required for R2D / D2R message / data transmission on the wireless interface between the AIoT reader (or UE reader) and the AIoT device.

[0176] - Configured AIoT Resource Index: An identifier for identifying / distinguishing the configured AIoT resource configuration (or the configured AIoT resource) in an AIoT wireless interface. A single configured AIoT resource configuration may be used by the terminal for R2D / D2R data transmission / reception to / from one or more AIoT device(s).

[0177] - Period: The period of the configured AIoT resource. The period can be set to the value of the period included in ConfiguredGrantConfig to be linked to the PUSCH timing of the terminal (for example, The following periodicities are supported depending on the configured subcarrier spacing [symbols]:15 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, 640} ...).

[0178] Alternatively, the period may be set to a value of the period included in SPS-Config (e.g., 10ms, ..., 640ms) to be linked to the PDSCH timing of the terminal.

[0179] Alternatively, the period may be specified in milliseconds. The period may include values ​​greater than the period values ​​included in SPS-config (e.g., 10ms, ..., 640ms) (e.g., 100ms, ..., 1000ms).

[0180] A single configured AIoT resource configuration can specify the cycle of an AIoT grant / radio resource for R2D / D2R data transmission to one or more AIoT device(s) through a single cycle information. Alternatively, a single configured AIoT resource configuration can specify the cycle of each radio resource for R2D / D2R data transmission to multiple AIoT devices through multiple cycle information.

[0181] - Time Reference SFN (System Frame Number): An SFN used to determine the offset of a resource in the time domain. A configured AIoT resource configuration may indicate the relevant information through one or more corresponding parameters for R2D / D2R data transmission to one or more AIoT device(s).

[0182] (If used in conjunction with the timing of the terminal's PUSCH / UL) the terminal (UE reader) may be made to use the closest (uplink) SFN with the indicated number preceding the reception of the configured AIoT resource configuration.

[0183] Alternatively, (if used in conjunction with the timing of the terminal's PDSCH / DL), the terminal (UE reader) may be configured to use the closest (downlink) SFN with the indicated number preceding the reception of the configured AIoT resource configuration.

[0184] Alternatively, (if used in conjunction with the timing of the terminal's PDSCH / DL) the time reference SFN (System Frame Number) parameter may not be used. And / or the (PDSCH / PDCCH / DL) start / start time SFN (e.g., SFNstart time) parameter associated with the first transmission of the PRDCH / PDRCH where the configured AIoT resource is initialized / re-initialized may be specified.

[0185] Alternatively, (for the AIoT wireless interface (R2D / D2R)) the terminal (UE reader) may use the AIoT SFN closest to the specified number before receiving the configured AIoT resource.

[0186] Alternatively, (for AIoT wireless interfaces (R2D / D2R)) the terminal (UE reader) may be made to use the first (logical) AIoT scheduling unit time / resource of the wireless resource after the start time of the AIoT SFN closest to the indicated number before receiving the configured AIoT resource.

[0187] Here, the AIoT SFN represents the radio frame number on the corresponding AIoT interface. The corresponding AIoT radio frame may have a time interval (10ms) similar to LTE / NR. (Alternatively, the corresponding AIoT radio frame may have a different time interval than LTE / NR. The AIoT radio frame may be configured to have a specific unit time value (ms).) For convenience of explanation, the AIoT radio frame unit time (or the corresponding unit time number) is referred to as the first unit time below. Here, the AIoT scheduling unit time / resource represents the unit time / resource (or the corresponding number / ID / index) scheduled on the AIoT interface, such as a slot in NR or a subframe in LTE. For convenience of explanation, the AIoT scheduling unit time (or the corresponding unit time number / ID / index) is referred to as the second unit time below.

[0188] - Time Domain Offset: Offset for a resource in the time domain,

[0189] (If used in conjunction with timing for base station / terminal PUSCH / UL) Offset of a resource with respect to (uplink) timeReferenceSFN in time domain

[0190] Or, (if used in conjunction with timing for base station / terminal PDSCH / DL) Offset of a resource with respect to (downlink) SFN = timeReferenceSFN in time domain

[0191] Alternatively, (if used in conjunction with timing for base station / terminal PDSCH / DL) the time domain offset parameter may not be used.

[0192] Or, (for AIoT wireless interface (R2D / D2R)) in the time domain, AIoT SFN = offset of the resource for the time reference SFN

[0193] Or, (for AIoT wireless interfaces (R2D / D2R) the first AIoT scheduling unit time / resource used by the terminal in the time domain (after the start time of the AIoT SFN)

[0194] Or, (for AIoT wireless interfaces (R2D / D2R)) offset for the corresponding AIoT SFN in the time domain and / or offset for the corresponding AIoT scheduling unit time / resource

[0195] - Time Domain Resources / Time Domain Allocations / Time Ranges: AIoT resources / allocations / time units configured in the time domain,

[0196] (If used in conjunction with the timing for the terminal's PUSCH / UL, the start symbol and length (startSymbolAndLength) (i.e., SLIV(Start and Length Indicator Value) in TS 38.214), or the start symbol (S), for reference, SLIV indicates the start symbol (or start symbol index) and the length of consecutive symbols.

[0197] Alternatively, it may be indicated by at least one of the (PDSCH / PDCCH / DL) start / start time slot (e.g., Slotstart time), the length of consecutive slots, the start time, and the duration (in ms) (if used in conjunction with the timing for the PDSCH / DL of the terminal, associated with the first transmission of the PRDCH / PDRCH in which the configured AIoT resource is initialized / re-initialized).

[0198] Or, (for AIoT wireless interfaces (R2D / D2R)) start time / scheduling unit time / second unit time and duration (days, e.g., ms or number of consecutive unit times)

[0199] Alternatively, the time domain resource / time domain allocation / time range may represent a time domain resource / time domain allocation / time range allocated for PRDCH / PDRCH / R2D / D2R message / data transmission on the AIoT wireless interface.

[0200] Alternatively, the parameter may be linked to time domain resources / time domain allocations for PRDCH / PDRCH on the AIoT wireless interface.

[0201] Alternatively, it can indicate the starting resource index and length of the initial PDRCH / PRDCH transmission of the configured AIoT resource.

[0202] Alternatively, it can indicate the temporal resource location of a configured AIoT resource. The corresponding index can be provided coded as a value indicating the temporal resource.

[0203] - If the timing of the AIoT wireless resource is used in conjunction with the timing of the terminal's PUSCH / UL and / or PDSCH / DL, information for indicating the linkage / relationship between the said timing and the timing of the AIoT wireless resource, for example, the relationship between the time of a wireless frame (e.g., SFN) on the Uu interface and a first unit time, the relationship between a slot on the Uu interface and a second unit time, or a code value for indicating said relationship.

[0204] - R2D / D2R (or PRDCH / PDRCH) distinction information: Information to indicate whether the radio resource is used for PRDCH (R2D message / data) transmission (e.g., 0 / 1) or for PDRCH (D2R message / data) reception / monitoring (e.g., 1 / 0) (and / or information to indicate that the radio resource is used for both PRDCH (R2D message / data) and PDRCH (D2R message / data reception / monitoring)).

[0205] As another example, configured AIoT resource configuration information may include information for indicating validity criteria / validity / validity time for the configured AIoT resource.

[0206] The information can be configured / instructed through the information on the number of valid (maximum) transmissions of the configured AIoT resource (for example, if it is 3 times, the configured AIoT resource is valid from the first transmission to the next cycle, the second transmission to the next cycle, and the third transmission (or the second / third / fourth transmissions excluding the first transmission)).

[0207] Alternatively, the information may be configured / instructed through information for indicating the validity period after the configured AIoT resource is configured / instructed / activated.

[0208] As another example, configured AIoT resource configuration information can be indicated through distinct configuration information (and / or distinguished configuration parameters), such as configured AIoT R2D resource configuration information for transmitting PRDCH (R2D message / data) to the AIoT device and configured AIoT D2R resource configuration information for receiving / monitoring PDRCH (D2R message / data) to the AIoT device.

[0209] As another example, upon configuration of a configured AIoT resource, the UE reader (or the UE reader's MAC object) may store the AIoT grants / resources provided by the RRC (for each configured AIoT grant / resource) as the configured AIoT resource. And / or for the configured AIoT grants / resources, the activation / deactivation of the configured AIoT resource may be directed by the PDCCH / MAC-CE / RRC.

[0210] (If used in conjunction with the timing for the PUSCH / UL of the terminal) the UE reader (or the MAC object of the UE reader) can initialize / re-initialize the configured AIoT grant / resource to start at the (associated) symbol / resource / slot / second unit time according to at least one of the time reference SFN, time domain offset, start symbol, and time domain resource / time domain allocation / time range. This can be made to reoccur at each corresponding period.

[0211] (If used in conjunction with the timing for base station / terminal PUSCH / UL) After one AIoT grant / resource (or one AIoT grant / resource linked to the corresponding uplink grant / resource) is configured as a configured AIoT grant / resource, the UE leader (or the UE leader's MAC entity) may consider that the configured AIoT resource will sequentially occur in the Nth cycle in conjunction with the following PUSCH / UL symbol.

[0212] [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)

[0213] + (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] =

[0214] (timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot

[0215] + timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity)

[0216] modulo(1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)

[0217] As another example, upon configuration of a configured AIoT resource, the UE reader (or the UE reader's MAC object) may store AIoT grants / resources provided by the RRC (for each configured AIoT grant / resource) as the configured AIoT resource. And / or for the configured AIoT grants / resources, the activation / deactivation of the configured AIoT resource may be directed by the PDCCH / MAC-CE / RRC.

[0218] (If used in conjunction with the timing of the PDSCH / PDCCH / DL of the terminal) the UE reader (or the UE reader's MAC object) can initialize / re-initialize the configured AIoT grant / resource to start at the (associated) corresponding start / start time SFN (e.g., SFNstart time) and start / start time slot (e.g., Slotstart time). It can be made to reoccur at each corresponding cycle.

[0219] (If used in conjunction with the timing for base station / terminal PDSCH / PDCCH / DL) After a single AIoT grant / resource (or a single AIoT grant / resource associated with the corresponding downlink allocation / resource) is configured as a configured AIoT grant / resource, the UE reader (or the MAC object of the UE reader) may consider that the configured AIoT resource will sequentially occur in conjunction with the following PDSCH / PDCCH / DL slots in the Nth cycle. Here, the start / start time SFN (e.g., SFNstart time) and start / start time slot (e.g., Slotstart time) may represent the SFN (or first unit time) and slot (or second unit time) of the first transmission of the PDSCH that initializes / re-initializes the configured AIoT grant / resource.

[0220] (numberOfSlotsPerFrame × SFN + slot number in the frame) =

[0221] [(numberOfSlotsPerFrame × SFNstart time + Slotstart time) + N × periodicity × numberOfSlotsPerFrame / 10] modulo (1024 × numberOfSlotsPerFrame)

[0222] As another example, upon configuration of a configured AIoT resource, the UE reader (or the UE reader's MAC object) may store AIoT grants / resources provided by the RRC (for each configured AIoT grant / resource) as the configured AIoT resource. And / or for the configured AIoT grants / resources, the activation / deactivation of the configured AIoT resource may be directed by the PDCCH / MAC-CE / RRC.

[0223] (For AIoT wireless interfaces (R2D / D2R)) A UE reader (or the MAC object of the UE reader) may initialize / re-initialize a configured AIoT grant / resource to determine the transmission start time and / or transmission duration of the corresponding PRDCH / PDRCH according to at least one of the time reference SFN, time domain offset, and time domain resource / time domain allocation / time range. This may be recurred at corresponding cycles.

[0224] Alternatively, (for AIoT wireless interfaces (R2D / D2R)) the UE reader (or the UE reader's MAC object) may initialize / re-initialize the corresponding configured AIoT grants / resources on the first transmission / reception of the corresponding PRDCH / PDRCH. This may be made to reoccur at corresponding cycles.

[0225] Alternatively, the start / start time SFN (e.g., SFNstart time) and start / start time slot (e.g., Slotstart time) may represent the SFN (or first unit time) and slot (or second unit time) of the first transmission of the PRDCH / PDRCH that the configured AIoT grant / resource initializes / reinitializes.

[0226] Alternatively, for the configured AIoT grant / resource, the time resource location of the first / start configured AIoT grant / resource for the configured AIoT resource may be received by PDCCH / MAC-CE / RRC. For example, the (logical) start / start time system frame / frame / resource set / first unit time number / index of the configured AIoT resource, (logical) start / start time slot / subframe / resource / second unit time number / index, where first unit time = m * second unit time, m=10, or m=10, 20, 40, 80 depending on the SCS.

[0227] Alternatively, the UE reader (or the UE reader's MAC object) may initialize / re-initialize the configured AIoT grant / resource to determine the time resource location / time domain resource / time domain allocation / time range / transmission duration for the transmission / reception of PDRCH / PRDCH for the configured AIoT resource. This may be made to reoccur at corresponding cycles.

[0228] Alternatively, after one AIoT grant / resource is configured as a configured AIoT grant / resource, the UE reader (or the UE reader's MAC object) may consider that the Nth configured AIoT grant / resource will occur sequentially in the following first slot / subframe / resource / second unit time.

[0229] Current slot (or 2nd unit time) = (Offset for AIoT SFN (or 1st unit time offset) + AIoT scheduling unit time / Offset for resource (or 2nd unit time offset) + N × Period) modulo Maximum number of slots (or 2nd unit times) for the corresponding AIoT resource

[0230] Or, current slot (or second unit time) = (time domain offset + N × period) modulo the maximum number of slots (or second unit time) of the corresponding AIoT resource

[0231] Or, (number of second unit times per first unit time × first unit time number / index + second unit time number / index within first unit time = [(number of second unit times per first unit time × start time for first unit time number / index + start time for second unit time number / index) + N × period × number of second unit times per first unit time / m] modulo (1024 × number of second unit times per first unit time), where the start time for first unit time number / index and the start time for second unit time number / index represent the first unit time and second unit time of the first transmission of the PRDCH / PDRCH where the configured AIoT resource is initialized / re-initialized.

[0232] The maximum number of slots (or second unit times) of the relevant AIoT resource represents the (total / maximum) number of slots / second unit times belonging to / included in any AIoT time resource associated with (or usable as) the relevant configured AIoT grant / resource (when the relevant configured AIoT resource is configured on the relevant terminal, or during a series of time domain periods / ranges / durations in which the relevant configured AIoT resource is used on the relevant terminal). For example, it may represent the maximum number of slots (or second unit times) in an AIoT resource / resource pool / resource group / resource set having a specific time range.

[0233] FIG. 10 is a flowchart illustrating a method of operation of a terminal according to one embodiment of the present specification.

[0234] Hereinafter, a method of operation of a terminal performing a reader function is described with reference to FIG. 10.

[0235] According to one embodiment of the present specification, a terminal in a wireless communication system receives a first Radio Resource Control (RRC) message from a base station containing a first Ambient Internet of Things (AIoT) parameter for an inventory request (S1001), and after receiving the first RRC message, performs an inventory procedure through an AIoT wireless interface (S1002). Additionally, after performing the inventory procedure, the terminal transmits a second RRC message to the base station in response to the first RRC message (S1003), wherein the second RRC message may include a second A-IoT parameter for at least one of a response to and a report regarding the inventory request.

[0236] The first AIoT parameter information may include at least one of AIoT device identification information, security parameter information, information for terminal reader selection, information regarding the number of target AIoT devices, and information regarding the size of the D2R (Device to Reader) response message according to the inventory request. Here, the first AIoT parameter information may be stored by an RRC entity.

[0237] The above AIoT device identification information may include either permanent AIoT device identification information or identification information that has been security-processed with respect to the permanent AIoT device identification information. Here, the security parameter information may be random parameter information used to generate the security-processed identification information.

[0238] Meanwhile, the first RRC message may be received via a specific signaling radio bearer (SRB), and the second RRC message may be transmitted via the specific signaling radio bearer (SRB). Here, the specific SRB may be an SRB type distinct from the existing SRB1, SRB2, SRB3, SRB4, and SRB5, and may be configured by the base station after Access Stratum (AS) security is activated. Additionally, the specific SRB may be configured with a lower priority compared to the existing SRB0 and SRB1.

[0239] The disclosures of this specification described above may be implemented through various means. For example, the disclosures of this specification may be implemented by hardware, firmware, software, or a combination thereof. Specifically, they will be described below with reference to the drawings.

[0240] FIG. 11 shows an apparatus according to one embodiment of the present specification.

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

[0242] The first device (100a) may be a base station, network node, transmission terminal, receiving terminal, wireless device, wireless communication device, vehicle, vehicle equipped with autonomous driving function, connected car, drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, fintech device (or financial device), security device, climate / environment device, device related to 5G service, or other device related to the field of the Fourth Industrial Revolution.

[0243] The second device (100b) may be a base station, network node, transmission terminal, receiving terminal, wireless device, wireless communication device, vehicle, vehicle equipped with autonomous driving function, connected car, drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, fintech device (or financial device), security device, climate / environment device, device related to 5G service, or other device related to the field of the Fourth Industrial Revolution.

[0244] 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 aforementioned functions, procedures, and / or methods. 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) is connected to the processor (1020a) and may store various forms of information and / or commands. The transceiver (1031a) is connected to the processor (1020a) and may be controlled to transmit and receive wireless signals.

[0245] 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 aforementioned functions, procedures, and / or methods. 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) is connected to the processor (1020b) and may store various forms of information and / or commands. The transceiver (1031b) is connected to the processor (1020b) and may be controlled to transmit and receive wireless signals.

[0246] The memory (1010a) and / or the memory (1010b) may be connected to the processor (1020a) and / or the processor (1020b) respectively, either internally or externally, and may also be connected to other processors through various technologies such as wired or wireless connections.

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

[0248] FIG. 12 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0249] In particular, FIG. 12 is a drawing illustrating the device of FIG. 11 in more detail.

[0250] 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 SIM (subscriber identification module) card, and one or more antennas.

[0251] 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 processors (1020) may be SNAPDRAGON™ series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIO™ series processors manufactured by MediaTek®, ATOM™ series processors manufactured by INTEL®, KIRINTM series processors manufactured by HiSilicon®, or corresponding next-generation processors.

[0252] The power management module (1091) manages power for 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) may be displayed on the display (1041). A SIM card is an integrated circuit used to securely store the International Mobile Subscriber Identity (IMSI) and associated keys used to identify and authenticate a subscriber in mobile devices such as mobile phones and computers. Contact information may also be stored on many SIM cards.

[0253] Memory (1010) is operably coupled with the processor (1020) and stores various information for operating the processor (610). Memory (1010) may include ROM (read-only memory), RAM (random access memory), flash memory, memory card, storage medium and / or other storage device. Where 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. Modules may be stored in memory (1010) and executed by the processor (1020). Memory (1010) may be implemented inside the processor (1020). Alternatively, memory (1010) may be implemented outside the processor (1020) and may be communically connected to the processor (1020) through various means known in the art.

[0254] The transceiver (1031) is operably coupled with the processor (1020) and transmits and / or receives a wireless signal. The transceiver (1031) includes a transmitter and a receiver. The transceiver (1031) may include a baseband circuit for processing a wireless frequency signal. The transceiver controls one or more antennas to transmit and / or receive a wireless signal. The processor (1020) transmits command information to the transceiver (1031) to transmit a wireless signal, for example, constituting voice communication data, in order to initiate communication. The antennas function to transmit and receive wireless signals. When receiving a wireless 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 a speaker (1042).

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

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

[0257] FIG. 13 shows a block diagram of a processor in which the disclosure of the present specification is implemented.

[0258] As can be seen with reference to FIG. 13, a processor (1020) in which the disclosure of this specification is implemented may include a plurality of circuits to implement the proposed functions, procedures and / or methods described in this specification. For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3). Additionally, although not illustrated, the processor (1020) may include more circuits. Each circuit may include a plurality of transistors.

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

[0260] FIG. 14 is a block diagram showing in detail the transceiver of the first device shown in FIG. 11 or the transceiver of the device shown in FIG. 12.

[0261] Referring to FIG. 14, the transceiver unit (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. Additionally, it may further include, for example, a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown), and a layer permutator (not shown), which may be positioned prior to the DFT unit (1031-11). That is, to prevent an increase in the PAPR (peak-to-average power ratio), the transmitter (1031-1) first passes the information through the DFT (1031-11) before mapping the signal to the subcarrier. After the signal spread (or precoded in the same sense) by the DFT section (1031-11) is mapped to the subcarrier through the subcarrier mapper (1031-12), it is then passed through the IFFT (Inverse Fast Fourier Transform) section (1031-13) to form a signal on the time axis.

[0262] The DFT unit (1031-11) performs a DFT on the input symbols to output 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-valued symbols to each subcarrier in the frequency domain. The complex-valued 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 an IFFT on the input symbols to output a baseband signal for the data, which is a time-domain signal. The CP insertion section (1031-14) copies a portion of the latter part of the base band signal for data and inserts it into the front part of the base band signal for data. Through CP insertion, Inter-Symbol Interference (ISI) and Inter-Carrier Interference (ICI) are prevented, so that orthogonality can be maintained even in a multipath channel.

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

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

[0265] In the exemplary system described above, methods are described based on a flowchart as a series of steps or blocks, but are not limited to the order of the described steps, and some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, a person skilled in the art will understand that the steps shown in the flowchart are not exclusive, and that other steps may be included, or that one or more steps of the flowchart may be omitted without affecting the scope of rights.

[0266] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.

Claims

1. A method of operation for a terminal that performs a reader function in a wireless communication system, A step of receiving a first RRC (Radio Resource Control) message containing first AIoT (Ambient Internet of Things) parameter information for an inventory request from a base station; After receiving the first RRC message, the step of performing an inventory procedure through the AIoT wireless interface; and After performing the above inventory procedure, the method includes the step of transmitting a second RRC message to the base station in response to the first RRC message, and A method in which the second RRC message comprises second A-IoT parameter information for at least one of a response to and reporting of the inventory request.

2. In Paragraph 1, A method comprising at least one of the following: the first AIoT parameter information, including AIoT device identification information, security parameter information, information for selecting a terminal reader, information regarding the number of target AIoT devices, and information regarding the size of a D2R (Device to Reader) response message according to the inventory request.

3. In Paragraph 2, The above AIoT device identification information includes one of the AIoT device permanent identification information or identification information that has been security-processed with respect to the above AIoT device permanent identification information, and A method in which the above security parameter information is random parameter information used to generate the above security-processed identification information.

4. In Paragraph 1, A method in which the above first AIoT parameter information is stored by an RRC entity.

5. In Paragraph 1, The above first RRC message is received through a specific signaling radio bearer (SRB), and A method in which the above second RRC message is transmitted through the above specific signaling radio bearer (SRB).

6. In Paragraph 5, The above specific SRB is an SRB type distinct from SRB1, SRB2, SRB3, SRB4, and SRB5, and is a method configured by the above base station after AS (Access Stratum) security is activated.

7. In Paragraph 5, A method in which the above specific SRB is set to a lower priority compared to SRB0 and SRB1.

8. As a terminal reader in a wireless communication system, At least one processor; and The operation performed based on the instruction being executed by the at least one processor includes at least one memory that stores instructions and is operablely electrically connected to the at least one processor: The step of receiving a first RRC (Radio Resource Control) message including a first AIoT (Ambient Internet of Things) parameter for an inventory request from a base station, and After receiving the first RRC message, the step of performing an inventory procedure through an AIoT wireless interface, and After performing the above inventory procedure, the method includes the step of transmitting a second RRC message to the base station in response to the first RRC message, and A terminal reader, wherein the second RRC message comprises a second A-IoT parameter for at least one of a response to and reporting of the inventory request.

9. In Paragraph 8, A terminal reader comprising at least one of the above first AIoT parameter information, AIoT device identification information, security parameter information, information for selecting a terminal reader, information on the number of target AIoT devices, and information on the size of a D2R (Device to Reader) response message according to the inventory request.

10. In Paragraph 9, The above AIoT device identification information includes one of the AIoT device permanent identification information or identification information that has been security-processed with respect to the above AIoT device permanent identification information, and The above security parameter information is random parameter information used to generate the above security-processed identification information, a terminal reader.

11. In Paragraph 8, The above first AIoT parameter is a terminal reader stored by an RRC entity.

12. In Paragraph 8, The above first RRC message is received through a specific signaling radio bearer (SRB), and The above second RRC message is transmitted via the above specific signaling radio bearer (SRB), a terminal reader.

13. In Paragraph 12, The above specific SRB is an SRB type distinct from SRB1, SRB2, SRB3, SRB4, and SRB5, and is a terminal reader configured by the base station after AS (Access Stratum) security is activated.

14. In Paragraph 12, A terminal reader in which the above specific SRB is set to a lower priority than SRB0 and SRB1.

Images