Communication apparatus and communication method

Abstract

This communication apparatus includes: a transmission unit that transmits a message including a write command to an ambient IoT (Internet of Things) device; and a reception unit that receives a message including a response to the write command from the ambient IoT device. The transmission unit transmits a message indicating execution of the write command to the ambient IoT device.

Description

Communication device and communication method

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

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that satisfy the requirements of 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 (for example, Non-Patent Document 1).

[0003] Furthermore, Release 18 of 3GPP (registered trademark) is studying Ambient Internet of Things (A-IoT) (see, 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.

[0004] 3GPP TS 38.300 V18.0.0 (2023-12)"New SID: Study on solutions for Ambient IoT (Internet of Things) in NR", RP-234058, 3GPP TSG RAN Meeting #102, December 20233GPP TR 38.848 V18.0.0 (2023-09)3GPP TS 24.501 V18.5.0 (2023-12)

[0005] When starting communication with an ambient IoT device, an ambient IoT reader transmits an initial trigger message to the ambient IoT device, initiating a random access-like procedure. The initial trigger message is a message that instructs the start of the random access-like procedure, and the name thereof is not limited to the initial trigger message. The random access-like procedure is a procedure for avoiding collisions of signals emitted by multiple devices, and the name thereof is not limited to the random access-like procedure. Here, since the D2R signal transmitted from the ambient IoT device has low strength, there is a possibility that the ambient IoT reader will fail to receive the signal.

[0006] The present invention has been made in consideration of the above points, and aims to suppress problems that occur when a signal transmitted from an Ambient Internet of Things (IoT) device does not arrive.

[0007] According to the disclosed technology, a communication device is provided that has a transmitting unit that transmits a message including a write command to an ambient IoT (Internet of Things) device, and a receiving unit that receives a message including a response to the write command from the ambient IoT device, and the transmitting unit transmits a message to the ambient IoT device instructing it to execute the write command.

[0008] According to the disclosed technology, it is possible to suppress malfunctions that occur when a signal transmitted from an Ambient Internet of Things (IoT) device does not arrive.

[0009] FIG. 1 is a diagram illustrating an example of a configuration of a wireless communication system. FIG. 1 is a diagram illustrating an example of a system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a topology (1) according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a topology (2) according to an embodiment of the present invention. FIG. 4 is a sequence diagram illustrating an example of a communication (1) according to an embodiment of the present invention. FIG. 5 is a sequence diagram illustrating an example of a communication (2) according to an embodiment of the present invention. FIG. 6 is a sequence diagram illustrating an example of a communication (3) according to an embodiment of the present invention. FIG. 7 is a sequence diagram illustrating an example of a communication (4) according to an embodiment of the present invention. FIG. 8 is a sequence diagram illustrating an example of a communication (5) according to an embodiment of the present invention. FIG. 9 is a sequence diagram illustrating an example of a communication (6) according to an embodiment of the present invention. FIG. 10 is a sequence diagram illustrating an example of a communication (7) according to an embodiment of the present invention. FIG. 11 is a sequence diagram illustrating an example of a communication (8) according to an embodiment of the present invention. FIG. 12 is a sequence diagram illustrating an example of a communication (9) according to an embodiment of the present invention. FIG. 13 is a diagram illustrating a write command according to an embodiment of the present invention. FIG. 14 is a diagram illustrating an example of a NAS message communication (1) according to an embodiment of the present invention. FIG. 15 is a diagram illustrating an example of a NAS message communication (2) according to an embodiment of the present invention. FIG. 16 is a diagram illustrating an example of a NAS message communication (3) according to an embodiment of the present invention. FIG. 17 is a sequence diagram illustrating an example of a command execution (1) according to an embodiment of the present invention. FIG. 18 is a sequence diagram illustrating an example of a command execution (2) according to an embodiment of the present invention. FIG. 1 is a sequence diagram illustrating an example (3) of command execution according to an embodiment of the present invention. FIG. 2 is a sequence diagram illustrating an example (4) of command execution according to an embodiment of the present invention. FIG. 3 is a sequence diagram illustrating an example (5) of command execution according to an embodiment of the present invention. FIG. 4 is a sequence diagram illustrating an example (6) of command execution according to an embodiment of the present invention. FIG. 5 is a sequence diagram illustrating an example (7) of command execution according to an embodiment of the present invention. FIG. 6 is a sequence diagram illustrating an example (8) of command execution according to an embodiment of the present invention. FIG. 7 is a sequence diagram illustrating an example (9) of command execution according to an embodiment of the present invention.Fig. 1 is a sequence diagram for explaining an example (10) of command execution according to an embodiment of the present invention. Fig. 2 is a diagram showing an example of the functional configuration of a base station 10 according to an embodiment of the present invention. Fig. 3 is a diagram showing an example of the functional configuration of a terminal 20 according to an embodiment of the present invention. Fig. 4 is a diagram showing an example of the hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. Fig. 5 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present 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 technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is 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] In addition, in the embodiments of the present invention described below, terms 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) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily stated as "NR-".

[0013] Furthermore, in the embodiment of the present invention, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters etc. 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 also 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 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). 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 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, 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 propagation path quality based on the reception results of the reference signals.

[0018] The terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with the 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 Internet of Things (AIoT) is being considered (see, for example, Non-Patent Document 2). Ambient IoT targets devices with extremely simple configurations that operate with extremely low power consumption and are intended for the lowest-end IoT applications.

[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 deployment. 3) Connectivity topology, e.g., which nodes (e.g., base stations, UEs, relays, repeaters, etc.) communicate with ambient IoT devices. 4) TDD or FDD, licensed or unlicensed frequency band. 5) Coexistence with UEs and infrastructure in frequency bands for existing 3GPP technologies. 6) Traffic assumptions originating from and / or terminating to the device.

[0022] RAN design targets based on the above deployment scenarios and characteristics for relevant use cases 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 to clarify expectations of required functionality to be supported.

[0025] For example, the following device categories may be envisioned 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 the 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] 2 is a diagram illustrating an example of a system according to an embodiment of the present invention. As shown in FIG. 2, in step 1, an Ambient IoT reader, which may be 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, compact protocol stacks 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 envisaged for 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. The 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 performs bidirectional communication directly with the base station. Furthermore, the BS is connected to an access and mobility management function (AMF) or a new node in a core network (CN). Hereinafter, the CN may refer to any node on the network.

[0034] FIG. 4 is a diagram illustrating an example topology (2) according to an embodiment of the present invention. The topology 2 illustrated in FIG. 4 is a configuration in which a base station 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 integrated access and backhaul (IAB) node, a UE, a repeater, or the like. The intermediate node may receive DL data or signaling intended for an AIot terminal from the base station 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 the IoT terminal, receive UL data or signaling from the IoT 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] Furthermore, 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 by performing ON-OFF keying.

