Wireless communication device and communication method
The wireless communication device and method address the issue of improper resource allocation in ambient IoT systems by determining frequency resources effectively, improving transmission and reception quality.
Patent Information
- Application Number
- PCT/JP2024/013654
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-04-02
- Publication Date
- 2025-10-09
AI Technical Summary
Existing communication systems fail to appropriately determine frequency resources for ambient IoT devices, leading to improper transmission and reception of channels and signals, which degrades system performance.
A wireless communication device and method that includes a communication unit to receive information on frequency resources and a control unit to determine these resources for ambient IoT devices, utilizing a control unit to manage frequency resources based on received information.
Enables proper determination of frequency resources, ensuring effective transmission and reception of channels and signals, thereby enhancing system performance.
Smart Images

Figure JP2024013654_09102025_PF_FP_ABST
Abstract
Description
Wireless communication device and communication method
[0001] The present disclosure relates to a wireless communication device and a communication method.
[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] Determining resources, including frequency resources, used for communications in a communication system that includes ambient IoT devices is a consideration. Failure to properly determine resources can result in improper transmission and reception of channels and / or signals, resulting in degraded system performance.
[0006] One aspect of the present disclosure provides a wireless communication apparatus and a communication method that can appropriately determine resources, including frequency resources, used for communication in a communication system that includes ambient IoT devices.
[0007] A wireless communication device according to one aspect of the present disclosure includes a communication unit that receives information regarding frequency resources to be used for communication involving an ambient Internet of Things (IoT) device, and a control unit that determines the frequency resources to be used for the communication based on the information.
[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure.
[0023] FIG. 1 illustrates Topology 1.
[0024] FIG. 2 illustrates Topology 3 in DL assistance.
[0025] FIG. 3 illustrates Topology 4 in UL assistance.
[0026] FIG. 4 illustrates Topology 5 in DL assistance.
[0027] FIG. 5 illustrates Topology 6 in UL assistance.
[0028] FIG. 6 illustrates Topology 7 in DL assistance.
[0029] FIG. 7 illustrates Topology 8 in UL assistance.
[0030] FIG. 8 illustrates Topology 9 in DL assistance.
[0031] FIG. 9 illustrates Topology 10 in DL assistance.
[0032] FIG. 10 illustrates Topology 11 in DL assistance.
[0033] FIG. 11 illustrates Topology 12 in UL assistance.
[0034] FIG. 12 illustrates Topology 13 in DL assistance.
[0035] FIG. 13 illustrates Topology 14 in UL assistance.
[0036] FIG. 14 illustrates Topology 15 in DL assistance.
[0037] FIG. 15 illustrates Topology 16 in DL assistance.
[0038] FIG. 16 illustrates Topology 17 in UL assistance.
[0039] FIG. 17 illustrates Topology 18 in DL assistance.
[0039] FIG. 18 illustrates Topology 20 in DL assistance.
[0039] FIG. 19 illustrates Topology 21 in DL assistance.
[0039] FIG. 20 illustrates Topology 22 in DL assistance.
[0039] FIG. 21 illustrates Topology 23 in DL assistance.
[0039] FIG. 22 illustrates Topology 24 in DL assistance.
[0039] FIG. 23 illustrates Topology 25 in DL assistance.
[0039] FIG. 24 illustrates Topology 26 in DL 1 is a diagram illustrating an example of mapping between virtual subcarriers / frequency units and physical subcarriers / frequency units; FIG. 2 is a diagram illustrating an example of mapping between interlaces and non-contiguous subcarriers / frequency units; FIG. 3 is a diagram illustrating an example of frequency resources used for CW / R2D / D2R transmission; FIG. 4 is a diagram illustrating an example of mapping between subcarrier / frequency units and hops; FIG. 5 is a diagram illustrating an example of frequency resources used for CW / R2D / D2R transmission; FIG. 6 is a diagram illustrating an example of mapping between subcarrier / frequency unit sets and hops; FIG. 7 is a diagram illustrating an example of operation of a wireless communication device according to an embodiment of the present disclosure; FIG. 8 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure; FIG. 9 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure; FIG. 10 is a diagram illustrating an example of hardware configurations of a base station and a device according to an embodiment of the present disclosure; FIG. 11 is a diagram illustrating an example of a 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 (RBs).
[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] <Device Types> The following three device types, Device 1, Device 2a, and Device 2b, are defined for A-IoT devices.
[0057] Device 1 (may be referred to as Type 1) Device 1 is a device type that consumes a peak power of 1 μW or less. Device 1 has energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million) (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Device 1 does not have any amplification in either DL or UL. UL transmission in Device 1 is performed by backscattering an externally provided carrier wave (CW), i.e., an unmodulated wave.
[0058] Device 2a (may be referred to as type 2a) Device 2a is a device type that consumes a peak power of several hundred μW. Device 2a has energy storage and has an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Furthermore, DL and / or UL amplification is performed in device 2a. UL transmission in device 2a is performed by backscattering in CW provided from an external device.
[0059] Device 2b (may be referred to as type 2b) Device 2b is a device type that consumes a peak power of several hundred μW. Device 2b has energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Furthermore, DL and / or UL amplification is performed in device 2b. UL transmission in device 2b is performed inside device 2b. In other words, UL transmission in device 2b does not need to be performed by backscattering in CW provided from an external source.
[0060] <Candidate Topologies> Next, candidate topologies for CW / R2D / D2R transmission will be described.
[0061] Fig. 8 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. Fig. 8 shows Topology 1A, Topology 1B, Topology 1C, Topology 1D, and Topology 1E as examples of candidate topologies.
[0062] As shown in FIG. 8, in topologies 1A to 1E, CW / R2D communication signals (sometimes referred to as "R2D" in FIG. 8 and below) / D2R communication signals (sometimes referred to as "D2R" in FIG. 8 and below) can be transmitted and received to A-IoT devices.
[0063] In this embodiment, DL and R2D (reader to device) may be interchangeable, and UL and D2R (device to reader) may be interchangeable, where the reader corresponds to a BS and / or an intermediate UE, and the device corresponds to an A-IoT device.
[0064] In Topology 1A, the node (first BS) that transmits the CW is different from the node (second BS) that receives the D2R communication signal transmitted by the A-IoT device via backscattering, and the node that transmits the CW is the same as the node that transmits the R2D communication signal. Also, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.
[0065] In Topology 1B, the node (BS) that transmits the CW, the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.
[0066] In topology 1C, the node that transmits the CW (CW node) is different from the node that transmits the R2D communication signal (BS). Also, in topology 1C, the node that transmits the CW is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in topology 1C, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR (network-controlled repeater) node / relay node / other type of node.
[0067] In Topology 1D, the node (BS) that transmits the signal for R2D communication is the same as the node that receives the signal for D2R communication generated and transmitted by the A-IoT device, i.e., R in R2D and R in D2R are the same.
[0068] In Topology 1E, the node (first BS) that transmits the R2D communication signal is different from the node (second BS) that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, the R in R2D is different from the R in D2R.
[0069] Fig. 9 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 2. Fig. 9 shows Topology 2A, Topology 2B, Topology 2C, Topology 2D, and Topology 2E as examples of candidate topologies.
[0070] As shown in Figure 9, in topologies 2A to 2E, CW / R2D communication signals (denoted as "R2D" in Figure 9) / D2R communication signals (denoted as "D2R" in Figure 9) can be sent and received to A-IoT devices.
[0071] In Topology 2A, the node (first intermediate UE) that transmits the CW is different from the node (second intermediate UE) that receives the D2R communication signal transmitted by the A-IoT device via backscattering, and the node that transmits the CW is the same as the node that transmits the R2D communication signal. Also, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.
[0072] In Topology 2B, the node that transmits the CW (intermediate UE), the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.
[0073] In Topology 2C, the node that transmits the CW (CW node) is different from the node that transmits the R2D communication signal (intermediate UE). Also, in Topology 1C, the node that transmits the CW is different from the node (BS) that receives the D2R communication signal transmitted by the A-IoT device via backscattering. Also, in Topology 1C, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR node / relay node / other type of node.
[0074] In Topology 2D, the node (intermediate UE) that transmits the signal for R2D communication is the same as the node that receives the signal for D2R communication generated and transmitted by the A-IoT device, i.e., R in R2D and R in D2R are the same.
[0075] In Topology 2E, the node (first intermediate UE) that transmits the R2D communication signal is different from the node (second intermediate UE) that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, R in R2D is different from R in D2R.
[0076] <Analysis> In a communication system including A-IoT devices, the above-mentioned candidate topologies are conceivable, but there is room for further consideration regarding notification of frequency resources (or frequency domain resources) used for communication in the communication system.
[0077] For example, in the candidate topologies described above, notification is made in the following cases. In the following description, the A-IoT device, intermediate UE, and A-IoT device are collectively referred to as wireless communication devices. In the case of R2D transmission from an intermediate UE in topologies 2A to 2E, notification is made from the BS to the intermediate UE. In the case of CW transmission from an intermediate UE or CW node in topologies 1C and 2C, notification is made from the BS to the intermediate UE or CW node. In the case of D2R reception at an intermediate UE in topologies 2A to 2E, notification is made from the BS to the intermediate UE. In the case of D2R transmission from an A-IoT device in topologies 1A to 1E and 2A to 2E, notification is made from the BS or intermediate UE to the A-IoT device. In the case of R2D reception at an A-IoT device in topologies 1A to 1E and 2A to 2E, notification is made from the BS or intermediate UE to the A-IoT device.
[0078] However, details of the above-mentioned notification are not clearly defined. For example, if the frequency resource is not properly notified to the wireless communication device, the wireless communication device cannot properly determine the frequency resource to use for communication, and the wireless communication device may not be able to properly transmit and receive channels and / or signals due to, for example, interference, etc., which may result in degradation of system performance.
[0079] Therefore, below we will describe proposals (Proposals 1 to 5) for appropriately notifying and determining resources, including frequency resources, used for communication in a communication system including an A-IoT device.
[0080] The items explained in the following proposals 1 to 5 may be combined as appropriate as long as no contradictions arise.
[0081] Hereinafter, "CW / R2D / D2R transmission" may be referred to as communication in a wireless communication system including an A-IoT device, communication of an A-IoT device, communication with an A-IoT device, communication involving an A-IoT device, etc.
[0082] In the following, notifications may be carried in the physical (PHY) layer / MAC (Medium Access Control) layer / RRC (Radio Resource Control) layer / a new layer defined for A-IoT.
[0083] In the following, a "frequency unit" may refer to multiple subcarriers (or a subcarrier group), or may refer to a new frequency unit defined for A-IoT. In the former case, the number of subcarriers included in one frequency unit may be specified in the specifications, or may be notified to the wireless communication device by the base station 10, an intermediate UE, or the like, or may be set in advance.
[0084] The "subcarriers," "frequency units," and "resource blocks (RBs)" described below may be referred to as frequency resources (or frequency domain resources). For example, one or a single "subcarrier," "frequency unit," and "resource block (RB)" are all examples of one or a single frequency resource.
[0085] In the following, a "resource block (RB)" may include multiple subcarriers / frequency units.
[0086] The bandwidth for A-IoT described below (also referred to as A-IoT bandwidth or A-IoT BW) may be specified in a specification, may be notified to a wireless communication device by a base station 10, an intermediate UE, or the like, or may be set in advance, and the entire A-IoT bandwidth or a portion thereof may be used for CW / R2D / D2R transmission. The A-IoT bandwidth may also be referred to as a bandwidth for CW / R2D / D2R transmission, etc.
[0087] <Proposal 1> A proposal (Proposal 1) regarding frequency resources for CW / R2D / D2R transmission will be described below, assuming that one subcarrier / frequency unit is used for CW / R2D / D2R transmission and frequency hopping is not performed. Note that the hatched area in Fig. 10 indicates an example of one subcarrier / frequency unit used for CW / R2D / D2R transmission.
[0088] The notification of one subcarrier / frequency unit for CW / R2D / D2R transmission may be carried in the PHY layer / MAC layer / RRC layer / new layer defined for A-IoT. Details of the notification are described below.
[0089] [Option 1] One subcarrier / frequency unit within the A-IoT bandwidth may be signaled to the wireless communication device.
[0090] Assuming that there are N subcarriers / frequency units within the A-IoT bandwidth, N code points (or indexes) may be used, and the N code points may be mapped to the N subcarriers / frequency units, respectively. The mapping between the N code points and the N subcarriers / frequency units (for example, the mapping in the form of a table shown in FIG. 11) may be specified in a specification, or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance. The size of the notification field for notifying the subcarriers / frequency units (referred to as a subcarrier / frequency unit notification field) is: or Some unused code points may be reserved or set aside as spares.
[0091] 11 is a diagram showing an example of mapping between N code points and N subcarrier / frequency units. As shown in FIG. 11, for example, a subcarrier / frequency unit notification field value "0" may be mapped to one subcarrier / frequency unit #0, a subcarrier / frequency unit notification field value "1" may be mapped to one subcarrier / frequency unit #1, ..., a subcarrier / frequency unit notification field value "N-1" may be mapped to one subcarrier / frequency unit #N-1. Also, as shown in FIG. 11, for example, L-(N-1) code points may be secured or reserved as spares.
[0092] The notified information of one subcarrier / frequency unit (e.g., one of N code points) may be referred to as information about a frequency resource (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about a frequency resource used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine (or set or select) one subcarrier / frequency unit to be used for CW / R2D / D2R transmission based on the received information.
[0093] [Option 2] One RB within the A-IoT bandwidth may be notified to the wireless communication device.
[0094] Assuming that N RBs exist within the A-IoT bandwidth, N code points may be used, and the N code points may be mapped to the N RBs, respectively. The mapping between the N code points and the N RBs (for example, the mapping in the form of a table shown in FIG. 12) may be specified in a specification, or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance. The size of the notification field for notifying the RBs (referred to as the RB notification field) is or Some unused code points may be reserved or secured as spares. Then, one subcarrier / frequency unit in one notified RB may be used for CW / R2D / D2R transmission. The one subcarrier / frequency unit in the RB used for CW / R2D / D2R transmission may be specified in the specifications. For example, subcarrier / frequency unit #0, #11, #5, or #6 may be specified in the specifications and used for CW / R2D / D2R transmission.
[0095] 12 is a diagram showing an example of mapping between N code points and N RBs. As shown in FIG. 12, for example, an RB notification field value "0" may be mapped to one RB #0, an RB notification field value "1" may be mapped to one RB #1, ..., an RB notification field value "N-1" may be mapped to one RB #N-1. Also, as shown in FIG. 12, for example, L-(N-1) code points may be secured or reserved as spares.
[0096] The notified information of one RB (e.g., one of N code points) may be referred to as information about frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine one subcarrier / frequency unit in one RB to be used for CW / R2D / D2R transmission based on the received information.
[0097] [Option 3] One RB within the A-IoT bandwidth may be notified to the wireless communication device, and one subcarrier / frequency unit within the notified RB may be notified to the wireless communication device.
[0098] Assuming that N RBs exist within the A-IoT bandwidth, N code points may be used, and the N code points may be mapped to the N RBs, respectively. The mapping between the N code points and the N RBs (for example, the mapping in the form of a table shown in the upper left of FIG. 13) may be defined in a specification, or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance. The size of the notification field for notifying the RBs (referred to as the RB notification field) is: or Option 3 may also be used. Some unused code points may be reserved or secured as spares. Then, one subcarrier / frequency unit in one notified RB may be used for CW / R2D / D2R transmission. Unlike Option 2, in Option 3, one subcarrier / frequency unit in an RB used for CW / R2D / D2R transmission may be notified. For example, assuming that there are M subcarriers / frequency units in one RB (for example, as described below, M may be 12, but M may also be another value), M code points may be used, and the M code points may be mapped to the M subcarriers / frequency units, respectively. The mapping between the M code points and the M subcarriers / frequency units (for example, the mapping in the table format shown in the upper right of FIG. 13 ) may be specified in a specification, may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance. The size of the notification field for notifying the subcarrier / frequency unit (referred to as the subcarrier / frequency unit notification field) is or Some unused code points may be reserved or set aside as spares.
[0099] 13 is a diagram showing an example of mapping between N code points and N RBs, and mapping between M code points and M subcarrier / frequency units. As shown in FIG. 13, for example, an RB notification field value "0" may be mapped to one RB #0, an RB notification field value "1" may be mapped to one RB #1, ..., an RB notification field value "N-1" may be mapped to one RB #N-1. Also, as shown in FIG. 13, for example, L-(N-1) code points may be secured or reserved as spares. Also, as shown in FIG. 13, for example, a subcarrier / frequency unit notification field value "0" may be mapped to one subcarrier / frequency unit #0, a subcarrier / frequency unit notification field value "1" may be mapped to one subcarrier / frequency unit #1, ..., a subcarrier / frequency unit notification field value "M-1" may be mapped to one subcarrier / frequency unit #M-1. 13, for example, L-(M-1) code points may be secured or reserved as spares. In the example shown in FIG. 13, an RB notification field value of "2" and a subcarrier / frequency unit notification field value of "1" are notified to the wireless communication device from the base station 10, an intermediate UE, etc., to notify that one subcarrier / frequency unit #1 in one RB #2 is used for CW / R2D / D2R transmission.
[0100] For example, the wireless communication device may receive first information regarding frequency resources to be used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. The wireless communication device may also receive second information regarding frequency resources to be used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine one subcarrier / frequency unit in one RB to be used for CW / R2D / D2R transmission based on the received first information and second information.
[0101] Finally, the various mappings mentioned above will be explained again.
[0102] In relation to Option 1, the mapping of subcarrier indexes / frequency unit indexes within the A-IoT bandwidth (i.e., the correspondence between subcarriers / frequency units and subcarrier indexes / frequency unit indexes) (see, for example, FIG. 11 ) may be defined in a specification, or may be notified to the wireless communication device by the PHY layer / MAC layer / RRC layer / a new layer defined for A-IoT (e.g., in RRC / MAC CE / DCI), or may be configured in advance.
[0103] In relation to options 2 and 3, the mapping of RB indices within the A-IoT bandwidth (i.e., the correspondence between physical resource blocks (PRBs) and RB indices) (see, for example, Figure 12) may be specified in the specifications, or may be notified to the wireless communication device by the PHY layer / MAC layer / RRC layer / a new layer defined for A-IoT, or may be pre-configured.
[0104] In relation to Option 3, the mapping of subcarrier indexes / frequency unit indexes within an RB (i.e., the correspondence between subcarriers / frequency units and subcarrier indexes / frequency unit indexes) (see, for example, the top right of Figure 13) may be specified in the specifications, or may be notified to the wireless communication device by the PHY layer / MAC layer / RRC layer / a new layer defined for A-IoT, or may be set in advance.
[0105] 14, for example, the beginning or start of RB#0 may be a predetermined offset (frequency) from the lower end of the A-IoT bandwidth. The offset may also be specified in the specifications, or may be notified to the wireless communication device by the PHY layer / MAC layer / RRC layer / a new layer defined for A-IoT, or may be set in advance.
[0106] As described above, the wireless communication device may receive information regarding frequency resources to be used for CW / R2D / D2R transmission, and may determine one subcarrier / frequency unit to be used for CW / R2D / D2R transmission based on the received information.
[0107] As described above, according to Proposal 1, the wireless communication device can determine the frequency resources to be used for CW / R2D / D2R transmission based on the received information, and can perform CW / R2D / D2R transmission appropriately.
[0108] <Proposal 2> A proposal (Proposal 2) regarding frequency resources for CW / R2D / D2R transmission is described below, assuming that multiple consecutive subcarriers / frequency units are used for CW / R2D / D2R transmission in each time unit and frequency hopping is not performed. Note that the hatched area in Fig. 15 indicates an example of multiple consecutive subcarriers / frequency units used for CW / R2D / D2R transmission.
[0109] The notification of multiple consecutive subcarriers / frequency units for CW / R2D / D2R transmissions may be carried in the PHY layer / MAC layer / RRC layer / a new layer defined for A-IoT. Details of such notification are described below.
[0110] [Option 1] A wireless communication device may be notified of a first or starting subcarrier / frequency unit (among a plurality of consecutive subcarriers / frequency units) and the number of subcarriers / frequency units within the A-IoT bandwidth, and a plurality of consecutive subcarriers / frequency units determined by the first or starting subcarrier / frequency unit and the number of subcarriers / frequency units may be used for CW / R2D / D2R transmission.
[0111] The initial or starting subcarrier / frequency unit and the number of subcarriers / frequency units may be notified by a Resource Indicator Value (RIV) similar to the NR PDSCH / PUSCH resource allocation. That is, the RIV may be given by the following formula: where L is the number of allocated subcarriers / frequency units, S is the initial or starting subcarrier / frequency unit, N is the number of subcarriers / frequency units in the A-IoT bandwidth, and L+S does not exceed N.
[0112] Alternatively, instead of being notified together like the RIV, the first or starting subcarrier / frequency unit and the number of subcarriers / frequency units may be notified separately to the wireless communication device.
[0113] The notified information on the RIV, the initial or starting subcarrier / frequency unit, and the number of subcarriers / frequency units may be referred to as information about frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine multiple consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0114] [Option 2] One RB within the A-IoT bandwidth may be signaled to the wireless communication device, and the entire RB (i.e., multiple consecutive subcarriers / frequency units included in the RB) may be used for CW / R2D / D2R transmission.
[0115] One RB may be signaled as described in proposal 1.
[0116] As a variation of Option 2, a Resource Block Group (RBG) within the A-IoT bandwidth may be signaled to the wireless communication device, and the entire RBG (i.e., the contiguous RBs contained within the RB, and therefore the contiguous subcarriers contained within these contiguous RBs) may be used for CW / R2D / D2R transmissions.
[0117] One RBG may be signaled in the same manner as the RB in Option 1. In addition, the number of RBs in an RBG may be specified in the specifications, may be signaled to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance.
[0118] Alternatively, one frequency unit group (or frequency resource group) within the A-IoT bandwidth may be notified to the wireless communication device, and the frequency unit group (i.e., consecutive frequency units included in the frequency unit group, and therefore consecutive frequency units included in these consecutive frequency units) may be used for CW / R2D / D2R transmission.
[0119] One frequency unit group may be notified in the same manner as the RB in Option 1. Furthermore, the number of frequency units in a frequency unit group may be defined in a specification, may be notified to the wireless communication device by the base station 10, an intermediate UE, or the like, or may be set in advance.
[0120] As another variation of Option 2, a subcarrier group within the A-IoT bandwidth may be signaled to the wireless communication device, and the entire subcarrier group (i.e., multiple contiguous subcarriers within the subcarrier group) may be used for CW / R2D / D2R transmissions.
[0121] One subcarrier group may be signaled in the same manner as the RB in Option 1. In addition, the number of subcarriers in a subcarrier group may be specified in the specifications, may be signaled to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance.
[0122] The notified information of one RB, one RBG, one frequency unit group, and one subcarrier group may be referred to as information about frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine multiple consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0123] [Option 3] One RB within the A-IoT bandwidth may be notified to the wireless communication device. Unlike Option 2, in Option 3, the RB may be specified in the specification. Then, the entire RB (i.e., multiple consecutive subcarriers / frequency units included in the RB) may be used for CW / R2D / D2R transmission.
[0124] For example, the wireless communication device may receive information regarding frequency resources to be used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, based on the received information, the wireless communication device may determine a plurality of consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission.
[0125] [Option 4] One RB within the A-IoT bandwidth may be notified to the wireless communication device. The one RB may be notified as described in Proposal 1. Also, the first or starting subcarrier / frequency unit (among multiple consecutive subcarriers / frequency units) and the number of subcarriers / frequency units within the RB may be notified to the wireless communication device. Then, multiple consecutive subcarriers / frequency units determined by the first or starting subcarrier / frequency unit and the number of subcarriers / frequency units may be used for CW / R2D / D2R transmission.
[0126] The initial or starting subcarrier / frequency unit and the number of subcarriers / frequency units may be signaled by an RIV similar to the NR PDSCH / PUSCH resource allocation, i.e., the RIV may be given by the following formula: where L is the number of allocated subcarriers / frequency units, S is the first or starting subcarrier / frequency unit, N is the number of subcarriers / frequency units in an RB, and L+S does not exceed N.
[0127] Alternatively, instead of being notified together like the RIV, the first or starting subcarrier / frequency unit and the number of subcarriers / frequency units may be notified separately to the wireless communication device.
[0128] The notified information on the RIV, the initial or starting subcarrier / frequency unit, and the number of subcarriers / frequency units may be referred to as information about frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine multiple consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0129] [Option 5] The wireless communication device may be notified of the first or starting RB (among a plurality of consecutive RBs) and the number of RBs in the A-IoT bandwidth, and the entire plurality of consecutive RBs (i.e., the plurality of consecutive subcarriers included in these consecutive RBs) determined by the first or starting RB and the number of RBs may be used for CW / R2D / D2R transmission.
[0130] The top or starting RB and the number of RBs may be signaled by the same RIV as the NR PDSCH / PUSCH resource allocation, i.e., the RIV may be given by the following formula: where L is the allocated number of RBs, S is the top or starting RB, N is the number of RBs in the A-IoT bandwidth, and L+S does not exceed N.
[0131] Alternatively, instead of being notified together like the RIV, the top or start RB and the number of RBs may be notified separately to the wireless communication device.
[0132] The notified information on the RIV, the first or starting RB, and the number of RBs may be referred to as information on the frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information on the frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine multiple consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0133] [Option 6] An index (code point) associated with a plurality of consecutive subcarriers / frequency units within the A-IoT bandwidth may be notified to the wireless communication device. That is, one notified index (code point) may be mapped to one "plurality of consecutive subcarriers / frequency units."
[0134] For example, the mapping between multiple code points and multiple "multiple consecutive subcarriers / frequency units" (e.g., the mapping in table format shown in Figure 16) may be specified in a specification, or may be notified to the wireless communication device by the base station 10, intermediate UE, etc., or may be set in advance.
[0135] 16 is a diagram showing an example of mapping between a plurality of code points and a plurality of "plurality of consecutive subcarriers / frequency units." As shown in FIG. 16, for example, a subcarrier / frequency unit notification field value "0" may be mapped to subcarrier / frequency units #0, #1, and #2, which are one "plurality of consecutive subcarriers / frequency units," and a subcarrier / frequency unit notification field value "1" may be mapped to subcarrier / frequency units #3, #4, and #5, which are one "plurality of consecutive subcarriers / frequency units."
[0136] The notified information about the plurality of consecutive subcarriers / frequency units (e.g., one of the plurality of code points) may be referred to as information about the frequency resource (used for CW / R2D / D2R transmission) or the like. For example, the wireless communication device may receive information about the frequency resource used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine the plurality of consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0137] Throughout Proposal 2, the entire A-IoT bandwidth, or a portion thereof, as specified or signaled may be used for CW / R2D / D2R transmissions.
[0138] Also, combinations of the above options may be applied (unless they are inconsistent).
[0139] The content of Proposal 1 may be considered as a subset of the content of Proposal 2.
[0140] As described above, the wireless communication device may receive information regarding frequency resources to be used for CW / R2D / D2R transmission, and may determine multiple consecutive subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0141] As described above, according to Proposal 2, the wireless communication device can determine the frequency resources to be used for CW / R2D / D2R transmission based on the received information, and can perform CW / R2D / D2R transmission appropriately.
[0142] <Proposal 3> A proposal (Proposal 3) regarding frequency resources for CW / R2D / D2R transmission is described below, assuming that in each time unit, a plurality of non-contiguous subcarriers / frequency units or some or all of the subcarriers / frequency units included in a plurality of non-contiguous RBs are used for CW / R2D / D2R transmission, and frequency hopping is not performed. Note that the hatched portion in Fig. 17 indicates an example of a plurality of non-contiguous subcarriers / frequency units used for CW / R2D / D2R transmission.
[0143] The notification of multiple non-contiguous subcarriers / frequency units for CW / R2D / D2R transmission may be carried in the PHY layer / MAC layer / RRC layer / new layer defined for A-IoT. Details of such notification are described below.
[0144] [Option 1] Multiple non-contiguous subcarriers / frequency units within the A-IoT bandwidth may be signaled to the wireless communication device.
[0145] Alt. 1: Each subcarrier / frequency unit of a plurality of non-contiguous subcarriers / frequency units may be individually signaled to the wireless communication device as described in Proposal 1.
[0146] Alt. 2: Multiple non-contiguous subcarriers / frequency units may be signaled to a wireless communication device via a bitmap. Assuming that there are N subcarriers / frequency units within the A-IoT bandwidth, the length of the bitmap may be N (bits). These N bits may be mapped to the N non-contiguous subcarriers / frequency units, respectively. Subcarriers / frequency units used for CW / R2D / D2R transmissions may be signaled as "1," and subcarriers / frequency units not used for CW / R2D / D2R transmissions may be signaled as "0." Alternatively, subcarriers / frequency units used for CW / R2D / D2R transmissions may be signaled as "0," and subcarriers / frequency units not used for CW / R2D / D2R transmissions may be signaled as "1."
[0147] Alt. 3 An index (code point) associated with a plurality of non-contiguous subcarriers / frequency units may be notified to a wireless communication device. That is, one notified index (code point) may be mapped to one "plurality of non-contiguous subcarriers / frequency units." For example, the mapping between a plurality of code points and a plurality of "plurality of non-contiguous subcarriers / frequency units" (e.g., the mapping in the form of a table shown in FIG. 18) may be specified in a specification, may be notified to the wireless communication device by the base station 10, an intermediate UE, or the like, or may be set in advance.
[0148] 18 is a diagram showing an example of mapping between a plurality of code points and a plurality of "discontinuous subcarriers / frequency units." As shown in FIG. 18, for example, a subcarrier / frequency unit notification field value "0" may be mapped to subcarrier / frequency units #0 and #7, which are one "discontinuous subcarriers / frequency units," and a subcarrier / frequency unit notification field value "1" may be mapped to subcarrier / frequency units #1 and #8, which are one "discontinuous subcarriers / frequency units."
[0149] Alt. 4 Contiguous "virtual subcarriers / frequency units" may be signaled to a wireless communication device, as described for contiguous subcarriers / frequency units in Proposal 2. The contiguous "virtual subcarriers / frequency units" may be mapped to interleaved "physical subcarriers / frequency units" according to rules specified in the specification or according to RRC / MAC CE / DCI signaling. The physical subcarriers / frequency units may be actually used for CW / R2D / D2R transmission. For example, the mapping between the virtual subcarriers / frequency units and the non-contiguous physical subcarriers / frequency units (e.g., the mapping in the form of a table shown in FIG. 19 ) may be specified in the specification, or may be signaled to the wireless communication device by the base station 10, intermediate UE, etc., or may be configured in advance.
[0150] 19 is a diagram showing an example of mapping between a plurality of virtual subcarriers / frequency units and a plurality of “a plurality of non-consecutive physical subcarriers / frequency units.” As shown in FIG. 19 , for example, virtual subcarrier / frequency unit #0 may be associated with physical subcarrier / frequency unit #0, virtual subcarrier / frequency unit #1 may be associated with physical subcarrier / frequency unit #3, and virtual subcarrier / frequency unit #2 may be associated with physical subcarrier / frequency unit #6.
[0151] Alt. 5 The first subcarrier / frequency unit of a plurality of non-consecutive subcarriers / frequency units may be notified to the wireless communication device as described in Proposal 1. The wireless communication device may then determine the second and subsequent subcarriers / frequency units based on the offset between the two subcarriers / frequency units. The offset may be fixed (e.g., specified in a specification), or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance. For example, if the first subcarrier / frequency unit is 1st , then the second subcarrier / frequency unit is (SC 1st+ offset) mod N (where N is the number of subcarriers / frequency units in the A-IoT bandwidth).
[0152] Alt. 6: Interlace / comb mapping may be introduced, in which each interlace / comb includes multiple non-contiguous subcarriers / frequency units arranged at equal intervals within the A-IoT bandwidth. One or more interlaces / combs may then be signaled to a wireless communication device. The mapping between multiple interlaces / combs and multiple "non-contiguous subcarriers / frequency units" (e.g., the mapping in the form of a table shown in FIG. 20) may be specified in a specification, signaled to a wireless communication device by a base station 10, an intermediate UE, or the like, or may be set in advance. The content of Alt. 6 may be considered a subset of the content of Alt. 3.
[0153] 20 is a diagram showing an example of mapping between multiple interlaces (interlace indices) and multiple "discontinuous subcarriers / frequency units." As shown in FIG. 20, for example, interlace (index) "0" may be mapped to subcarrier / frequency units #0, #3, #6, ..., which are one "discontinuous subcarriers / frequency units," and interlace (index) "1" may be mapped to subcarrier / frequency units #1, #4, #7, ..., which are one "discontinuous subcarriers / frequency units." Carrier / frequency unit #2 may be associated with physical subcarrier / frequency unit #6.
[0154] The notified information on subcarriers / frequency units, bitmaps, virtual subcarriers / frequency units, offsets, and interlaces / combs may be referred to as information about frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine multiple non-contiguous subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0155] [Option 2] One RB within the A-IoT bandwidth may be signaled to the wireless communication device. The one RB may be signaled as described in Proposal 1. Then, multiple non-contiguous subcarriers / frequency units within the signaled RB may be used for CW / R2D / D2R transmission as described in Alt. 1 to Alt. 7 below.
[0156] Alt. 1: Multiple non-contiguous subcarriers / frequency units (within an RB) may be predefined (e.g., in a specification). For example, non-contiguous subcarriers / frequency units (#0, #11) or (#0, #5) or (#5, #11) may be predefined.
[0157] Alt. 2: Each subcarrier / frequency unit of multiple non-contiguous subcarriers / frequency units (within an RB) may be signaled to the wireless communication device as described in Option 3 of Proposal 1.
[0158] Alt. 3: Multiple non-contiguous subcarriers / frequency units (within an RB) may be signaled to a wireless communication device via a bitmap. Assuming that there are N subcarriers / frequency units in an RB, the length of the bitmap may be N (bits). These N bits may be mapped to the N non-contiguous subcarriers / frequency units (within an RB). Subcarriers / frequency units used for CW / R2D / D2R transmissions may be signaled as "1," and subcarriers / frequency units not used for CW / R2D / D2R transmissions may be signaled as "0." Alternatively, subcarriers / frequency units used for CW / R2D / D2R transmissions may be signaled as "0," and subcarriers / frequency units not used for CW / R2D / D2R transmissions may be signaled as "1."
[0159] Alt. 4 An index (code point) associated with multiple non-contiguous subcarriers / frequency units (within an RB) may be notified to the wireless communication device. That is, one notified index (code point) may be mapped to one "multiple non-contiguous subcarriers / frequency units." For example, the mapping between multiple code points and multiple "multiple non-contiguous subcarriers / frequency units" (e.g., a mapping in a table format similar to that shown in FIG. 18) may be specified in a specification, may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be preset.
[0160] Alt. 5 Contiguous "virtual subcarriers / frequency units" may be signaled to a wireless communication device, as described for contiguous subcarriers / frequency units in Proposal 2. The contiguous "virtual subcarriers / frequency units" may be mapped to interleaved "physical subcarriers / frequency units" according to rules specified in the specification or according to RRC / MAC CE / DCI signaling. The physical subcarriers / frequency units may be actually used for CW / R2D / D2R transmission. For example, the mapping between the virtual subcarriers / frequency units and the non-contiguous physical subcarriers / frequency units (e.g., a table-format mapping similar to that shown in FIG. 19 ) may be specified in the specification, signaled to the wireless communication device by the base station 10, intermediate UE, etc., or configured in advance.
[0161] Alt. 6 The first subcarrier / frequency unit of a plurality of non-consecutive subcarriers / frequency units (within an RB) may be signaled to the wireless communication device as described in Proposal 1. The wireless communication device may then determine the second and subsequent subcarriers / frequency units based on the offset between the two subcarriers / frequency units. The offset may be fixed (e.g., specified in a specification), or may be signaled to the wireless communication device by the base station 10, an intermediate UE, etc., or may be preset. For example, if the first subcarrier / frequency unit is 1st, then the second subcarrier / frequency unit is (SC 1st + offset) mod N (where N is the number of subcarriers / frequency units in the A-IoT bandwidth).
[0162] Alt. 7: Interlace / comb mapping may be introduced, in which each interlace / comb includes multiple non-contiguous subcarriers / frequency units arranged at equal intervals within an RB. One or more interlaces / combs may then be signaled to a wireless communication device. The mapping between multiple interlaces / combs and multiple "non-contiguous subcarriers / frequency units" (e.g., a table-format mapping similar to that shown in FIG. 20) may be specified in a specification, signaled to a wireless communication device by a base station 10, an intermediate UE, or the like, or may be configured in advance. The content of Alt. 7 may be considered a subset of the content of Alt. 4.
[0163] The notified information on RB, subcarrier / frequency unit, bitmap, virtual subcarrier / frequency unit, offset, and interlace / comb may be referred to as information about frequency resources (used for CW / R2D / D2R transmission), etc. For example, the wireless communication device may receive information about frequency resources used for CW / R2D / D2R transmission from the base station 10, an intermediate UE, etc. Then, the wireless communication device may determine multiple non-contiguous subcarriers / frequency units to be used for CW / R2D / D2R transmission based on the received information.
[0164] [Option 3] Multiple non-contiguous RBs within the A-IoT bandwidth may be signaled to the wireless communication device. Each RB of the multiple RBs may be signaled as described in Alt. 1 to Alt. 5 below. Then, subcarriers / frequency units within each signaled RB may be used for CW / R2D / D2R transmission as described in A to D below.
[0165] Alt. 1 Each RB may be signaled to the wireless communication device as described in Proposal 1.
[0166] Alt. 2: Multiple RBs may be signaled to a wireless communication device via a bitmap. Assuming that there are N RBs in the A-IoT bandwidth, the length of the bitmap may be N (bits). These N bits may be mapped to the N RBs, respectively. RBs containing subcarriers / frequency units used for CW / R2D / D2R transmissions may be signaled as "1," and RBs containing only subcarriers / frequency units not used for CW / R2D / D2R transmissions may be signaled as "0." Alternatively, RBs containing subcarriers / frequency units used for CW / R2D / D2R transmissions may be signaled as "0," and RBs containing only subcarriers / frequency units not used for CW / R2D / D2R transmissions may be signaled as "1."
[0167] Alt. 3 One index (code point) associated with multiple RBs may be notified to the wireless communication device. That is, one notified index (code point) may be mapped to one "multiple RBs." For example, the mapping between multiple code points and multiple "multiple RBs" (e.g., a mapping in a table format similar to that shown in FIG. 18) may be specified in a specification, may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance.
[0168] Alt. 4 Contiguous "virtual RBs" may be signaled to a wireless communication device, as described for contiguous subcarriers / frequency units in Proposal 2. Contiguous "virtual RBs" may be mapped to interleaved "physical RBs" according to a rule specified in the specification or according to an RRC / MAC CE / DCI signal. The physical RBs may be actually used for CW / R2D / D2R transmission. For example, the mapping between virtual RBs and non-contiguous physical RBs (e.g., a table-format mapping similar to that shown in FIG. 19) may be specified in the specification, signaled to the wireless communication device by the base station 10, an intermediate UE, etc., or configured in advance.
[0169] Alt. 5 The first RB of a plurality of non-consecutive RBs may be notified to the wireless communication device as described in Proposal 1. Then, the wireless communication device may determine the second and subsequent RBs based on the offset between the two RBs. The offset may be fixed (e.g., specified in the specifications), or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., or may be set in advance. For example, if the first RB is RB 1st If , the second RB is (RB 1st + offset) mod N (N is the number of RBs in the A-IoT bandwidth).
[0170] Multiple subcarriers / frequency units within each signaled RB may be used for CW / R2D / D2R transmission as described in A to D below.
[0171] A As explained in Proposal 1, one subcarrier / frequency unit in each RB may be used for CW / R2D / D2R transmission.
[0172] B As explained in Proposal 2, multiple consecutive subcarriers / frequency units within each RB may be used for CW / R2D / D2R transmission.
[0173] As described in Option 2 of C Proposal 3, multiple non-contiguous subcarriers / frequency units within each RB may be used for CW / R2D / D2R transmission.
[0174] D Each entire RB (i.e., all subcarriers / frequency units contained in the RB) may be used for CW / R2D / D2R transmission.
[0175] As described above, the wireless communication device may receive information regarding frequency resources to be used for CW / R2D / D2R transmission, and may determine, based on the received information, multiple non-contiguous subcarriers / frequency units or multiple non-contiguous RBs (or subcarriers / frequency units included in them) to be used for CW / R2D / D2R transmission.
[0176] As described above, according to Proposal 3, the wireless communication device can determine the frequency resources to be used for CW / R2D / D2R transmission based on the received information, and can perform CW / R2D / D2R transmission appropriately.
[0177] <Proposal 4> A proposal (Proposal 4) regarding resources including frequency resources for CW / R2D / D2R transmission will be described, assuming that frequency hopping is performed and one subcarrier / frequency unit is used for CW / R2D / D2R transmission in each frequency hop (hereinafter simply referred to as a hop). Note that the hatched portion in Fig. 21 indicates an example of frequency resources used for CW / R2D / D2R transmission.
[0178] The subcarriers / frequency units used in the multiple hops may be signaled to the wireless communication device as described in Proposal 2 / 3. As mentioned above, one subcarrier / frequency unit may be used in each hop.
[0179] Next, the time resources (or time domain resources) of each hop will be described in detail.
[0180] [Option 1] The time resource for each hop may be 1 symbol / 1 slot / 1 time unit.
[0181] [Option 2] The time resource for each hop may be multiple symbols / slots / time units. For example, multiple symbols / slots / time units may be L symbols / L slots / L time units, where L may be specified, signaled, or determined as described in A-B below.
[0182] AL may be fixed (for example, defined in a specification), or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc. via RRC / MAC CE / DCI, or may be preset in the wireless communication device.
[0183] B. If the number of symbols / slots / time units used for CW / R2D / D2R transmission is M, the number of hops is N, and M symbols / M slots / M time units are divided into N hops, the wireless communication device may determine L based on M and N (e.g., For example, if there are two hops, the first hop may be The second hop is It may be time unit, or the first hop may be The second hop is It may be in units of hours.
[0184] [Option 3] The time resource for each hop may be one repetition. Note that repetition may mean one or more of the following 1) to 4). 1) The same sequence is transmitted and / or received multiple times. 2) A signal or channel carrying a higher layer payload is transmitted and / or received multiple times. The higher layer payload may be, for example, RRC signaling, MAC-CE, or MAC-PDU (protocol data unit). 3) A signal or channel carrying a PHY layer payload is transmitted and / or received multiple times. 4) For backscattering, a CW (Continuous Wave) waveform is transmitted and / or received multiple times.
[0185] [Option 4] The time resource for each hop may be multiple iterations. For example, the multiple iterations may be L iterations, where L may be specified, signaled, or determined as described in A-B below.
[0186] AL may be fixed (for example, defined in a specification), or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc. via RRC / MAC CE / DCI, or may be preset in the wireless communication device.
[0187] B. If the number of repetitions is M, the number of hops is N, and M repetitions are divided into N hops, the wireless communication device may determine L based on M and N (e.g., For example, if there are two hops, the first hop may be Repeat, the second hop is It may be repeated, and the first hop is Repeat, the second hop is It may be repeated.
[0188] Next, the mapping between multiple subcarriers / frequency units and multiple hops is described.
[0189] A. If the number of subcarriers / frequency units and the number of hops are the same, multiple subcarriers / frequency units may be mapped to multiple hops (each subcarrier / frequency unit may be mapped to a different hop).
[0190] B. When the number of subcarriers / frequency units (N) is less than the number of hops, the first subcarrier / frequency unit may be mapped to the first hop, the second subcarrier / frequency unit may be mapped to the second hop, ..., the Nth subcarrier / frequency unit may be mapped to the Nth hop, and the N+1th and subsequent subcarriers / frequency units may be mapped to their respective hops in the same manner as above, starting from the first hop. Figure 22 shows an example of mapping between subcarriers / frequency units and hops when the number of subcarriers / frequency units is less than the number of hops. The example shown in Figure 22 shows mapping when N=2 and the number of hops is 4.
[0191] As described above, a wireless communication device may receive information regarding frequency resources used for CW / R2D / D2R transmission, and based on the received information, determine the subcarriers / frequency units to be used for CW / R2D / D2R transmission when frequency hopping is being performed.
[0192] As described above, according to Proposal 4, a wireless communication device can determine the frequency resources to be used for CW / R2D / D2R transmission based on the received information, and can appropriately perform CW / R2D / D2R transmission while improving coverage.
[0193] <Proposal 5> A proposal (Proposal 5) regarding resources including frequency resources for CW / R2D / D2R transmission will be described under the assumption that frequency hopping is performed and multiple consecutive subcarriers / frequency units (referred to as a subcarrier / frequency unit set) are used for CW / R2D / D2R transmission at each hop. Note that the hatched portion in Fig. 23 indicates an example of frequency resources used for CW / R2D / D2R transmission.
[0194] The multiple subcarrier / frequency unit sets used in the multiple hops may be signaled to the wireless communication device as described below in Alt. 1-Alt. 2. As described above, one subcarrier / frequency unit set may be used in each hop.
[0195] Alt. 1 For each subcarrier / frequency unit set, multiple consecutive subcarriers / frequency units may be signaled to the wireless communication device as described in Proposal 2.
[0196] Alt. 2 For the first subcarrier / frequency unit set, multiple consecutive subcarriers / frequency units may be signaled to the wireless communication device as described in Proposal 2. Here, all subcarrier / frequency unit sets are assumed to have the same number of subcarriers / frequency units / RBs. In this case, the wireless communication device may determine the second and subsequent subcarrier / frequency unit sets based on the offset between the subcarriers / frequency units / RBs in the two subcarrier / frequency unit sets. The offset may be fixed (e.g., specified in a specification), or may be signaled to the wireless communication device by the base station 10, an intermediate UE, or the like, or may be set in advance. The offset may also be in units of subcarriers / frequency units / RBs. As in the previous proposal, the wireless communication device may determine the subcarriers / frequency units / RBs in the second and subsequent subcarrier / frequency unit sets as described in Options A to C below.
[0197] (Option A) For example, the first or starting subcarrier / frequency unit in the first subcarrier / frequency unit set is SC 1st , then the first or starting subcarrier / frequency unit in the second subcarrier / frequency unit set is (SC 1st + offset) mod N (where N is the number of subcarriers / frequency units in the A-IoT bandwidth).
[0198] (Option B) For example, the first or starting subcarrier / frequency unit in the first subcarrier / frequency unit set is SC 1st , then the first or starting subcarrier / frequency unit in the second subcarrier / frequency unit set is (SC 1st + offset) mod N (where N is the number of subcarriers / frequency units in an RB).
[0199] (Option C) For example, the first or starting RB in the first subcarrier / frequency unit set is RB 1st , then the first or starting RB in the second subcarrier / frequency unit set is (RB 1st+ offset) mod N (N is the number of RBs in the A-IoT bandwidth).
[0200] The time resource for each hop may be the same as or similar to that in Proposal 4, and therefore the explanation will be omitted.
[0201] Next, the mapping between multiple subcarrier / frequency unit sets and multiple hops is described.
[0202] A. When the number of subcarrier / frequency unit sets and the number of hops are the same, multiple subcarrier / frequency unit sets may be mapped to multiple hops respectively (each subcarrier / frequency unit set may be mapped to a different hop).
[0203] B. When the number of subcarrier / frequency unit sets (N) is smaller than the number of hops, the first subcarrier / frequency unit set may be mapped to the first hop, the second subcarrier / frequency unit set may be mapped to the second hop, ..., the Nth subcarrier / frequency unit set may be mapped to the Nth hop, and the N+1th and subsequent subcarrier / frequency unit sets may be mapped to their respective hops in the same manner as above, starting from the first hop. Figure 24 is a diagram showing an example of mapping between subcarrier / frequency unit sets and hops when the number of subcarrier / frequency unit sets is smaller than the number of hops. The example shown in Figure 24 shows mapping when N = 2 and the number of hops is 4.
[0204] As described above, a wireless communication device may receive information regarding frequency resources used for CW / R2D / D2R transmission, and based on the received information, determine the subcarriers / frequency units to be used for CW / R2D / D2R transmission when frequency hopping is being performed.
[0205] As described above, according to Proposal 5, a wireless communication device can determine the frequency resources to be used for CW / R2D / D2R transmission based on the received information, and can appropriately perform CW / R2D / D2R transmission while improving coverage.
[0206] <Additional Notes on Proposals 1 / 2 / 3> Regarding Proposals 1 / 2 / 3, the capabilities (information) of intermediate UEs, A-IoT devices, and CW nodes that support single subcarrier transmission or multiple subcarrier transmission may be reported to the network.
[0207] Also, with respect to Proposals 1 / 2 / 3, multi-subcarrier D2R transmission may only be supported by A-IoT devices capable of active RF generation (e.g., device 2b) and may not be supported by A-IoT devices that perform backscatter transmission (e.g., device 1 / 2a).
[0208] <Additional Notes Regarding Proposal 4 / 5> Regarding Proposal 4 / 5, the enabling / disabling of frequency hopping may be notified to the wireless communication device.
[0209] Regarding Proposals 4 and 5, the number of hops may be specified in the specifications, or may be notified to the wireless communication device by the base station 10, an intermediate UE, etc., via RRC / MAC CE / DCI, or may be preset in the wireless communication device.
[0210] Also, with regard to Proposal 4 / 5, the capabilities (information) of intermediate UEs, A-IoT devices, and CW nodes that support frequency hopping may be reported to the network.
[0211] Also, with regard to Proposal 4 / 5, the number of frequency hopping hops supported by an A-IoT device may be determined according to the device type (e.g., device 1 / 2a / 2b) and reported to the network. For example, if frequency hopping is advertised for D2R but device 1 is not frequency hopping capable, device 1 may interpret it as using one of the advertised hops for D2R transmission, while device 2 may apply frequency hopping for D2R transmission. This results in improved D2R coverage for device 2 that implements frequency hopping, but poor D2R coverage for device 1 that is not frequency hopping capable.
[0212] <Example of Operation According to Proposal> Next, an example of operation of the wireless communication device will be described with reference to FIG.
[0213] In step S11, the wireless communication device receives information about frequency resources used for communication involving an A-IoT device. As described above, the wireless communication device may be the A-IoT device, an intermediate UE, or a CW node.
[0214] In step S12, the wireless communication device determines the frequency resources to be used for communication involving the A-IoT device based on the information received in step S11.
[0215] It should be noted that steps S11 and S12 may be performed in accordance with suggestions 1 to 5, including options, Alt, variations, etc., described above.
[0216] As described above, according to this proposal, the wireless communication device can determine the frequency resources to be used for communication involving the A-IoT device based on the received information, and can appropriately carry out communication involving the A-IoT device.
[0217] 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.
[0218] <Configuration of Base Station> Fig. 26 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. 27) wirelessly. The base station 10 may be a terminal (an intermediate UE communicating with the device 20) or a CW node.
[0219] 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.
[0220] 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.
[0221] 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.
[0222] 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.
[0223] 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.
[0224] 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 .
[0225] 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.
[0226] 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.
[0227] 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.
[0228] 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 .
[0229] For example, the transmitting unit 101 may transmit information regarding frequency resources used for communication involving an A-IoT device to the device 20, etc.
[0230] Furthermore, for example, the communication unit may use the above frequency resources to perform communication involving an A-IoT device.
[0231] 27 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 a terminal (for example, an intermediate UE) or a CW node.
[0232] 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.
[0233] 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.
[0234] 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.
[0235] 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.
[0236] 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).
[0237] 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 .
[0238] 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.
[0239] 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.
[0240] 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.
[0241] 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.
[0242] Here, the receiving unit 201 and the transmitting unit 202 (which may be collectively referred to as a communication unit) communicate with the network, such as the base station 10 and intermediate UEs.
[0243] For example, the receiver 201 may receive information regarding frequency resources to be used for communication involving the A-IoT device from the base station 10 or the network of intermediate UEs, and the controller 203 may determine the frequency resources to be used for communication involving the A-IoT device based on the information received by the receiver 201. The frequency resources to be used for communication involving the A-IoT device may be one frequency resource, a plurality of contiguous frequency resources, or a plurality of non-contiguous frequency resources, and may include a first frequency resource used in a first frequency hop and a second frequency resource used in a second frequency hop.
[0244] Also, for example, the communication unit may use frequency resources determined by the control unit 203 to perform communication involving an A-IoT device.
[0245] (Summary of the embodiment) A wireless communication device according to one aspect of the present disclosure includes a receiving unit that receives information regarding frequency resources used for communication involving an ambient Internet of Things (IoT) device, and a control unit that determines frequency resources to be used for the communication based on the information.
[0246] By having the above configuration, the wireless communication device can determine the frequency resources to be used for communication involving the A-IoT device based on the received information, and can properly carry out communication involving the A-IoT device.
[0247] In one example, the frequency resource used for the communication is one frequency resource.
[0248] By having the above configuration, the wireless communication device can perform communications involving A-IoT devices using narrower frequencies, taking into account the simple configuration of A-IoT devices.
[0249] In one example, the frequency resources used for the communication are a plurality of contiguous frequency resources.
[0250] With the above configuration, the wireless communication device can use a wider range of frequencies to perform communications involving A-IoT devices.
[0251] In one example, the frequency resources used for the communication are a plurality of non-contiguous frequency resources.
[0252] With the above configuration, the wireless communication device can use a wider range of frequencies to perform communications involving A-IoT devices.
[0253] In one example, the frequency resources used for the communication include one or more first frequency resources used in a first frequency hop and one or more second frequency resources used in a second frequency hop.
[0254] With the above configuration, the wireless communication device can perform communication involving A-IoT devices while improving coverage.
[0255] A communication method according to one aspect of the present disclosure includes a wireless communication device receiving information regarding frequency resources to be used for communication involving an ambient Internet of Things (IoT) device, and determining, based on the information, frequency resources to be used for the communication.
[0256] By having the above configuration, the wireless communication device can determine the frequency resources to be used for communication involving the A-IoT device based on the received information, and can properly carry out communication involving the A-IoT device.
[0257] 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).
[0258] <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.
[0259] 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.
[0260] 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. 28 is a diagram showing 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.
[0261] 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.
[0262] 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.
[0263] 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.
[0264] 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.
[0265] 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.
[0266] 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.
[0267] 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.
[0268] 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).
[0269] 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.
[0270] 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.
[0271] <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.
[0272] <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).
[0273] <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.
[0274] <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.
[0275] <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.
[0276] <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.
[0277] <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 numerical comparison (e.g., comparison with a predetermined value).
[0278] <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).
[0279] 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.
[0280] <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.
[0281] 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.
[0282] 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.
[0283] 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.
[0284] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0285] <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.
[0286] 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.
[0287] <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.
[0288] 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.
[0289] 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.
[0290] Mobile Station In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.
[0291] 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.
[0292] <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.
[0293] 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.
[0294] 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.
[0295] Fig. 29 shows an example configuration of a vehicle 2001. As shown in Fig. 29, 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.
[0296] 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.
[0297] 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).
[0298] 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.
[0299] 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.
[0300] 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.
[0301] 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.
[0302] 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.
[0303] 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.
[0304] 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.
[0305] 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)).
[0306] 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.
[0307] <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.
[0308] 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.
[0309] <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.
[0310] <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."
[0311] "First," "Second" Any reference to an element using a designation 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.
[0312] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," etc.
[0313] 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.
[0314] <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.
[0315] 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.
[0316] 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.
[0317] 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.
[0318] 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.
[0319] 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.
[0320] 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.
[0321] 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.
[0322] 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.
[0323] 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.
[0324] 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.
[0325] 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.
[0326] 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.
[0327] 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.
[0328] 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.
[0329] 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.
[0330] 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.
[0331] 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."
[0332] 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.
[0333] <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.
[0334] 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 plural.
[0335] <"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."
[0336] One aspect of the present disclosure is useful in wireless communication systems.
[0337] 10 Base station 20 Device 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller
Claims
1. A wireless communication device comprising: a receiving unit that receives information regarding frequency resources to be used for communication involving an ambient IoT (Internet of Things) device; and a control unit that determines the frequency resources to be used for the communication based on the information.
2. The wireless communication device according to claim 1, wherein the frequency resource used for the communication is a single frequency resource.
3. The wireless communication device according to claim 1, wherein the frequency resources used for the communication are a plurality of contiguous frequency resources.
4. The wireless communication device according to claim 1, wherein the frequency resources used for the communication are a plurality of non-contiguous frequency resources.
5. The wireless communication device of claim 1, wherein the frequency resources used for the communication include one or more first frequency resources used in a first frequency hop and one or more second frequency resources used in a second frequency hop.
6. A communication method, comprising: a wireless communication device receiving information regarding frequency resources to be used for communication involving an ambient Internet of Things (IoT) device; and determining frequency resources to be used for the communication based on the information.