Device and communication method

Abstract

A device having a lower complexity than a narrow band Internet of Things (NB-IoT) device includes: a communication unit that receives or transmits a first signal; and a control unit that determines a second timing or a second period in which a second signal is transmitted by the communication unit on the basis of a first timing or a first period in which the first signal is received or transmitted.

Description

Device and communication method

[0001] The present disclosure relates to devices and communication methods.

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

[0003] Furthermore, in Release 18 (Rel-18) of 3GPP (registered trademark), ambient IoT (A-IoT: Ambient Internet of Things) is being considered (see, for example, Non-Patent Document 2). Ambient IoT targets devices with extremely simple configurations for low-end IoT applications that operate with extremely low power consumption.

[0004] 3GPP TS 38.300 V17.3.0 (2022-12)”Revised SID on Ambient IoT”, RP-232404, 3GPP TSG RAN Meeting #101, September 20233GPP TR 38.848 V1.0.0 (2023-09)3GPP TS 36.211 V16.8.0 (2023-09)”Study on solutions for Ambient IoT (Internet of Things) in NR”, RP-234058, 3GPP TSG RAN Meeting #102, December 2023

[0005] There is room for further consideration regarding the timing of communication in a communication system including an ambient IoT device. If the ambient IoT device cannot appropriately determine the communication timing, information or signals may not be transmitted or received appropriately, which may result in degradation of system performance. Therefore, it is desirable to determine the communication timing suitable for the communication system so that information or signals can be transmitted appropriately.

[0006] One aspect of the present disclosure provides a device and a communication method that can perform communication at appropriate times in a communication system including an ambient IoT device.

[0007] A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes a communication unit that receives or transmits a first signal, and a control unit that determines a second timing or second period at which a second signal is transmitted by the communication unit based on a first timing or first period at which the first signal is received or transmitted.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. A diagram illustrating Topology 1. A diagram illustrating Topology 2. A diagram illustrating Topology 3 in DL assistance. A diagram illustrating Topology 3 in UL assistance. A diagram illustrating Topology 4. A diagram illustrating backscatter transmission. A diagram illustrating a communication flow of DT in Topology 1. A diagram illustrating a communication flow of DO-DTT in Topology 1. A diagram illustrating a communication flow of DT in Topology 2. A diagram illustrating a communication flow of DO-DTT in Topology 2. A diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. A diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. A diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. A diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. A diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 1 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 2 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 3 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 4 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 5 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 6 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 7 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. 1 illustrates an example of an interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure.FIG. 1 is a diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of interaction between a base station and an A-IoT UE according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of operation of a device according to an embodiment of the present disclosure. FIG. 5 is a block diagram illustrating an example of the configuration of a base station according to an embodiment of the present disclosure. FIG. 6 is a block diagram illustrating an example of the configuration of a device according to an embodiment of the present disclosure. FIG. 7 is a diagram illustrating an example of the hardware configuration of a base station and a device according to an embodiment of the present disclosure. FIG. 8 is a diagram illustrating an example of the configuration of a vehicle according to an embodiment of the present disclosure.

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

[0010] In the operation of the wireless communication system according to the embodiment of the present disclosure, existing technology is used as appropriate. The existing technology is, for example, the existing LTE or NR, but is not limited to the existing LTE or NR. In addition, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced, unless otherwise specified.

[0011] In addition, in the embodiments of the present disclosure 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 referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0012] Furthermore, in the embodiments of the present disclosure, 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.).

[0013] Furthermore, in the embodiments of the present disclosure, "configuring" radio parameters, etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station, a device, a terminal, etc. are set.

[0014] (Embodiment) <Wireless Communication System> FIG. 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. As illustrated in FIG. 1, the wireless communication system 1 includes a base station 10 and a device 20. While FIG. 1 illustrates one base station 10 and one device 20, this is merely an example, and multiple base stations and devices may exist. The base station may also be referred to as a BS (Base Station), gNB, or the like. The device 20 may be a form of terminal (UE: User Equipment) and may be an ambient IoT device, which is a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device. The ambient IoT device may also be referred to as an ambient IoT terminal, ambient IoT UE, or the like.

[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the device 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. The frequency domain may be defined by the number of subcarriers or the number of resource blocks.

[0016] The base station 10 transmits DL signals such as control information, setting information, and data via DL (Downlink) to the device 20. The base station 10 receives UL signals such as control information, information related to the processing capability of the device 20 (device capability (information) or A-IoT capability (information); for example, capability, device capability, A-IoT capability, A-IoT device capability, etc.), and data via UP (Uplink) from the device 20.

[0017] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a physical downlink shared channel (PDSCH), and the control channel may include a physical downlink control channel (PDCCH). For example, the base station 10 transmits control information to the device 20 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel or a data channel, and the PDCCH is an example of a downlink control channel. The PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.

[0018] As will be described later, the wireless communication system may include intermediate nodes, assisting nodes, and / or terminals (UEs) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be written simply as " / ".

[0019] The device 20 is a communication device equipped with a wireless communication function, and may be an ambient IoT device (e.g., a sensor, etc.) as described above. Hereinafter, the ambient IoT device will also be referred to as an A-IoT UE.

[0020] The device 20 receives DL signals such as control signals, setting information, and data from the base station 10 via DL, and transmits UL signals such as control signals, capability information of the device 20, and data to the base station 10 via UL.

[0021] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel may include a physical uplink shared channel (PUSCH), and the control channel may include a physical uplink control channel (PUCCH). For example, the device 20 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel or a data channel, and the PUCCH is an example of an uplink control channel. Note that the PUSCH or the PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or the PUCCH.

[0022] <Ambient IoT> Rel-18 approved the study of ambient IoT, which is even lower-end than the existing NB-IoT (see, for example, Section 10 of Non-Patent Document 4) (see, for example, Non-Patent Document 2). Ambient IoT targets ultra-low power consumption and ultra-low complexity devices.

[0023] In Ambient IoT, for example, the following deployment scenarios and characteristics may be considered for relevant use cases: Indoor or outdoor environment Base station type, e.g., macro / micro / pico cell-based deployment Connectivity topology, e.g., which nodes communicate with Ambient IoT devices, such as base stations, terminals (UE), relays and repeaters Duplexing method, TDD or FDD, licensed or unlicensed frequency band Coexistence with UE and network equipment in frequency bands for existing 3GPP technologies Assumptions of traffic originating from / terminating to devices

[0024] Based on the above deployment scenarios and characteristics, for example, the following RAN design targets can be formulated: Power consumption Complexity Coverage Data rate Positioning accuracy

[0025] Based on deployment scenarios appropriate for the relevant use cases, compare and evaluate the feasibility of meeting design targets and identify supporting features.

[0026] <Device Types and Topologies> Based on the results of the study items, TR 38.848 (Non-Patent Document 3) was approved. TR 38.848 considers the following categories of ambient IoT devices: Device A: Device A has no power (energy) storage, no independent signal generation or signal amplification functions, and performs backscattering transmission. Device B: Device B has power storage, no independent signal generation function, and performs backscattering transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, independent signal generation function, and an active RF (radio frequency) component for transmission.

[0027] The complexity of device A is assumed to be about the same as RFID (Frequency Frequency Identification).

[0028] TR 38.848 defines the following topologies 1 to 4 in an ambient IoT network.

[0029] Fig. 2 is a diagram illustrating Topology 1. As shown in Fig. 2, Topology 1 is a configuration in which a base station (BS) and an ambient IoT device communicate with each other. The ambient IoT device directly communicates with the base station in a two-way manner.

[0030] 3 is a diagram illustrating Topology 2. As shown in FIG. 3, Topology 2 is a configuration in which a base station and an ambient IoT device communicate with each other 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.

[0031] 4 is a diagram illustrating Topology 3 in DL assistance. As shown in FIG. 4, Topology 3 is a configuration including communication between a base station and an assisting node, communication between the assisting node and an ambient IoT device, and communication between the ambient IoT device and a base station.

[0032] The support node supports DL communication. For example, as shown in Figure 4, the support node receives DL signals from the base station and transmits the received DL signals to the ambient IoT device. For UL communication, the ambient IoT device transmits UL signals directly to the base station.

[0033] Fig. 5 is a diagram illustrating Topology 3 in UL support. As shown in Fig. 5, Topology 3 is a configuration including communication between a base station and a support node, communication between a support node and an ambient IoT device, and communication between the ambient IoT device and a base station.

[0034] The support node supports UL communication. For example, as shown in Figure 5, the support node receives UL signals from the ambient IoT device and transmits the received UL signals to the base station. For DL ​​communication, the ambient IoT device receives DL signals directly from the base station.

[0035] The supporting nodes shown in FIGS. 4 and 5 may be, for example, relays, IAB nodes, UEs, repeaters, etc.

[0036] 6 is a diagram illustrating Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device performs bidirectional communication with the UE. Communication related to Topology 4 may be considered as side link (SL) communication.

[0037] In the above topologies 1 to 4, the ambient IoT device may be provided with a carrier wave from another node inside or outside the topology (see Section 4.2.1 of Non-Patent Document 3).

[0038] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE of Topology 4) in addition to the device 20. In this specification, the base station, the support node, the intermediate node, and the terminal may be read as a network or a (network) node. Also, an A-IoT device may be simply referred to as A-IoT.