[0037] For RFID in the 860 MHz-960 MHz 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. Also, PIE (Pulse Interval Encoding) coding is used for DL ​​information from the reader to the tag. ASK and / or PSK (Phase Shift Keying) modulation is used for UL backscattering. Also, FM0 coding and Miller coding are 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 with 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] 5 is a sequence diagram for explaining a communication example (1) according to an embodiment of the present invention. Using FIG. 5, an example will be described in which an initial trigger message is transmitted from an ambient IoT reader to an ambient IoT device in the case of topology 1, and a random access-like procedure is initiated.

[0043] The initial trigger message is a message sent from the reader to the device, instructing the ambient IoT device to start a random access-like procedure, and may include the device ID of the ambient IoT device to be instructed. The initial trigger message corresponds to step 2.

[0044] The random access-like procedure is a procedure for allocating a transmission opportunity (e.g., a transmission timing) for performing data transmission via D2R to each ambient IoT device. After this procedure is executed, the ambient IoT device transmits a D2R message to the ambient IoT reader using the allocated transmission opportunity. The random access-like procedure corresponds to steps 3 and 4.

[0045] Step 1: The AMF or the new node X sends a new NG-AP message to the leader BS. The new NG-AP message may include the device ID, device group ID, or location information of the target ambient IoT device, and is a message that at least requests a response from the ambient IoT device.

[0046] Step 2: The leader BS sends an initial trigger message containing the device ID or device group ID to the ambient IoT device.

[0047] Step 3: The ambient IoT device sends a RACH-like preamble to the leader BS.

[0048] Step 4: The leader BS sends a RACH-like response to the ambient IoT device, which may include a D2R grant.

[0049] Step 5: The ambient IoT device sends a D2R message to the leader BS, which may include a NAS-secured device ID and location information as D2R data.

[0050] Step 6: The leader BS sends a new NG-AP message to the AMF or the new node X. The new NG-AP message may include a NAS-secured device ID and location information.

[0051] 6 is a sequence diagram for explaining a communication example (2) according to an embodiment of the present invention. Using FIG. 6, an example will be described in which an initial trigger message is transmitted from an ambient IoT reader to an ambient IoT device in the case of topology 2, and a random access-like procedure is initiated.

[0052] Step 1: The AMF or new node X sends a new NG-AP message to the BS, which may include the device ID or device group ID of an ambient IoT device, whether location information is required, etc., and is a message that at least requests a response from the ambient IoT device.

[0053] Step 2: The BS sends a new RRC message to the leader intermediate node, which may include the device ID or device group ID of an ambient IoT device, whether location information is required, etc., and is a message that at least requests a response from the ambient IoT device.

[0054] Step 3: The intermediate node, which is the leader, sends an initial trigger message containing the device ID to the ambient IoT device.

[0055] Step 4: The ambient IoT device sends a RACH-like preamble to the intermediate node that is the leader.

[0056] Step 5: The intermediate node as the leader sends a RACH-like response to the ambient IoT device, which may include a D2R grant.

[0057] Step 6: The ambient IoT device sends a D2R message to the intermediate node as the leader, which may include a NAS-secured device ID and location information as D2R data.

[0058] Step 7: The leader intermediate node sends a new RRC message to the BS, which may include a NAS-secured device ID and location information.

[0059] Step 8: The BS sends a new NG-AP message to the AMF or the new node X. The new NG-AP message may include a NAS-secured device ID and location information.

[0060] Ambient IoT devices are being considered to support inventory and command use cases. Inventory is an operation in which an ambient IoT device reports a device ID or a temporary device ID to indicate that it is in the vicinity of a reader. A command is an operation in which memory in an ambient IoT device is read or written at the instruction of the reader. Hereinafter, a distinction will be made between read commands and write commands.

[0061] The procedure may be the same for both inventory and command use cases. Furthermore, the command message and inventory message may be included in the initial trigger message.

[0062] In topology 1, when an inventory, read command, or write command message is sent as an initial trigger message, the message type (inventory, read, or write), an information element to be reported in the case of a read, and information to be rewritten in the case of a write may be further included in STEP 1 and STEP 2 of Fig. 5. Furthermore, STEP 5 and STEP 6 of Fig. 5 may further include a device ID or temporary device ID that serves as an inventory response, requested information in the case of a read (Read command report), and a report of rewrite completion in the case of a write (Write complete report).

[0063] In topology 2, when an inventory, read command, or write command message is sent as an initial trigger message, the message type (inventory, read, or write), an information element to be reported in the case of a read, and information to be rewritten in the case of a write may be further included in STEP 1, STEP 2, and STEP 3 of Fig. 6. Furthermore, STEP 6, STEP 7, and STEP 8 of Fig. 6 may further include a device ID or temporary device ID serving as an inventory response, requested information in the case of a read (Read command report), and a report of rewrite completion in the case of a write (Write complete report).

[0064] 7 is a sequence diagram for explaining an example (3) of communication according to an embodiment of the present invention. In FIG. 7, steps 1 to 6 may be the same as those in FIG.

[0065] In STEP 7 and STEP 8 shown in Figure 7, the message type (inventory, read or write), the information elements to be reported in the case of a read, and the information to be rewritten in the case of a write may be notified from the CN to the BS or from the BS to the ambient IoT device by a NAS message.

[0066] In STEP 9 and STEP 10 shown in FIG. 7, a NAS message may be used to notify the ambient IoT device to the BS or the BS to the CN of the device ID or temporary device ID that serves as an inventory response, the requested information in the case of a read (Read command report), and a report of rewrite completion in the case of a write (Write complete report).

[0067] 8 is a sequence diagram for explaining an example (4) of communication according to an embodiment of the present invention. In FIG. 8, steps 1 to 8 may be the same as those in FIG.

[0068] In STEP 9, STEP 10 and STEP 11 shown in FIG. 8, the message type (inventory, read or write), the information elements to be reported in the case of a read, and the information to be rewritten in the case of a write may be notified by a NAS message from the CN to the BS, or from the BS to the intermediate node, or from the intermediate node to the ambient IoT device.

[0069] In STEP 12, STEP 13, and STEP 14 shown in FIG. 8, a NAS message may be sent from the ambient IoT device to the intermediate node, or from the intermediate node to the BS, or from the BS to the CN, to notify the device ID or temporary device ID that is the inventory response, the requested information in the case of a read (Read command report), or a report of rewrite completion in the case of a write (Write complete report).

[0070] Here, in particular, for device type device 1, there is no DL / UL amplifier, and UL transmission is performed only by backscattering transmission that harvests received radio waves. Therefore, it is assumed that the strength of the UL D2R signal is low.

[0071] On the other hand, considering the asymmetry between the device and the reader, where the ambient IoT reader is a BS or UE equipped with an amplifier, it is conceivable that a situation may arise in which the R2D signal transmitted from the reader to the device reaches the device, but the D2R signal transmitted from the device to the reader does not reach the reader.

