Method and device for data transmission and reception

Abstract

A method and a device for data transmission and reception in a wireless communication system are provided. This terminal receives a first message for triggering a specific service from a network. In addition, after receiving the first message, the terminal transmits a second message to the network, wherein the first message and / or the second message includes a non-access stratum (NAS) container in a medium access control (MAC) protocol data unit (PDU).

Description

Data transmission and reception method and device

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

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

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

[0004] An object of the present specification is to provide a method and device for transmitting and receiving data in a terminal providing ultra-low complexity and ultra-low power in a wireless communication system.

[0005] One embodiment of the present specification provides a method for a wireless communication system, wherein a terminal receives a first message for triggering a specific service from a network. Furthermore, after receiving the first message, the terminal transmits a second message to the network, wherein at least one of the first message and the second message includes a Non-Access Stratum (NAS) container in a Medium Access Control (MAC) Protocol Data Unit (PDU).

[0006] In addition, one embodiment of the present specification provides a wireless communication system, comprising at least one processor, and at least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: receiving a first message for triggering a specific service from a network; and transmitting a second message to the network after receiving the first message, wherein at least one of the first message and the second message includes a Non-Access Stratum (NAS) container in a Medium Access Control (MAC) Protocol Data Unit (PDU).

[0007] The NAS container may contain NAS layer messages between an ambient IoT (Internet of Things) terminal and an Ambient IoT Network Function (AIoTNF). And / or, the NAS container may contain user plane data.

[0008] The first message described above may include at least one of ambient IoT (Internet of Things) related identifier information, service type information, access timing information for radio resource control, and validity period information. Here, the ambient IoT related identifier information may include at least one of an ambient IoT terminal identifier, an ambient tag identifier, an application identifier, a service identifier, a protocol identifier, and a group identifier, and the service type information may include at least one of an inventory service, a read service, a write service, and a disable service.

[0009] User plane data that may be included in a NAS container may include at least one of an ambient Internet of Things (IoT) terminal identifier, a serial number, a unique item identifier, an application identifier, location data, sensor data, measurement data, and a product-related identifier.

[0010] Meanwhile, the first message may be a paging message, and the paging message may be a MAC message distinguished by a field within the MAC PDU.

[0011] Additionally, the second message may be a MAC message distinguished by fields within the MAC PDU.

[0012] According to the disclosure of this specification, data transmission and reception of a terminal providing ultra-low complexity and ultra-low power in a wireless communication system can be effectively supported.

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

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

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

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

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

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

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

[0020] Figures 8a to 8c illustrate examples of protocol structures for ambient IoT.

[0021] Figure 9 is a flowchart illustrating a method of operating a terminal according to one embodiment of the present specification.

[0022] Figure 10 illustrates a device according to one embodiment of the present specification.

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

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

[0025] FIG. 13 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 10 or the transmitter / receiver unit of the device illustrated in FIG. 11.

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

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

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

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

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

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

[0032] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0033] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

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

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

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

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

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

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

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

[0041] Wireless Communication System

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0060] Support for various numerologies

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0085] 1. DL only configuration

[0086] 2. UL only configuration

[0087] 3. Mixed UL-DL configuration

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

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

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

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

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

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

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

[0095] Communication between base stations and ambient IoT devices involves ambient IoT data and / or signaling. The base station transmitting to the ambient IoT device and the base station receiving from the ambient IoT device may be the same base station or different base stations.

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

[0097] As mentioned above, connectivity topology types for ambient IoT networks and devices have been defined, but specific data transmission and reception methods to support lower complexity, smaller size, reduced capabilities, and lower power consumption compared to existing 3GPP LPWA (Low-Power Wide-Area) IoT have not been provided.

[0098] To solve these problems, the present invention proposes a protocol providing structure, a data transmission / reception method, and a device for supporting the same to support lower complexity, smaller size, reduced capabilities, and lower power consumption compared to the existing 3GPP LPWA IoT.

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

[0100] 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)) through corresponding signaling. Alternatively, any function may be combined / combined and defined as a corresponding terminal capability and transmitted by the terminal to a base station / core network entity through corresponding signaling.

[0101] Ambient IoT terminals can be defined and categorized into at least one device type / category based on at least one capability (or combination thereof) they support. For example, based on energy storage capacity, devices can be categorized into devices with no storage at all, devices with a specific storage capacity (up to E1 Joules), and devices with another specific storage capacity (up to E2 Joules, where E2 > E1). Other examples include devices with no energy storage and no independent signal generation / amplification (e.g., backscatter transmission) (referred to as Device A below for convenience of description), devices with energy storage and no independent signal generation (e.g., backscatter transmission) (referred to as Device B below for convenience of description), where Device B's use of stored energy may include amplification of reflected signals), and devices with energy storage and independent signal generation (e.g., active RF components for transmission) (referred to as Device C below for convenience of description).

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

[0103] The base station / AIoTNF can transmit / instruct the terminal via RRC / MAC / NAS messages information to restrict any of the functions described below. For example, the prohibit timer for the corresponding function can be indicated. The prohibit timer can be started / restarted before or when the corresponding function is initiated. While the timer is running, the terminal can be restricted from initiating / executing the corresponding function.

[0104] The functions described below can be performed individually and independently. Alternatively, the functions described below can be arbitrarily combined and implemented, and this is also clearly included within the scope of the present invention. For example, one or more functions can be applied simultaneously.

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

[0106] For convenience of explanation, ambient IoT devices may be expressed as ambient IoT terminals, IoT devices, or terminals in the following.

[0107] Typical use cases for ambient IoT include inventory, sensor data collection, asset tracking, and actuator control. Typical use cases for ambient IoT can be supported via mobile networks. Ambient IoT use cases via mobile networks can be defined as ambient IoT services. For example, the primary purpose of an ambient IoT inventory service (e.g., inventory) is to search for products (e.g., boxes, containers, packages, tools) in a specific area. When a request is sent from the network within a specific area, ambient IoT devices attached to these products report identifiers associated with the products, and other information such as status, measurement results, and / or location can be added. Ambient IoT sensor services (e.g., sensor data collection) allow ambient IoT devices to connect / bind with sensors. Sensor data transmission can be initiated by the ambient IoT devices. It can be triggered periodically, when the ambient IoT terminal is powered on, or by the network. The main purpose of the ambient IoT tracking service (e.g. asset tracking) is to locate the goods. The ambient IoT terminal attached to such goods reports an identifier associated with the goods. This can then be combined with location information. Asset tracking can be initiated by the ambient IoT supporting assisting node / UE, or by one of the base station, core network entities (e.g. Access and Mobility Management Function (AMF) / Session Management Function (SMF) / Ambient IoT Network Function (AIoTNF) / Network Exposure Function (NEF)), or application server. The location of the ambient IoT terminal can be found within a certain range of the assisting node / UE / base station. Ambient IoT command service (e.g.Using actuator control, ambient IoT terminals are connected to actuators. Actuator command transmission is typically initiated by the network. The message size of typical use cases is small data, on the order of 100 bits or no more than 1 Kbit at most. The user experience data transmission rate requirement is 1 to 2 kbps or less. Therefore, upper layer protocols of conventional NR technology that support various functions (for example, at least one of RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol), SDAP (Service Data Adaptation Protocol), and RRC (Radio Resource Control)) may not be required.