[0039] Backscatter Transmission Base stations, intermediate nodes, support nodes, and other nodes transmit RF signals to ambient IoT devices that are activated and obtain power from the RF operating fields from the base stations, intermediate nodes, support nodes, and other nodes via inductive coupling.

[0040] The ambient IoT device backscatters and modulates the RF signals received from the base station, intermediate node, support node, and other nodes by switching the reflection coefficient of the device's antenna, and transmits information to the base station, intermediate node, support node, and other nodes.

[0041] FIG. 7 is a diagram illustrating backscatter transmission. FIG. 7 shows an example in which an ambient IoT device performs ON-OFF keying and transmits information. The dashed line area shown in FIG. 7 indicates an OFF section, which may correspond to information (bit) "0." A sine wave signal may correspond to information "1."

[0042] <Rel-19 SID> The Rel-19 SID (Study Item Description) examined solutions necessary and feasible for A-IoT (see Section 4.1 of Non-Patent Document 5). The examined solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

[0043] Additionally, for the DL and UL of A-IoT, several issues will be discussed under the leadership of RAN 1. One of the issues to be discussed is the scheduling and timing relationship between DL and UL in A-IoT. In discussing the scheduling and timing relationship, the following 1. traffic flow, 2. device assumptions, and 3. topology may be considered.

[0044] 1. Traffic Flow The following DT and DO-DTT are being considered as traffic flows for A-IoT.

[0045] DT (device terminated) Traffic includes transmission (DL) to the A-IoT UE, but no transmission (UL) from the A-IoT UE. In other words, there is information to be transmitted to the A-IoT UE, but no information to be transmitted from the A-IoT UE. DT corresponds to a command type in which there is an instruction such as a command or instruction to the A-IoT UE.

[0046] DO-DTT (device originated - device terminated triggered) Traffic includes a trigger from the network (NW) and a transmission (UL) from the A-IoT UE. In other words, traffic includes information transmitted from the A-IoT UE. DO-DTT corresponds to, for example, a sensor information report type in which the A-IoT UE transmits sensor information collected by the A-IoT UE.

[0047] In this disclosure, transmission of information corresponds to transmission of a signal containing information or transmission of a signal. In this disclosure, transmission to a certain device X corresponds to transmission of a signal (or information) to device X. In addition, transmission from a certain device X and transmission by a certain device X correspond to device X transmitting a signal (or information). In addition, reception from a certain device X corresponds to receiving a signal (or information) transmitted by device X. In addition, reception by a certain device X corresponds to device X receiving a signal (or information).

[0048] 2. Device Assumptions The following TX (transmission) and FR (frequency range) 1-FDD are assumed for A-IoT UE.

[0049] TX TX is a backscatter UL transmission without amplification or a general amplified UL transmission. Alternatively, an amplified backscatter UL transmission may be performed.

[0050] FR1-FDD FR1-FDD is applied to the A-IoT UE. That is, the A-IoT UE can switch carrier frequencies between DL carriers and UL carriers. However, the present disclosure is not limited to FR1-FDD and may be applied to TDD, FR2, or FR3.

[0051] The frequency bands of each FR are, for example, as follows: FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz FR3: 7.125 GHz to 24.25 GHz

[0052] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 kHz or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

[0053] 3. Topology Among the topologies shown in FIGS. 2 to 6, attention is focused on Topology 1 and Topology 2.

[0054] In Topology 1, UL and / or DL ​​communication is performed between a base station and an A-IoT UE without passing through an intermediate node. Note that the base station in Topology 1 may correspond to a microcell.

[0055] In Topology 2, communication is performed between a base station and an A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with an intermediate node located between the base station and the A-IoT UE. Note that the base station in the case of Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as an intermediate UE, int. UE (intermediate UE), etc.

[0056] <Communication Flow> The signal design for A-IoT UEs may be designed to be common between Topology 1 and Topology 2. In order to have a common signal design for A-IoT UEs, the communication flows of DT and DO-DTT in Topology 1 and Topology 2 can be considered. The following four communication flows can be assumed as the communication flows of DT and DO-DTT in Topology 1 and Topology 2.

[0057] As shown in the four communication flows 1. to 4. below, the A-IoT UE wakes up in step 1 and receives information (or a signal) in step 2. Also, as shown in the communication flows 2. and 4. below, the A-IoT UE transmits a signal (or information) in step 3.

[0058] 1. DT Communication Flow in Topology 1 Figure 8 is a diagram showing the DT communication flow in Topology 1. Figure 8 shows the flow of signals between the base station and the A-IoT UE. Note that the communication flow shown in Figure 8 is a DT communication flow, so there is information transmission from the base station to the A-IoT UE, but there is no information transmission from the A-IoT UE to the base station.

[0059] The following two steps are assumed in the DT communication flow in Topology 1. Note that Step 1 starts when a packet is generated in an upper layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 8 ).

[0060] Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform transmitted from a base station. The signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE. The carrier waveform may be replaced with a carrier wave. Step 2: The A-IoT UE receives information from the base station.

[0061] The A-IoT UE may be woken up by a signal (e.g., a radio frequency signal (RF) signal) transmitted from a source other than the base station. Here, the signal transmitted from a source other than the base station may correspond to an energy source that supplies energy to the A-IoT UE.

[0062] 2. DO-DTT Communication Flow in Topology 1 Figure 9 is a diagram showing the DO-DTT communication flow in Topology 1. Figure 9 shows the flow of signals between a base station and an A-IoT UE. Note that the communication flow shown in Figure 9 is a DO-DTT communication flow, and therefore includes information transmission from the base station to the A-IoT UE and information transmission from the A-IoT UE to the base station.

[0063] The following three steps are assumed in the DO-DTT communication flow in Topology 1. Note that Step 1 starts when a packet is generated in a higher layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 9).

[0064] Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform sent from the base station. Step 2: The A-IoT UE receives information from the base station. Step 3: The A-IoT UE sends a signal to the base station.

[0065] 3. DT Communication Flow in Topology 2 Figure 10 is a diagram showing the DT communication flow in Topology 2. Figure 10 shows the flow of signals between the base station, the int. UE, and the A-IoT UE. Note that the communication flow shown in Figure 10 is a DT communication flow, so there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0066] The following four steps are assumed in the DT communication flow in Topology 2. Note that Step 0 starts when a packet is generated in an upper layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 10).

[0067] Step 0: The int. UE receives a trigger from the base station to send a signal such as a carrier waveform to the A-IoT UE, and sends a signal to the A-IoT UE based on the trigger. Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform sent from the int. UE. Step 2: The A-IoT UE receives information from the int. UE. Step X: The int. UE sends a signal to the base station.

[0068] 4. DO-DTT Communication Flow in Topology 2 Figure 11 is a diagram showing the DO-DTT communication flow in Topology 2. Figure 11 shows the flow of signals between the base station, the int. UE, and the A-IoT UE. Note that the communication flow shown in Figure 11 is a DO-DTT communication flow, and therefore includes information transmission to the A-IoT UE and information transmission from the A-IoT UE.

[0069] The following five-step communication flow is assumed for the DO-DTT communication flow in Topology 2. Note that step 0 starts when a packet is generated in a higher layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 11).

[0070] Step 0: The int. UE receives a trigger from the base station to send a signal such as a carrier waveform to the A-IoT UE, and sends a signal to the A-IoT UE based on the trigger. Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform sent from the int. UE. Step 2: The A-IoT UE receives information from the int. UE. Step 3: The A-IoT UE sends a signal to the int. UE. Step X: The int. UE sends a signal to the base station.

[0071] In addition, in the above four communication flows 1. to 4., step 2 and step 3 may be divided into two steps (in other words, may have two sub-steps).

[0072] For example, in the communication flow of DT in Topology 1 / 2, step 2 may have the following two sub-steps (step 2A and step 2B): Step 2A: The A-IoT UE receives information A (e.g., control information or signaling) from the base station / int. UE. Step 2B: The A-IoT UE receives information B (e.g., data information or signaling) from the base station / int. UE.

[0073] Also, for example, in the communication flow of DO-DTT in Topology 1 / 2, step 3 may have the following two sub-steps (step 3A and step 3B): Step 3A: The A-IoT UE transmits signal A (e.g., control information or signal) to the base station / int. UE. Step 3B: The A-IoT UE transmits signal B (e.g., data information or signal) to the base station / int. UE.

[0074] <Analysis> In A-IoT, communication flows including DT and DO-DTT as described above are being considered, but there is room for further consideration regarding the transmission timing and / or reception timing in the communication flows.