[0072] Therefore, it is necessary to design a procedure that prevents malfunctions even if the D2R signal does not arrive. Since the type and content of the D2R signal are common to both Topology 1 and Topology 2, the following description will be given using only Topology 1 as an example for simplicity.

[0073] In the random access-like procedure in Figure 5, the D2R signals transmitted by the ambient IoT device are a preamble transmission in STEP 3 and a UL-NAS message transmission in STEP 5.

[0074] In STEP 3, the device selects and transmits one random-access-like preamble. If the reader receives the random-access-like preamble and there is no collision with another device, the reader transmits a random-access-like response (STEP 4) to the device. If the D2R signal is not received, the reader does not recognize the device.

[0075] Therefore, to strengthen the coverage of the preamble transmission in STEP 3, the ambient IoT device may repeat the preamble transmission in STEP 3. Also, the ambient IoT reader may repeat the initial trigger message transmission in STEP 2. Also, the ambient IoT reader may resend the initial trigger message in STEP 2 to the ambient IoT device that was unable to receive the preamble.

[0076] In STEP 5, a UL-NAS message is sent that includes the device ID or temporary device ID, a read command report if a read command was received in STEP 2, or a write completion report if a write command was received in STEP 2. If the D2R signal is not received, the CN does not recognize the device. If the CN instructed an inventory, read, or write process in STEP 1, it considers that process to have failed. If the write fails, there is a possibility that a discrepancy in recognition may occur between the device and the CN.

[0077] Therefore, to strengthen the coverage of the UL-NAS message transmission in STEP 5, the ambient IoT device may repeat the UL-NAS message transmission in STEP 5. Also, the ambient IoT reader may repeat the random access-like response transmission in STEP 4. Also, the ambient IoT reader may resend the initial trigger message in STEP 2 to the ambient IoT device that was unable to receive the UL-NAS message.

[0078] 7, when an inventory, a read command, or a write command is sent after the random access-like procedure, a NAS message is exchanged after the random access-like procedure is completed. In this exchange, the D2R signal sent by the ambient IoT device is the UL-NAS message transmission in STEP 9.

[0079] In STEP 9, a UL-NAS message is sent that includes the device ID or temporary device ID, a read command report if a read command was received in STEP 2, and a write completion report if a write command was received in STEP 2. Here, if the D2R signal is not received and the CN has instructed an inventory in STEP 7, the CN assumes that the inventory process has failed and that the device has moved away from the reader's vicinity. Also, if the CN has instructed a read in STEP 7, the CN assumes that the read process has failed. Also, if the CN has instructed a write in STEP 7, the CN assumes that the write process has failed. If the write fails, there is a possibility that a discrepancy in recognition may occur between the device and the CN.

[0080] Therefore, to enhance the coverage of the UL-NAS message transmission in STEP 9, the ambient IoT device may repeat the UL-NAS message transmission in STEP 9. Also, the ambient IoT reader may repeat a random access-like procedure. Also, the CN may retransmit the DL-NAS message if it fails to receive the UL-NAS message.

[0081] Also, from the reader's point of view, a contention-free access procedure, that is, an access method that does not involve a procedure similar to random access, is being considered.

[0082] 9 is a sequence diagram for explaining a communication example (5) according to an embodiment of the present invention. Using FIG. 9, an example will be described in which an inventory, a read command, or a write command is sent from an ambient IoT reader to an ambient IoT device using an initial trigger message in the case of topology 1.

[0083] Step 1: The CN sends an NG-AP message to the leader BS, which includes the target device ID or target group ID, the message type (inventory, read, or write), the information elements to be reported in the case of a read, and the information to be rewritten in the case of a write.

[0084] Step 2: The BS, which is the leader, sends an initial trigger message to the ambient IoT device, including the target device ID or target group ID, or the target temporary device ID or target temporary group ID, the message type (inventory, read, or write), the information element to be reported in the case of a read, and the information to be rewritten in the case of a write.

[0085] Step 3: The ambient IoT device sends a NAS message to the BS, which is the leader, via the D2R interface, including the device ID or temporary device ID as an inventory response, the requested information in the case of a read (Read command report), and a report of rewrite completion in the case of a write (Write complete report).

[0086] Step 4: The leader BS sends the NAS message to the CN via the NG-AP interface.

[0087] 10 is a sequence diagram illustrating a communication example (6) according to an embodiment of the present invention. Using FIG. 10, an example will be described in which an inventory, a read command, or a write command is sent from an ambient IoT reader to an ambient IoT device using an initial trigger message in the case of topology 2.

[0088] Step 1: The CN sends an NG-AP message to the BS, which includes the target device ID or target group ID, the message type (inventory, read, or write), the information element to be reported in the case of a read, and the information to be rewritten in the case of a write.

[0089] Step 2: The BS sends an RRC message to the intermediate node, which is the leader, including the target device ID or target group ID, the message type (inventory, read, or write), the information element to be reported in the case of a read, and the information to be rewritten in the case of a write.

[0090] Step 3: The intermediate node, which is the leader, sends an initial trigger message to the ambient IoT device, including the target device ID or target group ID, or the target temporary device ID or target temporary group ID, the message type (inventory, read, or write), the information element to be reported in the case of a read, and the information to be rewritten in the case of a write.

[0091] Step 4: The ambient IoT device sends a NAS message to the intermediate node (the leader) via the D2R interface, including the device ID or temporary device ID, the requested information (Read command report) in the case of a read, and a write complete report (Write complete report) in the case of a write.

[0092] Step 5: The intermediate node, which is the leader, sends the NAS message to the BS via the Uu interface.

[0093] Step 6: The BS sends the NAS message to the CN via the NG-AP interface.

[0094] 11 is a sequence diagram illustrating an example (7) of communication according to an embodiment of the present invention. Using FIG. 11, an example will be described in which an ambient IoT reader transmits an inventory, a read command, or a write command to an ambient IoT device after completing initial access in the case of topology 1.

[0095] Step 1: The CN sends an NG-AP message containing the target device ID or target group ID to the leader BS.

[0096] Step 2: The leader BS sends an initial trigger message to the ambient IoT device, including the target device ID or target group ID.

[0097] Step 3: The ambient IoT device sends a NAS message containing the device ID or temporary device ID to the leader BS via the D2R interface.

[0098] Step 4: The leader BS sends the NAS message to the CN via the NG-AP interface.

[0099] Step 5: The CN sends a NAS message to the leader BS via the NG-AP interface, including the target device ID or target group ID, message type (inventory, read, or write), information elements to be reported in the case of a read, and information to be rewritten in the case of a write.

[0100] Step 6: The leader BS sends the NAS message to the ambient IoT device via the R2D interface.