[0108] Protocol Structure for Ambient IoT Support

[0109] Figures 8a to 8c illustrate examples of protocol structures for ambient IoT.

[0110] The protocol structure shown in FIGS. 8a to 8c can be used to provide ambient IoT services.

[0111] The physical (PHY) layer can provide information transfer to the MAC layer and upper layers. The MAC layer of the ambient IoT (capable / support) terminal / base station / auxiliary node / general terminal is responsible for mapping between logical channels and transport channels (or mapping between logical channels and physical channels when no transport channel is defined), multiplexing / demultiplexing of MAC SDUs (service data units) belonging to one or another logical channel to / from transport blocks (TB) delivered to / from the physical layer on the transport channel (when no transport channel is defined), (multiplexing / demultiplexing of MAC SDUs belonging to one or another logical channel to / from transport blocks (TB) delivered to / from the physical layer), logical channel priority processing, padding, collision avoidance, access attempts by service triggers, and arbitrary data / messages of the ambient IoT terminal (e.g., user data, identification information, information managed by terminal operators / service providers / application servers, information directed / initiated / triggered by the network). Mapping function between configuration / setting / signaling messages / information (e.g., network registration, terminal control, radio resource control)) and logical channel / MAC messages, ambient IoT terminal service type (e.g., user data reception, identification information reception, location / sensor information reception, management information (e.g., enable / disable, disable time duration) configuration / setting, (memory) read / write, application layer, application identifier, service type / identifier, protocol identifier / description, group identifier, terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information (CN allocated temporary ID) allocated to the ambient IoT terminal by the core network control plane entity),It is possible to perform at least one function / operation among the mapping function between the identification information (RAN / Reader allocated temporary ID), request type, and classification / indication information for request information allocated to the corresponding ambient IoT terminal by the base station / general terminal / auxiliary node) and the logical channel / MAC message, information processing for indicating whether there is more data to be sent, and processing for the validity period.

[0112] The upper Access Stratum (upperAS) layer, if present, is configured for wireless resources, logical channels, PHY / MAC, etc. between the ambient IoT terminal and the base station, ambient IoT terminal service type (e.g., user data reception, identification information reception, location / sensor information reception, management information (e.g., enable / disable, disable time duration) configuration / setting, (memory) read / write, application identifier, service type / identifier, protocol identifier / description, group identifier, terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information allocated to the ambient IoT terminal by the core network control plane entity (CN allocated temporary ID), identification information allocated to the ambient IoT terminal by the base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), request type, and classification / indication information for request information) and logical channels, and controls related operations. It can provide functions (setting / modification / release). For example, the upper AS layer can represent RRC. In another example, the upper AS layer can be defined as a sublayer, distinct from RRC.As another example, the upperAS layer may have a mapping function between arbitrary data of an ambient IoT terminal (e.g., user data, identification information, information managed by a terminal operator / service provider / application server, configuration / setting / signaling messages / information directed / initiated / triggered by the network (e.g., network registration, terminal control, radio resource control)) and logical channels / upperAS messages (or ambient IoT terminal service types (e.g., user data reception, identification information reception, location / sensor information reception, management information (e.g., enable / disable, disable time duration) configuration / setting, (memory) read / write, application identifier, service type / identifier, protocol identifier / description, group identifier, terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information (CN allocated temporary ID) allocated to the ambient IoT terminal by a core network control plane entity), The ambient IoT terminal may be provided with one or more of the identification information (RAN / Reader allocated temporary ID), request type, and classification / indication information for request information) allocated to the ambient IoT terminal by the base station / general terminal / auxiliary node and a mapping function between logical channels. The upper AS layer may be optionally provided. For example, data communication may be performed between the ambient IoT terminal and the base station without the upper AS layer. The MAC layer, upper AS layer, NAS layer, and application layer are names shown for convenience of explanation and may be replaced with any other names (for example, MAC: lowerAS, upper AS: RRC, upperAS, NAS: Non Access Stratum). In FIGS. 8a to 8c, a base station and a core network NF (Network Function) or a core network NF and another core network NF may be interconnected through a service-based interface.In FIGS. 8a to 8c, a core network control plane entity (e.g., AMF / AIoTNF) having a terminal and NAS interface can be linked with a core network NF / Application Function (AF) / Application Server (AS) for providing ambient IoT services. For convenience of explanation, the network function / application function / application server for providing ambient IoT services is referred to as AIoTNF (Ambient IoT Service Function). This is for convenience of explanation and can be changed to any other name. A core network control plane entity (e.g., AMF / SMF / AIoTNF) having a terminal and interface can be linked with an external application server (AS) through a network exposure function (NEF) that provides network function (NF) capabilities and event linkage / exposure. For example, a specific core network control plane entity (e.g., AMF / AIoTNF) can forward data / messages received from ambient IoT terminals to AIoTNF / NEF / AS. AIoTNF can perform at least one of the following functions: authentication for an ambient IoT application server / application function, registration for an ambient IoT terminal, registration for a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal, transmission of an ambient IoT service trigger / request message to a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal according to a request of the ambient IoT application server / application function, reception of a service data / confirmation / response message in response to transmission of an ambient IoT service trigger / request message from a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal, and transmission of a message received from a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal to the ambient IoT application server / application function.Here, registration for an ambient IoT terminal or registration for a base station / general terminal / auxiliary node that provides wireless connection / access to an ambient IoT terminal represents an operation in which AIoTNF receives, stores, and manages an ambient IoT terminal context in order to manage information related to the ambient IoT terminal.

[0113] Data transmission and reception of ambient IoT terminals

[0114] Ambient IoT devices are ideally designed with ultra-low complexity. They transmit small amounts of data using low power when sufficient power is available for their intended operation. Therefore, establishing / modifying / teardown one or more user plane radio bearers, user plane tunnels (e.g., NG-U tunnels), and PDU sessions each time a device attempts data transmission can be excessive overhead.

[0115] For example, an ambient IoT terminal may be configured to transmit and receive user plane data without (or without performing) one or more of the following procedures: adding / setting up a radio bearer for user plane data transmission, setting up a tunnel between a base station and a core network user plane entity (e.g., a User Plane Function (UPF)), or setting up a PDU session (PDU) session (PDU) session).

