Method and apparatus for processing user plane data

Abstract

A method and an apparatus for processing user plane data in a wireless communication system are provided. The terminal receives a first message for triggering a specific service from a network. In addition, the terminal transmits a second message to the network after receiving the first message, wherein at least one of the first message and the second message includes Ambient Internet of Things (IoT)-related user plane data.

Description

User plane 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., IoT).

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

[0005] One embodiment of the present specification provides a method for a wireless communication system, wherein a terminal receives a first message from a network for triggering a specific service. Furthermore, after receiving the first message, the terminal transmits a second message to the network, wherein at least one of the first message and the second message includes ambient Internet of Things (IoT)-related user plane data.

[0006] In addition, one embodiment of the present specification provides a terminal in a wireless communication system, comprising at least one processor, and at least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: receiving a first message for triggering a specific service from a network; and transmitting a second message to the network after receiving the first message, wherein at least one of the first message and the second message includes ambient IoT (Internet of Things) related user plane data.

[0007] Meanwhile, the user plane data may be included in a NAS container (Non-Access Stratum Container) between the ambient IoT terminal and the ambient IoT network function.

[0008] On the other hand, the user plane data may include at least one of an identifier of an ambient IoT terminal, a serial number, a unique item identifier, an application identifier, location data, sensor data, measurement data, and an identifier related to a product.

[0009] At least one of the first message and the second message may be transmitted via an L2 (layer 2) protocol data block. Here, the L2 protocol data block may be a MAC (Medium Access Control) Service Data Unit (SDU) or a MAC Protocol Data Unit (PDU). In addition, the MAC SDU or MAC PDU may include a specific field, and based on the specific field, whether the user plane data is included in the first message or the second message may be indicated.

[0010] Meanwhile, the MAC PDU may include field information to indicate whether the terminal has more data to send.

[0011] Certain fields that may be included in a MAC SDU or MAC PDU may be 1-bit fields.

[0012] On the other hand, the MAC PDU may include service type information. Here, the service type information may include at least one of an inventory service, a read service, a write service, and a disable service.

[0013] According to the disclosure of this specification, data can be effectively processed for a terminal providing 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 method of operating a terminal 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.” Furthermore, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be suggested as an example of “control information.”

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

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

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

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

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

[0041] Wireless Communication System

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

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

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

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

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

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

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