[0101] Step 7: The ambient IoT device sends a NAS message to the leader BS via the D2R interface, including the device ID or temporary device ID, the requested information in the case of a read (Read command report), and a report of rewrite completion in the case of a write (Write complete report).

[0102] Step 8: The leader BS sends the NAS message to the CN via the NG-AP interface.

[0103] 12 is a sequence diagram illustrating an example of communication (8) according to an embodiment of the present invention. Using FIG. 12, an example will be described in which an ambient IoT reader transmits an inventory, a read command, or a write command to an ambient IoT device after completing initial access in the case of topology 2.

[0104] Step 1: The CN sends an NG-AP message containing the target device ID or target group ID to the BS.

[0105] Step 2: The BS sends an RRC message to the leader intermediate node, including the target device ID or target group ID.

[0106] Step 3: The intermediate node, which is the leader, sends an initial trigger message to the ambient IoT device, including the target device ID or target group ID.

[0107] Step 4: The ambient IoT device sends a NAS message containing the device ID or temporary device ID to the intermediate node acting as the leader via the D2R interface.

[0108] Step 5: The intermediate node, which is the leader, sends the NAS message to the BS via the Uu interface.

[0109] Step 6: The BS sends the NAS message to the CN via the NG-AP interface.

[0110] Step 7: The CN sends a NAS message to the BS via the NG-AP interface, including the target device ID or target group ID, the message type (inventory, read, or write), the information elements to be reported in the case of a read, and the information to be rewritten in the case of a write.

[0111] Step 8: The BS sends the NAS message to the intermediate node that is the leader via the Uu interface.

[0112] Step 9: The intermediate node, which is the leader, sends the NAS message to the ambient IoT device via the R2D interface.

[0113] Step 10: The ambient IoT device sends a NAS message to the intermediate node (the leader) via the D2R interface, including the device ID or temporary device ID, the requested information (Read command report) in the case of a read, and a write complete report (Write complete report) in the case of a write.

[0114] Step 11: The intermediate node, which is the leader, sends the NAS message to the BS via the Uu interface.

[0115] Step 12: The BS sends the NAS message to the CN via the NG-AP interface.

[0116] Hereinafter, the ambient IoT reader may refer to a BS in Topology 1, a terminal or an intermediate node, or a logical node that realizes the reader function installed in the BS and UE.

[0117] Fig. 13 is a sequence diagram for explaining an example (9) of communication according to an embodiment of the present invention. Steps 1 and 2 shown in Fig. 13 may be executed in the same manner as in Fig. 9. In step 3, assuming that the ambient IoT reader does not succeed in reception, the operation described below may be executed.

[0118] The ambient IoT reader may start a timer when it sends a command message (which may be called an initial trigger message) in step 2 that instructs the ambient IoT device to operate during an access procedure without contention resolution (which may be called contention-free random access).

[0119] The ambient IoT reader may stop the timer when it receives the D2R message of step 3 from the ambient IoT device.

[0120] When the timer expires, the ambient IoT reader may send a message to the ambient IoT device instructing it to resend the D2R message as in step 4'. The D2R message may be a message for instructing the resend, or may be a message identical to the command message of step 2 instructing the ambient IoT device to operate.

[0121] The period from the start to the expiration of the timer may be preset by the CN in the ambient IoT reader, or may be instructed by the CN in the NG-AP message of step 1 instructing the transmission of the command message.

[0122] The above-described operation allows the ambient IoT reader to receive D2R signals with a higher probability in an access procedure without collision resolution in an ambient IoT system, where high strength is not expected due to the performance of the ambient IoT device.

[0123] 14 is a diagram for explaining a write command according to an embodiment of the present invention. Assume that the CN issues a write command. Hereinafter, the same operation may be applied to both STEP 1 in FIG. 5 and STEP 7 in FIG. 5.

[0124] As shown in Figure 14, if the write command DL-NAS message reaches the device and the ambient IoT device rewrites the memory, and then the write completion report sent by the ambient IoT device does not reach the ambient IoT reader, the ambient IoT reader has no way of knowing whether the memory of the ambient IoT device has been rewritten, and there is a possibility that a discrepancy in the recognition of the memory contents will occur between the ambient IoT device and the ambient IoT reader.

[0125] Therefore, if the ambient IoT reader fails to receive the write completion report, it may send a write command failure message to the ambient IoT device. Also, the ambient IoT reader may send a write command notice to the ambient IoT device before sending the write command.

[0126] 15 is a diagram showing an example (1) of NAS message communication according to an embodiment of the present invention. As shown in FIG. 15, in topology 1, a NAS message or a NAS-like message may be sent from an A-IoT device to an AMF or new node X. The AMF or new node X is equipped with a NAS decoder and can decode the message.

[0127] Also, in topology 2, in FIG. 7, an intermediate node is inserted between the A-IoT device and the BS, and the NAS message may be sent from the A-IoT device to the receiving node, AMF or CN new node X.

[0128] 16 is a diagram showing an example (2) of NAS message communication according to an embodiment of the present invention. As shown in FIG. 16, in topology 1, a NAS message or a NAS-like message may be sent from an A-IoT device to a BS equipped with a NAS decoder. The BS is equipped with a NAS decoder and can decode the message.

[0129] Also, in topology 2, in FIG. 8, an intermediate node is inserted between the A-IoT device and the BS, and the NAS message may be sent from the A-IoT device to the receiving node, AMF or CN new node X.

[0130] 17 is a diagram showing an example (3) of NAS message communication according to an embodiment of the present invention. As shown in FIG. 17, in topology 1, a NAS message or a NAS-like message may be sent from an A-IoT device to a new node Y equipped with a NAS decoder. The new node Y is equipped with a NAS decoder and can therefore decode the message.

[0131] Also, in topology 2, in Figure 17, an intermediate node may be inserted between the A-IoT device and new node Y, and the NAS message may be sent from the A-IoT device to new node Y, which is the receiving node.

[0132] A case where an inventory, a read command, or a write command is sent in the initial trigger message in STEP 2 in FIG. 5 will be described.

[0133] The CN may notify the ambient IoT reader of the use case type (eg, inventory, read command, or write command) in the NG-AP message (STEP 1) instructing conflict resolution.

[0134] The ambient IoT device may report its own device ID or temporary device ID to the ambient IoT reader at the same time as transmitting the UL-NAS message (STEP 5) upon completion of collision resolution.

[0135] When the ambient IoT reader receives a write command from the CN in STEP 1, the ambient IoT reader may maintain the following timers.

[0136] Start: When an R2D message (STEP 4) notifying collision resolution is sent. Stop: When a UL-NAS message (STEP 5) and the device ID or temporary device ID of the ambient IoT device are received. Action upon expiration: Send a write command failure message to the ambient IoT device.

[0137] When the ambient IoT device receives a write command failure message, it may consider the most recently received write command to have failed and return the memory to the state it was in before receiving the write command.