[0075] For example, if the reception timing is inappropriate, the A-IoT UE may not be able to obtain appropriate information from a network such as a base station, and if the transmission timing is inappropriate, it may not be able to transmit information to the network appropriately, resulting in incorrect operation. Similar problems occur with base stations and int. UEs. Furthermore, since A-IoT UEs are expected to be devices with extremely simple configurations for low-end IoT applications that operate with extremely low power consumption, they may not have time synchronization capabilities. In this case, too, the timing at which the A-IoT UE performs transmission and / or reception can become an issue. Furthermore, if the A-IoT UE cannot transmit and / or receive at the appropriate timing, it may consume unnecessary power.

[0076] Therefore, below we will describe proposals regarding the communication timing of information or signals in the DT communication flow and DO-DTT communication flow in Topology 1 and Topology 2, taking into account the timing relationship between two of the steps mentioned above.

[0077] Specifically, this proposal includes Proposal 1, which relates to communication timing in the DT communication flow, and Proposal 2, which relates to communication timing in the DO-DTT communication flow. Proposal 1 is composed of more specific Proposal 1-1 and Proposal 1-2, and Proposal 2 is composed of more specific Proposals 2-1 to 2-3.

[0078] It should be noted that some or all of the proposals described below may be applied to all A-IoT device types (e.g., all of the above-mentioned devices A, B, and C), or may be applied to some A-IoT device types (e.g., only certain A-IoT device types).

[0079] Also, different options in the proposals described below may apply to different A-IoT device types.

[0080] Also, different A-IoT device types may have different A-IoT capabilities.

[0081] Furthermore, some or all of the suggestions described below may only apply if the corresponding capabilities are supported by the A-IoT device and / or if the corresponding functionality is enabled by the network.

[0082] Furthermore, the items explained in Proposal 1-1, Proposal 1-2, Proposal 2-1, Proposal 2-2, and Proposal 2-3 may be combined as appropriate as long as no contradictions arise.

[0083] In the following, "timing" may be replaced with "time."

[0084] "Wake up" may mean that the circuitry of the A-IoT UE activates or resumes from sleep (or a sleep state or mode). The state in which the A-IoT UE is awake may be referred to as a wake-up state or mode, a powered-up state or mode, a normal state or mode, an operating state or mode, a connected state or mode, etc. Thus, the A-IoT UE may have a wake-up state and a sleep state.

[0085] A signal such as a carrier waveform or RF signal transmitted from a base station, an int. UE, or the like to wake up an A-IoT UE (circuit) may be a WUS (Wake Up Signal) or a signal similar to a WUS used in current wireless communication systems. The signal may be referred to as a signal for waking up an A-IoT UE (circuit), a wake-up signal (WUS), a start-up signal, or the like.

[0086] <Proposal 1-1> Below, we will explain a proposal (Proposal 1-1) related to the timing relationship between Step 1 and Step 2 shown below for DT in Topology 1. Step 1: The A-IoT UE wakes up by a carrier waveform (or carrier wave, which may be replaced) or other RF signal transmitted from the BS as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the BS.

[0087] [Option 1] Step 2 may be performed at a time offset from step 1. The A-IoT UE may receive information from the BS at a time offset from step 1.

[0088] The granularity of the time offset can be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond or any time unit defined for A-IoT.

[0089] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0090] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0091] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) about the time offset from the BS before step 2( / 1), and the time offset may be preset by the information. When the time offset is notified by the BS, a minimum allowed value and / or a maximum allowed value may be specified in the specification or reported as the A-IoT capability (the A-IoT UE may report the minimum allowed value and / or the maximum allowed value to the BS as the A-IoT capability). In other words, the A-IoT UE may not assume a time offset smaller than value X (minimum allowed value) and / or a time offset larger than value Y (maximum allowed value) (the A-IoT UE may not assume a time offset smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value)).

[0092] FIG. 12 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 1-1.

[0093] As shown in the figure, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE in response to the occurrence of a packet in a higher layer such as the gNB's application layer (corresponding to "Packet arrival" shown in the figure), and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). Then, the gNB transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB at a time offset from Step 1 (Step 2).

[0094] [Option 2] Step 2 may be performed within a time window, which may also be referred to as a time interval, period, etc. (e.g., during which the A-IoT UE performs monitoring). For example, the A-IoT UE may receive information from the BS within the time window.

[0095] The beginning or start of the time window may be some time offset from step 1.

[0096] The granularity of the time window and time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond or any time unit defined for A-IoT.

[0097] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0098] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0099] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) about the time offset from the BS before step 2( / 1), and the time offset may be preset by the information. When the time offset is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specification or reported as the A-IoT capability (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as the A-IoT capability). In other words, the A-IoT UE may not assume a time offset smaller than value X (minimum allowed value) and / or a time offset larger than value Y (maximum allowed value) (the A-IoT UE may not assume a time offset smaller than value X (minimum allowed value) and / or a time offset larger than value Y (maximum allowed value)).

[0100] The length of the time window (time window length) may be specified / reported / notified as described in (2a) to (2c) below.

[0101] (2a) The time window length may be specified in the specification. In this case, the time window length may be, for example, 1 millisecond, 4 slots, etc. All A-IoT UEs may support this time window length value, or the time window length may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different time window lengths may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0102] (2b) The time window length may be reported as an A-IoT capability (an A-IoT UE may report the time window length to the BS as an A-IoT capability).

[0103] (2c) The time window length may be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) regarding the time window length from the BS before step 2( / 1), and the time window length may be preset by the information. When the time window length is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specification or reported as the A-IoT capability (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as the A-IoT capability). In other words, the A-IoT UE may not assume a time window length smaller than the value X (minimum allowed value) and / or larger than the value Y (maximum allowed value) (the A-IoT UE may not assume a time window length smaller than the value X (minimum allowed value) and / or larger than the value Y (maximum allowed value)).

[0104] FIG. 13 is a diagram showing an example of interaction between a BS and an A-IoT UE according to option 2 of proposal 1-1.

[0105] As shown in the figure, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE in response to the occurrence of a packet in a higher layer such as the gNB's application layer (corresponding to "Packet arrival" shown in the figure), and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). Then, the gNB transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within a time window starting at a time offset from Step 1 (Step 2).

[0106] Also, in option 2, the A-IoT UE may monitor information from the BS within a time window after waking up. In other words, the A-IoT UE may assume that information will be transmitted or received from the BS within the time window. Also, for example, if the A-IoT UE does not receive information from the BS within the time window, it may transition or move to a sleep state. In other words, if the A-IoT UE does not receive information from the BS within the time window, it may not receive / monitor information from the BS after the time window (it may not assume that information will be transmitted or received from the BS).

[0107] FIG. 14 is a diagram showing an example of communication between a BS and an A-IoT UE according to option 2 of proposal 1-1.

[0108] As shown in the figure, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE in response to the occurrence of a packet in a higher layer such as the gNB's application layer (corresponding to "Packet arrival" shown in the figure). In response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). Then, the A-IoT UE monitors information from the gNB within a time window that starts at a time offset from Step 1 (Step 2). After the time window, the A-IoT UE stops monitoring.

[0109] In option 2, the time window may be defined to include only the start or end timing of the signal / information transmitted / received in step 2 (i.e., the other timing may be outside the time window), or it may be defined to include the entire signal / information transmitted / received in step 2 (i.e., both the start timing and the end timing).

[0110] <Variation of Proposal 1-1> If step 2 is divided into step 2A and step 2B for DT in Topology 1 as follows, the content of Proposal 1-1 described above may also be applied to the timing relationship between step 1 and step 2A. In this case, the content of Proposal 1-1, in which "step 2" is replaced with "step 2A," applies. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the BS as an energy source that supplies energy to the A-IoT UE. Step 2A: The A-IoT UE receives information A (e.g., control information or a signal) from the BS. Step 2B: The A-IoT UE receives information B (e.g., data information or a signal) from the BS. In this case, for example, the A-IoT UE may receive / decode information B based on information included in information A (e.g., time / frequency / code (domain) resources, modulation / waveform / coding scheme, etc. included in information A). That is, information A includes information for encoding / receiving / decoding information B.

[0111] The contents of Proposal 1-1 and / or its variations described above may also be applied to the timing relationship between step 1 and step 2 and / or the timing relationship between step 1 and step 2A for DT in Topology 2. In this case, the contents of Proposal 1-1 and / or its variations, with "BS" replaced by "intermediate UE", apply. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the intermediate UE as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the intermediate UE. (Or, Step 2A: The A-IoT UE receives information A (e.g., control information or signal) from the intermediate UE. Step 2B: The A-IoT UE receives information B (e.g., data information or signal) from the intermediate UE.)

[0112] Finally, in Proposal 1-1, including its variants, the time offset may be defined as the period or interval between the start timing (beginning) or end timing (end) at which the signal / information is transmitted / received in step 1 and the start timing (beginning) or start timing (beginning) of the time window at which the signal / information is transmitted / received in step 2 / 2A.

