Communication apparatus and communication method

The introduction of a control unit for generating ambient IoT-MAC layer messages with optional AS-IDs addresses the lack of identifier notification in ambient IoT devices, improving communication efficiency.

JP2025157130APending Publication Date: 2025-10-15NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2025018804
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-02-06
Publication Date
2025-10-15

AI Technical Summary

Technical Problem

The introduction of a new layer similar to Medium Access Control (MAC) in the Radio Access Network (RAN) for ambient IoT devices lacks a specified message structure for notifying identifiers.

Method used

A communication device is provided with a control unit that generates a message for the ambient IoT-MAC layer, adding a subheader if an Access Stratum - ID (AS-ID) is necessary, and omitting it if not, to facilitate communication with ambient IoT devices.

Benefits of technology

This approach allows for the introduction of identifiers in ambient IoT device communications, enhancing communication efficiency and reducing unnecessary overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025157130000001_ABST
    Figure 2025157130000001_ABST
Patent Text Reader

Abstract

To provide a communication apparatus and a communication method that introduce identifiers into communication involving ambient IoT (Internet of Things) devices.SOLUTION: In a wireless communication system, a terminal 20, which is a communication apparatus, includes a control unit 240 that generates a message of an ambient IoT-MAC (Medium Access Control) layer and adds a sub-header in the ambient IoT-MAC layer to the message, and a transmitting unit 210 that transmits the message to another communication apparatus. The control unit 240 determines whether an AS-ID (Access Stratum-ID) is necessary, and if necessary, includes the AS-ID in the sub-header, and if not necessary, does not include the AS-ID in the sub-header.SELECTED DRAWING: Figure 25
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a communication device and a communication method in a wireless communication system. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

[0003] Furthermore, Release 18 of 3GPP (registered trademark) is considering Ambient Internet of Things (A-IoT) (for example, Non-Patent Document 2). Ambient IoT targets devices with extremely simple configurations for the lowest-end IoT applications that operate with extremely low power consumption. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V18.0.0 (2023-12) [Non-patent document 2] "New SID: Study on solutions for Ambient IoT (Internet of Things) in NR", RP-234058, 3GPP TSG RAN Meeting #102, December 2023 [Non-patent document 3] 3GPP TR 38.848 V18.0.0 (2023-09) [Non-patent document 4] 3GPP TS 38.321 V18.0.0 (2023-12) Summary of the Invention [Problem to be solved by the invention]

[0005] A new layer similar to Medium Access Control (MAC) is being considered as an upper layer in the Radio Access Network (RAN) for ambient IoT devices. When an identifier is introduced in this new layer, the message structure for notifying the identifier has not been specified.

[0006] The present invention has been made in view of the above points, and aims to introduce an identifier into communication related to ambient IoT (Internet of Things) devices. [Means for solving the problem]

[0007] According to the disclosed technology, a communication device is provided that has a control unit that generates a message of an ambient IoT (Internet of Things)-MAC (Medium Access Control) layer and adds a subheader in the ambient IoT-MAC layer to the message, and a transmission unit that transmits the message to another communication device, wherein the control unit determines whether an AS-ID (Access Stratum - ID) is necessary, and if necessary, includes the AS-ID in the subheader, and if not necessary, does not include the AS-ID in the subheader. [Effects of the Invention]