[0138] A case where an inventory, a read command, or a write command is sent after the random access-like procedure in FIG. 7 will be described.

[0139] The CN may notify the ambient IoT reader of the use case type (e.g., inventory, read command, or write command) at the same time as sending a DL-NAS message (STEP 7) indicating an inventory or command.

[0140] The ambient IoT device may report its own device ID or temporary device ID to the ambient IoT reader at the same time as sending an inventory or a UL-NAS message (STEP 9) in response to the command.

[0141] When the ambient IoT reader receives a write command from the CN in STEP 7, the ambient IoT reader may maintain the following timers.

[0142] Start: When an R2D message (STEP 8) transmitting a DL-NAS message is sent. Stop: When a UL-NAS message (STEP 9) and the device ID or temporary device ID of the ambient IoT device are received. Action upon expiration: Send a write command failure message to the ambient IoT device.

[0143] When the ambient IoT device receives a write command failure message, it may consider the most recently received write command to have failed and return the memory to the state it was in before receiving the write command.

[0144] 18 is a sequence diagram for explaining an example (1) of command execution according to an embodiment of the present invention. In FIG. 18, steps 1 to 6 may be executed in the same manner as in FIG.

[0145] A case where an inventory, a read command, or a write command is sent after the random access-like procedure in FIG. 18 will be described.

[0146] The CN may notify the ambient IoT reader of the use case type (e.g., inventory, read command, or write command) in a DL-NAS message (STEP 7) indicating an inventory or command.

[0147] The ambient IoT device may report its own device ID or temporary device ID to the ambient IoT reader at the same time as sending an inventory or a UL-NAS message (STEP 9) in response to the command.

[0148] The ambient IoT reader may transmit a write command notification message (STEP 8) to the ambient IoT device when a write command is instructed from the CN in STEP 7. When the ambient IoT device receives the write command notification message, it may transmit a write command notification ACK message (STEP 9) to the ambient IoT reader.

[0149] When the ambient IoT reader receives a write command from the CN in STEP 7, the ambient IoT reader may maintain the following timers.

[0150] Start: When a write command notification message (STEP 8) is sent Stop: When a write command notification ACK message (STEP 9) is received Action upon expiration: The write command is considered to have failed

[0151] When the ambient IoT reader receives the write command notification ACK message, the ambient IoT reader may transmit a DL-NAS message (STEP 10) including a write command to the ambient IoT device.

[0152] 19 is a diagram illustrating an example of command execution according to an embodiment of the present invention. As shown in FIG. 19, the ambient IoT reader transmits a command to the ambient IoT device. Subsequently, the ambient IoT device holds the command without executing it, and transmits a command ACK to the ambient IoT reader. Subsequently, the ambient IoT reader transmits a command execution indication to the ambient IoT device. Subsequently, the ambient IoT device executes the held command. The ambient IoT reader may transmit the command in an initial trigger message, or may transmit the command after random access is completed.

[0153] 20 is a sequence diagram for explaining an example (2) of command execution according to an embodiment of the present invention, which will be used to explain a case where an inventory, read command, or write command message is sent as an initial trigger message and where conflict resolution is performed.

[0154] Step 1: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0155] Step 2: The ambient IoT reader sends an initial trigger message including a device ID or a device group ID to the ambient IoT device. If the message of step 2 that triggers conflict resolution includes a write command message or includes an information element indicating a write command in its content, the ambient IoT device may postpone the write command without executing it.

[0156] Step 3: The ambient IoT device sends a RACH-like preamble to the ambient IoT reader.

[0157] Step 4: The ambient IoT reader sends a RACH-like response to the ambient IoT device, which may include a D2R grant.

[0158] Step 5: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a NAS message including a device ID as D2R data. When the ambient IoT device is pending a write command, the message notifying that the conflict resolution in step 5 has been completed may further include information notifying that the write command has been successfully received (which may be referred to as a write command ACK).

[0159] Step 6: The ambient IoT reader sends an NG-AP message to the CN, which may include the NAS message containing the device ID.

[0160] Step 7: When the CN receives a conflict resolution completion report (step 6) from the ambient IoT device including information (write command ACK) notifying that the write command has been successfully received, or when the CN receives a conflict resolution completion report (step 6) from the ambient IoT device that instructed the write command, the CN may send a message (step 7) to the ambient IoT device instructing it to execute the write command.

[0161] Step 8: When the ambient IoT device receives a message instructing it to execute the write command (step 8), it may execute the pending write command. If the ambient IoT device does not receive a message instructing it to execute the write command (step 8) even after a certain period of time has passed since it received the message that triggers conflict resolution in step 2 (which may be called an initial trigger message), it may discard the write command without executing it.

[0162] 21 is a sequence diagram for explaining an example (3) of command execution according to an embodiment of the present invention, which will be used to explain a case where an inventory, read command, or write command message is sent as an initial trigger message and where conflict resolution is performed.

[0163] Step 1: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0164] Step 2: The ambient IoT reader sends an initial trigger message including a device ID or a device group ID to the ambient IoT device. If the message of step 2 that triggers conflict resolution includes a write command message or includes an information element indicating a write command in its content, the ambient IoT device may postpone the write command without executing it.

[0165] Step 3: The ambient IoT device sends a RACH-like preamble to the ambient IoT reader.

[0166] Step 4: The ambient IoT reader sends a RACH-like response to the ambient IoT device, which may include a D2R grant.

[0167] Step 5: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a NAS message including a device ID as D2R data. When the ambient IoT device is pending a write command, the message notifying that the conflict resolution in step 5 has been completed may further include information notifying that the write command has been successfully received (which may be referred to as a write command ACK).

[0168] Step 6': When the ambient IoT reader receives a conflict resolution completion report message (step 5) including information (write command ACK) notifying that the write command has been successfully received from the ambient IoT device, or when the ambient IoT reader receives the conflict resolution completion report message (step 5) from the ambient IoT device that instructed the write command, the ambient IoT reader may send a message (step 6') instructing the ambient IoT device to execute the write command. Note that in step 6, the ambient IoT reader may also send the message from the ambient IoT device to the CN.

[0169] When the ambient IoT device receives a message instructing it to execute the write command (step 6′), it may execute the pending write command. If the ambient IoT device does not receive a message instructing it to execute the write command (step 6′) even after a certain period of time has passed since it received the message that triggers conflict resolution in step 2 (which may be called an initial trigger message), it may discard the write command without executing it.

[0170] 22 is a sequence diagram for explaining an example (4) of command execution according to an embodiment of the present invention, which will be used to explain a case where an inventory, read command, or write command message is sent as an initial trigger message and where conflict resolution is performed.

