Method and device for processing data

Abstract

A method and a device for processing data in a wireless communication system are provided. The device receives a medium access control (MAC) service data unit (SDU) for an ambient internet of things (IoT) service from an upper layer, generates a MAC protocol data unit (PDU) including a MAC header on the basis of the received MAC SDU, and then submits the generated MAC PDU to a lower layer, wherein the MAC header includes a segmentation indication field.

Description

Data processing method and device

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

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

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

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

[0005] One embodiment of the present specification provides a method for receiving, in a wireless communication system, a Medium Access Control (MAC) Service Data Unit (SDU) for an ambient Internet of Things (IoT) service from a higher layer. Then, based on the received MAC SDU, a MAC Protocol Data Unit (PDU) including a MAC header is generated. Subsequently, the generated MAC PDU is submitted to a lower layer, and the MAC header includes a segmentation indication field.

[0006] In addition, one embodiment of the present specification provides a wireless communication system comprising at least one processor, and at least one memory storing instructions and being operably electrically connected to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: receiving a MAC (Medium Access Control) SDU (Service Data Unit) for an ambient IoT (Internet of Things) service from a higher layer; and generating a MAC PDU (Protocol Data Unit) including a MAC header based on the received MAC SDU. Thereafter, the generated MAC PDU is submitted to a lower layer, and the MAC header includes a segmentation indication field.

[0007] Meanwhile, the device can segment a MAC SDU received from an upper layer into MAC SDU segments. This allows a MAC SDU segment to be included in a MAC PDU, and if this MAC SDU segment is not the last MAC SDU segment, a segmentation indication field can indicate that there is more data to be transmitted.

[0008] Alternatively, the device may segment a MAC SDU received from an upper layer into MAC SDU segments. This allows the MAC SDU segment to be included in a MAC PDU, and if this MAC SDU segment is the last MAC SDU segment, the segmentation indication field may indicate that there is no more data to be transmitted.

[0009] On the other hand, the device can receive wireless resource information from a reader, and the received wireless resource information can include information on the size of data to be transmitted.

[0010] The above MAC SDU may be a Non-Access Stratum (NAS) PDU. Here, the NAS PDU may include a NAS layer message between an ambient IoT (Internet of Things) terminal and an ambient IoT network function (AIoTNF).

[0011] The segmentation indication field included in the MAC header may be 1 bit.

[0012] Meanwhile, if the MAC PDU contains one MAC SDU, the segmentation indication field may indicate that there is no more data to be sent.

[0013] According to the disclosure of this specification, it is possible to effectively provide data processing for ambient IoT devices that provide ultra-low complexity and ultra-low power in a wireless communication system.

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

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

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

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

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

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

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

[0021] Figure 8 is a flowchart illustrating a data processing method according to one embodiment of the present specification.

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

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

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

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