[0008] According to the disclosed technology, an identifier can be introduced into communications related to ambient IoT (Internet of Things) devices. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a wireless communication system. [Figure 2] 1 is a diagram illustrating an example of a system according to an embodiment of the present invention. [Figure 3] FIG. 1 is a diagram showing an example (1) of a topology according to an embodiment of the present invention. [Figure 4] FIG. 10 is a diagram showing an example (2) of a topology according to an embodiment of the present invention. [Figure 5] FIG. 1 is a diagram illustrating an example (1) of an architecture according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram illustrating an example (2) of an architecture according to an embodiment of the present invention. [Figure 7] FIG. 2 is a diagram for explaining an example (1) of a protocol stack according to an embodiment of the present invention. [Figure 8] FIG. 2 is a diagram for explaining an example (2) of a protocol stack according to an embodiment of the present invention. [Figure 9] FIG. 2 is a sequence diagram illustrating an example (1) of a random access procedure according to an embodiment of the present invention. [Figure 10] FIG. 10 is a sequence diagram illustrating an example (2) of a random access procedure according to an embodiment of the present invention. [Figure 11] FIG. 10 is a sequence diagram illustrating an example (3) of a random access procedure according to an embodiment of the present invention. [Figure 12] FIG. 10 is a sequence diagram illustrating an example (4) of a random access procedure according to an embodiment of the present invention. [Figure 13] FIG. 10 is a sequence diagram illustrating an example (5) of a random access procedure according to an embodiment of the present invention. [Figure 14] 1 is a diagram illustrating an example of a PDU according to an embodiment of the present invention. FIG. [Figure 15] FIG. 10 is a diagram illustrating an example (1) of a MAC subheader. [Figure 16] FIG. 10 is a diagram illustrating an example (2) of a MAC subheader. [Figure 17] FIG. 10 is a diagram illustrating an example (3) of a MAC subheader. [Figure 18] FIG. 2 is a diagram illustrating an example of an AS-ID according to an embodiment of the present invention. [Figure 19]FIG. 2 is a diagram illustrating an example (1) of a MAC subheader according to an embodiment of the present invention. [Figure 20] FIG. 10 is a diagram illustrating an example (2) of a MAC subheader according to an embodiment of the present invention. [Figure 21] FIG. 10 is a diagram illustrating an example (3) of a MAC subheader according to an embodiment of the present invention. [Figure 22] FIG. 10 is a diagram illustrating an example (4) of a MAC subheader according to an embodiment of the present invention. [Figure 23] 1 is a flowchart illustrating an example of message generation according to an embodiment of the present invention. [Figure 24] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 25] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. [Figure 26] 1 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 27] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0013] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0015] Fig. 1 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0016] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, transmitted via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in the downlink (DL) and receives control signals or data from the terminal 20 in the uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0017] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0018] Terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0019] In response to this, Ambient IoT (Ambient Internet of Things, AIoT) is being considered (for example, Non-Patent Document 2). Ambient IoT targets devices with extremely simple configurations for the lowest-end IoT applications that operate with extremely low power consumption.

[0020] For example, Ambient IoT can be considered for the following deployment scenarios and characteristics:

[0021] 1) Indoor or outdoor environment. 2) Base station characteristics, e.g., macro, micro or pico cell based deployments. 3) Connectivity topology, e.g., which nodes (base stations, UEs, relays, repeaters, etc.) communicate with ambient IoT devices? 4) TDD or FDD, and whether the frequency band is licensed or unlicensed. 5) Coexistence with UE and infrastructure in frequency bands for existing 3GPP technologies. 6) Traffic assumptions from and / or to the device.

[0022] Based on the above deployment scenarios and characteristics for relevant use cases, RAN design targets may include at least the following aspects:

[0023] 1) Power consumption 2) Complexity 3) Coverage 4) Data rate 5) Positioning accuracy

[0024] The feasibility of RAN design targets for use cases based on suitable deployment scenarios may be weighed and assumptions of required capabilities supported may be made clear.

[0025] For example, the following device categories may be considered for ambient IoT:

[0026] Device A has no power storage and is not capable of independent signal generation and amplification. Backscattering transmission is possible.

[0027] Device B has power storage and is not capable of independent signal generation. It is capable of backscatter transmission and amplifying the reflected signal using stored power.

[0028] Device C has power storage and is capable of independently generating a signal, i.e., it has active RF components for transmission.

[0029] The complexity of device A may be assumed to be about the same as that of an RFID.

[0030] Figure 2 is a diagram illustrating an example of a system according to an embodiment of the present invention. As shown in Figure 2, in step 1, an ambient IoT reader, which is a BS or a UE, sends an R2D message to an ambient IoT device (e.g., an RFID tag). The R2D message is a message from the reader to the device. In step 2, the ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message is a message from the device to the reader. In step 3, the ambient IoT reader reports to the Access and Mobility Management Function (AMF) of the CN or the new node.

[0031] For ambient IoT devices, a compact protocol stack and reduced signaling procedures are being considered to enable Device-originating - Device-terminated triggered (DO-DTT) and Device-terminated (DT) data transmission, including paging, random access, data transmission including radio resource control aspects, and higher layer operations.

[0032] For example, the following network topology may be assumed for the ambient IoT (see Non-Patent Document 3).

[0033] FIG. 3 is a diagram showing an example topology (1) according to an embodiment of the present invention. Topology 1 shown in FIG. 3 is a configuration in which a BS and an ambient IoT device communicate with each other. The ambient IoT device communicates directly with the base station in a two-way manner. Furthermore, the BS is connected to an AMF (Access and Mobility Management Function) or a new node in a CN (Core Network). Hereinafter, a CN may refer to any node on the network.