[0171] Step 1: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0172] Step 2: The ambient IoT reader sends an initial trigger message including a device ID or a device group ID to the ambient IoT device. If the message of step 2 that triggers conflict resolution includes a write command message or includes an information element indicating a write command in its content, the ambient IoT device may postpone the write command without executing it.

[0173] Step 3: The ambient IoT device sends a RACH-like preamble to the ambient IoT reader. When the ambient IoT device has a write command pending, the ambient IoT device may further include information notifying the successful reception of the write command (which may be referred to as a write command ACK) in the D2R message used for collision resolution in step 3.

[0174] Step 4: The ambient IoT reader transmits a RACH-like response to the ambient IoT device. The RACH-like response may include a D2R grant. When the ambient IoT reader receives a D2R message (step 3) including information (write command ACK) notifying that the write command has been successfully received from the ambient IoT device, or when the ambient IoT reader receives a D2R message (step 3) from the ambient IoT device that instructed the write command, the ambient IoT reader may include information instructing execution of the write command in a message (step 4) notifying that collision resolution has been successful.

[0175] When the ambient IoT device receives an R2D message (step 4) notifying that the conflict resolution has been successful, the ambient IoT device may execute the pending write command. The ambient IoT device may execute the write command based on an explicit instruction by referring to information instructing the execution of the write command, or may execute the write command based on an implicit instruction without referring to information instructing the execution of the write command. If the ambient IoT device does not receive a message (step 4) notifying that the conflict resolution has been successful even after a certain period of time has elapsed since receiving the message that triggers conflict resolution (which may be referred to as an initial trigger message) in step 2, the ambient IoT device may discard the write command without executing it.

[0176] Step 5: The ambient IoT device sends a D2R message to the ambient IoT reader, which may include a NAS message containing the device ID as D2R data.

[0177] Step 6: The ambient IoT reader may send the NAS message from the ambient IoT device to the CN.

[0178] 23 is a sequence diagram for explaining an example (5) of command execution according to an embodiment of the present invention, which will be used to explain a case where an inventory, read command, or write command message is sent using an initial trigger message and conflict resolution is not performed.

[0179] Step 1: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0180] Step 2: The ambient IoT reader sends an initial trigger message including a device ID or a device group ID to the ambient IoT device. If the message for triggering access without conflict resolution (Step 2) includes a write command message, or if the message content includes an information element indicating a write command, the ambient IoT device may postpone executing the write command.

[0181] Step 3: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a NAS message including a device ID as D2R data, and the NAS message may be referred to as an access completion report message. When the ambient IoT device is pending a write command, the access completion report message (step 3) may further include information notifying that the write command has been successfully received (which may be referred to as a write command ACK).

[0182] Step 4: The ambient IoT reader sends an NG-AP message to the CN, which may include the NAS message containing the device ID.

[0183] Step 5: When the CN receives an access completion report message (step 4) from the ambient IoT device including information (write command ACK) notifying that the write command has been successfully received, or when the CN receives an access completion report message (step 4) from the ambient IoT device that instructed the write command, the CN may send a message (step 6) to the ambient IoT device instructing it to execute the write command.

[0184] Step 6: When the ambient IoT device receives a message instructing it to execute the write command (Step 6), it may execute the pending write command. If the ambient IoT device does not receive a message instructing it to execute the write command (Step 6) even after a certain period of time has passed since it received the message that triggers conflict resolution in Step 2 (which may be called an initial trigger message), it may discard the write command without executing it.

[0185] 24 is a sequence diagram for explaining an example (6) of command execution according to an embodiment of the present invention, which will be used to explain a case where an inventory, read command, or write command message is sent using an initial trigger message and conflict resolution is not performed.

[0186] Step 1: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0187] Step 2: The ambient IoT reader sends an initial trigger message including a device ID or a device group ID to the ambient IoT device. If the message for triggering access without conflict resolution (Step 2) includes a write command message, or if the message content includes an information element indicating a write command, the ambient IoT device may postpone executing the write command.

[0188] Step 3: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a NAS message including a device ID as D2R data, and the NAS message may be referred to as an access completion report message. The access completion report message may also be in a format recognizable by the ambient IoT reader. When the ambient IoT device is suspending a write command, the access completion report message (step 3) may further include information notifying that the write command has been successfully received (which may be referred to as a write command ACK).

[0189] Step 4: The ambient IoT reader sends an NG-AP message to the CN, which may include the NAS message containing the device ID.

[0190] Step 4': When the ambient IoT reader receives an access completion report message (step 3) from the ambient IoT device including information (write command ACK) notifying that the write command has been successfully received, or when the ambient IoT reader receives an access completion report message (step 3) from the ambient IoT device that instructed the write command, the ambient IoT reader may send a message (step 4') to the ambient IoT device instructing it to execute the write command.

[0191] When the ambient IoT device receives a message instructing it to execute the write command (step 6), it may execute the pending write command. If the ambient IoT device does not receive a message instructing it to execute the write command (step 4′) even after a certain period of time has elapsed since it received the message that triggers conflict resolution (which may be called an initial trigger message) in step 2, it may discard the write command without executing it.

[0192] 25 is a sequence diagram illustrating an example (7) of command execution according to an embodiment of the present invention, in which an inventory, read command, or write command message is sent after a random access-like procedure and collision resolution is performed.

[0193] Step 1: The CN sends a new NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, or location information of the target ambient IoT device, and is a message that at least requests a response from the target ambient IoT device.

[0194] Step 2: The ambient IoT reader sends an initial trigger message to the ambient IoT device, which includes the device ID or device group ID.

[0195] Step 3: The ambient IoT device sends a RACH-like preamble to the ambient IoT reader.

[0196] Step 4: The ambient IoT reader sends a RACH-like response to the ambient IoT device, which may include a D2R grant.

[0197] Step 5: The ambient IoT device sends a D2R message to the ambient IoT reader, which may include a NAS-secured device ID and location information as D2R data.

[0198] Step 6: The ambient IoT reader sends a new NG-AP message to the CN, which may include the NAS-secured device ID and location information.

[0199] Step 7: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0200] Step 8: The ambient IoT reader sends an R2D message including a write command to the ambient IoT device. If the R2D message (step 8) includes a write command message or includes an information element indicating a write command, the ambient IoT device may postpone the write command without executing it.

[0201] Step 9: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a UL-NAS message as D2R data. When the ambient IoT device is pending a write command, the ambient IoT device may further include information indicating successful reception of the write command (which may be referred to as a write command ACK) in the UL-NAS message (step 9) that is a response to the inventory or command from the CN.

[0202] Step 10: The ambient IoT reader sends an NG-AP message to the CN, which may include the UL-NAS message.

[0203] Step 11: When the CN receives an UL-NAS message (step 10) from an ambient IoT device carrying a response including information (write command ACK) notifying that the write command has been successfully received, or when the CN receives an UL-NAS message (step 10) from an ambient IoT device that instructed the write command, the CN may send a message (step 11) to the ambient IoT device instructing it to execute the write command.