[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.” Additionally, 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 a single numerology (e.g., SCS, CP length, etc.). A terminal can be configured with up to N (e.g., 4) BWPs in the downlink and uplink, respectively. Downlink or uplink transmission is performed through an activated BWP, and at a given time, only one BWP among the BWPs configured for the terminal can be activated. In the resource grid, each element is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[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 the convenience of explanation, the node is referred to as a base station hereinafter. This is for the convenience of explanation and may be referred to by any other name such as AIoT RAN node, AIoT RAN Reader, AIoT base station, or AIoT BS Reader. Communication between the base station and the ambient IoT device includes ambient IoT data and / or signaling. The base station transmitting to the ambient IoT device and the base station receiving from the ambient IoT device may be the same base station or different base stations.

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

[0096] As mentioned above, although connectivity topology types for ambient IoT networks and devices have been defined, no specific method has been provided for communication procedures and user data processing for ambient IoT devices that support lower complexity, smaller size, reduced capabilities, and lower power consumption compared to existing 3GPP LPWA (Low-Power Wide-Area) IoT.

[0097] To solve these problems, the present invention proposes a data processing method and device for providing communication of ambient IoT devices that support lower complexity, smaller size, reduced capabilities, and lower power consumption compared to existing 3GPP LPWA IoT.

[0098] 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 NR / 5GS standards (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.

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

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

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

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

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

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

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

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

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

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

[0110] In addition, in the present specification, RD / DR link resource / scheduling information includes: (for RD / DR link communication) start time / subframe / slot / symbol, (for RD / DR link communication) start time / subframe / slot / symbol offset, (for RD / DR link communication) start time / subframe / slot / symbol based on a specific reference time, (for RD / DR link communication) start time / subframe / slot / symbol offset based on a specific reference time, (for RD / DR link communication) duration, (RD / DR link) transmission ocassion, (RD / DR link) transmission cycle, available time slot, available time slot range, maximum number of time slots, uplink / downlink start time / subframe / slot / symbol of the associated base station / auxiliary terminal for indicating RD / DR link start time, start time / subframe / slot / symbol offset, RD / DR link frequency domain information, RD / DR link subchannel number / index, It may include at least one of the following information: RD / DR link frequency offset, RD / DR link MCS, RD / DR link transmission block size / transmission data size, communication range / Range, location information, priority, RD / DR link retransmission count, and (RD / DR link communication) validity period / time.

[0111] Segmentation method on RD / DR link

[0112] In the representative use cases of the aforementioned ambient IoT services, message sizes are small, typically around 100 bits or no more than 1,000 bits. Considering this, the RD / DR communication protocol can be designed with a maximum message size of 1,000 bits for either the maximum message size received from or transmitted by an ambient IoT device. Considering the low complexity and power of ambient IoT devices, segmentation of packets with maximum message sizes may be necessary. For this purpose, the following methods can be considered.

[0113] For example, segmentation functions and / or sequence number (SN) processing functions can be supported at the MAC (Medium Access Control) layer of an ambient IoT device and a base station / auxiliary terminal / general terminal (peered therewith). Segmentation functions and / or sequence number processing functions can be provided without the RLC (Radion Link Control) / PDCP (Packet Data Convergence Protocol) layer.

[0114] A MAC entity can perform segmentation function for a single data received from an upper layer (e.g., Upper layer SDU / PDU, IP SDU / PDU, A-IoT application SDU / PDU, NAS SDU / PDU, etc.).

[0115] If the whole MAC SDU fits in the RD / DR transmission resources of the MAC entity, i.e., if the total size of the MAC PDU (including the MAC header to the MAC SDU) fits in the RD / DR transmission block size / transmission data size, the MAC entity may not segment (or not segment) a single data (e.g., NAS SDU / PDU) received from the upper layer.

[0116] Otherwise, the MAC entity may segment the segments to maximize the size of the segments to fill the available RD / DR transmission resources / grants for the RD / DR transmission occasion.

[0117] The MAC header may include a sequence number field, which can be used to distinguish sequence numbers and control them (e.g., to remove duplicates).

[0118] For example, a MAC header (or subheader, referred to as header hereinafter for convenience of explanation, but also included in the subheader is included in the scope of the present invention) may include a sequence number field. The sequence number may indicate a counter value of a transmitted packet / SDU (Service Data Unit) / PDU (Protocol Data Unit). The sequence number / counter may start from 0. The MAC entity may increment / accumulate by 1 (for example, increment by one for every MAC SDU) each time an upper layer packet (e.g., NAS SDU / PDU) is processed. The sequence number may be calculated with a modular value. For example, if provided with 5 bits, it may have a modular value of 32. Or, if provided with 6 bits, it may have a modular value of 64.

[0119] As another example, the MAC header may include a sequence number field with a specific bit length. The bit length may be indicated / configured by the network, or the bit length may be pre-configured.

[0120] As another example, the bit length of the sequence number field may be defined and distinguished by the capabilities of the corresponding device. Alternatively, the bit length of the sequence number field may be applied / preconfigured / configured / indicated based on (or linked to) the device type.

[0121] As another example, the MAC header may include a segment number field. This segment number is used when slicing and processing upper-layer packets. The first segment number of a MAC SDU is 0. Subsequent segments are sequentially incremented / accumulated by 1 to facilitate frame reconstructing. For example, the segment number may be provided as 3 bits. Alternatively, the segment number may be provided as 2 bits.

[0122] As another example, the MAC header may include a field (e.g., 1 bit) to indicate whether the corresponding segment is the last MAC SDU segment of the MAC SDU containing the corresponding segment. For convenience of explanation, this is referred to as a segmentation indication field hereinafter. This is for convenience of explanation and may be replaced with any other name (e.g., last MAC SDU segment indication field, more data / data segment presence indication field, segmentation / segment presence indication field, etc.). The last MAC SDU segment belonging to a MAC SDU may have this field set to a specific value (e.g., 1 / 0). For example, in an ambient IoT device, if the MAC PDU is transmitted including the last MAC SDU segment belonging to a MAC SDU, the MAC entity may indicate that there is no more data to send (e.g., there is no more data, there is no more MAC segment) because all MAC SDU segments belonging to the corresponding MAC SDU have been transmitted.

[0123] Except for the last segment, all other segments may have that field set to a different value (e.g., 0 / 1) than the above-mentioned specific value. For example, in an ambient IoT device, if the MAC PDU transmits any one MAC segment other than the last MAC SDU segment belonging to a MAC SDU, the MAC entity may indicate that there is more data to send (e.g., there is more data, there are more MAC segments) because it must transmit at least the last MAC SDU segment belonging to the MAC SDU.

[0124] If the total size of the MAC PDU (which includes the MAC header added to the MAC SDU in the ambient IoT device) fits the RD / DR transmission block size / transmission data size, the MAC entity does not segment one data (e.g., NAS SDU / PDU) received from the upper layer, but transmits one MAC PDU containing one MAC SDU. In this case, the MAC entity has no more segments to send. Therefore, it can indicate this by setting the field (segmentation indication field) to indicate that there is no more data to send (e.g., there is no more data, there is no more MAC segment).

[0125] As another example, the MAC header may include a sequence number field. The sequence number may start from 0. The MAC entity may increment / accumulate the sequence number by 1 for every segmented MAC SDU processed. The sequence number may be calculated using a modular value. For example, if provided with 5 bits, it may have a modular value of 32. Or, if provided with 6 bits, it may have a modular value of 64.

[0126] As another example, the MAC header may include a field to indicate whether an SDU is segmented (or fragmented) and whether there are other segments of that SDU. For example, if the upper layer packet is processed by MAC segmentation, all other segments except the last segment may have that field set to 1 (or 0). For example, in an ambient IoT device, if the MAC PDU is transmitted including any one MAC segment other than the last MAC SDU segment belonging to a MAC SDU, the MAC entity must transmit at least the last MAC SDU segment belonging to that MAC SDU, and thus may indicate that there is more data to send (e.g., there is more data, there is more MAC segments) through the fragmentation indication field. Alternatively, if the MAC PDU in question is transmitted including the last MAC SDU segment belonging to a MAC SDU, the segmentation indication field may indicate that there is no more data to send (e.g., there is no more data, there is no more MAC segment) because the MAC entity has transmitted all MAC SDU segments belonging to the MAC SDU.

[0127] As another example, the MAC header may include fields to indicate whether a MAC PDU contains a complete MAC SDU or the first, middle, or last segment of a MAC SDU. For example, it may contain 00 to contain all bytes of a MAC SDU, 01 to contain the first segment of a MAC SDU, 10 to contain the last segment of a MAC SDU, or 11 to contain neither the first nor the last segment of a MAC SDU. Note that 00, 01, 10, and 11 can be changed.

[0128] As another example, the MAC header may include a field (e.g., segment offset) to indicate the position of a MAC SDU segment in bytes within the original MAC SDU. The first bit / byte of the original MAC SDU may start with a zero value. The field may indicate the first bit / byte of the corresponding MAC SDU segment within the original MAC SDU. For example, when an ambient IoT device transmits a MAC PDU containing one MAC segment, the ambient IoT device may include in the MAC header information indicating the first bit / byte of the corresponding MAC SDU segment within the original MAC SDU. Alternatively, when an ambient IoT device transmits a MAC PDU containing one MAC segment and the corresponding reader successfully receives the MAC PDU, the corresponding reader may include in the ambient IoT device information indicating the first bit / byte of the corresponding MAC SDU segment within the successfully received original MAC SDU. The information may be transmitted through the MAC header included in the corresponding MAC PDU or the corresponding PRDCH control information.

[0129] As another example, the MAC header may include a segment offset start field and a segment offset end field. The segment offset start field may indicate the first bit / byte of the corresponding MAC SDU segment within the original MAC SDU. The segment offset end field may indicate the last bit / byte of the corresponding MAC SDU segment within the original MAC SDU. A field (e.g., segment offset) for indicating the position of the MAC SDU segment in bytes within the original MAC SDU may be included. The first byte of the original MAC SDU may start with a value of zero. This field may indicate the first bit of the corresponding MAC SDU segment within the original MAC SDU. For example, when an ambient IoT device transmits a MAC PDU containing one MAC segment, the ambient IoT device may include one or more of the following information in the MAC header: information about the first bit / byte of the corresponding MAC SDU segment within the corresponding MAC SDU, information about the last bit / byte of the corresponding MAC SDU segment within the corresponding MAC SDU. Alternatively, if an ambient IoT device transmits a MAC PDU containing one MAC segment, and the reader successfully receives the MAC PDU, the reader may include one or more pieces of information among bit / first byte information of the corresponding MAC SDU segment in the MAC SDU successfully received by the ambient IoT device, and last bit / byte information of the corresponding MAC SDU segment in the MAC SDU. The information may be transmitted through a MAC header included in the MAC PDU or through corresponding PRDCH control information.

[0130] As another example, a MAC PDU header may include a sequence number (SN) field only when the corresponding MAC SDU is segmented. The sequence number field may be incremented by 1 for every segmented MAC SDU.

[0131] As another example, a MAC PDU carrying the first segment of a MAC SDU may not include a field in its header to indicate the segment offset.

[0132] As another example, if a MAC PDU with duplicate sequence numbers and / or segment numbers is received, the MAC PDU (or MAC SDU or MAC SDU segment) may be discarded.

[0133] As another example, a MAC PDU may contain either a complete MAC SDU or a MAC SDU segment.

[0134] As another example, a transmitting MAC entity may generate MAC PDU(s) for each MAC SDU. The transmitting MAC entity may include relevant MAC headers / subheaders in the MAC PDU. The transmitting MAC entity may segment the MAC SDU as needed (e.g., when notified of a transmission opportunity by a lower layer and / or according to configured / indicated transmission resources and / or to fit within the indicated overall size of the MAC PDU). It may update the corresponding MAC PDUs with the MAC header / subheaders. For example, an ambient IoT device may receive radio resource information from a reader about which radio resources the ambient IoT device will transmit to the reader. This information may include transport block size / transmission data size information.

[0135] As another example, when a receiving MAC entity receives MAC PDUs, the receiving MAC entity can detect the loss of MAC SDU segments in a lower layer (e.g., the physical layer). The receiving entity can reassemble MAC SDUs from the received MAC PDUs. The receiving entity can deliver the MAC SDUs to an upper layer. The receiving entity can discard received MAC PDUs that cannot be reassembled into a single MAC SDU due to loss of a MAC PDU belonging to a specific MAC SDU in a lower layer.

[0136] As another example, if a MAC SDU or MAC SDU segment containing a MAC header / subheader is retransmitted, the MAC SDU or MAC SDU segment may be retransmitted as the MAC SDU or MAC SDU segment without re-segmentation (or re-segmentation is not supported).

[0137] As another example, if a MAC SDU or MAC SDU segment containing a MAC header / subheader is retransmitted, the MAC SDU or MAC SDU segment may be resegmented if necessary (e.g., when notified of a transmission opportunity by a lower layer and / or according to configured / indicated transmission resources and / or to fit within the overall size of the indicated MAC PDU). For example, the MAC SDU may be segmented, or the MAC SDU segment(s) may be resegmented into MAC SDU segments. For example, if an ambient IoT device transmits a MAC PDU containing a MAC segment, and the reader successfully receives the MAC PDU, the reader may include one or more of the following information in the successfully received MAC SDU: bits / first byte information of the corresponding MAC SDU segment, last bits / byte information of the corresponding MAC SDU segment in the MAC SDU. The ambient IoT device may not further segment the MAC SDU segment if the last MAC SDU segment from the last bit / byte of the previously successfully transmitted MAC SDU segment to the last bit / byte of the corresponding MAC SDU fits the RD / DR transmission resource of the MAC entity, i.e., if the total size of the corresponding MAC PDU including the MAC header to the corresponding MAC SDU segment fits the RD / DR transmission block size / transmission data size. Otherwise, the MAC entity may segment the segment to maximize the size of the segment to fill the available RD / DR transmission resource / grant for the RD / DR transmission opportunity, starting from the last bit / byte of the previously successfully transmitted MAC SDU segment.

[0138] As another example, when submitting a MAC PDU to a lower layer, the transmitting MAC entity may set the sequence number (SN) of the MAC PDU to the sequence number of the corresponding MAC SDU if the MAC PDU contains one segment of one MAC SDU.

[0139] As another example, when submitting a MAC PDU to a lower layer, the transmitting MAC entity may set the sequence number (SN) of the MAC PDU to the sequence number assigned for the newly generated (first generated) MAC PDU by the MAC SDU to which the corresponding MAC SDU segment belongs, if the MAC PDU contains one segment of one MAC SDU.

[0140] As another example, when submitting a MAC PDU to a lower layer, the transmitting MAC entity may increment the sequence number (SN) of the MAC PDU by 1 for each segment of the MAC SDU if the MAC PDU contains one or more segments of a single MAC SDU.

[0141] As another example, a timer (or time window) can be specified / configured / pre-configured to control / limit reassembly time. If the timer is not running, it can be started when a single lost MAC SDU segment is present. If a lost MAC SDU segment is received, the timer can be stopped / reset.

[0142] When this timer expires / terminated, the receiving MAC entity may discard the (unreassembled) MAC SDU segment.

[0143] As another example, when a higher layer instructs a specific MAC SDU to be discarded, the transmitting MAC entity may discard the instructed MAC SDU. If the MAC SDU or any segment of the MAC SDU is not instructed to the lower layer, the MAC SDU may be discarded.

[0144] For another example, segmentation functionality can be supported by adding an RLC layer to the ambient IoT device and the base station / auxiliary terminal / general terminal (peered with it).

[0145] For example, segmentation can be provided via RLC UM (Unacknowledged Mode).

[0146] As another example, certain data / commands / messages that do not require segmentation can be transmitted and received via RLC TM (Transparent Mode).

[0147] As another example, the RLC header may include a sequence number field. The sequence number may indicate a counter value of the transmitted packet / SDU / PDU. The sequence number / counter may start from 0. The RLC entity may increment / accumulate by 1 each time an upper layer packet is processed (e.g., increment by one for every RLC SDU). The sequence number may be calculated using a modular value. For example, if provided with 5 bits, it may have a modular value of 32. Or, if provided with 6 bits, it may have a modular value of 64.

[0148] As another example, the RLC header may include a sequence number field with a specific bit length. The bit length may be indicated / configured by the network, or the bit length may be pre-configured.

[0149] As another example, the bit length of the sequence number field may be defined and distinguished by the capabilities of the corresponding device. As another example, the bit length of the sequence number field may be applied / preconfigured / configured / indicated based on (or linked to) the device type.

[0150] As another example, the RLC header may include a segment number field. This segment number is used when slicing and processing upper-layer packets. The first segment number of an RLC SDU is 0. Subsequent segments are sequentially incremented / accumulated by 1 to facilitate frame reconstructing. For example, the segment number may be provided as 3 bits. Alternatively, the segment number may be provided as 2 bits.

[0151] As another example, the RLC header may include a field (e.g., 1 bit) to indicate whether the segment is the last RLC SDU segment of the RLC SDU containing the segment. The last RLC SDU segment in an RLC SDU may have this field set to a specific value (e.g., 1 / 0). All other segments except the last segment may have this field set to a different value (e.g., 0 / 1).

[0152] As another example, the RLC header may include a sequence number field. The sequence number may start from 0. The RLC entity may increment / accumulate the sequence number by one for every segmented RLC SDU processed. The sequence number may be calculated using a modular value. For example, if provided with 5 bits, it may have a modular value of 32. Or, if provided with 6 bits, it may have a modular value of 64.

[0153] As another example, the RLC header may include a field indicating whether an SDU is segmented (or fragmented) and whether other segments of that SDU exist. For example, if an upper layer packet is processed by RLC segmentation, all other segments except the last segment may have this field set to 1 (or 0).

[0154] As another example, the RLC header may include a field to indicate whether an RLC PDU contains a complete RLC SDU or the first, middle, or last segment of an RLC SDU. For example, it may contain 00 if it contains all bytes of an RLC SDU, 01 if it contains the first segment of an RLC SDU, 10 if it contains the last segment of an RLC SDU, or 11 if it contains neither the first nor the last segment of an RLC SDU. Note that 00, 01, 10, and 11 can be changed.

[0155] As another example, the RLC header may include a field (e.g., segment offset) that indicates the position of an RLC SDU segment in bytes within the original RLC SDU. The first byte of the original RLC SDU may start with a value of zero. This field may indicate the first byte of the corresponding RLC SDU segment within the original RLC SDU.

[0156] As another example, the RLC header may include a Segment Offset Start field and a Segment Offset End field. The Segment Offset Start field may indicate the first byte of the corresponding RLC SDU segment within the original RLC SDU. The Segment Offset End field may indicate the last byte of the corresponding RLC SDU segment within the original RLC SDU.

[0157] The original RLC SDU may include a field (e.g., segment offset) that indicates the location of an RLC SDU segment in bytes. The first byte of the original RLC SDU may start with a value of zero. This field may indicate the first byte of the corresponding RLC SDU segment within the original RLC SDU.

[0158] As another example, an RLC PDU header may include a sequence number (SN) field only when the corresponding RLC SDU is segmented. The sequence number field may be incremented by 1 for every segmented RLC SDU.

[0159] As another example, an RLC PDU carrying the first segment of an RLC SDU may not include a field in its header to indicate the segment offset.

[0160] As another example, if an RLC PDU with duplicate sequence numbers and / or segment numbers is received, the RLC PDU (or RLC SDU or RLC SDU segment) may be discarded.

[0161] As another example, one RLC PDU may contain either one complete RLC SDU or one RLC SDU segment.

[0162] As another example, a transmitting RLC entity may generate an RLC PDU(s) for each RLC SDU. The transmitting RLC entity may include the associated RLC header / subheader in the RLC PDU. The transmitting RLC entity may segment the RLC SDU as needed (e.g., when notified of a transmission opportunity by a lower layer and / or according to configured / indicated transmission resources and / or to fit within the indicated overall size of the RLC PDU). The corresponding RLC PDUs may be updated with the RLC header / subheader.

[0163] As another example, when a receiving RLC entity receives RLC PDUs, the receiving RLC entity can detect the loss of RLC SDU segments in a lower layer (e.g., the physical layer). The receiving entity can reassemble RLC SDUs from the received RLC PDUs. The receiving entity can deliver the corresponding RLC SDUs to an upper layer. The receiving entity can discard received RLC PDUs that cannot be reassembled into a single RLC SDU due to loss of one RLC PDU in a lower layer belonging to a particular RLC SDU.

[0164] As another example, if an RLC SDU or RLC SDU segment containing an RLC header is retransmitted, the RLC SDU or RLC SDU segment may be retransmitted as a corresponding RLC C SDU or a corresponding RLC C SDU segment without re-segmentation (or re-segmentation is not supported).

[0165] As another example, if an RLC SDU or RLC SDU segment containing an RLC header is retransmitted, the RLC SDU or RLC SDU segment may be resegmented if necessary (e.g., when notified of a transmission opportunity by a lower layer and / or according to configured / indicated transmission resources and / or to fit within the overall size of the indicated RLC PDU). For example, the RLC SDU may be segmented, or the RLC SDU segment(s) may be resegmented into RLC SDU segments.

[0166] As another example, when submitting an RLC PDU to a lower layer, the transmitting RLC entity may set the sequence number (SN) of the RLC PDU to the sequence number of the corresponding RLC SDU if the RLC PDU contains one segment of one RLC SDU.

[0167] As another example, when submitting an RLC PDU to a lower layer, the transmitting RLC entity may set the sequence number (SN) of the RLC PDU to the sequence number assigned for the newly generated (first generated) RLC PDU to which the RLC SDU segment belongs, if the RLC PDU contains one segment of one RLC SDU.

[0168] As another example, when submitting an RLC PDU to a lower layer, the transmitting RLC entity may increment the sequence number (SN) of the RLC PDU by 1 for each corresponding RLC SDU segment if the RLC PDU contains one or more segments of an RLC SDU.

[0169] As another example, a timer (or time window) can be instructed / configured / pre-configured to control / limit the reassembly time. If the timer is not running, it can start when a single lost RLC SDU segment is present. If a lost RLC SDU segment is received, the timer can be stopped / reset.

[0170] When the timer expires / terminated, the receiving RLC entity may discard the (un-reassembled) MAC SDU segment.

[0171] As another example, when a higher layer instructs a specific RLC SDU to be discarded, the transmitting RLC entity may discard the instructed RLC SDU. If the RLC SDU or any of the RLC SDU segments are not instructed by the lower layer, the RLC SDU may be discarded.

[0172] Figure 8 is a flowchart illustrating a data processing method according to one embodiment of the present specification.

[0173] The data processing method of FIG. 8 can be applied to an ambient IoT device, and can also be applied to a base station, auxiliary terminal, or general terminal peered with an ambient IoT device.

[0174] Referring to FIG. 8, the aforementioned device receives a MAC (Medium Access Control) SDU (Service Data Unit) for an ambient IoT (Internet of Things) service from a higher layer (S801). Then, based on the received MAC SDU, a MAC PDU (Protocol Data Unit) including a MAC header is generated (S802). Thereafter, the generated MAC PDU is submitted to a lower layer (S803). The MAC header includes a segmentation indication field.

[0175] Meanwhile, the device can segment a MAC SDU received from an upper layer into MAC SDU segments. This allows a MAC SDU segment to be included in a MAC PDU, and if this MAC SDU segment is not the last MAC SDU segment, a segmentation indication field can indicate that there is more data to be transmitted.

[0176] Alternatively, the device may segment a MAC SDU received from an upper layer into MAC SDU segments. This allows the MAC SDU segment to be included in a MAC PDU, and if this MAC SDU segment is the last MAC SDU segment, the segmentation indication field may indicate that there is no more data to be transmitted.

[0177] On the other hand, the device can receive wireless resource information from a reader, and the received wireless resource information can include information on the size of data to be transmitted.

[0178] The above MAC SDU may be a Non-Access Stratum (NAS) PDU. Here, the NAS PDU may include a NAS layer message between an ambient IoT (Internet of Things) terminal and an ambient IoT network function (AIoTNF).

[0179] The segmentation indication field included in the MAC header may be 1 bit.

[0180] Meanwhile, if the MAC PDU contains one MAC SDU, the segmentation indication field may indicate that there is no more data to be sent.

[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 9 illustrates a device according to one embodiment of the present specification.

[0183] Referring to FIG. 9, the 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 field of the 4th industrial revolution.

[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. 10 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0191] In particular, FIG. 10 is a drawing illustrating the device of FIG. 9 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 11 shows a block diagram of a processor in which the disclosure of this specification is implemented.

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

[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. 12 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 9 or the transmitter / receiver unit of the device illustrated in FIG. 10.

[0203] Referring to FIG. 12, the transceiver unit (1031) includes a transmitter (1031-1) and a receiver (1031-2). The transmitter (1031-1) includes a DFT (Discrete Fourier Transform) 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 data processing method in a wireless communication system, A step of receiving a MAC (Medium Access Control) SDU (Service Data Unit) for an ambient IoT (internet of things) service from an upper layer; A step of generating a MAC PDU (Protocol Data Unit) including a MAC header based on the received MAC SDU; and Including a step of submitting the generated MAC PDU to a lower layer, A method wherein the above MAC header includes a segmentation indication field.

2. In paragraph 1, A method further comprising a step of segmenting the received MAC SDU into MAC SDU segments.

3. In paragraph 2, The above MAC SDU segment is included in the above MAC PDU, A method in which, if the above MAC SDU segment is not the last MAC SDU segment, the segmentation indication field indicates that there is more data to be sent.

4. In paragraph 2, The above MAC SDU segment is included in the above MAC PDU, A method in which, if the above MAC SDU segment is the last MAC SDU segment, the segmentation indication field indicates that there is no more data to be sent.

5. In paragraph 1, Further comprising a step of receiving wireless resource information from a reader, A method wherein the wireless resource information includes information on the size of data to be transmitted.

6. In paragraph 1, The above MAC SDU is a NAS (Non-Access Stratum) PDU.

7. In paragraph 6, The above NAS PDU is a method including a NAS layer message between an ambient IoT (Internet of Things) terminal and an ambient IoT network function (AIoTNF).

8. In paragraph 1, The above division instruction field is 1 bit.

9. In paragraph 1, A method in which, when the above MAC PDU contains one MAC SDU, the segmentation indication field indicates that there is no more data to be sent.

10. As a device 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 MAC (Medium Access Control) SDU (Service Data Unit) for an ambient IoT (internet of things) service from an upper layer, A step of generating a MAC PDU (Protocol Data Unit) including a MAC header based on the received MAC SDU, and Including a step of submitting the generated MAC PDU to a lower layer, A device wherein the MAC header includes a segmentation indication field.

11. In paragraph 10, Based on the above instruction being executed by the at least one processor, the operations performed are: A device further comprising a step of segmenting the received MAC SDU into MAC SDU segments.

12. In paragraph 11, The above MAC SDU segment is included in the above MAC PDU, If the above MAC SDU segment is not the last MAC SDU segment, the segmentation indication field indicates that there is more data to be sent.

13. In paragraph 11, The above MAC SDU segment is included in the above MAC PDU, A device in which the segmentation indication field indicates that there is no more data to be sent if the above MAC SDU segment is the last MAC SDU segment.

14. In paragraph 10, Based on the above instruction being executed by the at least one processor, the operations performed are: Further comprising a step of receiving wireless resource information from a reader, A device wherein the wireless resource information includes information on the size of data to be transmitted.

15. In paragraph 10, The above MAC SDU is a NAS (Non-Access Stratum) PDU, device.

16. In paragraph 15, The above NAS PDU is a device that includes a NAS layer message between an ambient IoT (Internet of Things) terminal and an ambient IoT network function (AIoTNF).

17. In paragraph 10, The above division instruction field is 1 bit, device.

18. In paragraph 10, A device in which, if the above MAC PDU contains one MAC SDU, the segmentation indication field indicates that there is no more data to be sent.

Images