[0034] Figure 4 is a diagram showing an example topology (2) according to an embodiment of the present invention. Topology 2 shown in Figure 4 is a configuration in which a BS and an ambient IoT device communicate via an intermediate node. The ambient IoT device performs bidirectional communication with the intermediate node located between the base station and the ambient IoT device. The intermediate node may be, for example, a relay, an IAB (Integrated Access and Backhaul) node, a UE, a repeater, etc. The intermediate node may receive DL data or signaling for an AIoT terminal from the BS and transmit the DL data or signaling to the AIoT terminal.

[0035] The intermediate node and the BS may be connected via a Uu interface. Uu is a wireless interface between a Universal Terrestrial Radio Access Network (UTRAN) and a User Equipment (UE). The intermediate node may transmit unmodulated waves to an AIoT terminal, receive UL data or signaling from the AIoT terminal, and transmit the UL data or signaling to the BS. The BS may also be connected to an AMF or a new node in the CN.

[0036] In addition, the base station, intermediate node, support node, or other node transmits an RF signal to the ambient IoT device. The ambient IoT device is activated and obtains power from an RF operating field from the base station, intermediate node, support node, or other node via inductive coupling. The ambient IoT device transmits information to the base station, intermediate node, support node, or other node by backscattering modulation of the RF signal received from the base station, intermediate node, support node, or other node by switching the reflection coefficient of its own antenna. For example, the ambient IoT device may transmit information using ON-OFF keying.

[0037] For RFID in the 860MHz-960MHz band, the reader of the RFID system corresponds to the base station, intermediate node, or support node of the ambient IoT system. The tag corresponds to the ambient IoT device. The RF signal from the reader to the tag is usually a sine wave of a predetermined frequency. ASK (Amplitude Shift Keying) modulation is used for DL ​​information from the reader to the tag. PIE (Pulse Interval Encoding) coding is also used for DL ​​information from the reader to the tag. ASK and / or PSK (Phase Shift Keying) modulation is used for UL backscattering. FM0 coding and Miller coding are also used for UL backscattering.

[0038] Additionally, the following device types may be defined:

[0039] Device 1) A device with a maximum power consumption of 1 μW or less, with energy storage and no DL or UL amplifiers. UL transmission is performed by backscattering an externally supplied carrier wave.

[0040] Device 2a) A device with a maximum power consumption of a few hundred μW or less, with power storage and DL and / or UL amplifiers. UL transmission is performed by backscattering an externally supplied carrier wave.

[0041] Device 2b) A device with a maximum power consumption of a few hundred μW or less, with power storage and with DL and / or UL amplifiers, where the UL transmission is generated internally within the device.

[0042] FIG. 5 is a diagram showing an example (1) of an architecture according to an embodiment of the present invention. FIG. 6 is a diagram showing an example (2) of an architecture according to an embodiment of the present invention. FIGS. 5 and 6 show examples of defining an architecture in which Topology 1 and Topology 2 are common. In FIGS. 5 and 6, a BS or an intermediate node (e.g., a UE) has an internal reader function node, and this node functions as a reader. In addition to this node, the BS and UE have an internal RAN function node. The RAN function node performs communication with a CN or a BS.

[0043] Figure 7 is a diagram for explaining an example (1) of a protocol stack according to an embodiment of the present invention. It has been agreed that the RRC, SDAP, PDCP, and RLC layers will not be supported in communication between an ambient IoT device and a network. Therefore, as shown in Figure 7, the following protocol stack is assumed:

[0044] NAS (Non-access stratum) / A-IoT NAS: A layer that transmits control information related to ambient IoT devices. It may be assumed to support end-to-end security protection. Note that "NAS / A-IoT NAS" may also mean "NAS or A-IoT NAS."

[0045] MAC / A-IoT MAC: Supports A-IoT random access procedures. May support other functions, such as BSR and SR-like functions. Note that "MAC / A-IoT MAC" may also mean "MAC or A-IoT MAC."

[0046] PHY / A-IoT PHY: Supports physical channels specific to the A-IoT system (PDRSH, PRDSH). May also support other required physical layer protocols. Note that "PHY / A-IoT PHY" may also mean "PHY or A-IoT PHY."

[0047] Figure 8 is a diagram for explaining an example (2) of a protocol stack according to an embodiment of the present invention. The protocol stack shown in Figure 8 is considered in Topology 1. In addition to the protocol stack shown in Figure 7, a Next Generation Application Protocol (NGAP) layer via an NG interface is defined between the gNB and the AIoT function (AMF or new node).

[0048] Figure 9 is a sequence diagram for explaining an example (1) of a random access procedure according to an embodiment of the present invention. Figure 9 shows an example in which random access solution 1 or 3-step contention-based random access (RA) is applied to the A-IoT random access procedure. The A-IoT reader may be a BS or a UE, which is an intermediate node. When an intermediate node is used, communication between the intermediate node and the CN may be performed via the BS.