[0116] For example, an ambient IoT device can use a control plane / NAS container / PDU to transmit and receive user plane data. The NAS container can contain the ambient IoT device, core network control plane entities, and NAS messages.

[0117] As another example, the user plane data transmitted by the ambient IoT terminal can be transmitted to the core network (e.g., AMF / SMF / AIoTNF / NEF / AF / AS) by the base station through a control plane message (e.g., NG Application Protocol (NGAP) message, Service Based Interface (SBI) operation). For example, the user plane data can be included in an NAS container and transmitted and received through NGAP messages.

[0118] As another example, ambient IoT terminals can transmit and receive control planes / NAS containers / PDUs to and from base stations via signaling wireless bearers.

[0119] As another example, an ambient IoT terminal can transmit and receive control plane / NAS containers / PDUs and / or user data (or application PDUs containing user data) to and from a base station via SRB0 (Signaling Radio Bearer 0) for CCCH (Common Control Channel) transmission (or for RRC messages using the corresponding logical channel).

[0120] As another example, an ambient IoT terminal may transmit and receive control plane / NAS containers / PDUs and / or user data (or application PDUs containing user data) to and from a base station via one of SRB1 / SRB2 / SRB4 for RRC messages using the Dedicated Control Channel (DCCH) logical channel.

[0121] As another example, ambient IoT terminals can transmit and receive control plane / NAS containers / PDUs and / or user data (or application PDUs containing user data) to and from a base station via newly defined SRBs / RBs that are distinct from SRB0 / SRB1 / SRB2 / SRB4 of the prior art. For example, the SRBs can be defined as signaling message and / or user data (or application PDUs containing user data) transmission channels for ambient IoT terminals operating without an RRC state.

[0122] As another example, a dedicated signaling / data logical channel for ambient IoT terminals can be defined to transmit and receive control plane / NAS containers / PDUs and / or user data (or application PDUs containing user data) through that logical channel.

[0123] As another example, MAC PDU (protocol data unit) / SDU (service data unit) / CE (control element) are defined for transmitting and receiving control plane / NAS container / PDU and / or user data (or application PDU containing user data), and control plane / NAS container / PDU and / or user data (or application PDU containing user data) can be transmitted and received through the MAC PDU / SDU / CE. For example, a NAS container can be included in a specific MAC PDU. A NAS container can be included as a MAC SDU in a MAC PDU. A NAS container can be included as a specific MAC header / field in a MAC PDU.

[0124] As another example, an ambient IoT terminal can send and receive RRC messages containing user plane data (or application PDUs containing user data) of the ambient IoT terminal over a signaling radio bearer.

[0125] As another example, an ambient IoT terminal can transmit and receive user plane data (or application PDUs containing user data) of the ambient IoT terminal via a signaling radio bearer.

[0126] As another example, ambient IoT terminals can piggyback control plane / NAS messages / containers / PDUs into RRC messages using the CCCH logical channel.

[0127] As another example, ambient IoT terminals can piggyback control plane / NAS messages / containers / PDUs into RRC messages using the DCCH logical channel.

[0128] For another example, a base station can transmit user plane data (or application PDU including user data or NAS PDU including user plane data of an ambient IoT terminal) received from a terminal to a core network control plane entity (e.g., AMF / SMF / AIoTNF) (having a terminal and NAS interface). The core network control plane entity (e.g., AMF / SMF / AIoTNF) having a terminal and NAS interface can forward the data to an AIoTNF / AF / AS providing the application. The core network control plane entity (e.g., AMF / SMF / AIoTNF) having a terminal and NAS interface can transmit and receive the data to and from an external application server (AS) via an AIoTNF or NEF.

[0129] For example, an ambient IoT terminal may initiate / start data communication / transmission when triggered by the network. A core network control plane entity (e.g., AMF / SMF / AIoTNF) may receive a request message from an AF / AS and / or AIoTNF / NEF providing the application to trigger a service for the ambient IoT terminal (e.g., receiving user data, receiving identification information, receiving location / sensor information, configuring / setting management information (e.g., enable / disable, disable time duration), reading / writing (memory). The request message may include one or more of the following information: an ambient IoT terminal / tag identifier, an application identifier, a service type / identifier, a protocol identifier / description, a group identifier, a terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information allocated to the ambient IoT terminal by a core network control plane entity (CN allocated temporary ID), identification information allocated to the ambient IoT terminal by a base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), a request type, classification / indication information for the requested information, identification / classification information for the requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage, maximum number of requests / triggers / repetitions / cycles, and a validity period. The application identifier or service type / identifier or protocol identifier / description or request type or request information distinguishing / indicating information may include information for distinguishing services for ambient IoT terminals (e.g., receiving user data, receiving identification information, receiving location / sensor information, configuring / setting management information (e.g., enable / disable, disable time duration), (memory) read / write).A (memory) write may include information to distinguish between one or more of data changes and data deletion / removal.

[0130] Here, the requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage identification / classification information may include base station / cell identification information of a base station leader servicing the ambient IoT terminal, for the ambient IoT terminal connected to the base station controlling the radio resources of the ambient IoT terminal via a wireless interface (Uu). The base station / cell identification information servicing the ambient IoT terminal may include one or more pieces of information from among information for identifying the base station leader servicing the ambient IoT terminal and information for identifying the cell of the base station leader servicing the ambient IoT terminal. The cell of the base station leader servicing the ambient IoT terminal may indicate information for identifying an area in which the service can be provided through the cell coverage of the base station leader. For example, it may indicate one or more of the following information: NR CGI (Cell Global Identifier), arbitrary service area identification information, geographic area identification information, coverage identification information, and information for distinguishing coverage for the frequency band of the corresponding base station leader.

[0131] Alternatively, the requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage identification / division information may include identification information of an auxiliary node / general terminal leader servicing the ambient IoT terminal, for the ambient IoT terminal connected through the base station controlling the radio resources of the ambient IoT terminal and the auxiliary terminal / general terminal. The identification information of the auxiliary node / general terminal leader servicing the ambient IoT terminal may include one or more pieces of information from among information for identifying the auxiliary node / general terminal leader servicing the ambient IoT terminal and information for identifying the cell of the auxiliary node / general terminal leader servicing the ambient IoT terminal. Here, the cell of the auxiliary node / general terminal leader servicing the ambient IoT terminal may indicate information for identifying an area in which the service can be provided through the wireless / cell coverage of the auxiliary node / general terminal leader. For example, it may indicate one or more of the following information: NR CGI (Cell Global Identifier), arbitrary service area identification information, geographic area identification information, coverage identification information, and information for distinguishing coverage for the frequency band of the corresponding base station leader.