[0049] The numerical value of the frequency range of the NR system can be changed. For example, FR1 can include a band from 410 MHz to 7125 MHz, as shown in Table 1. That is, FR1 can include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 can include unlicensed bands. Unlicensed bands can be used for various purposes, such as for communications for vehicles (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. Alternatively, the ambient IoT device receives data / signals from the base station and transmits the data / signals to an assisting (or supporting) node. Alternatively, the ambient IoT device receives data / signals from an assisting node connected to the base station via a wireless interface (Uu) and transmits the data / signals to the assisting node. The assisting node may be referred to as a terminal reader, which is a counterpart node for a tag such as the ambient IoT device. For convenience of explanation, a node connected to the base station via a wireless interface (Uu) is referred to as an assisting node hereinafter. This is for convenience of explanation and may be referred to by any other name, such as AIoT Assisting UE, UE connected / associated with AIoT enabled RAN, AIoT UE reader, etc. In this topology, auxiliary (or support) nodes can be ambient IoT-enabled relays, Integrated Access Backhaul (IAB), UEs, repeaters, etc. In Fig. 7c, the ambient IoT device communicates bidirectionally with the UE (e.g., a general terminal). Communication between the UE and the ambient IoT device includes ambient IoT data and / or signaling.

[0096] As mentioned above, connectivity topology types for ambient IoT networks and devices have been defined, but no specific method has been provided for communication procedures and user data processing of ambient IoT terminals 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 communication procedure and a user data processing method and a device for an ambient IoT terminal that support lower complexity, smaller size, reduced capabilities, and lower power consumption compared to the existing 3GPP LPWA IoT.

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

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

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

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

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

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

[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 search for products (e.g., boxes, containers, packages, tools) in a specific area. When a request is sent from the network within a specific area, ambient IoT devices attached to these products report identifiers associated with the products, and other information such as status, measurement results, and / or location can be added. Ambient IoT sensor services (e.g., sensor data collection) allow ambient IoT devices to connect / bind with sensors. Sensor data transmission can be initiated by the ambient IoT devices. It can be triggered periodically, when the ambient IoT terminal is powered on, or by the network. The main purpose of ambient IoT tracking services (e.g., asset tracking) is to locate goods. Ambient IoT terminals attached to these goods report identifiers associated with the goods, which can then be combined with location information. Asset tracking can be initiated by an ambient IoT-supporting assisting node / UE, or by a base station, a core network entity (e.g., Access and Mobility Management Function (AMF) / Session Management Function (SMF) / Ambient IoT Service Function (AIoTNF) / Network Exposure Function (NEF)), or an application server. The location of an ambient IoT terminal can be located within a specific range of an assisting node / UE / base station.Actuator control connects ambient IoT terminals to actuators. Actuator command transmission is typically initiated by the network. Here, AIoTNF (Ambient IoT Service 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. A core network control plane entity (e.g., AMF / SMF / AIoTNF) with a terminal and a Non-Access Stratum (NAS) interface can interface with an external application server (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 an ambient IoT terminal to AIoTNF / NEF / AS. AIoTNF can perform at least one of the following functions: authentication for an ambient IoT application server / application function, registration for an ambient IoT terminal, registration for a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal, transmission of an ambient IoT service trigger / request message to a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal according to a request of the ambient IoT application server / application function, reception of a service data / confirmation / response message in response to transmission of an ambient IoT service trigger / request message from a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal, and transmission of a message received from a base station / general terminal / auxiliary node that provides wireless connection / access to the ambient IoT terminal to the ambient IoT application server / application function.Here, registration for an ambient IoT terminal or registration for a base station / general terminal / auxiliary node that provides wireless connection / access to an ambient IoT terminal represents an operation in which the AIoTNF receives, stores, and manages an ambient IoT terminal context in order to manage information related to the ambient IoT terminal.

[0107] MAC features for ambient IoT support

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

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

[0110] The network can trigger services for ambient IoT terminals (e.g., receiving user data, receiving identification information, receiving location / sensor information, configuring / setting management information (e.g., enable / disable, disable time duration), and reading / writing (memory).

[0111] When a service for an ambient IoT terminal is triggered by a network and / or when a service for the ambient IoT terminal is triggered and the ambient IoT terminal transmits an acknowledgment / response to the trigger message / signal / command to the network, the ambient IoT terminal may transmit and receive user plane data with the base station. The user plane data may include at least one of an identifier of the ambient IoT terminal, a serial number / device permanent ID, an application identifier, location / sensor / measurement data, and an identifier related to a product. The ambient IoT terminal may transmit and receive control plane / control data for network registration with the base station, service triggering for the ambient IoT terminal, ambient IoT terminal status / context management / control, radio resource control, and terminal capability exchange / transmission / reception.

[0112] For example, if user plane data is transmitted and received together with control plane data / messages (e.g., concatenate, encapsulate, include with container), the ambient IoT terminal can transmit and receive user plane data through base station and control plane signaling.

[0113] For example, an ambient IoT terminal / base station can transmit / receive user plane data by including / encapsulating application / control plane / NAS (Non Access Stratum) container (e.g., DedicatedNAS-Message) / PDU / SDU / message containing user data (or data container) within (specific / arbitrary) RRC message (e.g., ULInformationTransfer / ULInformationTransfer) through RRC layer. Here, application PDU (protocol data unit) / SDU (service data unit) represents PDU / SDU carrying the payload of one unit of information generated at the application level. Here, the control plane PDU / SDU refers to a PDU / SDU that contains control information in the interface / session between the terminal and the AS (Application Server) / AF (Application Function) / AIoTNF at a layer located above the wireless access protocol (e.g., NAS layer, Application layer, layer located between the NAS layer and the Application layer).

[0114] As another example, an ambient IoT terminal can transmit and receive user plane data by concatenating an application / control plane / NAS container / PDU / SDU / message containing (specific / arbitrary) RRC message and user data through the RRC layer.

[0115] As another example, ambient IoT terminals / base stations can transmit / receive user plane data by including / encapsulating application / control plane / NAS containers / PDUs / SDUs / messages containing user data (or containers containing user data) within control PDUs / SDUs (e.g., MAC CEs) of L2 protocols (e.g., MAC / RLC / PDCP) without an RRC layer (or without using RRC messages / RRC containers / RRC headers). A NAS container can be included as a MAC SDU within a MAC control PDU. A NAS container can be included as a specific MAC header / field within a MAC control PDU.

[0116] As another example, ambient IoT terminals / base stations can transmit / receive user plane data by including / encapsulating application / control plane / NAS containers / PDUs / SDUs / messages containing user data (or containers containing user data) within data PDUs / SDUs (e.g., MAC data PDUs) of L2 protocols (e.g., MAC / RLC / PDCP) without an RRC layer (or without using RRC messages / RRC containers / RRC headers). A NAS container can be included as a MAC SDU within a MAC data PDU. A NAS container can be included as a specific MAC header / field within a MAC data PDU.

[0117] As another example, ambient IoT terminals / base stations can transmit and receive user plane data by including / encapsulating application / control plane / NAS containers / PDUs / SDUs / messages containing user data (or containers containing user data) within PDUs / SDUs of L2 protocols (e.g., MAC / RLC / PDCP) without an RRC layer (or without using RRC messages / RRC containers / RRC headers). The MAC PDU may not include a field for distinguishing between control PDUs and data PDUs. The NAS container may be included as a MAC SDU within a MAC PDU. The NAS container may be included as a specific MAC header / field within a MAC PDU.

[0118] As another example, ambient IoT terminals / base stations can transmit / receive user plane data by concatenating (specific / arbitrary) application / control plane / NAS containers / PDUs / SDUs / messages with user data (or containers containing user data) without an RRC layer (or without using RRC messages / RRC containers / RRC headers). For example, one MAC PDU can multiplex one NAS container and one user / application data container.

[0119] As another example, ambient IoT terminals / base stations can transmit and receive user plane data via MAC PDU / CE / message without configuring / setting logical channels (e.g., Dedicated Traffic Channel (DTCH) / RLC channel / data radio bearer / signaling radio bearer) for user plane data traffic transmission.

[0120] As another example, an ambient IoT terminal / base station can transmit and receive user plane data through a logical channel (e.g., Dedicated Control Channel (DCCH)) / RLC channel / signaling radio bearer for control plane data traffic transmission without configuring / setting the logical channel (e.g., Dedicated Traffic Channel (DTCH)) / RLC channel / data radio bearer / signaling radio bearer for user plane data traffic transmission.

[0121] As another example, the ambient IoT terminal does not need to have the configuration (or any dedicated radio resource configuration) of a logical channel (e.g., DTCH) / RLC channel / data radio bearer / signaling radio bearer / MAC message) for transmitting user plane data traffic and / or a logical channel (e.g., DCCH) / RLC channel / signaling radio bearer / MAC message for transmitting control plane data traffic before any data transmission / reception is triggered from the base station / network / general terminal / auxiliary node. When any / specific data transmission / reception is triggered from the base station / network / general terminal / auxiliary node (e.g., ambient IoT service trigger), the ambient IoT terminal can determine the logical channel / RLC channel / radio bearer / MAC message according to the service trigger / data type and transmit the data to the corresponding / another base station / network / general terminal / auxiliary node. For example, when an ambient IoT terminal triggers any / specific data transmission / reception from a base station / network / general terminal / auxiliary node (e.g., ambient IoT service trigger), the logical channel identifier / RLC entity / radio bearer entity / MAC message is set according to the service trigger / data type, and the data can be transmitted to the corresponding / other base station / network / general terminal / auxiliary node.

[0122] As another example, an ambient IoT terminal / base station may be configured to transmit control plane signaling / messages that contain only control plane data and control plane / control data signaling / messages that contain user plane data.

[0123] For example, an ambient IoT terminal / base station can transmit / receive user plane data by restricting / limiting RRC messages that can contain / encapsulate / concatenate application / control plane / NAS container / PDU / SDU containing user data through the RRC layer to a specific message (e.g. message type).

[0124] As another example, an ambient IoT terminal / base station can transmit / receive control plane data by restricting / limiting the RRC message that can be transmitted to include / encapsulate control plane / NAS signaling messages / containers / PDUs / SDUs that do not contain user data through the RRC layer to another specific message.

[0125] As another example, ambient IoT terminals / base stations can transmit this by including a field to indicate whether or not it contains user data via the RRC layer.

[0126] As another example, ambient IoT terminals / base stations can use different LCIDs at the MAC layer to distinguish between control plane signaling / messages containing only control plane data and control plane signaling / messages containing user plane data.

[0127] As another example, ambient IoT terminals / base stations can define a specific field (or a field to indicate whether user data is included) to distinguish between control plane signaling / messages that contain only control plane data and control plane signaling / messages that contain user plane data, without using / including the LCID field in the MAC layer. This distinction can be made, for example, through a 1-bit field.

[0128] As another example, ambient IoT terminals / base stations can transmit / receive user plane data by restricting / limiting MAC control PDUs / messages to specific messages (e.g. message / service type) that can contain / encapsulate / concatenate application / control plane / NAS containers / PDUs / SDUs containing user data in the MAC layer without using the RRC layer.

[0129] As another example, an ambient IoT terminal / base station can transmit / receive control plane data by restricting / limiting the MAC control PDU to another specific MAC message (e.g. message / service type) that can contain / encapsulate control plane / NAS signaling messages / containers / PDUs / SDUs that do not contain user data in the MAC layer without using the RRC layer.

[0130] As another example, ambient IoT terminals / base stations may support MAC PDU / SDU formats that do not use / include the LCID (logical channel identifier) ​​field in the MAC layer, but instead include a 1-bit field (e.g., control / data) to distinguish between control plane data and user plane data.

[0131] As another example, an ambient IoT terminal / base station can transmit and receive control plane data via a specific signaling radio bearer / MAC message, as well as control plane / NAS signaling messages / containers / PDUs / SDUs that do not contain user data via the RRC layer.

[0132] As another example, an ambient IoT terminal / base station can send and receive user plane data via another specific signaling radio bearer / MAC message, and control plane / NAS message / container / PDU / SDU containing user data via the RRC layer.

[0133] As another example, an ambient IoT terminal / base station can transmit / receive an application / control plane / NAS container / PDU / SDU / message containing (specific / arbitrary) user data via a MAC PDU / SDU / CE / message without an RRC layer (or without using an RRC message / RRC container / RRC header). The MAC PDU / SDU / CE / message can indicate / distinguish that the data is an application / control plane / NAS container / PDU / SDU / message containing user plane data via an LCID, or via a specific field included in the MAC PDU without using an LCID. The LCID or the specific field can be pre-configured in the terminal or indicated by the base station / network / core network.

[0134] As another example, an ambient IoT terminal / base station can transmit / receive (specific / arbitrary) user data (or a data container containing user data) via MAC PDU / SDU / CE / message without an RRC layer. The MAC PDU / SDU / CE / message can indicate / distinguish that the data is an application / control plane / NAS container / PDU / SDU containing user plane data via an LCID, or via a specific field included in the MAC PDU without using an LCID. The LCID or the specific field can be pre-configured in the terminal or indicated by the base station.

[0135] As another example, if the data received from the upper layer is an application / control plane / NAS message / container / PDU / SDU containing user data, the ambient IoT terminal / base station can transmit and receive data through an LCID linked / mapped to the application / control plane / NAS message / container type or a MAC PDU / SDU / CE / message containing the specific field.

[0136] As another example, if the data received from the upper layer is user data (or a data container / PDU / SDU containing user data), the ambient IoT terminal / base station can transmit and receive data through an LCID linked / mapped to the corresponding data container / PDU / SDU type or a MAC PDU / SDU / CE / message containing the corresponding specific field.

[0137] As another example, an ambient IoT terminal / base station may include a field (e.g., payload) in the upper layer header to distinguish whether the data received by the MAC entity from the upper layer contains user plane data.

[0138] As another example, an ambient IoT terminal / base station can transmit and receive control plane / NAS signaling messages / containers / PDUs / SDUs that do not contain user data via MAC PDUs / SDUs without an RRC layer. The MAC PDUs / SDUs can indicate / distinguish that the data is a NAS container containing control plane data via an LCID or a specific field included within the MAC PDU without using an LCID. The LCID or the specific field can be pre-configured in the terminal or indicated by the base station.

[0139] For another example, an ambient IoT terminal may transmit / receive a physical channel (e.g., PDSCH / PUSCH, or PDSCH / PUSCH dedicated to the ambient IoT terminal) containing user plane data and / or control plane data together with (or included in a single message) a random access physical channel (e.g., PRACH (physical random access channel), or PRACH dedicated to the ambient IoT terminal, or physical access channel dedicated to the ambient IoT terminal).

[0140] For another example, an ambient IoT terminal may transmit user plane data of the ambient IoT terminal by including it in a MAC PDU / SDU. For example, the ambient IoT terminal may transmit and receive control plane / NAS container / message / PDU / SDU to and from a base station through a MAC PDU / CE (Control Element). For another example, the ambient IoT terminal may transmit and receive user plane data to and from a base station through a MAC PDU / SDU having a 1-octet MAC subheader including a logical channel identifier (LCID) field. For another example, a dedicated MAC format for the ambient IoT terminal may be defined. For another example, the ambient IoT terminal may transmit and receive user plane data to and from a base station through a MAC PDU / SDU having a 2-octet MAC subheader including a logical channel identifier (LCID) field and an (8-bit / 16-bit) length (L) field. As another example, considering that an ambient IoT terminal has a maximum size of 1K, it can transmit and receive user plane data to and from a base station through a MAC PDU / SDU having a 2-octet MAC subhead that includes a 10-bit length (L) field and a 6-bit (or less) logical channel identifier (LCID) field.

[0141] For example, when an ambient IoT service is triggered by a network, collisions can be avoided during the wireless access process of the ambient IoT terminal.

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

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

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

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

[0146] For example, based on the indicated / pre-configured / set access timing information, the ambient IoT terminal may attempt to access by transmitting a wireless signal through the indicated / pre-configured / set frequency band / channel / subchannel. The access timing information represents wireless resource information in the time domain used by the ambient IoT terminal to transmit a response message in response to receiving a paging message. The wireless signal may represent a message including service response information for the ambient IoT terminal. Accordingly, the base station may identify the ambient IoT terminal. The access timing information may include at least one of a start subframe / slot, a duration, a validity period, an available time slot, an available time slot range, and a maximum time slot. As another example, after the base station generates a carrier frequency and receives the service trigger message, the ambient IoT terminal may initiate / start access / communication for transmitting a message including service response information for the ambient IoT terminal. As another example, the ambient IoT terminal may initiate / start access / communication for transmitting a message including service response information to the ambient IoT terminal based on one or more pieces of information included in the access timing information at a specific point in time when the base station generates a carrier frequency and receives the corresponding service trigger message. As another example, the ambient IoT terminal may generate a random number in the range from 0 to the indicated number of time slots, and initiate / start access / communication for transmitting a message including service response information to the ambient IoT terminal in a time slot matching the random number.

[0147] In another example, the presence of a wireless signal on a given frequency band / channel / subchannel may be detected during a designated / pre-configured / set / specific time / period / duration. The time / period / duration may be pre-configured as a fixed value or may be configured / setup / applied as directed by the base station. In another example, the time / period / duration may be determined by multiplying (or adding) a specific integer value generated through random number generation by another specific fixed value. In another example, if a wireless signal is detected, a random number may be generated to attempt / retry collision avoidance. Otherwise, the wireless signal may be transmitted on the given frequency band / channel / subchannel after another specific time / period / duration (or based on access timing information) after the completion of the detection time. In another example, the time / period / duration may be pre-configured as a fixed value or may be configured as directed by the base station. For another example, the time / period / duration may be determined by multiplying (or adding) a specific integer value generated through random number generation to another specific fixed value.

[0148] RLC / PDCP features for ambient IoT support

[0149] As mentioned above, in typical use cases, the message size is small, around 100 bits or no more than 1K bit. Therefore, the radio link control (RLC) layer, which provides automatic repeat request (ARQ), segmentation, etc., and / or the packet data convergence protocol (PDCP) layer, which provides SNs (sequence numbers) maintenance / management, header compression, ciphering / deciphering, timer-based SDU discard, reordering, duplicate discarding, etc., may be unnecessary. Alternatively, it may be desirable to utilize the corresponding sublayers transparently.

[0150] For example, ambient IoT terminals and base stations may not include an RLC layer. Upper layer control plane data (e.g., NAS signaling, RRC signaling, NAS containers containing user data, RRC messages containing NAS containers containing user data) and / or upper layer user plane data (e.g., user data, containers containing user data) may be mapped / associated with logical channels and submitted / transmitted to or received from the MAC layer / entity.

[0151] For another example, the RLC layer between an ambient IoT terminal and a base station can be configured to support only transparent mode. The ambient IoT terminal and the base station can be configured with a TM (transparent mode) RLC entity. The TM-RLC entity can include a transmit buffer, which can receive RLC SDUs from upper layers and transmit RLC PDUs / SDUs to a peer receiving RLC entity through lower layers. TM mode does not include any RLC header and consists only of data fields.

[0152] For another example, ambient IoT terminals and base stations may not include a PDCP layer. Upper layer control plane data (e.g., NAS signaling, RRC signaling, RRC messages including NAS containers containing user data) and / or upper layer user plane data (e.g., user data, containers including user data) may be mapped / associated with logical channels and submitted / transmitted to or received from a MAC layer / entity. Alternatively, upper layer control plane data and / or upper layer user plane data may be mapped / associated with an RLC channel and submitted / transmitted to or received from a TM mode RLC layer / entity.

[0153] For example, the PDCP TM mode can be defined and the PDCP layer between the ambient IoT terminal and the base station can only support the transparent mode. For convenience of explanation, the mode for supporting PDCP between the ambient IoT terminal and the base station is denoted as PDCP TM mode. This is for convenience of explanation and can be changed to any other name. The ambient IoT terminal and the base station can be configured with a TM PDCP entity. The TM-RLC entity can include a transmit buffer. Through this, it can receive PDCP SDUs from the upper layer and transmit PDCP PDU / SDUs to the peer receiving PDCP entity through the lower layer. For example, the PDCP TM mode can be configured to not include any PDCP header (e.g., R (Reserved) field, D / C (Data / Control) field, PDCP SN (Sequence Number) field, MAC-I (Message Authentication Code-Integrity) field) and to consist only of the data field. As another example, PDCP TM mode may not perform at least one of the following operations: PDCP SN maintenance, header compression, ciphering / deciphering, timer-based SDU discard, reordering, duplicate discard, routing for split bearer, and out-of-order delivery. As another example, PDCP TM mode may not include the PDCP SN field. As another example, PDCP TM mode may not include PDCP control PDU / SDU. As another example, upper layer control plane data and / or upper layer user plane data may be mapped / associated with the radio bearer and submitted / transmitted to or received from the TM mode PDCP layer / entity.

[0154] For example, integrity protection and confidentiality / ciphering / deciphering of user plane data for ambient IoT terminals can be provided using NAS PDU / SDU integrity protection and ciphering. The ambient IoT terminal and the AMF can perform NAS PDU / SDU integrity protection and ciphering. For example, NAS messages between the ambient IoT terminal and the AIoTNF can perform one or more of integrity protection and ciphering based on corresponding security parameter information (e.g., a security key used for decryption / verification of encrypted AIoT device identification information in the AIoT device, a fresh value (which changes to prevent trace), a counter, a security algorithm). One or more of the corresponding security parameter information can be included in the NAS message. One or more of the corresponding security parameter information can be pre-configured in the ambient IoT terminal and the AIoTNF. One or more of the security parameter information may be configured / instructed to the ambient IoT terminal by AIoTNF.

[0155]

[0156] For example, for ambient IoT terminals, integrity protection and confidentiality / ciphering / deciphering of user plane data can be performed by the ambient IoT terminal and SMF / AIoTNF / NEF / AF / AS. For example, the ambient IoT terminal and the base station can transmit and receive scrambled (e.g., CRC (cyclic redundancy check) scramble) data using the identifier of the terminal (or a part of the identifier of the terminal or a specific bit range of the identifier of the terminal).

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

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

[0159] After receiving the first message, the terminal transmits a second message to the network (S802). Here, at least one of the first message and the second message may include ambient IoT (Internet of Things)-related user plane data.

[0160] Meanwhile, the user plane data may be included in a NAS container (Non-Access Stratum Container) between the ambient IoT terminal and the ambient IoT network function.

[0161] On the other hand, the user plane data may include at least one of an identifier of an ambient IoT terminal, a serial number, a unique item identifier, an application identifier, location data, sensor data, measurement data, and an identifier related to a product.

[0162] At least one of the first message and the second message may be transmitted via an L2 (layer 2) protocol data block. Here, the L2 protocol data block may be a MAC (Medium Access Control) Service Data Unit (SDU) or a MAC Protocol Data Unit (PDU). In addition, the MAC SDU or MAC PDU may include a specific field, and based on the specific field, whether the user plane data is included in the first message or the second message may be indicated.

[0163] Meanwhile, the MAC PDU may include field information to indicate whether the terminal has more data to send.

[0164] Certain fields that may be included in a MAC SDU or MAC PDU may be 1-bit fields.

[0165] On the other hand, the MAC PDU may include service type information. Here, the service type information may include at least one of an inventory service, a read service, a write service, and a disable service.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. In a method of operating a terminal in a wireless communication system, A step of receiving a first message for triggering a specific service; and comprising the step of transmitting a second message after receiving the first message; A method wherein at least one of the first message and the second message includes ambient IoT (Internet of Things) related user plane data.

2. In paragraph 1, A method in which the above user plane data is included in a NAS container (Non-Access Stratum Container) between an ambient IoT terminal and an ambient IoT network function.

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

4. In paragraph 1, A method wherein at least one of the first message and the second message is transmitted via an L2 (layer 2) protocol data block.

5. In paragraph 4, The above L2 protocol data block is a MAC (Medium Access Control) SDU (Service Data Unit) or MAC PDU (Protocol Data Unit), The above MAC SDU or MAC PDU contains specific fields, A method in which, based on the specific field, it is indicated whether the user plane data is included in the first message or the second message.

6. In paragraph 5, A method wherein the MAC PDU includes field information for indicating whether the terminal has more data to send.

7. In paragraph 5, The above specific field is a 1-bit field.

8. In paragraph 5, A method wherein the above MAC PDU includes service type information.

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

10. As a terminal in a wireless communication system, at least one processor; and At least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor are: A step of receiving a first message for triggering a specific service, and comprising the step of transmitting a second message after receiving the first message; A terminal, wherein at least one of the first message and the second message includes ambient IoT (Internet of Things) related user plane data.

11. In paragraph 10, The above user plane data is included in a NAS container (Non-Access Stratum Container) between an ambient IoT terminal and an ambient IoT network function.

12. In paragraph 10, The above user plane data includes at least one of an identifier of an ambient IoT terminal, a serial number, a unique item identifier, an application identifier, location data, sensor data, measurement data, and an identifier related to a product.

13. In paragraph 10, A terminal, wherein at least one of the first message and the second message is transmitted via an L2 (layer 2) protocol data block.

14. In paragraph 13, The above L2 protocol data block is a MAC (Medium Access Control) SDU (Service Data Unit) or MAC PDU (Protocol Data Unit), The above MAC SDU or MAC PDU contains specific fields, A terminal, wherein, based on the specific field, it is indicated whether the user plane data is included in the first message or the second message.

15. In paragraph 14, The terminal, wherein the MAC PDU includes field information for indicating whether the terminal has more data to send.

16. In paragraph 14, The above specific field is a 1-bit field, terminal.

17. In paragraph 14, The above MAC PDU includes service type information, terminal.

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

Images