[0049] In ambient IoT systems, devices always perform random access when exchanging messages with the network, including 3-step random access, 2-step CBRA, and contention-free access.

[0050] Step 1: The CN sends a new NG-AP message to the A-IoT reader, which may include the target device ID or device group ID and other information.

[0051] Step 2: The A-IoT reader sends an A-IoT paging message to the A-IoT device. The A-IoT paging message may include the target device ID or device group ID, or it may target all devices if it does not include either.

[0052] Step 3: The A-IoT device sends Msg1 to the A-IoT reader. Msg1 may include a 16-bit random ID. The A-IoT device may randomly select a transmission opportunity (e.g., frequency, time slot) to send Msg1. Msg1 may include other information.

[0053] Step 4: The A-IoT reader sends Msg2 to the A-IoT device. Msg2 may include the random ID included in Msg1.

[0054] Step 5: The A-IoT device sends Msg3 to the A-IoT reader. Msg3 is an upper layer message and may include the device ID or other information.

[0055] Step 6: The A-IoT reader sends Msg3 to the CN, which may include the device ID or other information.

[0056] Steps 3 to 6 may be called Random Access Solution 1.

[0057] Step 6′: The A-IoT reader may send a message to the A-IoT device notifying it of the failure or success of the random access.

[0058] Step X: After the A-IoT random access is completed, an upper layer message may be sent from the CN to the A-IoT device. The CN sends an instruction to the A-IoT reader to send an upper layer message addressed to the A-IoT device.

[0059] Step X+1: The A-IoT reader forwards the upper layer message to the A-IoT device.

[0060] Step X+2: The A-IoT device replies to the CN according to the contents of the upper layer message received from the CN. For example, if the A-IoT device receives a read command, it replies with the read information.

[0061] Step X+3: The A-IoT reader forwards the upper layer message to the CN.

[0062] Steps X to X+3 may be executed after the completion of three-step random access, after the completion of two-step CBRA, or after contention-free access.

[0063] Figure 10 is a sequence diagram for explaining an example (2) of a random access procedure according to an embodiment of the present invention. Figure 10 shows an example in which random access solution 1 or 3-step contention-based random access (RA) is applied to the A-IoT random access procedure. The A-IoT reader may be a BS or a UE, which is an intermediate node. When an intermediate node is used, communication between the intermediate node and the CN may be performed via the BS.

[0064] Step 1: The CN sends a new NG-AP message to the A-IoT reader, which may include the target device ID or device group ID and other information.

[0065] Step 2: The A-IoT reader sends an A-IoT paging message to the A-IoT device. The A-IoT paging message may include the target device ID or device group ID, or it may target all devices if it does not include either.

[0066] Step 3: The A-IoT device sends Msg1 to the A-IoT reader. Msg1 may include a 16-bit random ID. The A-IoT device may randomly select a transmission opportunity (e.g., frequency, time slot) to send Msg1. Msg1 may include other information.

[0067] Step 4: The A-IoT reader sends Msg2 to the A-IoT device. Msg2 may include the random ID included in Msg1.

[0068] Step 5: The A-IoT device sends Msg3 to the A-IoT reader. Msg3 is an upper layer message and may include the device ID or other information.

[0069] Step 6: The A-IoT reader sends Msg3 to the CN, which may include the device ID or other information.

[0070] Steps 3 to 6 may be called Random Access Solution 1.

[0071] Step 6′: The A-IoT reader may send a message to the A-IoT device notifying it of the failure or success of the random access.

[0072] Figure 11 is a sequence diagram for explaining an example (3) of a random access procedure according to an embodiment of the present invention. Figure 11 shows an example in which random access solution 2 or 2-step contention-based random access (RA) is applied to the A-IoT random access procedure. The A-IoT reader may be a BS or a UE, which is an intermediate node. When an intermediate node is used, communication between the intermediate node and the CN may be performed via the BS.

[0073] Step 1: The CN sends a new NG-AP message to the A-IoT reader, which may include the target device ID or device group ID and other information.

[0074] Step 2: The A-IoT reader sends an A-IoT paging message to the A-IoT device. The A-IoT paging message may include the target device ID or device group ID, or may include neither and target all devices. It may also include command type information (e.g., read or write), and may also include other information.

[0075] Step 3: The A-IoT device sends Msg1 to the A-IoT reader. Msg1 may include a 16-bit random ID. The A-IoT device may randomly select a transmission opportunity (e.g., a timeslot) to send Msg1. Msg1 may include other information.