[0113] As described above, the A-IoT UE may determine the second timing or second period at which information / information A in step 2 / 2A is received based on the first timing or first period at which the wake-up signal in step 1 is received.

[0114] As described above, according to Proposal 1-1, the A-IoT UE can receive signals / information transmitted from the BS / intermediate UE at the appropriate timing / period.

[0115] <Proposal 1-2> Next, we will explain a proposal (Proposal 1-2) related to the timing relationship of Step 2B shown below for DT in Topology 1. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the BS as an energy source to supply energy to the A-IoT UE. Step 2A: The A-IoT UE receives information A (e.g., control information or a signal) from the BS. Step 2B: The A-IoT UE receives information B (e.g., data information or a signal) from the BS. In this case, for example, the A-IoT UE may receive / decode information B based on information included in information A (e.g., time / frequency / code (domain) resources, modulation / waveform / coding scheme, etc. included in information A). That is, information A includes information for encoding / receiving / decoding information B.

[0116] [Option 1] Step 2B may be performed at a time offset from the previous step, as shown in (a) to (c) below. For example, the A-IoT UE may receive information B from the BS at a time offset from the previous step: (a) at a time offset from step 2A; (b) at a time offset from step 1; or (c) at a time offset from the start / end of the time window of step 2A, if information A is received within the time window in step 2A.

[0117] The granularity of the time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond, or any time unit defined for A-IoT.

[0118] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0119] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0120] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) related to the time offset from the BS prior to step 2B / 2A( / 1), and the time offset may be preset by the information. If the time offset is notified by the BS, the time offset may be notified in information A transmitted / received in step 2A (the A-IoT UE may receive information A from the BS including information notifying the time offset). If the time offset is notified by the BS, a minimum and / or maximum allowable value may be specified in the specification or reported as an A-IoT capability (the A-IoT UE may report the minimum and / or maximum allowable value to the BS as an A-IoT capability). In other words, the A-IoT UE may not expect time offsets smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value).

[0121] 15 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 1-2. This example corresponds to the above case (a).

[0122] As shown in the figure, the BS (gNB) transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A (step 2A). Then, the gNB transmits information B to the A-IoT UE, and in response, the A-IoT UE receives information B from the gNB at a time offset after step 2A (step 2B).

[0123] 16 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 1-2. This example corresponds to the above case (b).

[0124] As shown in the figure, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE, and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). The gNB transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A from the gNB (Step 2A). Then, the gNB transmits information B to the A-IoT UE, and in response, the A-IoT UE receives information B from the gNB at a time offset from Step 1 (Step 2B).

[0125] 17 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 1-2. This example corresponds to the above case (c).

[0126] As shown, the BS (gNB) transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A from the gNB within a time window (step 2A). The gNB then transmits information B to the A-IoT UE, and in response, the A-IoT UE receives information B from the gNB at a time offset from the start / end of the time window in step 2A (step 2B).

[0127] [Option 2] Step 2B may be performed within a certain time window, for example, the A-IoT UE may receive information B from the BS within a certain time window.

[0128] Note that time synchronization may or may not be maintained between the A-IoT UE and the BS. If time synchronization is not maintained, the A-IoT UE may not know the exact time when information B arrives. Therefore, in option 2, the A-IoT UE may monitor information B within a certain time window after receiving information A. In this case, information (e.g., a preamble) marking the start (beginning) of information B may be transmitted at the beginning of information B.

[0129] The start (beginning) of the time window may be a timing at which a certain time offset has elapsed from the previous step, as shown in (a) to (c) below. For example, the A-IoT UE may receive information B from the BS within a time window that starts at a timing at which a certain time offset has elapsed from the previous step: (a) A timing at which a time offset has elapsed from step 2A; (b) A timing at which a time offset has elapsed from step 1; (c) A timing at which a time offset has elapsed from the start (beginning) / end (end) of the time window of step 2A, if information A is received within the time window in step 2A.

[0130] The granularity of the time window and time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond or any time unit defined for A-IoT.

[0131] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0132] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0133] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) related to the time offset from the BS prior to step 2B / 2A( / 1), and the time offset may be preset by the information. If the time offset is notified by the BS, the time offset may be notified in information A transmitted / received in step 2A (the A-IoT UE may receive information A from the BS including information notifying the time offset). If the time offset is notified by the BS, a minimum and / or maximum allowable value may be specified in the specification or reported as an A-IoT capability (the A-IoT UE may report the minimum and / or maximum allowable value to the BS as an A-IoT capability). In other words, the A-IoT UE may not expect time offsets smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value).

[0134] The length of the time window (time window length) may be specified / reported / notified as described in (2a) to (2c) below.

[0135] (2a) The time window length may be specified in the specification. In this case, the time window length may be, for example, 1 millisecond, 4 slots, etc. All A-IoT UEs may support the time window length value, or the time window length may be specified depending on the details / characteristics of the carrier waveform. In the latter case, the time window length may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of the carrier waveform, etc.

[0136] (2b) The time window length may be reported as an A-IoT capability (an A-IoT UE may report the time window length to the BS as an A-IoT capability).

[0137] (2c) The time window length may be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) regarding the time window length from the BS prior to step 2B / 2A( / 1), and the time window length may be preset by the information. Also, if the time window length is notified by the BS, the time window length may be notified in information A transmitted / received in step 2A (the A-IoT UE may receive information A from the BS including information notifying the time window length). If the time window length is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specifications or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not assume a time window length smaller than the value X (minimum allowed value) and / or a time window length larger than the value Y (maximum allowed value).

[0138] 18 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 1-2. This example corresponds to the above case (a).

[0139] As shown, the BS (gNB) transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A (step 2A). The gNB then transmits information B to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within a time window that starts at a time offset from step 2A (step 2B).

[0140] Also, in option 2, the A-IoT UE may monitor information from the BS within a time window. In other words, the A-IoT UE may assume that information will be transmitted or received from the BS within the time window. Also, for example, if the A-IoT UE does not receive information from the BS within the time window, it may transition or move to a sleep state. In other words, if the A-IoT UE does not receive information from the BS within the time window, it may not receive / monitor information from the BS after the time window (it may not assume that information will be transmitted or received from the BS).

[0141] FIG. 19 is a diagram showing an example of communication between a BS and an A-IoT UE according to option 2 of proposal 1-2.

[0142] As shown, the BS (gNB) transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A (step 2A). The gNB then transmits information B to the A-IoT UE, and in response, the A-IoT UE monitors information from the gNB within a time window starting at a time offset from step 2A (step 2B). After the time window, the A-IoT UE stops monitoring.

[0143] 20 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 1-2. This example corresponds to the above case (b).

[0144] As shown, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE, and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). The gNB transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A from the gNB (Step 2A). The gNB then transmits information B to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within a time window starting at a time offset from Step 1 (Step 2B).

[0145] In option 2, the A-IoT UE may monitor information from the BS within a time window. In other words, the A-IoT UE may assume that information from the BS will be transmitted or received within the time window. For example, if the A-IoT UE does not receive information from the BS within the time window, it may transition or move to a sleep state. In other words, if the A-IoT UE does not receive information from the BS within the time window, it may not receive / monitor information from the BS after the time window (it may not assume that information will be transmitted or received from the BS). In this case, the A-IoT UE monitors information from the gNB within a time window starting at a time offset from step 1 (step 2B), and stops monitoring after the time window (see FIG. 19).

[0146] 21 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 1-2. This example corresponds to the above case (c).

[0147] As shown, the BS (gNB) transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information A from the gNB within a time window (step 2A). The gNB then transmits information B to the A-IoT UE, and in response, the A-IoT UE receives information B from the gNB within a time window that starts at a time offset from the start / end of the time window in step 2A (step 2B).

[0148] In option 2, the A-IoT UE may monitor information from the BS within a time window. In other words, the A-IoT UE may assume that information from the BS will be transmitted or received within the time window. For example, if the A-IoT UE does not receive information from the BS within the time window, it may transition or move to a sleep state. In other words, if the A-IoT UE does not receive information from the BS within the time window, it may not receive / monitor information from the BS after the time window (it may not assume that information will be transmitted or received from the BS). In this case, the A-IoT UE monitors information from the gNB within a time window that starts at a time offset from the start / end of the time window in step 2A (step 2B), and stops monitoring after the time window (see FIG. 19).

[0149] In option 2, the time window for step 2B may be defined to include only the start or end timing of the signal / information (information B) transmitted / received in step 2B (i.e., the other timing may be outside the time window), or it may be defined to include the entire signal / information (information B) transmitted / received in step 2B (i.e., both the start timing and the end timing).