[0204] Step 12: When the ambient IoT device receives the message instructing it to execute the write command (step 8), it may execute the pending write command. If the ambient IoT device does not receive the message instructing it to execute the write command (step 12) even after a certain period of time has passed since it received the write command message in step 8, it may discard the write command without executing it.

[0205] 26 is a sequence diagram illustrating an example (8) of command execution according to an embodiment of the present invention, in which an inventory, read command, or write command message is sent after a random access-like procedure and collision resolution is performed.

[0206] Step 1: The CN sends a new NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, or location information of the target ambient IoT device, and is a message that at least requests a response from the target ambient IoT device.

[0207] Step 2: The ambient IoT reader sends an initial trigger message to the ambient IoT device, which includes the device ID or device group ID.

[0208] Step 3: The ambient IoT device sends a RACH-like preamble to the ambient IoT reader.

[0209] Step 4: The ambient IoT reader sends a RACH-like response to the ambient IoT device, which may include a D2R grant.

[0210] Step 5: The ambient IoT device sends a D2R message to the ambient IoT reader, which may include a NAS-secured device ID and location information as D2R data.

[0211] Step 6: The ambient IoT reader sends a new NG-AP message to the CN, which may include the NAS-secured device ID and location information.

[0212] Step 7: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0213] Step 8: The ambient IoT reader sends an R2D message including a write command to the ambient IoT device. If the R2D message (step 8) includes a write command message or includes an information element indicating a write command, the ambient IoT device may postpone the write command without executing it.

[0214] Step 9: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a UL-NAS message as D2R data. When the ambient IoT device is pending a write command, it may send a UL-NAS message (step 9) that is a response to the inventory or command from the CN, and may also send a D2R message (step 9′) to the ambient IoT reader that includes information notifying the ambient IoT reader that the write command was successfully received (which may be referred to as a write command ACK).

[0215] Step 10: The ambient IoT reader sends an NG-AP message to the CN, which may include the UL-NAS message.

[0216] Step 10': When the ambient IoT reader receives a D2R message (step 9') from the ambient IoT device including information (write command ACK) notifying that the write command has been successfully received, or when the ambient IoT reader receives a UL-NAS message (step 9) including an inventory from the CN or a response to the command from the ambient IoT device that instructed the write command, the ambient IoT reader may send a message (step 10') to the ambient IoT device instructing it to execute the write command.

[0217] When the ambient IoT device receives a message instructing it to execute the write command (step 10′), it may execute the pending write command. If the ambient IoT device does not receive a message instructing it to execute the write command (step 10′) even after a certain period of time has passed since it received the write command message in step 8, it may discard the write command without executing it.

[0218] 27 is a sequence diagram illustrating an example (9) of command execution according to an embodiment of the present invention, in which an inventory, read command, or write command message is sent after initial access is completed and conflict resolution is not performed.

[0219] Step 1: The CN sends an NG-AP message containing the target device ID or target group ID to the ambient IoT reader.

[0220] Step 2: The ambient IoT reader sends an initial trigger message to the ambient IoT device, including the target device ID or target group ID.

[0221] Step 3: The ambient IoT device sends a NAS message containing the device ID or temporary device ID to the ambient IoT reader via the D2R interface.

[0222] Step 4: The ambient IoT leader sends the NAS message to the CN via the NG-AP interface.

[0223] Step 5: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0224] Step 6: The ambient IoT reader sends an R2D message including a write command to the ambient IoT device. If the R2D message (step 6) includes a write command message or if the content of the R2D message includes an information element indicating a write command, the ambient IoT device may postpone executing the write command.

[0225] Step 7: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a UL-NAS message as D2R data. When the ambient IoT device is pending a write command, the ambient IoT device may further include information notifying the successful reception of the write command (which may be referred to as a write command ACK) in the UL-NAS message (step 7) that is a response to the inventory or command from the CN.

[0226] Step 8: The ambient IoT reader sends an NG-AP message to the CN, which may include the UL-NAS message.

[0227] Step 9: When the CN receives an UL-NAS message (step 8) from the ambient IoT device carrying a response including information (write command ACK) notifying that the write command has been successfully received, or when the CN receives an UL-NAS message (step 8) from the ambient IoT device that instructed the write command, the CN may send a message (step 9) to the ambient IoT device instructing it to execute the write command.

[0228] Step 10: When the ambient IoT device receives the message instructing it to execute the write command (step 8), it may execute the pending write command. If the ambient IoT device does not receive the message instructing it to execute the write command (step 10) even after a certain period of time has passed since it received the write command message in step 6, it may discard the write command without executing it.

[0229] 28 is a sequence diagram for explaining an example (10) of command execution according to an embodiment of the present invention. Using FIG. 28, a case where an inventory, read command, or write command message is sent after initial access is completed and conflict resolution is not performed will be described.

[0230] Step 1: The CN sends an NG-AP message containing the target device ID or target group ID to the ambient IoT reader.

[0231] Step 2: The ambient IoT reader sends an initial trigger message to the ambient IoT device, including the target device ID or target group ID.

[0232] Step 3: The ambient IoT device sends a NAS message containing the device ID or temporary device ID to the ambient IoT reader via the D2R interface.

[0233] Step 4: The ambient IoT leader sends the NAS message to the CN via the NG-AP interface.

[0234] Step 5: The CN sends an NG-AP message to the ambient IoT reader, which may include the device ID, device group ID, etc. of the target ambient IoT device, and may also include a write command.

[0235] Step 6: The ambient IoT reader sends an R2D message including a write command to the ambient IoT device. If the R2D message (step 6) includes a write command message or if the content of the R2D message includes an information element indicating a write command, the ambient IoT device may postpone executing the write command.

[0236] Step 7: The ambient IoT device sends a D2R message to the ambient IoT reader. The D2R message may include a UL-NAS message as D2R data. When the ambient IoT device is pending a write command, it may send a UL-NAS message (step 7) that is a response to the inventory or command from the CN, and may also send a D2R message (step 7′) to the ambient IoT reader that includes information notifying the ambient IoT reader that the write command was successfully received (which may be referred to as a write command ACK).

[0237] Step 8: The ambient IoT reader sends an NG-AP message to the CN, which may include the UL-NAS message.