[0076] Step 4: The A-IoT reader sends Msg3 to the CN.

[0077] Steps 3 and 4 may be called random access solution 2.

[0078] Step 4′: The A-IoT reader may send a message to the A-IoT device notifying it of the failure or success of the random access.

[0079] Figure 12 is a sequence diagram for explaining an example (4) of a random access procedure according to an embodiment of the present invention. Figure 12 is an example of applying random access solution 3 to an A-IoT random access procedure. Random access solution 3 may be called a combined solution of random access solutions 1 and 2. The A-IoT reader may be a BS or a UE, which is an intermediate node. When an intermediate node is used, communication between the intermediate node and the CN may be performed via the BS.

[0080] Step 1: The CN sends a new NG-AP message to the A-IoT reader, which may include the target device ID or device group ID and other information.

[0081] Step 2: The A-IoT reader sends an A-IoT paging message to the A-IoT device. The A-IoT paging message may include the target device ID or device group ID, or if it does not include either, it may target all devices. It may also include command type information (e.g., read or write). It may also include other information. It may also indicate whether or not to include upper layer data in the D2R message of step 3.

[0082] Step 3: Thereafter, send a D2R message based on the instructions in the A-IoT paging message to initiate random access solution 1 or random access solution 2.

[0083] Figure 13 is a sequence diagram for explaining an example (5) of a random access procedure according to an embodiment of the present invention. Figure 13 shows an example in which contention-free random access (2-step contention-free random access, CFRA) is applied to the A-IoT random access procedure. The A-IoT reader may be a BS or a UE, which is an intermediate node. When an intermediate node is used, communication between the intermediate node and the CN may be performed via the BS.

[0084] Step 1: The CN sends a new NG-AP message to the A-IoT reader, which may include the target device ID or device group ID and other information.

[0085] Step 2: The A-IoT reader sends an A-IoT paging message to the A-IoT device. The A-IoT paging message may include the target device ID or device group ID, or may include neither and target all devices. It may also include command type information (e.g., read or write), and may also include other information.

[0086] Step 3: The A-IoT device sends a higher layer message containing the device ID and other information to the A-IoT reader with the D2R resource specified in step 2.

[0087] Step 4: The A-IoT reader forwards the upper layer message received in step 3 to the CN.

[0088] Step 4′: The A-IoT reader may send a message to the A-IoT device notifying it of the failure or success of the random access.

[0089] 14 is a diagram illustrating an example of a PDU according to an embodiment of the present invention. In the ambient IoT, a new layer similar to the MAC in NR may be introduced. Taking the NR MAC layer as an example, in the D2R direction, a PDU may be transmitted in the PDU configuration shown in FIG. 14.

[0090] The names AIoT-MAC-subheader, AIoT-MAC-SDU, AIoT-MAC-CE, and AIoT-MAC-subPDU in Figure 14 are not limited to these.

[0091] In ambient IoT, multiplexing is performed. That is, AIoT-MAC-subPDUs are not necessarily concatenated. In other words, only one combination of AIoT-MAC-subheader + {AIoT-MAC-SDU or AIoT-MAC-CE} may be passed to the lower layer as a MAC-PDU.

[0092] Figure 15 is a diagram illustrating an example of a MAC subheader (1). Figure 16 is a diagram illustrating an example of a MAC subheader (2). Figure 17 is a diagram illustrating an example of a MAC subheader (3). Figures 15, 16, and 17 show examples of MAC subheaders in NR (see Non-Patent Document 4).

[0093] According to Non-Patent Document 4, the MAC subheader of DL-SCH or UL-SCH (excluding Transparent MAC and Random Access Response) is as shown in Figure 15 or 16, except for the fixed size MAC CE, padding, and MAC SDU containing UL CCCH. The fixed size MAC CE and padding are as shown in Figure 17, with LX or R being replaced with R. The MAC SDU containing UL CCCH is as shown in Figure 17(A), with LX or R being replaced with LX.

[0094] For each element of the MAC subheader in NR, when applied to an ambient IoT system, the following may be used:

[0095] R field: Reserved bit. May be used as AS-ID (Access Stratum - ID, described later).

[0096] F field: Notifies the length of the L field (1 byte or 2 bytes). Since the TB size of an ambient IoT system is expected to be at most 1000 bits, a 1-byte L field (maximum payload length 256 bytes) is considered sufficient, so the F field may be omitted.

[0097] L field: Indicates the length of the payload (in bytes). If the maximum payload length is less than 256 bytes, it may be further shortened and reused as an AS-ID.