[0150] <Modification of Proposal 1-2> The above-mentioned content of Proposal 1-2 may also be applied to the timing relationship of step 2B for DT in Topology 2. In this case, the content of Proposal 1-2 is applied, with "BS" replaced with "intermediate UE." Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the intermediate UE as an energy source to supply energy to the A-IoT UE. Step 2A: The A-IoT UE receives information A (e.g., control information or a signal) from the intermediate UE. Step 2B: The A-IoT UE receives information B (e.g., data information or a signal) from the intermediate UE. In this case, for example, the A-IoT UE may receive / decode information B based on information included in information A (e.g., time / frequency / code (domain) resources, modulation / waveform / coding scheme, etc. included in information A). That is, information A includes information for encoding / receiving / decoding information B.

[0151] Finally, in Proposal 1-2, including its variants, the time offset may be defined as the period or interval between the start timing (beginning) or end timing (end) of the signal / information transmitted / received in step 1 / 2A or the start timing (beginning) or end timing (end) of the time window and the start timing (beginning) or start timing (beginning) of the time window in step 2B.

[0152] As described above, the A-IoT UE may determine the second timing or second period at which information B in step 2B is received based on the first timing or first period at which the wake-up signal in step 1 / information A in step 2A is received.

[0153] As described above, according to Proposal 1-2, the A-IoT UE can receive signals / information transmitted from the BS / intermediate UE at the appropriate timing / period.

[0154] <Modification of Proposal 1> In Option 2 of Proposal 1-2, it has been explained that information (e.g., a preamble) marking the start (beginning) of information B may be transmitted at the beginning of information B, but the same may also be applied to information A. That is, information (e.g., a preamble) marking the start (beginning) of information A may be transmitted at the beginning of information A.

[0155] <Operation Example According to Proposal 1> Next, an operation example of the device 20 will be described with reference to FIG.

[0156] In step S11, device 20 receives a first signal. Step S11 may correspond to step 1 for DT in topology 1 / 2 described above, or may correspond to step 2A for DT in topology 1 / 2 described above. The first signal may correspond to the wake-up signal received in step 1, or may correspond to information A received in step 2A.

[0157] In step S12, the device 20 determines a second timing or second period during which the second signal is received based on the first timing or first period during which the first signal is received. The second signal may correspond to the information received in step 2 regarding the DT in the topology 1 / 2 described above, or may correspond to the information B received in step 2B regarding the DT in the topology 1 / 2 described above.

[0158] In step S13, the device 20 receives a second signal at the determined second timing or within the determined second period. Step S13 may correspond to step 2 for DT in topology 1 / 2 described above, or may correspond to step 2B for DT in topology 1 / 2 described above.

[0159] Note that steps S11 to S13 may be performed in accordance with Proposals 1-1 to 1-2, including the options and variations described above.

[0160] As described above, according to Proposal 1, the timing / period of receiving DL signals / information can be appropriately determined, so that signals / information transmitted from the BS / intermediate UE can be appropriately received.

[0161] <Proposal 2-1> Regarding DL reception in the DO-DTT communication flow, the contents of Proposal 1-1, including modifications, may be applied to the timing relationship between Step 1 and Step 2 shown below for DO-DTT in Topology 1. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the BS as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the BS.

[0162] Furthermore, with regard to DL reception in the DO-DTT communication flow, the contents of Proposal 1-1, including modifications, may be applied to the timing relationship between Step 1 and Step 2 shown below for DO-DTT in Topology 2. In this case, the contents of Proposal 1-1 and / or its modifications, in which "BS" is replaced with "intermediate UE", are applied. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the intermediate UE as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the intermediate UE.

[0163] As described above, according to Proposal 2-1, the A-IoT UE can receive signals / information transmitted from the BS / intermediate UE at the appropriate timing / period.

[0164] <Proposal 2-2> Next, we will explain a proposal (Proposal 2-2) related to the timing relationship of Step 3 shown below for DO-DTT in Topology 1. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the BS as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the BS. Step 3: The A-IoT UE transmits a signal to the BS.

[0165] [Option 1] Step 3 may be performed at a time offset from the previous step, as shown in (a) to (c) below. For example, the A-IoT UE may transmit a signal to the BS at a time offset from the previous step: (a) at a time offset from step 2; (b) at a time offset from step 1; or (c) at a time offset from the start / end of the time window in step 2, if the information in step 2 is received within the time window.

[0166] The granularity of the time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond, or any time unit defined for A-IoT.

[0167] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0168] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0169] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) about the time offset from the BS before step 3 / 2 ( / 1), and the time offset may be preset by the information. If the time offset is notified by the BS, the time offset may be notified in the information transmitted / received in step 2 (the A-IoT UE may receive information from the BS including information notifying the time offset). If the time offset is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specification or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not expect time offsets smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value).

[0170] 22 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 2-2. This example corresponds to the above case (a).

[0171] As shown in the figure, the BS (gNB) transmits information to the A-IoT UE, and in response, the A-IoT UE receives the information (step 2).Then, the A-IoT UE transmits a signal to the gNB at a timing after a time offset has elapsed since step 2 (step 3).

[0172] 23 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 2-2. This example corresponds to the above case (b).

[0173] As shown in the figure, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE, and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). The gNB transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB (Step 2). Then, the A-IoT UE transmits a signal to the gNB at a time offset from Step 1 (Step 3).

[0174] 24 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 2-2. This example corresponds to the above case (c).

[0175] As shown, the BS (gNB) transmits information A to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within a time window (step 2).Then, the A-IoT UE transmits a signal to the gNB at a time offset from the start / end of the time window in step 2 (step 3).

[0176] [Option 2] Step 3 may be performed within a certain time window, for example, the A-IoT UE may transmit a signal to the BS within a certain time window.

[0177] It should be noted that time synchronization may or may not be maintained in the A-IoT UE. If time synchronization is not maintained, the A-IoT UE may not be notified of the exact time to transmit a signal and may not know the exact time to transmit a signal. Therefore, in Option 2, the A-IoT UE may transmit a signal at any time within a certain time window. In this case, information marking the start (head) of the signal (e.g., a preamble) may be transmitted at the beginning of the signal.

[0178] The start (beginning) of the time window may be a time offset from the previous step, as shown in (a) to (c) below. For example, the A-IoT UE may transmit a signal to the BS within a time window that starts at a time offset from the previous step: (a) a time offset from step 2; (b) a time offset from step 1; or (c) a time offset from the start (beginning) / end (end) of the time window in step 2, if the information in step 2 is received within the time window.

[0179] The granularity of the time window and time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond or any time unit defined for A-IoT.

[0180] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0181] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0182] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) about the time offset from the BS before step 3 / 2 ( / 1), and the time offset may be preset by the information. If the time offset is notified by the BS, the time offset may be notified in the information transmitted / received in step 2 (the A-IoT UE may receive information from the BS including information notifying the time offset). If the time offset is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specification or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not expect time offsets smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value).

[0183] The length of the time window (time window length) may be specified / reported / notified as described in (2a) to (2c) below.

[0184] (2a) The time window length may be specified in the specification. In this case, the time window length may be, for example, 1 millisecond, 4 slots, etc. All A-IoT UEs may support this time window length value, or the time window length may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different time window lengths may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0185] (2b) The time window length may be reported as an A-IoT capability (an A-IoT UE may report the time window length to the BS as an A-IoT capability).

[0186] (2c) The time window length may be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) regarding the time window length from the BS before step 3 / 2 ( / 1), and the time window length may be preset by the information. Also, if the time window length is notified by the BS, the time window length may be notified in the information transmitted / received in step 2 (the A-IoT UE may receive information from the BS including information notifying the time window length). If the time window length is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specifications or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not assume a time window length smaller than the value X (minimum allowed value) and / or a time window length larger than the value Y (maximum allowed value).

[0187] 25 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 2-2. This example corresponds to the above case (a).

[0188] As shown, the BS (gNB) transmits information to the A-IoT UE, and in response, the A-IoT UE receives the information (step 2).The A-IoT UE then transmits a signal to the gNB within a time window that starts a time offset from step 2 (step 3).

[0189] 26 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 2-2. This example corresponds to the above case (b).

[0190] As shown, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE, and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (Step 1). The gNB transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB (Step 2). The A-IoT UE then transmits a signal to the gNB within a time window that begins a time offset from Step 1 (Step 3).

[0191] 27 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 2-2. This example corresponds to the above case (c).

[0192] As shown, the BS (gNB) transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within the time window of step 2 (step 2). The A-IoT UE then transmits a signal to the gNB within a time window that starts at a time offset from the start / end of the time window of step 2 (step 3).

[0193] In addition, in option 2, the time window for step 3 may be defined to include only the start or end timing of the signal / information transmitted / received in step 3 (i.e., the other timing may be outside the time window), or it may be defined to include the entire signal / information transmitted / received in step 3 (i.e., both the start timing and the end timing).