[0132] The base station may receive the request message to trigger a service for the ambient IoT terminal through the core network control plane entity (e.g., AMF / SMF / AIoTNF). The request message may include one or more of the following information: an ambient IoT terminal / tag identifier, an application identifier, a service type / identifier, a protocol identifier / description, a group identifier, a terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information allocated to the ambient IoT terminal by the core network control plane entity (CN allocated temporary ID), identification information allocated to the ambient IoT terminal by the base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), a request type, classification / indication information for the request information, identification / classification information for the requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage, maximum number of requests / triggers / repetitions / cycles, and a validity period.

[0133] Here, the service type / identifier represents information for identifying the ambient IoT service type. For example, the ambient IoT service may include one or more of an inventory service for performing inventory operations from an ambient IoT device, a read service for reading information from an ambient IoT device, a write service for writing information from an ambient IoT device, and a disable service for disabling capabilities of an ambient IoT device.

[0134] A base station can transmit a message to a corresponding ambient IoT terminal to trigger a service for the corresponding ambient IoT terminal in order to receive service-related data from the corresponding terminal. For convenience of explanation, this is referred to as a paging message hereinafter. This is for convenience of explanation and may be replaced with any other name (e.g., ambient IoT paging message, notification message, command message, service trigger message). The paging message may include one or more of the following information: an ambient IoT terminal / tag identifier of a single ambient IoT terminal, an application identifier, a service type / identifier, a protocol identifier / description, a group identifier mapped to multiple ambient IoT terminals, a terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information allocated to the ambient IoT terminal by a core network control plane entity (CN allocated temporary ID), identification information allocated to the ambient IoT terminal by a base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), a request type, classification / indication information for the request information, identification / classification information for the requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage, maximum number of requests / triggers / repetitions / cycles, validity period, access timing information, and backoff information.

[0135] Here, the service type / identifier represents information for identifying the ambient IoT service type. For example, the ambient IoT service may include one or more of an inventory service for performing an inventory operation from an ambient IoT device, a read service for reading information from an ambient IoT device, a write service for writing information from an ambient IoT device, and a disable service for disabling a capability of the ambient IoT device. The access timing information represents radio resource information in a time domain used by the ambient IoT terminal to transmit a response message in response to a paging message. The validity period may represent a time period / range during which the radio resource information in a time domain used by the ambient IoT terminal to transmit the response message according to the paging message is valid.

[0136] The paging message may include information for instructing all ambient IoT terminals that can be received within the base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage to transmit an access / response / confirmation message including the service information to the base station / general terminal / auxiliary node. For example, this may be instructed by designating a specific value for any field (e.g., a single / group terminal identifier field) included in the paging message. Or, this may be instructed through information for instructing not to include a specific field (e.g., a single / group terminal identifier field) in the paging message. The paging message may include information (e.g., a group terminal identifier) ​​for instructing ambient IoT terminals included in a specific group / service that can be received within the base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage to transmit a message including the service information to the base station.

[0137] If the information contained in the received message matches the configured / set / allocated / pre-configured / built-in / instructed / specified service / information / rule / rule of the terminal, the ambient IoT terminal can transmit a message containing service / service response information for the corresponding ambient IoT terminal to the base station. For example, if the received ambient IoT terminal / device identifier matches the stored ambient IoT terminal / device identifier, a message containing response information for the requested service for the ambient IoT terminal can be transmitted to the base station.

[0138] Information included in a message received by an ambient IoT terminal may be at least one of ambient IoT terminal / tag identifier, application identifier, service type / identifier, protocol identifier / description, group identifier, terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the corresponding ambient IoT terminal, identification information allocated to the corresponding ambient IoT terminal by a core network control plane entity (CN allocated temporary ID), identification information allocated to the corresponding ambient IoT terminal by a base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), request type, classification / indication information for the requested information, identification / classification information for the corresponding requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage, access timing information, and backoff information. Service response information for the ambient IoT terminal may be at least one of ambient IoT terminal / tag identifier, application identifier, service type / identifier, protocol identifier / description, group identifier, terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the ambient IoT terminal, identification information allocated to the ambient IoT terminal by the core network control plane entity (CN allocated temporary ID), identification information allocated to the ambient IoT terminal by the base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), request type, classification / indication information for the requested information, identification / indication information for the requested base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage, information for indicating whether there is more data to be sent, a validity period, and user plane data.Here, the user plane data may include at least one of the following: an identifier of the ambient IoT terminal, a serial number / device permanent ID, an application identifier, location / sensor / measurement data, and an identifier related to the product. Information indicating whether there is more data to be sent may be indicated using 1-bit information. Information indicating whether there is more data to be sent may be indicated using multi-bit information to indicate the size of the data to be sent.

[0139] A base station that receives a message including service response information for an ambient IoT terminal may transmit a message including one or more pieces of information included in the message to a core network control plane entity (e.g., AMF / SMF). Alternatively, a base station that receives a message including service response information for an ambient IoT terminal may transmit a message including at least one piece of information included in the message to an AF / AIoTNF / NEF. Alternatively, a base station that receives a message including service response information for an ambient IoT terminal may transmit a message including at least one piece of information included in the message to an AF / AIoTNF / NEF via a core network control plane entity (e.g., AMF / SMF / AIoTNF).

[0140] When a base station / general terminal / auxiliary node that has received a message containing service response information for an ambient IoT terminal transmits the service response information to a core network control plane entity or AF / AIoTNF / NEF, the base station / general terminal / auxiliary node can include information linked to the ambient IoT terminal / service by mapping it to the received data. The message transmitted by the base station / general terminal / auxiliary node may include at least one of the following information: ambient IoT terminal / tag identifier, application identifier, service type / identifier, protocol identifier / description, group identifier, terminal / tag serial number / unique item identifier (device permanent ID), subscription information for the corresponding ambient IoT terminal, identification information allocated to the corresponding ambient IoT terminal by the core network control plane entity (CN allocated temporary ID), identification information allocated to the corresponding ambient IoT terminal by the base station / general terminal / auxiliary node (RAN / Reader allocated temporary ID), request type, classification / indication information for the request information, and identification / classification information for the corresponding base station / general terminal / auxiliary node / cell / area / service area / geographic area / coverage. For example, for an ambient IoT terminal connected to a base station that controls the radio resources of the ambient IoT terminal through a wireless interface (Uu), the base station may transmit information related to the ambient IoT terminal to the core network control plane entity (e.g., AMF / SMF / AIoTNF). The information related to the ambient IoT terminal may include one or more of the following: an identifier of the ambient IoT terminal, location information of the ambient IoT terminal, and identification information of the base station / cell servicing the ambient IoT terminal.The base station / cell identification information servicing the ambient IoT terminal may include one or more of information for identifying the base station leader servicing the ambient IoT terminal and information for identifying the cell of the base station leader servicing the ambient IoT terminal. Here, the cell of the base station leader servicing the ambient IoT terminal may indicate information for identifying an area in which the service can be provided through the cell coverage of the base station leader. For example, it may indicate one or more of NR CGI (Cell Global Identifier), arbitrary service area identification information, geographic area identification information, coverage identification information, and information for distinguishing the coverage for the frequency band of the base station leader.