[0098] LCID field: Logical channel ID. If the payload part is MAC-CE, it notifies the type of MAC-CE. If it is not MAC-CE, it notifies the logical channel number. In NR, it is 6 bits. Since it is assumed that many types of AIoT-MAC-CE are not required in an ambient IoT system, it may be shortened and used as AS-ID. Note that only one logical channel may be supported in an ambient IoT system.

[0099] eLCID field: A field introduced to expand the number of LCIDs. It is assumed that one logical channel is supported in an ambient IoT system. Also, since the number of signalings required to be introduced in an ambient IoT system is not large, it is considered that there is little need to expand the LCID. Therefore, the eLCID field may be abolished in an ambient IoT system.

[0100] LX: This bit is introduced to extend the number of LCIDs without increasing the number of bytes. As mentioned above, there is no need to extend LCIDs in ambient IoT systems, so the LX field can be abolished.

[0101] FIG. 18 is a diagram illustrating an example of an AS-ID according to an embodiment of the present invention. The introduction of AS-IDs in the upper layers of the RAN for ambient IoT is being considered. The AS-IDs are used for scheduling D2R messages and receiving R2D messages. As shown in FIG. 18, the A-IoT reader may specify D2R transmission resources associated with the AS-ID, and the A-IoT device may receive R2D messages with its own AS-ID assigned.

[0102] Additionally, the A-IoT device may assign its own AS-ID to the D2R message. However, the AS-ID may not be assigned to some messages, such as the R2D ambient IoT paging message and D2R-Msg1.

[0103] The length of the AS-ID may be set to allow for hundreds to thousands of AS-IDs, since they must be uniquely assigned to each A-IoT device within the range of A-IoT devices that a single A-IoT reader communicates with. Since the only upper layer in the Ambient IoT protocol stack is the Ambient IoT-MAC, the AS-ID must be assigned within the Ambient IoT-MAC layer. Therefore, an AS-ID field may be introduced into the Ambient IoT-MAC subheader. In other words, a field capable of generating hundreds to thousands of AS-IDs may be introduced into the Ambient IoT-MAC sublayer.

[0104] 19 is a diagram illustrating an example (1) of a MAC subheader according to an embodiment of the present invention. An AS-ID field may be reserved in the ambient IoT-MAC subheader as shown in FIG.

[0105] Figure 19(A) shows an example of inserting 2 bytes as the AS-ID. The AS-ID is 2 bytes (=>65535), so there is little concern about it running out. The LCID is 6 bits (=>64), so there is little concern about it running out. L is 1 byte (=>maximum message length 2048 bits), so it is sufficient.

[0106] Figure 19(B) shows an example where one byte is inserted as the AS-ID and the reserved bit is reused. The entire subheader is three bytes, so overhead is small. The LCID is six bits (=> 64 bits), so there is little concern about depletion. L is one byte (=> maximum message length 2048 bits), so it is sufficient.

[0107] Figure 19(C) shows an example where one byte is inserted as the AS-ID, the reserved bit is reused, and the LCID is shortened and reused. The entire subheader is three bytes, so the overhead is small. The AS-ID is 12 bits (=> 4096), which is sufficient. L is 1 byte (=> maximum message length 2048 bits), which is sufficient.

[0108] Figure 19(D) shows an example in which one byte is inserted as the AS-ID, the reserved bit is reused, the LCID is shortened and reused, and L is shortened and reused. The overhead is small, as the entire subheader is three bytes. The AS-ID is 12 bits (=>4096), which is sufficient. L is 7 bits (=>maximum message length 1024 bits), which is sufficient.

[0109] 20 is a diagram illustrating an example (2) of a MAC subheader according to an embodiment of the present invention. When transmitting a message with a fixed payload length, there is no need to report the payload length using the L field, so the L field may be deleted as shown in FIG.

[0110] Figure 20(A) shows an example of inserting two bytes as an AS-ID. Figure 20(B) shows an example of inserting one byte as an AS-ID and reusing the reserved bit. Figure 20(C) shows an example of inserting one byte as an AS-ID, reusing the reserved bit, and shortening and reusing the LCID. Figure 20(D) shows an example of inserting one byte as an AS-ID, reusing the reserved bit, shortening and reusing the LCID, and shortening and reusing L.