[0194] <Modification of Proposal 2-2> If step 3 is divided into step 3A and step 3B for DO-DTT in Topology 1 as follows, the content of Proposal 2-2 described above may also be applied to the timing relationship of step 3A. In this case, the content of Proposal 2-2, with "step 3" replaced with "step 3A," applies. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the BS as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the BS. Step 3A: The A-IoT UE transmits signal A (e.g., control information or signal) to the BS. Step 3B: The A-IoT UE transmits signal B (e.g., data information or signal) to the BS. In this case, for example, the A-IoT UE may determine time / frequency / code (domain) resources, modulation / waveform / coding scheme, etc., and may notify the BS of the determined contents in signal A. That is, signal A contains information for encoding / transmitting / decoding signal B.

[0195] The above-mentioned contents of Proposal 2-2 and / or its variations may also be applied to the timing relationship of Step 3 and / or Step 3A for DO-DTT in Topology 2. In this case, the contents of Proposal 2-2 and / or its variations, with "BS" replaced by "intermediate UE", apply. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the intermediate UE as an energy source to power the A-IoT UE. Step 2: The A-IoT UE receives information from the intermediate UE. Step 3: The A-IoT UE transmits a signal to the intermediate UE. (Or, Step 3A: The A-IoT UE transmits signal A (e.g., control information or a signal) to the intermediate UE. Step 3B: The A-IoT UE transmits signal B (e.g., data information or a signal) to the intermediate UE.)

[0196] Finally, in Proposal 2-2, including its variants, the time offset may be defined as the period or interval between the start timing (beginning) or end timing (end) of the signal / information transmitted / received in step 1 / 2, or the start timing (beginning) or end timing (end) of the time window, and the start timing (beginning) or start timing (beginning) of the time window, of the signal / information transmitted / received in step 3 / 3A.

[0197] As described above, the A-IoT UE may determine the second timing or second period at which the signal in step 3 / 3A / signal A is transmitted based on the first timing or first period at which the wake-up signal in step 1 / information in step 2 is received.

[0198] As described above, according to Proposal 2-2, the A-IoT UE can transmit signals / information to the BS / intermediate UE at appropriate timing / period.

[0199] <Proposal 2-3> Next, we will explain a proposal (Proposal 2-3) related to the timing relationship of Step 3B shown below for DO-DTT in Topology 1. Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the BS as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the BS. Step 3A: The A-IoT UE transmits Signal A (e.g., control information or a signal) to the BS. Step 3B: The A-IoT UE transmits Signal B (e.g., data information or a signal) to the BS. In this case, for example, the A-IoT UE may determine the time / frequency / code (domain) resources, modulation / waveform / coding scheme, etc., and may notify the BS of the determined contents in Signal A. In other words, Signal A includes information for encoding / transmitting / decoding Signal B.

[0200] [Option 1] Step 3B may be performed at a time offset from the previous step, as shown in (a) to (e) below. For example, the A-IoT UE may transmit signal B to the BS at a time offset from the previous step: (a) at a time offset from step 3A; (b) at a time offset from step 2; (c) at a time offset from step 1; (d) at a time offset from the start (beginning) / end (end) of the time window of step 2, if the information is received within the time window in step 2; or (e) at a time offset from the start (beginning) / end (end) of the time window of step 3A, if the signal is transmitted within the time window in step 3A.

[0201] The granularity of the time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond, or any time unit defined for A-IoT.

[0202] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0203] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0204] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) related to the time offset from the BS prior to step 3B / 3A / 2( / 1), and the time offset may be preset by the information. If the time offset is notified by the BS, the time offset may be notified in the information transmitted / received in step 2 (the A-IoT UE may receive information from the BS including information notifying the time offset). If the time offset is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specification or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not expect time offsets smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value).

[0205] The time offset may also be notified to the BS by the A-IoT UE. For example, the A-IoT UE may store information including information notifying the time offset and transmit it to the BS (the BS may receive and store the information from the A-IoT UE). If the time offset is notified by the A-IoT UE, the time offset may also be notified in signal A transmitted / received in step 3A.

[0206] Figure 28 is a diagram showing an example of communication between a BS and an A-IoT UE according to option 1 of proposal 2-3. This example corresponds to the above case (a).

[0207] As shown in the figure, the A-IoT UE transmits signal A to the BS (gNB) (step 3A). Then, the A-IoT UE transmits signal B to the gNB at a timing after a time offset has elapsed since step 3A (step 3B).

[0208] Figure 29 is a diagram showing an example of communication between a BS and an A-IoT UE according to option 1 of proposal 2-3. This example corresponds to the above cases (b) and (c).

[0209] As shown in the figure, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE, and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (step 1). The gNB transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB (step 2). The A-IoT UE transmits signal A to the gNB (step 3A). Then, the A-IoT UE transmits signal B to the gNB at a time offset after step 2 (step 3B). Alternatively, the A-IoT UE transmits signal B to the gNB at a time offset after step 1 (step 3B).

[0210] Figure 30 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 1 of Proposal 2-3. This example corresponds to the above cases (d) and (e).

[0211] As shown, the BS (gNB) transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within the time window of step 2 (step 2). The A-IoT UE transmits signal A to the gNB within the time window of step 3A (step 3A). The A-IoT UE then transmits signal B to the gNB at a time offset after the start / end of the time window of step 2 (step 3B). Alternatively, the A-IoT UE transmits signal B to the gNB at a time offset after the start / end of the time window of step 3A (step 3B).

[0212] [Option 2] Step 3B may be performed within a certain time window, for example, the A-IoT UE may transmit signal B to the BS within a certain time window.

[0213] It should be noted that time synchronization may or may not be maintained in the A-IoT UE. If time synchronization is not maintained, the A-IoT UE may not be notified of the exact time to transmit a signal and may not know the exact time to transmit a signal. Therefore, in option 2, the A-IoT UE may transmit signal B at any time within a certain time window. In this case, information (e.g., a preamble) marking the start (beginning) of signal B may be transmitted at the beginning of signal B.

[0214] The start (beginning) of the time window may be a timing that is a certain time offset from the previous step, as shown in (a) to (e) below. For example, the A-IoT UE may transmit signal B to the BS within a time window that starts at a certain time offset from the previous step: (a) A timing that is a time offset from step 3A; (b) A timing that is a time offset from step 2; (c) A timing that is a time offset from step 1; (d) A timing that is a time offset from the start (beginning) / end (end) of the time window of step 2, if information is received within the time window in step 2; (e) A timing that is a time offset from the start (beginning) / end (end) of the time window of step 3A, if a signal is transmitted within the time window in step 3A.

[0215] The granularity of the time window and time offset may be subframe / slot / slot group / symbol / symbol group / second / millisecond / microsecond or any time unit defined for A-IoT.

[0216] The time offset may be specified in a specification. In this case, the time offset may be, for example, 0 seconds, 1 millisecond, 1 slot, etc. All A-IoT UEs may support the time offset value, or the time offset may be specified depending on the details / characteristics of the carrier waveform. In the latter case, different offsets may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of carrier waveform, etc.

[0217] The time offset may also be reported as an A-IoT capability (an A-IoT UE may report the time offset to the BS as an A-IoT capability).

[0218] The time offset may also be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) related to the time offset from the BS prior to step 3B / 3A / 2( / 1), and the time offset may be preset by the information. If the time offset is notified by the BS, the time offset may be notified in the information transmitted / received in step 2 (the A-IoT UE may receive information from the BS including information notifying the time offset). If the time offset is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specification or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not expect time offsets smaller than value X (minimum allowed value) and / or larger than value Y (maximum allowed value).

[0219] The time offset may also be notified to the BS by the A-IoT UE. For example, the A-IoT UE may store information including information notifying the time offset and transmit it to the BS (the BS may receive and store the information from the A-IoT UE). If the time offset is notified by the A-IoT UE, the time offset may also be notified in signal A transmitted / received in step 3A.

[0220] The length of the time window (time window length) may be specified / reported / notified as described in (2a) to (2d) below.

[0221] (2a) The time window length may be specified in the specification. In this case, the time window length may be, for example, 1 millisecond, 4 slots, etc. All A-IoT UEs may support the time window length value, or the time window length may be specified depending on the details / characteristics of the carrier waveform. In the latter case, the time window length may be specified depending on, for example, whether the carrier waveform is modulated or not, the type of the carrier waveform, etc.

[0222] (2b) The time window length may be reported as an A-IoT capability (an A-IoT UE may report the time window length to the BS as an A-IoT capability).

[0223] (2c) The time window length may be notified to the A-IoT UE by the BS. For example, the A-IoT UE may receive and store information (e.g., configuration information) regarding the time window length from the BS prior to step 3B / 3A / 2( / 1), and the time window length may be preset by the information. Also, if the time window length is notified by the BS, the time window length may be notified in the information transmitted / received in step 2 (the A-IoT UE may receive information from the BS including information notifying the time window length). If the time window length is notified by the BS, the minimum and / or maximum allowed values ​​may be specified in the specifications or reported as A-IoT capabilities (the A-IoT UE may report the minimum and / or maximum allowed values ​​to the BS as A-IoT capabilities). In other words, the A-IoT UE may not assume a time window length smaller than the value X (minimum allowed value) and / or a time window length larger than the value Y (maximum allowed value).