[0141] Alternatively, for an ambient IoT terminal connected to a base station controlling radio resources of the ambient IoT terminal through an auxiliary terminal / general terminal, the base station may transmit information related to the ambient IoT terminal to the core network control plane entity (e.g., AMF / SMF / AIoTNF). The information related to the ambient IoT terminal may include one or more of the following: an identifier of the ambient IoT terminal, location information of an auxiliary node connected to the ambient IoT terminal, and identification information of an auxiliary node servicing the ambient IoT terminal. The location information of the auxiliary node connected to the ambient IoT terminal indicates location information of the auxiliary node terminal operating as an auxiliary node. The identification information of the auxiliary terminal servicing the ambient IoT terminal may include one or more of the following: information for identifying an auxiliary node terminal leader servicing the ambient IoT terminal, and information for identifying a cell of an auxiliary node leader servicing the ambient IoT terminal. Here, the cell of the auxiliary node leader servicing the ambient IoT terminal may indicate information for identifying the area in which the service can be provided through the cell coverage of the auxiliary node leader. For example, it may indicate one or more of the following information: NR CGI (Cell Global Identifier), arbitrary service area identification information, geographic area identification information, coverage identification information, information for distinguishing the coverage for the frequency band of the auxiliary node / general terminal leader, and cell / base station identification information accessed by the auxiliary node.

[0142] As another example, if a base station / general terminal / auxiliary node / core network control plane entity / AF / AIoTNF / NEF does not receive a message containing one or more service information for an ambient IoT terminal during the validity period, the service trigger for the ambient IoT terminal may be considered failed. The base station / general terminal / auxiliary node / core network control plane entity may forward this to the core network control plane entity / AF / AIoTNF / NEF / application server. The base station / general terminal / auxiliary node / core network control plane entity / AF / AIoTNF / NEF may release / remove / fail the previous service trigger. The base station / general terminal / auxiliary node / core network control plane entity / AF / AIoTNF / NEF may retry the service trigger. For example, if the time period / range in which the radio resource information in the time domain used to transmit the corresponding response message instructed by the base station expires, the base station may consider the service trigger for the corresponding ambient IoT terminal to have failed.

[0143] For another example, a terminal and a core network control plane entity (e.g., an SMF performing session management or an AMF performing registration management) can avoid establishing a user plane connection (e.g., a data radio bearer (DRB), an N3 tunnel) for an ambient IoT terminal (or for a PDU session of the terminal) by sending and receiving user plane data (or application PDUs containing user data) of the terminal through the payload of a NAS message.

[0144] For example, the existing QoS model that provides QoS flow-based processing can be avoided by not setting up user plane resources for sessions (e.g., PDU sessions) between the ambient IoT terminal and the data network.

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

[0146] Ambient IoT devices / terminals cannot always be assumed to have power for transmitting and receiving data. Ambient IoT terminals can perform their functions only when valid power required for any operation is secured / obtained / supplied to the terminal. For ambient IoT devices A / B that transmit data via backscattering, the terminals can perform their functions only when valid power for the operation is secured / obtained / supplied (via radio waves received from the network and / or by energy harvesting). For ambient IoT device C that has energy storage, the terminals can also perform their functions only when valid power for a specific operation is secured / obtained / supplied by energy harvesting. For example, data can be transmitted when an electromagnetic field is formed at the terminal via signal(s) received from a base station / general terminal / auxiliary node, and when suitable / sufficient power to operate the terminal is secured / obtained / supplied. This can be taken into account in the transmission and reception of ambient IoT service data.

[0147] For example, when an ambient IoT terminal transmits data to a base station / general terminal / auxiliary node, the terminal may transmit including help information for indicating the next preparation state (e.g., at least one of energy harvesting expected time / duration, a code value for the expected time, the minimum number of paging requests required for energy harvesting, a minimum time period, related terminal capabilities, an unavailable period duration, information for indicating that there is more data to be transmitted, and the size of the data to be transmitted). For example, when the terminal transmits the data in response to a message received by the base station / general terminal / auxiliary node, the terminal may transmit including the information.

[0148] As another example, the reachability category for the ambient IoT terminal may be negotiated / signaled between the ambient IoT terminal and the core network control plane node and / or between the base station / general terminal / auxiliary node accessed by the ambient IoT terminal and the core network control plane node. A category may be defined to indicate a case in which valid power is not secured / obtained / supplied to the ambient IoT terminal. For example, an unavailability period duration category for securing / obtaining / supplying valid power may be defined. The unavailability period duration category may be divided into 1-bit information indicating a state in which the ambient IoT terminal is not able to secure / obtain / supplied valid power for data transmission and a state in which valid power is secured / obtained / supplied. Alternatively, the unavailability period duration category may be divided into multiple-bit information indicating a level at which valid power is secured / obtained / supplied to the ambient IoT terminal for data transmission. When an ambient IoT terminal receives a message triggered by a base station / general terminal / auxiliary node / core network control plane node and transmits data in response thereto, the information may be transmitted to the base station / general terminal / auxiliary node / core network control plane node. During the unavailable period, mobile outgoing data and / or mobile incoming data may not be transmitted. Alternatively, an ambient IoT service trigger procedure may not be initiated / applied during the unavailable period. Alternatively, signal transmission for the terminal to support energy harvesting may be performed during the unavailable period.

[0149] As another example, base stations / general terminals / auxiliary nodes and core network control plane nodes can consider an ambient IoT terminal unreachable upon receiving any service data from the ambient IoT terminal. Furthermore, after the unavailability period has elapsed / expired, the service for the ambient IoT terminal can be considered available.

[0150] As another example, when a base station / general terminal / auxiliary node / core network control plane node receives an ambient IoT service trigger request from AIoTNF / AF / AS / NEF, if the ambient IoT terminal is unreachable, the terminal can store the service trigger request.

[0151] As another example, the application layer may include one or more of an application identifier, a protocol identifier, a terminal / tag identifier, a group identifier, a terminal / tag serial number / device permanent ID, a protocol description, physical layer protocol control information, MAC layer protocol control information, a message type, a validity period, information indicating whether there is more data to be sent, and a size of data to be sent in the application layer header and / or payload. The protocol control information may indicate physical layer attribute information (e.g., information encoding a backscatter length range, information encoding a communication distance / range, etc.) and / or information for distinguishing / identifying MAC layer attribute information when the ambient IoT terminal / tag is backscattered. The validity period may indicate a time period during which the corresponding ambient IoT service request / instruction / data is valid, according to the corresponding ambient IoT service request / instruction. Information indicating whether there is more data to be sent can be information for indicating that one or more data to be sent is waiting (remaining) from the ambient IoT terminal / tag (or base station / AMF / AIoTNF / AS) to the terminal / tag (or base station / AMF / AIoTNF / AS) to the base station / AMF / AIoTNF / AS (or terminal / tag). For example, an ambient IoT terminal such as a read-only tag does not require additional communication. It can transmit information including information for indicating that there is no data to be sent. The information for indicating whether there is more data to be sent can be indicated by 1-bit information. The information for indicating whether there is more data to be sent can be indicated by multi-bit information to indicate the size of the data to be sent.