[0111] Figure 21 is a diagram illustrating an example (3) of a MAC subheader according to an embodiment of the present invention. For messages that do not require an AS-ID to be assigned (e.g., paging, Msg1), one of the ambient IoT-MAC subheaders shown in Figure 21 may be assigned, since the position and length of the LCID differ depending on the form of the ambient IoT-MAC subheader of the message to which an AS-ID is assigned. Figure 21(A) corresponds to the case of Figure 19(A). Figure 21(B) corresponds to the case of Figure 19(B). Figure 21(C) corresponds to the case of Figure 19(C). Figure 21(D) corresponds to the case of Figure 19(D).

[0112] As shown in Figure 21, when an AS-ID is not assigned to a subheader, a logical channel ID with the same bit width as the bit width of the logical channel ID field of the subheader when an AS-ID is assigned may be used. Also, when an AS-ID is not assigned to a subheader, some of the bits of the AS-ID field of the subheader when an AS-ID is assigned may be reserved bits.

[0113] FIG. 22 is a diagram illustrating an example (4) of a MAC subheader according to an embodiment of the present invention. When transmitting a message with a fixed payload length, there is no need to report the payload length using the L field, so the L field may be deleted as shown in FIG. 22. For messages that do not require an AS-ID to be assigned (e.g., paging, Msg1), one of the ambient IoT-MAC subheaders shown in FIG. 22 may be assigned because the position and length of the LCID differ depending on the form of the ambient IoT-MAC subheader of the message to which the AS-ID is assigned. FIG. 22(A) corresponds to the case of FIG. 20(A). FIG. 22(B) corresponds to the case of FIG. 20(B). FIG. 22(C) corresponds to the case of FIG. 20(C). FIG. 22(D) corresponds to the case of FIG. 20(D).

[0114] As shown in Figure 21, when an AS-ID is not assigned to a subheader, a logical channel ID with the same bit width as the bit width of the logical channel ID field of the subheader when an AS-ID is assigned may be used. Also, when an AS-ID is not assigned to a subheader, some of the bits of the AS-ID field of the subheader when an AS-ID is assigned may be reserved bits.

[0115] 23 is a flowchart illustrating an example of message generation according to an embodiment of the present invention. In step S101, the A-IoT reader or A-IoT device generates an A-IoT-MAC layer message (MAC-SDU or MAC-CE). In step S102, the A-IoT reader or A-IoT device determines whether the message requires an AS-ID. If the message requires an AS-ID, proceed to step S103 (YES in S102); if the message does not require an AS-ID, proceed to step S106 (NO in S102).

[0116] In step S103, the A-IoT reader or A-IoT device determines whether the payload length is variable. If the payload length is variable, proceed to step S104 (YES in S103), and if the payload length is not variable, proceed to step S105 (NO in S103).

[0117] In step S104, the A-IoT reader or A-IoT device adds one of the subheaders shown in Figure 19 and proceeds to step S109. In step S105, the A-IoT reader or A-IoT device adds one of the subheaders shown in Figure 20 and proceeds to step S109.

[0118] In step S106, the A-IoT reader or A-IoT device determines whether the payload length is variable. If the payload length is variable, proceed to step S107 (YES in S106), and if the payload length is not variable, proceed to step S108 (NO in S106).

[0119] In step S107, the A-IoT reader or A-IoT device adds one of the subheaders shown in Figure 21 and proceeds to step S109. In step S108, the A-IoT reader or A-IoT device adds one of the subheaders shown in Figure 22 and proceeds to step S109.

[0120] Following step S109, the A-IoT reader or A-IoT device may send the A-IoT-MAC layer message with the subheader added to the A-IoT device or A-IoT reader.

[0121] As mentioned above, A-IoT devices and A-IoT readers can exchange messages with AS-IDs using a new protocol in the upper wireless layer.

[0122] That is, an identifier can be introduced into communications involving ambient IoT (Internet of Things) devices.

[0123] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0124] <Base station 10> Fig. 24 is a diagram showing an example of the functional configuration of base station 10 in the embodiment of the present invention. As shown in Fig. 24, base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 24 is merely an example. The functional divisions and names of the functional units may be any names as long as they can perform the operations related to the embodiment of the present invention.

[0125] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0126] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to communication with the ambient IoT device.

[0127] The control unit 140 performs control to realize the functions described in the embodiments. Furthermore, as described in the embodiments, the control unit 140 performs control related to communication with the ambient IoT device. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0128] <Terminal 20> Fig. 25 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 25, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 25 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0129] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0130] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The setting information includes, for example, information related to communication with the ambient IoT device.