[0224] (2d) The time window length may be notified to the BS by the A-IoT UE. For example, the A-IoT UE may store information including information notifying the time window length and transmit it to the BS (the BS may receive and store the information from the A-IoT UE). Also, if the time window length is notified by the A-IoT UE, the time window length may be notified in the signal A transmitted / received in step 3A.

[0225] Figure 31 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 2-3. This example corresponds to the above cases (a), (b), and (c).

[0226] As shown, the BS (gNB) transmits a carrier wave / RF signal as an energy source to the A-IoT UE, and in response, the A-IoT UE wakes up by receiving the carrier wave / RF signal (step 1). The gNB transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB (step 2). The A-IoT UE transmits signal A to the gNB (step 3A). Then, the A-IoT UE transmits signal B to the gNB within a time window starting at a time offset from step 3A (step 3B). Alternatively, the A-IoT UE transmits signal B to the gNB within a time window starting at a time offset from step 2 (step 3B). Alternatively, the A-IoT UE transmits signal B to the gNB within a time window starting at a time offset from step 1 (step 3B).

[0227] 32 is a diagram showing an example of communication between a BS and an A-IoT UE according to Option 2 of Proposal 2-3. This example corresponds to the above cases (d) and (e).

[0228] As shown, the BS (gNB) transmits information to the A-IoT UE, and in response, the A-IoT UE receives information from the gNB within the time window of step 2 (step 2). The A-IoT UE transmits signal A to the gNB within the time window of step 3A (step 3A). The A-IoT UE then transmits signal B to the gNB within a time window that starts a time offset from the start / end of the time window of step 2 (step 3B). Alternatively, the A-IoT UE transmits signal B to the gNB within a time window that starts a time offset from the start / end of the time window of step 3A (step 3B).

[0229] In addition, in option 2, the time window of step 3B may be defined to include only the start or end timing of the signal / information (signal B) transmitted / received in step 3B (i.e., the other timing may be outside the time window), or it may be defined to include the entire signal / information (signal B) transmitted / received in step 3B (i.e., both the start timing and the end timing).

[0230] <Modification of Proposal 2-3> The above content of Proposal 2-3 may also be applied to the timing relationship of step 3B for DO-DTT in Topology 2. In this case, the content of Proposal 2-3 applies, with "BS" replaced by "intermediate UE". Step 1: The A-IoT UE wakes up by a carrier waveform or other RF signal transmitted from the intermediate UE as an energy source to supply energy to the A-IoT UE. Step 2: The A-IoT UE receives information from the intermediate UE. Step 3A: The A-IoT UE transmits signal A (e.g., control information or signal) to the intermediate UE. Step 3B: The A-IoT UE transmits signal B (e.g., data information or signal) to the intermediate UE.

[0231] Finally, in Proposal 2-3, including its variants, the time offset may be defined as the period or interval between the start timing (beginning) or end timing (end) of the signal / information transmitted / received in step 1 / 2 / 3A or the start timing (beginning) or end timing (end) of the time window and the start timing (beginning) or start timing (beginning) of the time window in step 3B.

[0232] As described above, the A-IoT UE may determine the second timing or second period for transmitting signal B in step 3B based on the first timing or first period for receiving the wake-up signal in step 1 / information in step 2 or transmitting signal A in step 3A.

[0233] As described above, according to Proposal 2-3, the A-IoT UE can transmit signals / information to the BS / intermediate UE at appropriate timing / period.

[0234] <Modification of Proposal 2> In Option 2 of Proposal 2-2 and Option 2 of Proposal 2-3, it has been explained that information (for example, a preamble) marking the start (beginning) of information B may be transmitted at the beginning of information B, but the same may also be applied to information A. In other words, information (for example, a preamble) marking the start (beginning) of information A may be transmitted at the beginning of information A.

[0235] <Operation Example According to Proposal 2> Next, an operation example of the device 20 will be described with reference to FIG.

[0236] In step S21, device 20 receives or transmits a first signal. Step S21 may correspond to step 1 for DO-DTT in topology 1 / 2 described above, step 2 for DO-DTT in topology 1 / 2 described above, or step 3A for DO-DTT in topology 1 / 2 described above. The first signal may correspond to a wake-up signal received in step 1, information received in step 2, or signal A transmitted in step 3A.

[0237] In step S22, the device 20 determines a second timing or a second period for transmitting a second signal based on the first timing or a first period for receiving or transmitting the first signal. The second signal may correspond to the signal transmitted in step 3 for DO-DTT in topology 1 / 2 described above, or may correspond to signal B transmitted in step 3B for DO-DTT in topology 1 / 2 described above.

[0238] In step S23, the device 20 transmits a second signal at the determined second timing or within the determined second period. Step S23 may correspond to step 3 for DO-DTT in topology 1 / 2 described above, or may correspond to step 3B for DO-DTT in topology 1 / 2 described above.

[0239] Note that steps S21 to S23 may be performed according to proposals 2-1 to 2-3, including the options and variations described above.

[0240] As described above, according to Proposal 2, the timing / period of DL signal / information reception and UL signal / information transmission can be appropriately determined, so that signals / information transmitted from the BS / intermediate UE can be appropriately received and signals / information can be appropriately transmitted to the BS / intermediate UE.

[0241] Next, the configurations of the base station 10 and the device 20 will be described. Note that the configurations of the base station 10 and the device 20 described below are examples of functions related to this embodiment. The base station 10 and the device 20 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to this embodiment.

[0242] <Configuration of Base Station> Fig. 35 is a block diagram showing an example of the configuration of a base station 10 according to an embodiment. The base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 10 communicates with the device 20 (see Fig. 36) by radio. The base station 10 may be an intermediate node, a support node, or a terminal (a terminal of an SL that communicates with the device 20).

[0243] The transmitter 101 transmits a downlink (DL) signal to the device 20. For example, the transmitter 101 transmits the DL signal under the control of the controller 103.

[0244] The DL signal may include, for example, a downlink data signal and control information (e.g., DCI (Downlink Control Information)). The DL signal may also include information indicating scheduling related to signal transmission of the device 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of RRC (Radio Resource Control)). The DL signal may also include a reference signal.

[0245] The channels used for transmitting DL signals include, for example, a data channel and a control channel. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 10 transmits control information to the device 20 using the PDCCH and transmits downlink data signals using the PDSCH.

[0246] The reference signal included in the DL signal may include at least one of, for example, a Demodulation Reference Signal (DMRS), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as the DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

[0247] The receiving unit 102 receives an uplink (UL) signal transmitted from the device 20. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

[0248] The control unit 103 controls the communication operations of the base station 10 , including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102 .

[0249] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0250] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals (e.g., data and control information, etc.) received from the device 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the device 20.

[0251] The control unit 103 configures PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to the configuration of the PUCCH, such as a PUCCH cell timing pattern (PUCCH configuration information), may be notified to the device 20 by RRC.

[0252] Here, the transmitting unit 101 and the receiving unit 102 (which may be collectively referred to as a communication unit) communicate with the device 20 .

[0253] For example, the transmitter 101 may transmit a first signal and a second signal. The first signal may be a signal for waking up the device 20 or a signal including information for receiving the second signal.

[0254] Furthermore, for example, the transmitting unit 101 may transmit a first signal, and the receiving unit 102 may receive the first signal. The receiving unit 102 may receive the first signal, and the first signal may be a signal including information for transmitting a second signal. The receiving unit 102 may receive the second signal at any timing within the second period.

[0255] <Device Configuration> Fig. 36 is a block diagram showing an example of the configuration of the device 20 according to the embodiment. The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with, for example, the base station 10 wirelessly. The device 20 may be, for example, an A-IoT UE.

[0256] The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal under the control of the control unit 203.

[0257] The transmitting unit 202 transmits the UL signal to the base station 10. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

[0258] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI (Uplink Control Information)). For example, information related to the processing capability of the device 20 (e.g., A-IoT capability) may be included. The UL signal may also include a reference signal.

[0259] The channels used for transmitting UL signals include, for example, a data channel and a control channel. For example, the data channel may include a PUSCH (Physical Uplink Shared Channel), and the control channel may include a PUCCH (Physical Uplink Control Channel). For example, the device 20 transmits control information from the base station 10 using the PUCCH and transmits uplink data signals using the PUSCH.

[0260] The reference signal included in the UL signal may include, for example, at least one of a DMRS, a PTRS, a CSI-RS, an SRS, and a PRS. For example, the reference signal such as the DMRS or the PTRS is used for demodulating an uplink data signal and is transmitted using an uplink channel (for example, a PUSCH).

[0261] The control unit 203 controls the communication operations of the device 20 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