[0152] Some ambient IoT terminals can operate in passive mode to support low complexity and transmit data using backscattering. Ambient IoT terminals can initiate / start data communication / transmission when triggered by the network. To provide services to ambient IoT terminals through the 3GPP system, it may be necessary to register the ambient IoT terminal with the network and establish a terminal context within the network. This allows the network to stably provide repetitive services to the terminal after the service for the ambient IoT terminal is initiated. For example, AIoTNF can receive and manage the ambient IoT terminal context. By managing the ambient IoT terminal context, such as the ambient IoT terminal identifier, the ambient IoT terminal location, and the last service base station / auxiliary node identification information of the ambient IoT terminal, services can be stably provided to the corresponding ambient IoT terminal.

[0153] When an ambient IoT terminal transmits data due to a network trigger, the ambient IoT terminal can perform a registration procedure with the network. For example, when an ambient IoT terminal transmits arbitrary data to the network due to a network trigger, a registration procedure for the ambient IoT terminal can be performed.

[0154] When an ambient IoT terminal transmits data due to a network trigger, a terminal context setup procedure for the ambient IoT terminal can be performed. For example, when an ambient IoT terminal transmits arbitrary data to the network due to a network trigger, a terminal context for the ambient IoT terminal can be set up at the corresponding network node.

[0155] Ambient IoT terminals, similar to conventional mobile terminals, can perform a registration procedure with a core network node via NAS signaling. Alternatively, unlike conventional mobile terminals, ambient IoT terminals can be configured such that a base station that triggers data transmission performs a registration procedure with a core network node. Alternatively, unlike conventional mobile terminals, ambient IoT terminals can perform a registration procedure between a core network node and a base station when an action for the terminal is triggered by an application server / AF / core network.

[0156] For example, the terminal may transmit ambient IoT terminal support indication information in a registration request message. The ambient IoT terminal support indication information may include one or more of ambient IoT terminal capabilities, whether the ambient IoT terminal supports transmitting and receiving user plane data via control plane / NAS PDU / container / message, whether the base station supports transmitting user plane data of the ambient IoT terminal to AMF / SMF / AIoTNF / AF / AS via control plane / NAS PDU / container / message, and whether the ambient IoT terminal supports transmitting and receiving user plane data of the ambient IoT terminal to UPF via N3 tunnel. For example, the ambient IoT terminal may transmit the corresponding information to the AIoTNF via the base station. Alternatively, an assisting UE connected to the base station via a wireless interface (Uu) may transmit the corresponding information to the AIoTNF via the base station.

[0157] As another example, a registration accept message that a core network control plane entity instructs a base station / terminal may include ambient IoT terminal capabilities, information indicating support of the corresponding function in the core network (or information for confirming / responding to support of the corresponding function in the core network, or information for requesting support of the corresponding function in the core network). The information indicating support of the corresponding function may include one or more of whether the core network entity supports transmitting / receiving user plane data of the ambient IoT terminal through the control plane / NAS PDU / container / message, whether supports transmitting user plane data of the ambient IoT terminal to AMF / SMF / AIoTNF / AF / AS from the base station through the control plane / NAS PDU / container / message, and whether supports transmitting / receiving user plane data of the ambient IoT terminal to UPF through the N3 tunnel.

[0158] As another example, when transmitting and receiving user plane data of an ambient IoT terminal via control plane / NAS PDU / container / message / payload, a base station / core network control plane entity (e.g., AFM / SMF / AIoTNF) can receive subscription information of the terminal from another core network entity (e.g., UDM (Unified Data Management) / HSS (Home Subscriber Server)). The information can receive NEF / AIoTNF / AF / AS information that will perform signaling / data transmission with the ambient IoT terminal.

[0159] As another example, when transmitting and receiving user plane data of an ambient IoT terminal via control plane / NAS PDU / container / message / payload, the base station / core network control plane entity (e.g., AFM / SMF) can select NEF / AIoTNF / AF / AS from the information in the terminal's subscription information.

[0160] As another example, when data communication / transmission to an ambient IoT terminal is triggered by the network, the ambient IoT terminal subscription information may be transmitted to the base station / core network control plane entity.

[0161] As another example, when the user plane data of an ambient IoT terminal is transmitted and received only through the control plane / NAS PDU / container / message / payload, the core network control plane entity (e.g., AMF / SMF) may transmit information (e.g., control plane only indicator) to another core network control plane entity (e.g., AMF / SMF / AIoTNF / AF / AS) and / or the core network user plane entity to indicate that the user plane data is transmitted and received only through the control plane / NAS PDU / container / message / payload during the PDU session setup.

[0162] As another example, when the user plane data of an ambient IoT terminal is transmitted and received only through the control plane / NAS PDU / container / message / payload, the core network control plane entity (e.g., AMF / SMF) can transmit information (e.g., control plane only indicator) to another core network control plane entity (e.g., AMF / SMF / AIoTNF / AF / AS) and / or the core network user plane entity to indicate that the user plane data is transmitted and received only through the control plane / NAS PDU / container / message / payload without establishing a PDU session.

[0163] As another example, if the user plane data of an ambient IoT terminal is transmitted and received only through the control plane / NAS PDU / container / message / payload, the core network control plane entity (e.g., AMF / SMF) can transmit information (e.g., control plane only indicator) to the base station during PDU session setup to indicate that the user plane data is transmitted and received only through the control plane / NAS PDU / container / message / payload.

[0164] As another example, when the user plane data of an ambient IoT terminal is transmitted and received only through the control plane / NAS PDU / container / message / payload, the core network control plane entity (e.g., AMF / SMF) can transmit information (e.g., a control plane only indicator) to the base station to indicate that the user plane data is transmitted and received only through the control plane / NAS PDU / container / message / payload without establishing a PDU session.

[0165] As another example, if the user plane data of an ambient IoT terminal is transmitted and received only through the control plane / NAS PDU / container / message / payload, the core network control plane entity (e.g., AMF / SMF) can transmit information (e.g., control plane only indicator) to the terminal during PDU session setup to indicate that the user plane data is transmitted and received only through the control plane / NAS PDU / container / message / payload.

