Method and device for supporting do-a traffic in next-generation ambient IoT system
The method and apparatus for supporting DO-A traffic in next-generation mobile communication systems optimize resource allocation and processing for low-power Ambient IoT devices, enhancing communication efficiency and data management in environments with limited mobility and energy constraints.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- SAMSUNG ELECTRONICS CO LTD
- Filing Date
- 2025-12-10
- Publication Date
- 2026-06-18
AI Technical Summary
The challenge in next-generation mobile communication systems is to enhance the operation of terminals and base stations, particularly in supporting device-originated autonomous (DO-A) traffic within Ambient IoT systems, which includes low-power devices with limited mobility and energy harvesting capabilities, and to improve communication efficiency through optimized resource allocation and processing procedures.
The solution involves a method and apparatus for terminals and base stations to support DO-A traffic by receiving and transmitting paging messages with indicators, performing random access procedures, and configuring resources for processing DO-A traffic, utilizing transceivers, processors, and memory to manage these operations effectively.
This approach enables improved communication efficiency and resource management for low-power Ambient IoT devices, ensuring efficient data transmission and reception, even in environments with limited mobility and energy constraints.
Smart Images

Figure KR2025021238_18062026_PF_FP_ABST
Abstract
Description
Method and device for supporting DO-A traffic in next-generation ambient IoT systems
[0001] The present disclosure relates to mobile communication system terminals and base station operations. The present disclosure relates to a method and apparatus for supporting DO-A (device originated - autonomous) traffic in a wireless communication system.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.
[0008] The problem to be solved in the various embodiments of the present disclosure is to provide improved operation of a terminal and a base station in a next-generation mobile communication system.
[0009] In addition, the problem to be solved in the various embodiments of the present disclosure relates to a method and apparatus for supporting DO-A traffic in a next-generation Ambient IoT (internet of things) system.
[0010] The present disclosure, for solving the above-mentioned problems, comprises a method performed by a terminal supporting DO-A (device originated - autonomous) traffic in a wireless communication system, the method including: receiving a paging message from a base station containing an indicator related to the support of said DO-A traffic; performing a random access procedure based on the indicator related to the support of said DO-A traffic; and receiving resource configuration information related to the transmission of said DO-A traffic from the base station, wherein when said DO-A traffic occurs at the terminal, the method includes triggering a procedure for processing said DO-A traffic based on the resource configuration information.
[0011] Additionally, the present disclosure relates to a method performed by a base station for device-originated autonomous (DO-A) traffic in a wireless communication system, comprising: transmitting a paging message to a terminal that includes an indicator related to the support of the DO-A traffic; performing a random access procedure based on the indicator related to the support of the DO-A traffic; and transmitting resource configuration information related to the transmission of the DO-A traffic to the terminal, wherein when the DO-A traffic occurs at the terminal, a procedure for processing the DO-A traffic based on the resource configuration information is triggered.
[0012] Additionally, the present disclosure comprises a terminal supporting DO-A (device originated - autonomous) traffic in a wireless communication system, at least one transceiver; at least one processor connected to communicate with the at least one transceiver; and a memory connected to communicate with the at least one processor and executable of the at least one processor individually or in any combination thereof, the memory storing instructions for the terminal to receive a paging message from a base station containing an indicator related to the support of the DO-A traffic, to perform a random access procedure based on the indicator related to the support of the DO-A traffic, and to receive resource configuration information related to the transmission of the DO-A traffic from the base station; wherein, when the DO-A traffic occurs in the terminal, the terminal triggers a procedure for processing the DO-A traffic based on the resource configuration information.
[0013] Additionally, the present disclosure comprises, in a base station for device-originated autonomous (DO-A) traffic in a wireless communication system, at least one transceiver; at least one processor connected to the at least one transceiver so as to be communicable with the at least one transceiver; and a memory connected to the at least one processor so as to be communicable with the at least one processor and capable of executing the at least one processor individually or in any combination thereof, the memory storing instructions for the base station to transmit a paging message to a terminal including an indicator related to the support of the DO-A traffic, to perform a random access procedure based on the indicator related to the support of the DO-A traffic, and to transmit resource configuration information related to the transmission of the DO-A traffic to the terminal; wherein, when the DO-A traffic occurs at the terminal, a procedure for processing the DO-A traffic based on the resource configuration information is triggered.
[0014] The technical problems to be solved in the embodiments of the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.
[0015] According to various embodiments of the present disclosure, improved operation of a terminal and a base station in a next-generation mobile communication system can be provided.
[0016] In addition, according to various embodiments of the present disclosure, a method and apparatus for supporting DO-A traffic in a next-generation Ambient IoT system can be provided.
[0017] FIG. 1 is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure.
[0018] FIG. 2 is a diagram showing the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure.
[0019] FIG. 3 is a diagram illustrating a topology and deployment scenario in which ambient IoT (Internet of Things) communication is supported in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0020] FIG. 4 is a diagram illustrating a use case in which Ambient IoT (Internet of Things) communication is applied in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0021] FIG. 5 is a diagram illustrating a procedure for inventorying all Ambient IoT (Internet of Things) devices in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0022] FIG. 6 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0023] FIG. 7 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0024] FIG. 8 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0025] FIG. 9 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0026] FIG. 10 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0027] FIG. 11 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0028] FIG. 12 is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure.
[0029] FIG. 13 is a block diagram showing the configuration of an NR base station according to one embodiment of the present disclosure.
[0030] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. In this regard, it should be noted that identical components in the attached drawings are indicated by the same reference numerals whenever possible. Furthermore, detailed descriptions of known functions and configurations that may obscure the essence of the present invention will be omitted.
[0031] In describing the embodiments in this specification, technical details that are well known in the technical field to which the present invention belongs and are not directly related to the present invention are omitted. This is intended to convey the essence of the present invention more clearly without obscuring it by omitting unnecessary explanations.
[0032] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.
[0033] The advantages and features of the present invention and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below but can be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.
[0034] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0035] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.
[0036] In this embodiment, the term "part" refers to a software or hardware component, such as an FPGA or ASIC, and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to operate one or more processors. Accordingly, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." Furthermore, the components and "parts" may be implemented to operate one or more CPUs within a device or secure multimedia card.
[0037] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a Node B, BS (Base Station), eNB (eNode B), gNB (gNode B), a radio access unit, a base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, embodiments of the present disclosure may be applied to other communication systems having a technical background or channel type similar to the embodiments of the present disclosure described below. Additionally, embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, provided that they do not deviate significantly from the scope of the present disclosure. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0038] Terms used in the following description to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0039] For the convenience of the following explanation, some terms and names defined in the 3GPP (3rd generation partnership project) LTE (long term evolution) standards and / or 3GPP NR (new radio) standards may be used. However, the present invention is not limited by the above terms and names and can be applied in the same way to systems conforming to other standards.
[0040] In various embodiments of the present disclosure, an Ambient-IoT device is defined as an A-IoT device, and an A-IoT device may also be defined as an IoT device. In various embodiments of the present disclosure, a Reader may be defined as a base station or an intermediate terminal, and an intermediate terminal may be defined as a terminal. In various embodiments of the present disclosure, DO-A traffic may be defined as specific traffic. In various embodiments of the present disclosure, messages such as R2D messages and D2R messages are examples of message names, and it does not exclude defining the name of the message as a different message name.
[0041] FIG. 1 is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure.
[0042] Referring to FIG. 1, as illustrated, the wireless access network of a next-generation mobile communication system (hereinafter NR or 2g) consists of a next-generation base station (New Radio Node B, hereinafter NR gNB or NR base station) (1-10) and an NR CN (1-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) (1-15) connects to an external network through the NR gNB (1-10) and the NR CN (1-05).
[0043] In FIG. 1, the NR gNB (1-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (1-15) via a wireless channel and can provide superior service compared to the existing Node B. In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device is required to collect state information such as the buffer status, available transmission power status, and channel status of the UEs and perform scheduling, and this is handled by the NR NB (1-10). A single NR gNB typically controls multiple cells. To achieve ultra-high-speed data transmission compared to current LTE, it can have a maximum bandwidth greater than the existing maximum bandwidth, and orthogonal frequency division multiplexing (hereinafter referred to as OFDM) can be used as a wireless access technology, and additional beamforming technology can be incorporated. In addition, an adaptive modulation & coding (hereinafter referred to as AMC) method is applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The NR CN (1-05) performs functions such as mobility support, bearer configuration, and QoS (quality of service) configuration. The NR CN (1-05) is a device responsible for various control functions as well as mobility management functions for the terminal, and is connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with existing LTE systems, and the NR CN (1-05) is connected to the MME (mobility management entity, 1-25) via a network interface. The MME (1-25) is connected to the existing base station eNB (1-30).
[0044] FIG. 2 is a diagram showing the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure.
[0045] Referring to FIG. 2, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (service data adaptation protocol) (2-01, 2-45), NR PDCP (packet data convergence protocol) (2-05, 2-40), NR RLC (radio link control) (2-10, 2-35), and NR MAC (medium access control) (2-15, 2-30) at the terminal and the NR base station, respectively.
[0046] The main functions of NR SDAP (2-01, 2-45) may include some of the following functions.
[0047] - User data transfer function (transfer of user plane data)
[0048] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink
[0049] - Marking QoS flow ID in both DL and UL packets for uplink and downlink
[0050] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0051] Regarding the above SDAP layer device, the terminal may receive a radio resource control (RRC) message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers using the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The above SDAP header may include QoS flow ID information indicating QoS. The above QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.
[0052] The main functions of NR PDCP (2-05, 2-40) may include some of the following functions.
[0053] Header compression and decompression (ROHC only)
[0054] - User data transfer function (Transfer of user data)
[0055] - Sequential delivery function (In-sequence delivery of upper layer PDUs)
[0056] - Out-of-sequence delivery of upper layer PDUs
[0057] - Reordering function (PDCP PDU reordering for reception)
[0058] - Duplicate detection function (Duplicate detection of lower layer SDUs)
[0059] - Retransmission of PDCP SDUs
[0060] - Encryption and decryption functions (Ciphering and deciphering)
[0061] - Timer-based SDU discard in uplink.
[0062] In the above, the reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or a function of transmitting immediately without considering the order, may include a function of recording lost PDCP PDUs by reordering, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.
[0063] The main functions of NR RLC(2-10, 2-35) may include some of the following functions.
[0064] - Data transfer function (Transfer of upper layer PDUs)
[0065] - Sequential delivery function (In-sequence delivery of upper layer PDUs)
[0066] - Out-of-sequence delivery of upper layer PDUs
[0067] - ARQ function (Error Correction through ARQ)
[0068] - Concatenation, segmentation, and reassembly functions of RLC SDUs
[0069] - Re-segmentation function (Re-segmentation of RLC data PDUs)
[0070] - Reordering function (Reordering of RLC data PDUs)
[0071] - Duplicate detection
[0072] - Error detection function (Protocol error detection)
[0073] - RLC SDU discard function
[0074] RLC re-establishment function
[0075] In the above, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from a lower layer to an upper layer in sequence; it may include a function to reassemble and deliver them if a single RLC SDU is received divided into multiple RLC SDUs; it may include a function to rearrange received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number); it may include a function to record lost RLC PDUs after rearranging the order; it may include a function to report the status of lost RLC PDUs to the transmitting side; it may include a function to request retransmission of lost RLC PDUs; if there are lost RLC SDUs, it may include a function to deliver only the RLC SDUs prior to the lost RLC SDU to the upper layer in sequence; or if a predetermined timer has expired even if there are lost RLC SDUs, it may include a function to deliver all RLC SDUs received before the timer started to the upper layer in sequence; or It may include a function that delivers all RLC SDUs received up to the present to the upper layer in order once a predetermined timer has expired, even if there are lost RLC SDUs. Additionally, the RLC PDUs mentioned above may be processed in the order they are received (regardless of the order of sequence numbers, but in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and then delivered to the PDCP device.The above NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with the multiplexing function of the NR MAC layer.
[0076] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function of reassembling and delivering them when a single RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.
[0077] The NR MAC (2-15, 2-30) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include some of the following functions.
[0078] - Mapping function (Mapping between logical channels and transport channels)
[0079] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)
[0080] - Scheduling information reporting function
[0081] - HARQ function (Error correction through HARQ)
[0082] - Priority handling between logical channels of one UE
[0083] - Priority handling between UEs by means of dynamic scheduling
[0084] - MBMS service identification function
[0085] - Transport format selection function
[0086] - Padding
[0087] The NR PHY layer (2-20, 2-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.
[0088] FIG. 3 is a diagram illustrating a topology and deployment scenario in which ambient IoT (Internet of Things) communication is supported in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0089] An Ambient IoT device (3-01, 3-02) according to the present disclosure is a device with very low maximum power consumption, capable of supporting a maximum peak power consumption of 1 µW or a peak power consumption of several hundred µW. The device can perform uplink transmission through backscattering. That is, the device can perform uplink transmission using an external carrier wave. During uplink transmission, the device may or may not perform amplification. Of course, the device may also generate uplink transmission internally. The device does not have an RRC state and does not support mobility such as cell selection or cell reselection. Furthermore, the device is a low-spec device that does not support Hybrid Automatic Repeat and reQuest (HARQ) and Automatic Repeat reQuest (ARQ).
[0090] An Ambient IoT device (3-01, 3-02) may mean a device that uses energy harvesting to generate power and may have no battery or have limited energy storage capacity.
[0091] An Ambient IoT device (3-01) can perform direct bidirectional communication with a base station (3-05). That is, the device (3-01) can transmit and receive Ambient IoT data and / or signaling (3-20) with the base station (3-05). For reference, the device (3-01) may transmit (or receive) Ambient IoT data and / or signaling to the base station (3-05) and receive (or transmit) Ambient IoT data and / or signaling from another base station (3-10). For reference, the device (3-01) may be located indoors, and the base station (3-05, 3-10) may also be located indoors. The communication may not be supported through the conventional Uu interface between the terminal and the base station, but may be supported through a new interface. In this disclosure, the new interface may be referred to as the Ax interface.
[0092] An Ambient IoT device (3-02) performs bidirectional communication with a terminal (3-15) operating as an intermediate node through an Ax interface, and accordingly, the terminal (3-15) operating as an intermediate node may also perform bidirectional communication with a base station (3-01) through a Uu interface. That is, the device (3-02) transmits and receives Ambient IoT data and / or signaling (3-25) with the terminal (3-15) operating as an intermediate node, and the terminal (3-15) operating as an intermediate node can transmit and receive Ambient IoT data and / or signaling (3-30) with the base station (3-10). For reference, the device (3-02) and the terminal (3-15) operating as an intermediate node may be located indoors, and the base station (3-10) may be located outdoors.
[0093] FIG. 4 is a diagram illustrating a use case in which Ambient IoT (Internet of Things) communication is applied in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0094] Referring to FIG. 4, a service may be provided to a specific Ambient IoT device (4-10), a service may be provided to a group of Ambient IoT devices consisting of two or more Ambient IoT devices (4-05), or a service may be provided to all Ambient IoT devices (4-01).
[0095] Figure 4-01 illustrates a scenario for an automated warehouse inventory. In this scenario, various warehousing information can be generated for the transfer of goods, storage of goods, and inventory of goods. Specifically, this scenario can be composed of five steps.
[0096] - Step 1: Verification and unloading of goods
[0097] - Step 2: Move items into the gate (gate-in inventory)
[0098] - Step 3: Inventory Management
[0099] - Step 4: Move items out of the gate (gate-out inventory)
[0100] - Step 5: Check and Loading
[0101] In the above scenario, Ambient IoT devices can be attached for each item for automated warehouse inventory, and warehouse inventory can be managed efficiently by performing an inventory procedure on all Ambient IoT devices and a command procedure, which is a procedure to write and read the characteristics of each item.
[0102] Figure 4-05 illustrates a scenario in which the surrounding environment is sensed through an Ambient IoT device. In this scenario, when planting an orchid, an Ambient IoT device is attached to the plant to monitor the plant's surrounding environment and provide the generated monitoring information to authorized users and third parties.
[0103] In the above scenario, plants can be managed efficiently by performing an inventory procedure on Ambient IoT devices attached to multiple plants (i.e., a group of Ambient IoT devices) and a command procedure, which is a procedure to activate or deactivate each Ambient IoT device.
[0104] Figure 4-10 illustrates a scenario for managing the health of the elderly through an Ambient IoT device. In this scenario, the health status of the elderly with heart disease or chronic diseases can be continuously monitored, and the generated monitoring information can be periodically provided to authorized users (e.g., doctors).
[0105] In the above scenario, the health status of an elderly person can be managed efficiently by performing an inventory procedure on an Ambient IoT device attached to a specific elderly person and a command procedure, which is a procedure to read the necessary information from the Ambient IoT device.
[0106] FIG. 5 is a diagram illustrating a procedure for inventorying all Ambient IoT (Internet of Things) devices in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0107] Referring to FIG. 5, a core network (hereinafter CN (5-08)) may initiate an inventory procedure by transmitting an Inventory request message (5-10) to a Reader (5-05) to identify all Ambient IoT (A-IoT) devices (5-01, 5-02, 5-03) or to reach all A-IoT devices (5-01, 5-02, 5-03). For reference, the CN (5-08) may refer to an AMF (access and mobility management function) for supporting Ambient IoT communication or may refer to an entity within the core network that supports Ambient IoT. The Inventory request message (e.g., message N2') may include at least one of the following information.
[0108] - Information indicating the message type: Information distinguishing whether it is an Inventory request message or a Command message
[0109] - Device Information: It may not include an indicator to perform the Inventory procedure for all A-IoT devices or a separate A-IoT device identifier. That is, while a separate identifier (Identifier or Id) must be included to indicate that one or more A-IoT devices should initiate the Inventory procedure, by omitting this, it is possible to instruct all A-IoT devices to perform the Inventory procedure.
[0110] - Periodic Information: Information for sending Inventory request messages periodically, information to send as a one-shot, or information for sending non-periodically.
[0111] In step 5-20, the Reader (5-05) that receives the Inventory request message may broadcast an Initial Trigger Message (or A-IoT Paging) to all A-IoT devices (5-01, 5-02, 5-03). The Reader (5-05) may refer to a base station (hereinafter BS) or user equipment (hereinafter UE) that supports Ambient IoT communication. The Initial Trigger Message (or A-IoT Paging) may include at least one of the information included in the Inventory request message received in step 5-10. For example, device information may be included in the Initial Trigger Message (or A-IoT Paging). Additionally, the Initial Trigger Message (or A-IoT Paging) may include at least one of the following information.
[0112] - Frequency shift or frequency channel information
[0113] - Information on parameters required to perform Slotted Aloha random access:
[0114] >> Connection Probability Information
[0115] >> Connection time information
[0116] In step 5-30, a certain A-IoT device (5-01) that has successfully received an Initial Trigger Message (or A-IoT Paging) may send Message 1 (Msg1) to Reader (5-05) to perform random access with Reader (5-05) using the slotted aloha protocol. For example, Msg 1 may mean a message containing a random access ID through a specific frequency.
[0117] In step 5-40, the Reader (5-05) may send a response message (Message 2: Msg 2) to the A-IoT device (5-01) to indicate that it has successfully received Msg 1. The A-IoT device (5-01) may store in memory the state that it has successfully performed the inventory procedure or the random access procedure. In this case, even if an Initial Trigger Message (or A-IoT Paging) for the device is subsequently received, the device may not initiate the random access procedure separately.
[0118] In step 5-50, the A-IoT device (5-01) may send message 3 (Msg 3) to the Reader (5-05) to provide additional device information. The Msg 3 may include at least one of the following information.
[0119] - Device ID information capable of additionally identifying the above A-IoT device
[0120] - Capability information of the above A-IoT device
[0121] - Capability information of the above A-IoT device
[0122] Capability information regarding whether the upper layer device of the above A-IoT device supports segmented messages
[0123] Capability information regarding whether the AS layer device of the above A-IoT device supports segmented messages
[0124] The above A-IoT device (5-01) may store in memory the state that the inventory procedure or random access procedure has been successfully performed. In this case, even if an Initial Trigger Message (or A-IoT Paging) for the device is received later, the device may not initiate a random access procedure separately.
[0125] In step 5-55, the Reader (5-05) may send a response message to the A-IoT device (5-01) to indicate that it has successfully received Msg 3. Upon receiving the response message, the A-IoT device (5-01) may store in memory the state that it has successfully performed the inventory procedure or the random access procedure. In this case, even if an Initial Trigger Message (or A-IoT Paging) for the device is subsequently received, the device may not initiate the random access procedure separately.
[0126] For reference, this step of sending a response message may be omitted.
[0127] In step 5-60, the Reader (5-05) can transmit a message received from the A-IoT device (5-01) to the CN (5-08). For reference, the message may be an Inventory response message, such as the N2' message.
[0128] In the present disclosure, an inventory procedure is initiated for all A-IoT devices (5-01, 5-02, 5-03), but only a specific A-IoT device (5-01) can successfully perform the inventory procedure. As a result, the inventory procedure can be initiated again for all remaining A-IoT devices (5-02, 5-03), excluding only the A-IoT device (5-01) that successfully performed the inventory procedure.
[0129] In step 5-70, the core network (5-08) may initiate an inventory procedure by transmitting an Inventory request message to a Reader (5-05) (5-70) to identify all remaining Ambient IoT (A-IoT) devices (5-02, 5-03) excluding the A-IoT device (5-01) that has successfully performed the Inventory procedure, or to reach all remaining Ambient IoT (A-IoT) devices (5-02, 5-03) excluding the A-IoT device (5-01) that has successfully performed the Inventory procedure. In the present disclosure, the Inventory request message may include at least one of the following information.
[0130] - Information indicating the message type: Information distinguishing whether it is an Inventory request message or a Command message
[0131] - Device Information: At least one of the following information may be included to instruct all A-IoT devices other than A-IoT device (5-01) to perform the Inventory procedure.
[0132] >> Information or list of A-IoT devices to exclude
[0133] For example, an identifier (Device ID or Random Access ID) that can identify an A-IoT device (5-01)
[0134] An indicator indicating that A-IoT device(s) that have successfully completed the inventory procedure should not perform the inventory procedure separately.
[0135] - Periodic Information: Information for sending Inventory request messages periodically, information to send as a one-shot, or information for sending non-periodically.
[0136] In step 5-80, the Reader (5-05) that received the Inventory request message may broadcast an Initial Trigger Message (or A-IoT Paging) to all remaining Ambient IoT (A-IoT) devices (5-02, 5-03), excluding the A-IoT device (5-01) that successfully performed the Inventory procedure. The Initial Trigger Message (or A-IoT Paging) may include at least one of the information contained in the Inventory request message received in step 5-70 or step 5-10. For example, device information may be included in the Initial Trigger Message (or A-IoT Paging). Of course, the Initial Trigger Message may be generated separately by the Reader based on the information received in step 5-10. At this time, the message may include at least one of the following information.
[0137] - Device Information: At least one of the following information may be included to instruct all A-IoT devices other than A-IoT device (5-01) to perform the Inventory procedure.
[0138] >> Information or list of A-IoT devices to exclude
[0139] For example, an identifier (Device ID or Random Access ID) that can identify an A-IoT device (5-01)
[0140] An indicator indicating that A-IoT device(s) that have successfully completed the inventory procedure should not perform the inventory procedure separately.
[0141] Subsequently, Ambient IoT (A-IoT) devices (5-02, 5-03) may perform an inventory procedure according to the steps described above. For example, each device (5-02, 5-03) may perform an action corresponding to 5-30 to 5-60. For reference, the devices may transmit Message 1 using a Random Access ID other than the Random Access ID used by the Ambient IoT device (5-01). That is, the Random Access ID may be re-derived.
[0142] In step 5-90, the Ambient IoT device (5-01) may send message 1 (Msg1) to the Reader (5-05) to perform random access with the Reader (5-05) using the slotted aloha protocol. At this time, the device according to the present disclosure may send a message containing some information of the random access ID used in step 5-30 and / or an indicator that the inventory procedure was successfully performed and / or the device ID used in step 5-50. Of course, the A-IoT device (5-01) may not initiate a separate random access procedure if it is stored in memory in a state that the inventory procedure or the random access procedure was successfully performed.
[0143] FIG. 6 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0144] Referring to FIG. 6, a Reader (6-05) can broadcast an A-IoT Paging message to an A-IoT device (6-01) (6-10). The Reader (6-05) may refer to a base station or terminal that supports Ambient IoT communication. The A-IoT Paging message may include at least one of the following.
[0145] - An ID that can identify an A-IoT device (6-01).
[0146] The above ID may mean an upper layer device ID that can directly identify the A-IoT device, or it may mean an AS layer ID assigned to the A-IoT device.
[0147] - Device-originated - an indicator that allows the transmission of autonomous (DO-A) traffic
[0148] The above indicator may be applied to one or more A-IoT devices capable of transmitting D0-A traffic. Additionally, the above indicator may be applied only to an ID capable of identifying the A-IoT device.
[0149] - Capability information indicating that the Reader can support DO-A traffic
[0150] - ID that can identify Reader(6-05)
[0151] >> Through the above Reader ID, the above A-IoT device (6-01) can transmit Do-A traffic only to the above Reader.
[0152] - Frequency shift or frequency channel information
[0153] - Information on parameters required to perform Slotted Aloha random access in 3-step CBRA (contention-based random access), 2-step CBRA, or 2-step CFRA (contention-free random access).
[0154] >> Connection Probability Information
[0155] The above information can be configured for 3-step CBRA, 2-step CBRA, and 2-step CFRA.
[0156] >> Connection time information
[0157] The above information can be configured for 3-step CBRA, 2-step CBRA, and 2-step CFRA.
[0158] An indicator showing which random access to perform among 3-step CBRA, 2-step CBRA, and 2-step CFRA.
[0159] The above indicator may be mapped to the A-IoT device ID described above, or it may be applied commonly to all A-IoT devices.
[0160] In step 6-20, an A-IoT device (6-01) that has successfully received an A-IoT Paging message may send message 1 (Msg 1) to Reader (6-05) to perform random access with Reader (6-05) using the slotted aloha protocol. Msg 1 may include a random access ID consisting of 16 bits. Of course, in the case of CFRA, Msg 1 may not include a random access ID. According to the present disclosure, the A-IoT device may include an indicator in Msg 1 indicating that Msg 1 was sent for DO-A traffic. Since DO-A traffic may be traffic with lower priority than other traffic, Reader (6-05) may determine whether to send Msg 2 to the A-IoT device based on the wireless resource saturation according to the indicator. Additionally, in the case of a 2-step CBRA or a 2-step CFRA, Msg 1 may include the A-IoT device ID described above in the Paging message. Additionally, Msg 1 may include capability information indicating that the A-IoT device supports DO-A traffic. The capability information that may be included in Msg 1 may be included in at least one of a 2-step CBRA, a 2-step CFRA, or a 3-step CBRA.
[0161] In step 6-30, the Reader (6-05) can send message 2 (Msg 2) to the A-IoT device (6-01). The Msg 2 may include at least one of the following.
[0162] - Random access ID included in Msg 1
[0163] - ID identifying the A-IoT device (6-01) in the A-IoT Paging message
[0164] - ACK indicating that Msg 1 sent by the A-IoT device (6-01) has been successfully received
[0165] - Wireless resource information that enables an A-IoT device to transmit the following message
[0166] - Capability information indicating that the above Reader can support DO-A traffic
[0167] Through the above capability information, Reader can determine whether the above A-IoT device can autonomously transmit traffic to Reader.
[0168] In step 6-40, the A-IoT device (6-01) may transmit message 3 (Msg 3) to the Reader (6-05) in the case of a 3-step CBRA. The Msg 3 may include the ID described above in the Paging message. When the A-IoT device (6-01) following the present disclosure transmits Msg 3 for DO-A traffic, it may include an indicator in Msg 3 indicating that it is transmitting for DO-A traffic. This may be limited to cases where Msg 1 does not include an indicator indicating that Msg 1 was transmitted for DO-A traffic. Alternatively, the Msg 3 may include capability information indicating that the A-IoT device (6-01) supports DO-A traffic. Of course, after Msg 3, the above A-IoT device (6-01) may directly send capability information indicating that it supports DO-A traffic to the Reader (6-05) as a separate D2R (Device to Reader) message, or it may send it if the Reader requests it.
[0169] In step 6-50, the Reader (6-05) may send an indicator or the next data message (e.g., a Command message) to the A-IoT device (6-01) indicating that message 3 has been successfully received.
[0170] FIG. 7 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0171] Referring to FIG. 7, a Reader (7-05) can broadcast an A-IoT Paging message to an A-IoT device (7-01) (7-10). The Reader (7-05) may refer to a base station or terminal that supports Ambient IoT communication. The A-IoT Paging message may follow the aforementioned embodiment. In addition to the above disclosure, the A-IoT Paging message may include at least one of the following.
[0172] - Random access ID range information to be included in Msg 1 may be included. For example, a specific range of IDs within 16 bits can be set. That is, when the above A-IoT device transmits Msg 1 for DO-A traffic, 2 16 - The purpose is to allow the A-IoT device to transmit a random access ID within the range of [0, 100] so that the Reader can determine whether Msg 1 is transmitted by DO-A traffic.
[0173] - Specific bit information may be included so that the random access ID to be included in Msg 1 can be sent as a specific bit instead of 16 bits. For example, if it is set to 5 bits, when the A-IoT device transmits Msg 1 for DO-A traffic, a random access ID consisting of 5 bits can be included in Msg 1. Through this, the Reader can determine whether the A-IoT device has transmitted DO-A traffic.
[0174] - Separate wireless resource information for transmitting DO-A traffic may be included.
[0175] Frequency shift or frequency channel information for DO-A traffic
[0176] Information on parameters required to perform Slotted Aloha random access in 3-step CBRA (contention-based random access), 2-step CBRA, or 2-step CFRA (contention-free random access) for DO-A traffic
[0177] >> Connection Probability Information
[0178] >>>> The above information can be configured for 3-step CBRA, 2-step CBRA, and 2-step CFRA. For reference, the above information may be additionally configured for DO-A traffic, or only some of the existing information (radio resource information configured for traffic other than DO-A traffic) may be configured.
[0179] >> Connection time information
[0180] The above information can be configured for 3-step CBRA, 2-step CBRA, and 2-step CFRA. The above information may be additionally configured for DO-A traffic, or only some of the existing information (radio resource information configured for traffic other than DO-A traffic) may be configured.
[0181] An indicator showing which random access to perform among 3-step CBRA, 2-step CBRA, and 2-step CFRA.
[0182] The above indicator may be mapped to the A-IoT device ID described above, or it may be applied commonly to all A-IoT devices.
[0183] In step 7-20, an A-IoT device (7-01) that has successfully received an A-IoT Paging message may send message 1 (Msg 1) to Reader (7-05) to perform random access with Reader (7-05) using the slotted aloha protocol. If Msg 1 is sent for DO-A traffic, Msg 1 may include a random access ID composed of bits indicated in the Paging message. Alternatively, if Msg 1 is sent for DO-A traffic, the A-IoT device (7-01) may send Msg 1 through a (random) resource set for DO-A traffic. Additionally, Msg 1 may include capability information indicating that the A-IoT device (7-01) supports DO-A traffic. The capability information that may be included in the above Msg 1 may be included in at least one of a 2-step CBRA, a 2-step CFRA, or a 3-step CBRA.
[0184] In step 7-30, the Reader (7-05) can send message 2 (Msg 2) to the A-IoT device (7-01). The Msg 2 may include at least one of the following.
[0185] - Random access ID included in Msg 1
[0186] - ID identifying the A-IoT device (7-01) in the A-IoT Paging message
[0187] - ACK indicating successful reception of Msg 1 sent by the A-IoT device (7-01)
[0188] - Wireless resource information that enables an A-IoT device to transmit the following message
[0189] - Capability information indicating that the above Reader can support DO-A traffic
[0190] Through the above capability information, Reader can determine whether the above A-IoT device can autonomously transmit traffic to Reader.
[0191] In step 7-40, the A-IoT device (7-01) may transmit message 3 (Msg 3) to the Reader (7-05) in the case of a 3-step CBRA. The Msg 3 may include the ID described above in the Paging message. When the A-IoT device (7-01) following the present disclosure transmits Msg 3 for DO-A traffic, it may include an indicator in Msg 3 indicating that it is transmitting for DO-A traffic. This may be limited to cases where Msg 1 does not include an indicator indicating that Msg 1 was transmitted for DO-A traffic. Alternatively, the Msg 3 may include capability information indicating that the A-IoT device (7-01) supports DO-A traffic. Of course, after Msg 3, the above A-IoT device (7-01) may directly send capability information indicating that it supports DO-A traffic to the Reader (7-05) as a separate D2R (Device to Reader) message, or it may send it if the Reader requests it.
[0192] In step 7-50, the Reader (7-05) may send an indicator or the next data message (e.g., a Command message) to the A-IoT device (7-01) indicating that message 3 has been successfully received.
[0193] FIG. 8 is a diagram showing an Ambient IoT (Internet of Things) device transmitting Device-originated - autonomous (DO-A) traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0194] Referring to FIG. 8, the Reader (8-05) can transmit an R2D (Reader to Device) message to an A-IoT device (8-01) (8-10). The R2D message may include wireless resource configuration information (e.g., wireless resource information for transmitting a transport block) to inform the Reader (8-05) if the A-IoT device (8-01) needs to transmit DO-A traffic. That is, according to the wireless resource configuration information, the A-IoT device (8-01) is characterized by including only configuration information to indicate when DO-A traffic occurs, rather than sending the DO-A traffic itself. Of course, the R2D message may also include an ID representing the A-IoT device (i.e., an AS layer ID or an upper layer device ID).
[0195] In step 8-20, when DO-A traffic occurs, the A-IoT device (8-01) may transmit a D2R message to the Reader (8-05) containing information indicating that DO-A traffic has occurred based on the resources set in step 8-10. Additionally, the D2R message may also include information regarding the size of the wireless resources required to transmit the DO-A traffic. The information regarding the size of the wireless resources is auxiliary information for the Reader (8-05) to appropriately allocate the wireless resources required for the DO-A traffic to the A-IoT device (8-01) later.
[0196] In step 8-30, the Reader (8-05) can transmit an R2D message containing wireless resource configuration information to the A-IoT device (8-01) so that the A-IoT device (8-01) can transmit DO-A traffic. In step 8-40, the A-IoT device (8-01) can transmit DO-A traffic to the Reader (8-05). The A-IoT device (8-01) can transmit DO-A traffic to the Reader (8-05) using the wireless resource configuration information.
[0197] If the A-IoT device (8-05) fails to receive an R2D message containing wireless resource configuration information for a certain period of time to transmit DO-A traffic, the A-IoT device (8-05) may determine that the information received in step 8-10 is invalid. The A-IoT device (8-05) may transmit DO-A traffic according to at least one of the aforementioned embodiments (Figs. 6 and 7). Of course, the A-IoT device (8-01) may also perform step 8-20 again. If step 8-20 is performed again, the operations 8-30 and 8-40 described above may be performed in correspondence with the operation 8-20.
[0198] FIG. 9 is a diagram showing an Ambient IoT device transmitting DO-A traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0199] Referring to FIG. 9, the Reader (9-05) can transmit an R2D message to the A-IoT device (9-01) (9-10). The R2D message may include periodic wireless resource configuration information (e.g., wireless resource information for transmitting a transport block) to inform the Reader (9-05) when the A-IoT device (9-01) needs to transmit DO-A traffic. That is, according to the periodic wireless resource configuration information, the A-IoT device (9-01) is characterized by being able to notify that there is a DO-A traffic to be transmitted from a wireless resource according to the corresponding period when DO-A traffic occurs, rather than sending the DO-A traffic itself. Of course, the R2D message may also include an ID representing the A-IoT device (9-01) (i.e., an AS layer ID or an upper layer device ID). Additionally, if the A-IoT device (9-01) does not use wireless resources more than a certain number of times, or if it uses wireless resources more than a certain number of times but fails to successfully transmit a D2R message to the Reader (9-05), the A-IoT device (9-01) may be configured via the R2D message to release the wireless resources set in step 9-10.
[0200] In step 9-20, when DO-A traffic occurs, the A-IoT device (9-01) may transmit a D2R message to the Reader (9-05) containing information indicating that DO-A traffic has occurred according to the resources set in step 9-10. Additionally, the D2R message may include the size of the wireless resources required to transmit the DO-A traffic. This serves as auxiliary information for the Reader (9-05) to appropriately allocate the wireless resources required for the DO-A traffic to the A-IoT device (9-01) later. If the wireless resources are not used more than a certain number of times, or if the wireless resources are used more than a certain number of times but the D2R message is not successfully transmitted to the Reader (9-05), the A-IoT device (9-01) may release the wireless resources set in step 9-10.
[0201] In step 9-30, the Reader (9-05) can transmit an R2D message containing wireless resource configuration information to the A-IoT (9-01) device so that the A-IoT device (9-01) can transmit DO-A traffic. In step 9-40, the A-IoT device (9-01) can transmit DO-A traffic to the Reader (9-05). The A-IoT device (9-01) can transmit DO-A traffic to the Reader (9-05) based on the wireless resource configuration information.
[0202] If the A-IoT device (9-01) fails to receive an R2D message containing wireless resource configuration information for transmitting DO-A traffic for a certain period of time, or if the A-IoT device (9-01) fails to successfully transmit more than a certain number of D2R messages to the Reader (9-05), the A-IoT device (9-01) may determine that the information received in step 9-10 is invalid. The A-IoT device (9-01) may transmit DO-A traffic to the Reader (9-05) according to at least one of the aforementioned embodiments (the embodiment of FIG. 6, FIG. 7, or FIG. 8). Of course, the A-IoT device may also perform step 9-20 again. If step 9-20 is performed again, the 9-30 and 9-40 operations described above may be performed in correspondence with the 9-20 operation.
[0203] FIG. 10 is a diagram showing an Ambient IoT device transmitting DO-A traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0204] Referring to FIG. 10, a Reader (10-05) can transmit an R2D message to an A-IoT device (10-01) (10-10). The R2D message may include wireless resource configuration information that enables the A-IoT device (10-01) to transmit DO-A traffic. That is, according to the wireless resource configuration information, the A-IoT device can transmit DO-A traffic to the Reader (10-05). Of course, the R2D message may also include an ID representing the A-IoT device (10-01) (i.e., an AS layer ID or an upper layer device ID). Additionally, a timer value may be set in the R2D message. If the above timer value is set, the timer is driven with the timer value (the timer is driven in the A-IoT device and / or Reader), and if steps 10-20 are not performed before the timer expires or steps 10-20 are not successfully performed, the A-IoT device (10-01) can release the set wireless resource.
[0205] In step 10-20, the A-IoT device (10-01) may transmit DO-A traffic to the Reader (10-05) based on the resources set in step 10-10 when DO-A traffic occurs. If the A-IoT device (10-01) fails to successfully transmit DO-A traffic for a certain period of time, or if the Reader (10-10) fails to successfully receive DO-A traffic, the A-IoT device (10-01) may determine that the information received in step 10-10 is invalid. The A-IoT device (10-01) may transmit DO-A traffic to the Reader (10-10) according to at least one of the aforementioned embodiments (the embodiment of FIG. 6, FIG. 7, FIG. 8, or FIG. 9). Of course, the A-IoT device (10-01) may perform step 10-20 again.
[0206] In step 10-30, the Reader (10-05) may send an R2D message or an ACK message to the A-IoT device (10-05) to indicate that it has successfully received DO-A traffic. Of course, the Reader (10-05) may also send a NACK to the A-IoT device (10-01) indicating that it has not successfully received DO-A traffic, or it may repeat step 10-10. If step 10-10 is repeated, the previously described actions 10-20 and 10-30 may be performed in response to the action 10-10.
[0207] FIG. 11 is a diagram showing an Ambient IoT device transmitting DO-A traffic in a next-generation mobile communication system according to an embodiment of the present disclosure.
[0208] Referring to FIG. 11, the Reader (11-05) can transmit an R2D message to an A-IoT device (11-01) (11-10). The R2D message may include periodic wireless resource configuration information that enables the A-IoT device (11-01) to transmit DO-A traffic. That is, according to the periodic wireless resource configuration information, if there is DO-A traffic, the A-IoT device can transmit DO-A traffic to the Reader (11-05) using the periodic wireless resource configuration information. Of course, the R2D message may also include an ID representing the A-IoT device (11-01) (i.e., an AS layer ID or an upper layer device ID). Additionally, if the A-IoT device (11-01) does not use wireless resources more than a certain number of times, or if it uses wireless resources more than a certain number of times but fails to successfully transmit a D2R message to the Reader (11-05), the A-IoT device may be configured via the R2D message to release the wireless resources set in step 11-10.
[0209] In step 11-20, the A-IoT device (11-01) may transmit DO-A traffic to the Reader (11-05) based on the resources set in step 11-10 when DO-A traffic occurs. If the A-IoT device (11-01) does not use wireless resources more than a certain number of times, or uses wireless resources more than a certain number of times but fails to successfully transmit a D2R message to the Reader (11-05), the A-IoT device (11-05) may determine that the information received in step 11-10 is invalid. The A-IoT device (11-01) may transmit DO-A traffic to the Reader (11-05) according to at least one of the aforementioned embodiments (the embodiment of FIG. 6, FIG. 7, FIG. 8, FIG. 9, or FIG. 10).
[0210] In step 11-30, the Reader (11-05) may send an R2D message or an ACK message to the A-IoT device (11-05) to indicate that it has successfully received DO-A traffic. Of course, the Reader (11-05) may also send a NACK to the A-IoT device (11-01) indicating that it has not successfully received DO-A traffic, or it may repeat step 11-10. If step 10-10 is repeated, the previously described actions 10-20 and 10-30 may be performed in response to the action 10-10.
[0211] 12 is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure.
[0212] Referring to the drawings above, the terminal includes an RF (Radio Frequency) processing unit (12-10), a baseband processing unit (12-20), a storage unit (12-30), and a control unit (12-40). The control unit (12-40) may include a multiple connection processing unit (12-42). Meanwhile, the terminal of the present disclosure may refer to the A-IoT device described above.
[0213] The RF processing unit (12-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (12-10) up-converts the baseband signal provided by the baseband processing unit (12-20) into an RF band signal, transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (12-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc. Although only one antenna is shown in the drawing, the terminal may be equipped with multiple antennas. In addition, the RF processing unit (12-10) may include multiple RF chains. Furthermore, the RF processing unit (12-10) may perform beamforming. For the above beamforming, the RF processing unit (12-10) can adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processing unit can perform MIMO and can receive multiple layers when performing MIMO operation.
[0214] The baseband processing unit (12-20) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (12-20) generates complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (12-20) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (12-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (12-20) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the complex symbols to subcarriers, and then constructs OFDM symbols through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. Additionally, upon receiving data, the baseband processing unit (12-20) divides the baseband signal provided by the RF processing unit (12-10) into OFDM symbol units, restores the signals mapped to subcarriers through a fast Fourier transform (FFT), and then restores the received bit sequence through demodulation and decoding.
[0215] The baseband processing unit (12-20) and the RF processing unit (12-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (12-20) and the RF processing unit (12-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (12-20) and the RF processing unit (12-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (12-20) and the RF processing unit (12-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), cellular network (e.g., LTE), etc. In addition, the above different frequency bands may include super high frequency (SHF) bands (e.g., 2 NRHz, NRHz) and millimeter wave (e.g., 60 GHz) bands.
[0216] The storage unit (12-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (12-30) can store information related to a second connection node that performs wireless communication using a second wireless connection technology. Additionally, the storage unit (12-30) provides the stored data upon request from the control unit (12-40).
[0217] The control unit (12-40) controls the overall operations of the terminal. For example, the control unit (12-40) transmits and receives signals through the baseband processing unit (12-20) and the RF processing unit (12-10). Additionally, the control unit (12-40) writes and reads data to and from the storage unit (12-40). To this end, the control unit (12-40) may include at least one processor. For example, the control unit (12-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications.
[0218] FIG. 13 is a block diagram showing the configuration of an NR base station according to one embodiment of the present disclosure.
[0219] As illustrated in the drawing above, the base station is configured to include an RF processing unit (13-10), a baseband processing unit (13-20), a backhaul communication unit (13-30), a storage unit (13-40), and a control unit (13-50). The control unit (13-50) may further include a multiple connection processing unit (13-52). Meanwhile, the base station of the present disclosure may refer to the Reader or intermediate UE described above.
[0220] The RF processing unit (13-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (13-10) up-converts the baseband signal provided by the baseband processing unit (13-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (13-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in the drawing, the first connection node may be equipped with multiple antennas. In addition, the RF processing unit (13-10) may include multiple RF chains. Furthermore, the RF processing unit (13-10) may perform beamforming. For the above beamforming, the RF processing unit (13-10) can adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit can perform down-to-down MIMO operation by transmitting one or more layers.
[0221] The baseband processing unit (13-20) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (13-20) generates complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (13-20) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (13-10). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (13-20) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the complex symbols to subcarriers, and then constructs OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (13-20) divides the baseband signal provided by the RF processing unit (13-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operations, and then restores the received bit sequence through demodulation and decoding. The baseband processing unit (13-20) and the RF processing unit (13-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (13-20) and the RF processing unit (13-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.
[0222] The backhaul communication unit (13-30) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (13-30) converts a bit sequence transmitted from the main base station to another node, e.g., an auxiliary base station, a core network, etc., into a physical signal, and converts a physical signal received from the other node into a bit sequence.
[0223] The storage unit (13-40) stores data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (13-40) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (13-40) can store information that serves as a criterion for determining whether to provide multiple connections to the terminal or to disconnect them. Furthermore, the storage unit (13-40) provides the stored data upon the request of the control unit (13-50).
[0224] The control unit (13-50) controls the overall operations of the main station. For example, the control unit (13-50) transmits and receives signals through the baseband processing unit (13-20) and the RF processing unit (13-10) or through the backhaul communication unit (13-30). Additionally, the control unit (13-50) writes and reads data to and from the storage unit (13-40). To this end, the control unit (13-50) may include at least one processor.
[0225] It should be noted that the aforementioned configuration diagrams, exemplary diagrams of control / data signal transmission methods, exemplary diagrams of operation procedures, and configuration diagrams are not intended to limit the scope of the rights of the present disclosure. That is, all components, entities, or steps of operation described in the embodiments of the present disclosure should not be interpreted as essential components for the implementation of the disclosure, and may be implemented within a scope that does not impair the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.
[0226] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading the program code stored in the memory device using a processor or CPU (Central Processing Unit) and executing it.
[0227] Various components of entities, base stations, or terminal devices and modules described in this disclosure may be operated using hardware circuits, such as, for example, complementary metal oxide semiconductor-based logic circuits, firmware, software, and / or a combination of hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.
[0228] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.
[0229] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0230] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
[0231] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.
[0232] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and another embodiment may be combined to operate a base station and a terminal. Additionally, the embodiments of the present disclosure are applicable to other communication systems, and other variations based on the technical concept of the embodiments may also be possible.
Claims
1. A method performed by a terminal supporting DO-A (device originated - autonomous) traffic in a wireless communication system, A step of receiving a paging message from a base station that includes an indicator related to the support of the DO-A traffic; A step of performing a random access procedure based on an indicator related to the support of the above DO-A traffic; and The method includes the step of receiving resource configuration information related to the transmission of the DO-A traffic from the base station. A method for triggering a procedure to process the DO-A traffic based on the resource configuration information when the DO-A traffic occurs at the terminal.
2. In Paragraph 1, A step of transmitting information instructing the generation of the DO-A traffic to the base station based on the resource setting information related to the transmission of the DO-A traffic; A step of receiving resource information for transmitting the above DO-A traffic from the base station; and A method comprising the step of transmitting the DO-A traffic to the base station based on the above resource information.
3. In Paragraph 1, The method further includes the step of transmitting the DO-A traffic to the base station based on the resource configuration information related to the transmission of the DO-A traffic. A method in which the resource setting information further includes an identifier of the terminal or timer information for determining the validity of the resource setting information.
4. In Paragraph 1, The paging message comprises at least one of an identifier capable of identifying the terminal, capability information indicating whether the base station can support the DO-A traffic, an identifier capable of identifying the base station, and information for performing Slotted Aloha random access, and A method in which message 1 of the above random access procedure includes an indicator indicating that message 1 is transmitted for the DO-A traffic.
5. A method performed by a base station for DO-A (device originated - autonomous) traffic in a wireless communication system, A step of transmitting a paging message to a terminal that includes an indicator related to the support of the above DO-A traffic; A step of performing a random access procedure based on an indicator related to the support of the above DO-A traffic; and It includes the step of transmitting resource configuration information related to the transmission of the above DO-A traffic to the terminal, and A method in which, when the DO-A traffic occurs at the terminal, a procedure for processing the DO-A traffic is triggered based on the resource configuration information.
6. In Paragraph 5, A step of receiving information from the terminal instructing the generation of the DO-A traffic based on the resource configuration information related to the transmission of the DO-A traffic; A step of transmitting resource information for transmitting the above DO-A traffic to the terminal; and A method comprising the step of receiving the DO-A traffic from the terminal based on the above resource information.
7. In Paragraph 5, The method further includes the step of receiving the DO-A traffic from the terminal based on the resource configuration information related to the transmission of the DO-A traffic, A method in which the resource setting information further includes an identifier of the terminal or timer information for determining the validity of the resource setting information.
8. In Paragraph 5, The paging message comprises at least one of an identifier capable of identifying the terminal, capability information indicating whether the base station can support the DO-A traffic, an identifier capable of identifying the base station, and information for performing Slotted Aloha random access, and A method in which message 1 of the above random access procedure includes an indicator indicating that message 1 is transmitted for the DO-A traffic.
9. In a terminal supporting DO-A (device originated - autonomous) traffic in a wireless communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The terminal is connected to communicate with at least one processor and is capable of executing individually or in any combination of the at least one processor, so that the terminal, Receive a paging message from a base station containing an indicator related to the support of the above DO-A traffic, and A random access procedure is performed based on an indicator related to the support of the above DO-A traffic, and It includes a memory that stores a command to receive resource configuration information related to the transmission of the DO-A traffic from the base station; and A terminal that, when the DO-A traffic occurs at the terminal, triggers a procedure for processing the DO-A traffic based on the resource configuration information.
10. In Paragraph 9, The above command is for the above terminal, Based on the resource configuration information related to the transmission of the above DO-A traffic, information instructing the generation of the above DO-A traffic is transmitted to the base station, and Receiving resource information for the transmission of the above DO-A traffic from the base station, and A terminal that transmits the DO-A traffic to the base station based on the above resource information.
11. In Paragraph 9, The above command causes the terminal to transmit the DO-A traffic to the base station based on the resource configuration information related to the transmission of the DO-A traffic, and The above resource setting information further includes the identifier of the terminal or timer information for determining the validity of the above resource setting information.
12. In Paragraph 9, The paging message comprises at least one of an identifier capable of identifying the terminal, capability information indicating whether the base station can support the DO-A traffic, an identifier capable of identifying the base station, and information for performing Slotted Aloha random access, and Message 1 of the above random access procedure is a terminal including an indicator that the message 1 is transmitted for the DO-A traffic.
13. In a base station for DO-A (device originated - autonomous) traffic in a wireless communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The base station is connected to communicate with at least one processor and is capable of executing individually or in any combination of the at least one processor, and, Send a paging message to the terminal that includes an indicator related to the support of the above DO-A traffic, and A random access procedure is performed based on an indicator related to the support of the above DO-A traffic, and It includes a memory that stores a command to transmit resource configuration information related to the transmission of the above DO-A traffic to the terminal; and A base station in which, when the DO-A traffic occurs at the terminal, a procedure for processing the DO-A traffic is triggered based on the resource configuration information.
14. In Paragraph 13, The above command is for the above base station, Based on the resource configuration information related to the transmission of the above DO-A traffic, information instructing the generation of the above DO-A traffic is received from the terminal, and Resource information for transmitting the above DO-A traffic is transmitted to the terminal, and A base station that controls the reception of the DO-A traffic from the terminal based on the above resource information.
15. In Paragraph 13, The above command causes the base station to receive the DO-A traffic from the terminal based on the resource configuration information related to the transmission of the DO-A traffic, and A base station that further includes the resource setting information, the identifier of the terminal, or timer information for determining the validity of the resource setting information.