[0238] Step 8': When the ambient IoT reader receives a D2R message (step 7') from the ambient IoT device including information (write command ACK) notifying that the write command has been successfully received, or when the ambient IoT reader receives a UL-NAS message (step 7) from the ambient IoT device that instructed the write command, the ambient IoT reader may send a message (step 8') to the ambient IoT device instructing it to execute the write command.

[0239] When the ambient IoT device receives a message instructing it to execute the write command (step 8'), it may execute the pending write command. If the ambient IoT device does not receive a message instructing it to execute the write command (step 8') even after a certain period of time has passed since it received the write command message in step 6, it may discard the write command without executing it.

[0240] Embodiments of the present invention may only be applied if the corresponding capability is supported by the UE, IAB or ambient IoT device and / or enabled by the corresponding higher layer parameters.

[0241] The above-described embodiment can reduce the probability of memory recognition discrepancies occurring between an ambient IoT device and an ambient IoT reader or control node due to undelivered signaling in a write command use case.

[0242] In other words, it is possible to suppress problems that occur when a signal transmitted from an Ambient Internet of Things (IoT) device does not arrive.

[0243] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. 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.

[0244] <Base Station 10> Figure 29 is a diagram showing an example of the functional configuration of the base station 10 in an embodiment of the present invention. As shown in Figure 29, the 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 Figure 29 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.

[0245] The transmitter 110 has 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 has 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.

[0246] 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 an ambient IoT device.

[0247] 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. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0248] <Terminal 20> Figure 30 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 30, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 30 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.

[0249] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals 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.

[0250] 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 setting information that is set in advance. The content of the setting information is, for example, information related to communication with an ambient IoT device.

[0251] 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. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0252] (Hardware Configuration) The block diagrams (FIGS. 29 and 30) 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 directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0253] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, 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.

[0254] 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. 31 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.

[0255] In the following description, the term "apparatus" can be interpreted 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.

[0256] Each function in the base station 10 and the terminal 20 is realized by loading specified 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.

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

[0258] 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. 29 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 30 may be implemented by a control program stored in the storage device 1002 and running on 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 also be transmitted from a network via a telecommunications line.

[0259] 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 read-only memory (EPROM), an electrically erasable programmable read-only memory (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.

[0260] 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 (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0261] 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, a communication module, etc. 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.

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

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

[0264] Furthermore, the base station 10 and the 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, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0265] Fig. 32 shows an example configuration of a vehicle 2001. As shown in Fig. 32, 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.

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

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

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

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

[0270] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

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

[0274] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle 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.

[0275] (Summary of the embodiment) As described above, according to the embodiment of the present invention, there is provided a communication device having a transmitter that transmits a message including a write command to an ambient Internet of Things (IoT) device, and a receiver that receives a message including a response to the write command from the ambient IoT device, wherein the transmitter transmits a message to the ambient IoT device instructing it to execute the write command.

[0276] The above configuration can reduce the probability of memory recognition discrepancies occurring between an ambient IoT device and an ambient IoT reader or control node due to signaling failure in a write command use case. That is, it can suppress malfunctions caused when a signal transmitted from an ambient IoT (Ambient Internet of Things) device does not arrive.

[0277] The transmitter may transmit an initial trigger message including the write command to the ambient IoT device. This configuration can reduce the probability of a memory recognition discrepancy occurring between the ambient IoT device and an ambient IoT reader or control node due to a signaling failure in a write command use case.

[0278] The transmitter may transmit a message including the write command to the ambient IoT device after the initial access is completed. This configuration can reduce the probability of a memory recognition discrepancy occurring between the ambient IoT device and an ambient IoT reader or control node due to a write command use case not being received.

[0279] When the receiving unit receives a collision resolution report message or an access completion report message including a response to the write command from the ambient IoT device, or when the receiving unit receives a collision resolution report message or an access completion report message from the ambient IoT device that transmitted the write command, the transmitting unit may transmit a message instructing the ambient IoT device to execute the write command. This configuration can reduce the probability of a memory recognition discrepancy occurring between the ambient IoT device and an ambient IoT reader or control node due to signaling failure in a write command use case.

[0280] The transmitter may start a timer when transmitting an initial trigger message to the ambient IoT device, and may retransmit the initial trigger message when the timer expires. With this configuration, in an access procedure in an ambient IoT system without collision resolution, an ambient IoT reader can receive a D2R signal that is not expected to have high strength due to the performance of the ambient IoT device with a higher probability.

[0281] Furthermore, according to an embodiment of the present invention, a communication method is provided in which a communication device executes the steps of sending a message including a write command to an ambient Internet of Things (IoT) device, receiving a message including a response to the write command from the ambient IoT device, and sending a message to the ambient IoT device instructing it to execute the write command.

[0282] The above configuration can reduce the probability of memory recognition discrepancies occurring between an ambient IoT device and an ambient IoT reader or control node due to signaling failure in a write command use case. That is, it can suppress malfunctions caused when a signal transmitted from an ambient IoT (Ambient Internet of Things) device does not arrive.

[0283] (Supplementary Notes on the Embodiments) 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to 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 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, but such devices may be realized by 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, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

[0285] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: 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 a 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 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable 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 LTE and / or LTE-A with 5G).

[0286] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged 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.

[0287] In this specification, a specific operation described as being performed by the base station 10 may 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).

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

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

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

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

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

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

[0294] Note that terms described 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.

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

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

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

[0298] 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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0299] 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 partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

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

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

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

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

[0304] 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 multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). 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.

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

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

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

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

[0309] 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."

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

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

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

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

[0314] Numerology may be communication parameters that apply to the transmission and / or 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, specific windowing operations performed by the transceiver in the time domain, etc.

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

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

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

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

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

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

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

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

[0323] 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 greater than or equal to 1 ms.

[0324] A resource block (RB) is a resource allocation unit in the time domain and the 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 the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

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

[0326] 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, etc.

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

[0328] 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 BWP and numbered within the BWP.

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

[0330] 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."

[0331] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to 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.

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

[0333] 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."

[0334] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

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

[0336] REFERENCE SIGNS LIST 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Core network 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire 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 system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A communications device comprising: a transmitter that transmits a message including a write command to an ambient IoT (Internet of Things) device; and a receiver that receives a message including a response to the write command from the ambient IoT device, wherein the transmitter transmits a message to the ambient IoT device instructing it to execute the write command.

2. The communication device according to claim 1, wherein the transmitter transmits an initial trigger message including the write command to the ambient IoT device.

3. The communication device according to claim 1, wherein the transmitter transmits a message including the write command to the ambient IoT device after initial access is completed.

4. A communication device as described in claim 1, wherein the transmitting unit transmits a message to the ambient IoT device instructing it to execute the write command when the receiving unit receives a collision resolution report message or an access completion report message including a response to the write command from the ambient IoT device, or when the transmitting unit receives a collision resolution report message or an access completion report message from the ambient IoT device that transmitted the write command.

5. The communication device of claim 1, wherein the transmitter starts a timer when transmitting an initial trigger message to the ambient IoT device, and retransmits the initial trigger message when the timer expires.

6. A communication method in which a communication device executes the steps of: sending a message including a write command to an ambient IoT (Internet of Things) device; receiving a message including a response to the write command from the ambient IoT device; and sending a message to the ambient IoT device instructing it to execute the write command.

Images