[0166] As another example, when the user plane data of an ambient IoT terminal is transmitted and received only through the control plane / NAS PDU / container / message / payload, the core network control plane entity (e.g., AMF / SMF) can transmit information (e.g., a control plane only indicator) to the terminal to indicate that the user plane data is transmitted and received only through the control plane / NAS PDU / container / message / payload without establishing a PDU session.

[0167] As another example, when a base station / general terminal / auxiliary node transmits a message to trigger a service (e.g., receiving user data, receiving identification information, receiving location / sensor information, configuring / setting management information (e.g., enable / disable, disable time duration), reading / writing (memory)) for the ambient IoT terminal to the ambient IoT terminal in order to transmit / receive data related to the service (e.g., when transmitting a paging message, when transmitting a service trigger command) and / or when the base station / general terminal / auxiliary node receives any data / message transmitted by the ambient IoT terminal triggered by the base station / general terminal / auxiliary node, the base station / general terminal / auxiliary node transmits a message for requesting registration for the ambient IoT terminal (or an initial terminal message, or a message for transmitting information received from the terminal, or information associated with the terminal (e.g., location information, cell identification information accessed by the terminal (e.g., NR CGI)). A message for transmission, or a message for setting up a terminal context) can be transmitted to a core network control plane entity (e.g., AMF / SMF / AIoTNF). A message that a base station / general terminal / auxiliary node transmits to a core network control plane entity (e.g., AMF / SMF / AIoTNF) may include information received from the terminal and / or information associated with the terminal. A message that a base station / general terminal / auxiliary node transmits to a core network control plane entity (e.g., AMF / SMF / AIoTNF) may include ambient IoT terminal support instruction information.The ambient IoT terminal support instruction information may include at least one of ambient IoT terminal capability, whether to support transmitting and receiving user plane data of the ambient IoT terminal through a control plane / NAS PDU / container / message, whether to support transmitting user plane data of the ambient IoT terminal from a base station / general terminal / auxiliary node to AMF / SMF / AIoTNF / AF / AS through a control plane / NAS PDU / container / message, and whether to support transmitting and receiving user plane data of the ambient IoT terminal to UPF through an N3 tunnel.

[0168] As another example, a message for confirming / responding to a registration instructed by a core network control plane entity (e.g., AMF / SMF / AIoTNF) to a base station / general terminal / auxiliary node (or a message for registration accept or setting up a terminal context) may include information indicating support for the corresponding function in the core network (or information for confirming / responding to support for the corresponding function in the core network or information for requesting support for the corresponding function in the core network). The corresponding function support instruction information may include at least one of whether the core network entity supports transmitting and receiving user plane data of an ambient IoT terminal through a control plane / NAS PDU / container / message, whether the base station / general terminal / auxiliary node supports transmitting user plane data of an ambient IoT terminal to AMF / SMF / AIoTNF / AF / AS through a control plane / NAS PDU / container / message, and whether the user plane data of an ambient IoT terminal is supported through an N3 tunnel to a UPF.

[0169] As another example, a core network control plane entity (e.g., AMF / SMF / AIoTNF) may receive a request message from an AF and / or AIoTNF / NEF providing the application to trigger a service (e.g., receiving user data, receiving identification information, receiving location / sensor information, configuring / setting management information (e.g., enable / disable, disable time duration), reading / writing (memory)) for an ambient IoT terminal. A base station / general terminal / auxiliary node may receive a message for requesting a service trigger for an ambient IoT terminal through the core network control plane entity (e.g., AMF / SMF / AIoTNF). The service trigger request message may include information for requesting terminal context setup to the base station / general terminal / auxiliary node. The service trigger request message may be transmitted via a terminal context setup request message. The service trigger request message may include information for requesting / instructing network registration for the ambient IoT terminal. The service trigger request message may include information for requesting / instructing registration for a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal. The service trigger request message may be transmitted including ambient IoT terminal support indication information. The ambient IoT terminal support indication information may include at least one of ambient IoT terminal capability, whether to support transmitting / receiving user plane data of the ambient IoT terminal through a control plane / NAS PDU / container / message, whether to support transmitting user plane data of the ambient IoT terminal from the base station to AMF / SMF / AIoTNF / AF / AS through a control plane / NAS PDU / container / message, and whether to support transmitting / receiving user plane data of the ambient IoT terminal to UPF through an N3 tunnel.

[0170] When a base station / general terminal / auxiliary node transmits a message to the ambient IoT terminal to trigger a service for the ambient IoT terminal in order to receive service-related data from the ambient IoT terminal, and receives any data / message from the ambient IoT terminal, the base station / general terminal / auxiliary node may transmit a control plane message (e.g., an NGAP message or an SBI message) containing the received data / message (or based on the data / message) to the core network control plane entity. If the control plane message uses an NGAP message, the NGAP message may be a response message to a service trigger request. The NGAP message may include a message for requesting / instructing / confirming registration for the ambient IoT terminal. The NGAP message may be a message for responding to the setup of a terminal context. The NGAP message may be transmitted through a terminal context setup response message. The message may be transmitted by the base station to the core network control plane entity (e.g., AMF / SMF / AIoTNF) including ambient IoT terminal support indication information. The ambient IoT terminal support indication information may include at least one of ambient IoT terminal capability, whether to support transmitting and receiving user plane data of the ambient IoT terminal through the control plane / NAS PDU / container / message, whether to support transmitting user plane data of the ambient IoT terminal from the base station to AMF / SMF / AIoTNF / AF / AS through the control plane / NAS PDU / container / message, and whether to support transmitting and receiving user plane data of the ambient IoT terminal to UPF through the N3 tunnel. The ambient IoT terminal support indication information may be set based on information received through the terminal. And / or ambient IoT terminal support instructions can be set based on base station capabilities / support.And / or ambient IoT terminal support instructions can be set based on the capabilities / support of the core network control plane entity (e.g., AMF / SMF / AIoTNF).