[0131] The control unit 240 performs control to realize the functions described in the embodiments. Furthermore, as described in the embodiments, the control unit 240 performs control related to communication with the ambient IoT device. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0132] (Hardware configuration) The block diagrams (FIGS. 24 and 25) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0133] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0134] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 26 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0135] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0136] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0137] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0138] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 24 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 25 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0139] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0140] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0141] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0142] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0143] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0144] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0145] Fig. 27 shows an example configuration of a vehicle 2001. As shown in Fig. 27, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0146] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0147] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0148] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0149] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0150] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0151] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0152] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0153] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0154] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0155] (Summary of the embodiment) The terminal or base station of this embodiment may be configured as a communication device, terminal, or base station shown in the following items. Also, the following communication method may be implemented.

[0156] (Section 1) a control unit that generates a message of an ambient Internet of Things (IoT)-Medium Access Control (MAC) layer and adds a subheader in the ambient Internet of Things (IoT)-MAC layer to the message; a transmitting unit that transmits the message to another communication device; The control unit determines whether an AS-ID (Access Stratum - ID) is necessary, and if necessary, includes the AS-ID in the subheader, and if not necessary, does not include the AS-ID in the subheader. (Section 2) The communication device according to claim 1, wherein the control unit determines whether the payload length is variable, and if it is variable, includes a field indicating the payload length in the subheader, and if it is not variable, does not include a field indicating the payload length in the subheader. (Section 3) 2. The communication device according to claim 1, wherein the control unit deletes the AS-ID from the field of the subheader when the AS-ID is not assigned to the subheader and when the AS-ID is assigned. (Section 4) The communication device described in claim 1, wherein when an AS-ID is not assigned to the subheader, the control unit uses a logical channel ID with the same bit width as the bit width of the logical channel ID field of the subheader when an AS-ID is assigned. (Section 5) The communication device according to claim 1, wherein the control unit reserves some of the bits in the AS-ID field of the subheader when an AS-ID is not assigned to the subheader and when an AS-ID is assigned. (Section 6) generating an ambient IoT (Internet of Things)-MAC (Medium Access Control) layer message and adding a subheader in the ambient IoT-MAC layer to the message; transmitting the message to another communication device; A communication method in which a communication device executes a procedure of determining whether an AS-ID (Access Stratum - ID) is necessary, and if necessary, including the AS-ID in the subheader, and if not necessary, not including the AS-ID in the subheader.

[0157] Any of the above configurations provides a technology for introducing identifiers into communications related to ambient IoT (Internet of Things) devices. According to paragraphs 2 to 5, A-IoT devices and A-IoT readers can exchange messages with AS-IDs attached using a new upper wireless layer protocol.

[0158] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0159] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0160] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0161] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0162] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0163] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0164] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0165] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0166] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0167] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0168] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0169] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0170] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0171] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0172] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0173] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0174] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0175] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0176] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0177] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0178] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0179] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0180] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0181] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0182] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0183] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0184] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0185] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0186] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0187] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0188] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0189] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0190] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0191] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0192] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0193] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0194] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0195] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0196] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0197] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0198] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0199] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0200] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0201] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0202] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0203] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0204] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0205] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0206] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0207] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0208] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0209] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0210] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0211] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 30 Core Network 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. a control unit that generates a message of an ambient Internet of Things (IoT)-Medium Access Control (MAC) layer and adds a subheader in the ambient IoT-MAC layer to the message; a transmitting unit that transmits the message to another communication device; The control unit determines whether an AS-ID (Access Stratum - ID) is necessary, and if necessary, includes the AS-ID in the subheader, and if not necessary, does not include the AS-ID in the subheader.

2. 2. The communication device according to claim 1, wherein the control unit determines whether the payload length is variable, and if it is variable, includes a field indicating the payload length in the subheader, and if it is not variable, does not include a field indicating the payload length in the subheader.

3. 2. The communication device according to claim 1, wherein the control unit, when not adding an AS-ID to the subheader, deletes the AS-ID from the field of the subheader when an AS-ID is added.

4. 2. The communication device according to claim 1, wherein when an AS-ID is not assigned to the subheader, the control unit uses a logical channel ID having the same bit width as the bit width of the logical channel ID field of the subheader when an AS-ID is assigned.

5. 2. The communication device according to claim 1, wherein the control unit reserves some of the bits in the AS-ID field of the subheader when an AS-ID is not assigned to the subheader and when an AS-ID is assigned to the subheader.

6. generating a message of an ambient Internet of Things (IoT)-Medium Access Control (MAC) layer and adding a subheader in the ambient Internet of Things (IoT)-MAC layer to the message; transmitting the message to another communication device; A communication method in which a communication device executes a procedure of determining whether an AS-ID (Access Stratum - ID) is necessary, and if necessary, including the AS-ID in the subheader, and if not necessary, not including the AS-ID in the subheader.