[0262] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

[0263] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ ACK / NACK, Channel State Information (CSI), or a Scheduling Request (SR). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted, for example, in PUCCH resources.

[0264] Control unit 203 configures PUCCH resources based on configuration information (for example, configuration information such as a PUCCH cell timing pattern and / or DCI notified by RRC) received from base station 10. Control unit 203 determines PUCCH resources to be used for transmitting information to be fed back to base station 10. Under the control of control unit 203, transmission unit 202 transmits the information to be fed back to base station 10 in the PUCCH resources determined by control unit 203.

[0265] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit DCI including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0266] Here, the receiving unit 201 and the transmitting unit 202 (which may be collectively referred to as a communication unit) communicate with a network such as the base station 10 .

[0267] For example, the communication unit may receive a first signal, and the control unit 203 may determine a second timing or a second period during which the communication unit receives a second signal based on a first timing or a first period during which the first signal is received. The control unit 203 may determine the second timing to be a timing when a specific time has elapsed since the first timing, the start timing of the first period, or the end timing of the first period. The control unit 203 may determine the start timing of the second period to be a timing when a specific time has elapsed since the first timing, the start timing of the first period, or the end timing of the first period. The first signal may be a signal for waking up the device 20 or a signal including information for receiving a second signal. In the wake-up mode, the device 20 may monitor the second signal within a second period, and if the device 20 does not receive the second signal within the second period, transition from the wake-up mode to the sleep mode after the second period.

[0268] Furthermore, for example, the communication unit may receive or transmit a first signal, and the control unit 203 may determine a second timing or a second period at which the communication unit transmits a second signal based on a first timing or a first period at which the first signal is received or transmitted. The control unit 203 may determine the second timing to be a timing at which a specific time has elapsed since the first timing, the start timing of the first period, or the end timing of the first period. The control unit 203 may determine the start timing of the second period to be a timing at which a specific time has elapsed since the first timing, the start timing of the first period, or the end timing of the first period. The communication unit may transmit a first signal, and the first signal may be a signal including information for transmitting a second signal. The communication unit may transmit the second signal at any timing within the second period.

[0269] (Summary of the embodiment) A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes a communication unit that receives a first signal, and a control unit that determines a second timing or a second period at which a second signal is received by the communication unit based on a first timing or a first period at which the first signal is received.

[0270] With the above configuration, the device can properly determine the timing or period for receiving DL signals / information, and can therefore properly receive signals / information transmitted from the network.

[0271] In one example, the control unit determines the second timing to be a timing when a specific time has elapsed since the first timing, the start timing of the first period, or the end timing of the first period.

[0272] With the above configuration, the device can receive signals / information transmitted from the network at the appropriate timing.

[0273] In one example, the control unit determines the start timing of the second period to be the first timing, the start timing of the first period, or a timing when a specific time has elapsed since the end timing of the first period.

[0274] With the above configuration, the device can properly receive signals / information transmitted from the network even if it does not have a time synchronization function.

[0275] In one example, the first signal is a signal for waking up the device or a signal including information for receiving the second signal.

[0276] With the above configuration, the device can receive signals / information transmitted from the network at appropriate timing or period.

[0277] In one example, the device monitors the second signal within the second period in wake-up mode, and if the device does not receive the second signal within the second period, transitions from the wake-up mode to the sleep mode after the second period.

[0278] By having the above configuration, the device is less likely to consume excess power.

[0279] A communication method according to one aspect of the present disclosure includes a device with lower complexity than a Narrow Band Internet of Things (NB-IoT) device receiving a first signal and determining, based on a first timing or a first period at which the first signal is received, a second timing or a second period at which a second signal is received by the device.

[0280] With the above configuration, the device can properly determine the timing or period for receiving DL signals / information, and can therefore properly receive signals / information transmitted from the network.

[0281] A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes a communication unit that receives or transmits a first signal, and a control unit that determines a second timing or second period at which a second signal is transmitted by the communication unit based on a first timing or first period at which the first signal is received or transmitted.

[0282] By having the above configuration, the device can properly determine the timing or duration of UL signal / information transmission, and therefore can properly transmit the signal / information to the network.

[0283] In one example, the control unit determines the second timing to be a timing when a specific time has elapsed since the first timing, the start timing of the first period, or the end timing of the first period.

[0284] With the above configuration, the device can transmit signals / information to the network at appropriate times.

[0285] In one example, the control unit determines the start timing of the second period to be the first timing, the start timing of the first period, or a timing when a specific time has elapsed since the end timing of the first period.

[0286] With the above configuration, the device can properly transmit signals / information to the network even if it does not have a time synchronization function.

[0287] In one example, the communication unit transmits the first signal, and the first signal is a signal including information for transmitting the second signal.

[0288] With the above configuration, the device can notify the network of information for the network to receive signals / information.

[0289] In one example, the communication unit transmits the second signal at any timing within the second period.

[0290] With the above configuration, the device can properly transmit signals / information to the network even if it does not have a time synchronization function.

[0291] A communication method according to one aspect of the present disclosure includes a device with lower complexity than a Narrow Band Internet of Things (NB-IoT) device receiving or transmitting a first signal, and determining a second timing or second period at which a second signal is transmitted by the device based on a first timing or first period at which the first signal is received or transmitted.

[0292] With the above configuration, the device can appropriately determine the timing of UL signal / information transmission, and can therefore appropriately transmit the signal / information to the network.

[0293] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

[0294] <Hardware Configuration, etc.> The block diagrams 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 (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0295] Functions include, but are not limited to, judgment, determination, assessment, 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.

[0296] For example, a base station, a device, 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. 37 is a diagram illustrating an example of the hardware configuration of a base station and a device according to an embodiment. The above-described base station 10 and device 20 may be physically configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

[0298] Each function in the base station 10 and the device 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

[0299] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by 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 103 and control unit 203 may be realized by the processor 1001.

[0300] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 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 103 of the base station 10 and the control unit 203 of the device 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be used for other functional blocks. 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.

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

[0302] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, 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. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0303] 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, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

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

[0305] Furthermore, each device, such as the processor 1001 and the memory 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.

[0306] Furthermore, the base station 10 and the device 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.

[0307] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described in the present disclosure and may be performed using other methods. For example, 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, 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.

[0308] <Applicable Systems> The embodiments described in the present disclosure are applicable to 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)), 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 (WiMAX (registered trademark 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).

[0309] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. 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.

[0310] <Operation of Base Station> In the present disclosure, specific operations described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0311] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0312] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.

[0313] <Determination method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0314] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

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

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

[0320] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0321] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

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

[0323] <Base Station> In the present disclosure, terms such as "base station (BS)," "radio base station," "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.

[0324] 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 remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

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

[0328] <Base Station / Mobile Station> 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 an autonomous mobile object operating 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.

[0329] Furthermore, the base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the device 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 communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0330] Similarly, the term "terminal" in the present disclosure may be read as a base station. In this case, the base station 10 may be configured to have the functions of the device 20 described above.

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

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

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

[0334] 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 rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels 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.

[0335] 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 that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0336] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

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

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

[0340] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 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 to 2029, 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.

[0341] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also 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 received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0342] Furthermore, the communication module 2013 stores 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, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0343] <Meaning and Interpretation of Terms> 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 a table, database, or other data structure), ascertaining something that is considered to be a "judging" or "determining," 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 that are considered to be a "judging" or "determining." 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.

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

[0345] <Reference Signal> A reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applicable standard.

[0346] <Meaning of "based on"> 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."

[0347] "First," "Second" Any reference to an element using designations such as "first," "second," etc., used in this disclosure 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 precede the second element in some way.

[0348] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," or the like.

[0349] Open Format: 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.

[0350] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> 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.

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

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

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

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

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

[0356] 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 radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

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

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

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

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

[0361] 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 numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

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

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

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

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

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

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

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

[0369] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0370] Articles 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.

[0371] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that 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."

[0372] One aspect of the present disclosure is useful in wireless communication systems.

[0373] 10 Base station 20 Device 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device, comprising: a communication unit that receives or transmits a first signal; and a control unit that determines a second timing or second period at which a second signal is transmitted by the communication unit based on a first timing or first period at which the first signal is received or transmitted.

2. The device according to claim 1, wherein the control unit determines the second timing to be a timing a specific time after the first timing, the start timing of the first period, or the end timing of the first period.

3. The device according to claim 1, wherein the control unit determines the start timing of the second period to be the first timing, the start timing of the first period, or a timing a specific time after the end timing of the first period.

4. The device according to claim 1, wherein the communication unit transmits the first signal, and the first signal is a signal including information for transmitting the second signal.

5. The device according to claim 1, wherein the communication unit transmits the second signal at any timing within the second period.

6. A communication method in which a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device receives or transmits a first signal, and determines a second timing or second period at which a second signal is transmitted by the device based on a first timing or first period at which the first signal is received or transmitted.

Images