[0171] As another example, when the auxiliary node (or support node) of FIG. 7b or the general terminal (for example, a terminal that is distinct from the corresponding ambient IoT terminal) of FIG. 7c transmits a message to trigger a service for the ambient IoT terminal (for example, receiving user data, receiving identification information, receiving location / sensor information, configuring / setting management information (for example, enable / disable, disable time duration), reading / writing (memory)) in order to receive data related to the service from the corresponding ambient IoT terminal, and / or when the support node / general terminal receives any data / message transmitted by the corresponding ambient IoT terminal triggered by the corresponding support node / general terminal, the support node / general terminal transmits a message for requesting registration for the corresponding ambient IoT terminal (or an initial terminal message, or a message for transmitting information received from the corresponding ambient IoT terminal, or information linked to the corresponding ambient IoT terminal (for example, location information, the corresponding ambient A message for transmitting identification information of a general terminal / auxiliary node accessed by an IoT terminal, identification information of a cell accessed by a general terminal / auxiliary node accessed by the ambient IoT terminal, or a message for setting up a terminal context may be transmitted to a core network control plane entity (e.g., AMF / SMF / AIoTNF) and / or a base station providing a cell accessed by the general terminal / auxiliary node accessed by the ambient IoT terminal. A message transmitted by a support node / general terminal to a core network control plane entity (e.g., AMF / SMF / AIoTNF) may include information received from the ambient IoT terminal and / or information associated with the terminal. A message transmitted by a support node / general terminal to a core network control plane entity may include ambient IoT terminal support instruction information.The ambient IoT terminal support instruction information may include at least one of ambient IoT terminal capability, whether to support transmitting and receiving user plane data of the ambient IoT terminal through a control plane / NAS PDU / container / message, whether to support transmitting user plane data of the ambient IoT terminal from a base station to AMF / SMF / AIoTNF / AF / AS through a control plane / NAS PDU / container / message, and whether to support transmitting and receiving user plane data of the ambient IoT terminal to UPF through an N3 tunnel.

[0172] As another example, a message for confirming / responding to a registration directed by a core network control plane entity to a support node / general terminal / base station (or a message for accepting a registration or setting up a terminal context) may include information indicating support for a corresponding function in the core network (or information for confirming / responding to support for the corresponding function in the core network, or information for requesting support for the corresponding function in the core network). The information indicating support for a corresponding function may include at least one of whether the core network entity supports transmitting / receiving user plane data of an ambient IoT terminal through a control plane / NAS PDU / container / message, whether the base station supports transmitting user plane data of an ambient IoT terminal to AMF / SMF / AIoTNF / AF / AS through a control plane / NAS PDU / container / message, and whether the base station supports transmitting / receiving user plane data of an ambient IoT terminal to a UPF through an N3 tunnel.

[0173] Figure 9 is a flowchart illustrating a method of operating a terminal according to one embodiment of the present specification.

[0174] Referring to FIG. 9, a terminal receives a first message for triggering a specific service from a network (S901). Here, the terminal may correspond to an ambient IoT device, and the network may correspond to a base station and / or a core network.

[0175] After receiving the first message, the terminal transmits the second message to the network (S902). Here, at least one of the first message and the second message may include a Non-Access Stratum (NAS) container in a Medium Access Control (MAC) Protocol Data Unit (PDU).

[0176] The NAS container may contain NAS layer messages between an ambient IoT (Internet of Things) terminal and an Ambient IoT Network Function (AIoTNF). And / or, the NAS container may contain user plane data.

[0177] The first message described above may include at least one of ambient IoT (Internet of Things) related identifier information, service type information, access timing information for radio resource control, and validity period information. Here, the ambient IoT related identifier information may include at least one of an ambient IoT terminal identifier, an ambient tag identifier, an application identifier, a service identifier, a protocol identifier, and a group identifier, and the service type information may include at least one of an inventory service, a read service, a write service, and a disable service.

[0178] User plane data that may be included in a NAS container may include at least one of an ambient Internet of Things (IoT) terminal identifier, a serial number, a unique item identifier, an application identifier, location data, sensor data, measurement data, and a product-related identifier.

[0179] Meanwhile, the first message may be a paging message, and the paging message may be a MAC message distinguished by a field within the MAC PDU.

[0180] Additionally, the second message may be a MAC message distinguished by fields within the MAC PDU.

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

[0182] Figure 10 illustrates a device according to one embodiment of the present specification.

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

[0184] The first device (100a) may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or any other device related to the 4th industrial revolution field.

[0185] The second device (100b) may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or any other device related to the 4th industrial revolution field.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0202] FIG. 13 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 10 or the transmitter / receiver unit of the device illustrated in FIG. 11.

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

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

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

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

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

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

Claims

1. In a method of operating a terminal in a wireless communication system, A step of receiving a first message for triggering a specific service; and comprising the step of transmitting a second message after receiving the first message; A method wherein at least one of the first message and the second message includes a Non-Access Stratum (NAS) container in a Medium Access Control (MAC) Protocol Data Unit (PDU).

2. In paragraph 1, A method wherein the NAS container includes NAS layer messages between an ambient IoT (Internet of Things) terminal and an ambient IoT network function (AIoTNF).

3. In paragraph 1, A method wherein the NAS container includes user plane data.

4. In paragraph 1, A method wherein the first message includes at least one of ambient IoT (Internet of Things) related identifier information, service type information, access timing information for radio resource control, and validity period information.

5. In paragraph 4, A method wherein the above ambient IoT related identifier information includes at least one of an ambient IoT terminal identifier, an ambient tag identifier, an application identifier, a service identifier, a protocol identifier, and a group identifier.

6. In paragraph 4, A method wherein the above service type information includes at least one of an inventory service, a read service, a write service, and a disable service.

7. In paragraph 3, A method wherein the user plane data includes at least one of an identifier, a serial number, a unique item identifier, an application identifier, location data, sensor data, measurement data, and a product-related identifier of an ambient IoT (internet of things) terminal.

8. In paragraph 1, A method wherein the first message is a paging message.

9. In paragraph 8, A method wherein the above paging message is a MAC message distinguished through a field within the MAC PDU.

10. In paragraph 1, A method wherein the second message is a MAC message distinguished through a field within the MAC PDU.

11. As a terminal in a wireless communication system, at least one processor; and At least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor are: A step of receiving a first message for triggering a specific service, and comprising the step of transmitting a second message after receiving the first message; A terminal, wherein at least one of the first message and the second message includes a Non-Access Stratum (NAS) container in a Medium Access Control (MAC) Protocol Data Unit (PDU).

12. In paragraph 11, The above NAS container is a terminal that includes NAS layer messages between an ambient IoT (Internet of Things) terminal and an ambient IoT network function (AIoTNF).

13. In paragraph 11, The above NAS container is a terminal that contains user plane data.

14. In paragraph 11, A terminal, wherein the first message includes at least one of ambient IoT (Internet of Things) related identifier information, service type information, access timing information for radio resource control, and validity period information.

15. In paragraph 14, The above ambient IoT related identifier information is a terminal including at least one of an ambient IoT terminal identifier, an ambient tag identifier, an application identifier, a service identifier, a protocol identifier, and a group identifier.

16. In paragraph 14, The terminal, wherein the above service type information includes at least one of an inventory service, a read service, a write service, and a disable service.

17. In paragraph 13, The above user plane data includes at least one of an identifier, serial number, unique item identifier, application identifier, location data, sensor data, measurement data, and product-related identifier of an ambient IoT (internet of things) terminal.

18. In paragraph 11, The above first message is a paging message, terminal.

19. In paragraph 18, The above paging message is a MAC message distinguished by a field within the MAC PDU.

20. In paragraph 11, The second message is a MAC message distinguished by a field within the MAC PDU.

Images