Communication device

Abstract

This communication device, to which power is supplied by energy harvesting, includes: a receiving unit that receives downlink control information including information related to unicasting, multicasting, and broadcasting of a downlink signal; and a control unit that determines reception of the downlink signal on the basis of the downlink control information.

Description

communication equipment

[0001] The present disclosure relates to a communication device.

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

[0003] Furthermore, 3GPP (registered trademark) Release 18 is considering Ambient Internet of Things (A-IoT) (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.7.0 (2021-09)" New SID: Study on solutions for Ambient IoT (Internet of Things) in NR ", RP-234058, 3GPP TSG RAN Meeting #102, December 2023

[0005] In ambient IoT, unicast, multicast, and broadcast have not been sufficiently studied, and further study is required.

[0006] In ambient IoT, device-specific transmission, group-based transmission, and cell-based transmission in the uplink direction have not been sufficiently studied, and further study is required.

[0007] One aspect of the present disclosure is to provide a communication device capable of communication in an appropriate cast type.

[0008] One aspect of the present disclosure is to provide a communication device that can appropriately perform upstream transmission.

[0009] A communication device according to one aspect of the present disclosure is a communication device that receives power from an environmentally-powered source, and includes a receiving unit that receives downlink control information including information regarding unicast, multicast, and broadcast downlink signals, and a control unit that determines reception of the downlink signals based on the downlink control information.

[0010] A communication device according to one aspect of the present disclosure is a communication device that receives power from an environmental harvester, and includes a receiving unit that receives downlink control information including information regarding device-specific transmission, group-based transmission, and cell-based transmission of an uplink signal, and a control unit that determines transmission of the uplink signal based on the downlink control information.

[0011] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating Topology 1. FIG. 2 is a diagram illustrating Topology 3 in DL support. FIG. 3 is a diagram illustrating Topology 3 in UL support. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating L1 R2D control information to be discussed. FIG. 7 is a diagram illustrating Proposal 1. FIG. 8 is a diagram illustrating Proposal 1. FIG. 9 is a diagram illustrating Proposal 1. FIG. 10 is a diagram illustrating Proposal 1. FIG. 11 is a diagram illustrating Proposal 1. FIG. 12 is a diagram illustrating Proposal 2. FIG. 13 is a diagram illustrating Proposal 2. FIG. 14 is a diagram illustrating Proposal 2. FIG. 15 is a block diagram illustrating an example of the configuration of a reader according to an embodiment. FIG. 16 is a block diagram illustrating an example of the configuration of a device according to an embodiment. FIG. 17 is a diagram illustrating an example of the hardware configuration of a reader and a device according to the present embodiment. FIG. 18 is a diagram illustrating an example of the configuration of a vehicle.

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

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

[0014] Furthermore, in the embodiments of the present disclosure described below, terms used in existing LTE, such as SS (synchronization signal), PSS (primary SS), SSS (secondary SS), PBCH (physical broadcast channel), PRACH (physical random access channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), and PUSCH (physical uplink shared channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

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

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

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

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

[0019] The base station 10 transmits DL signals such as control information, setting information, and data to the device 20 via DL (Downlink). 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 from the device 20 via UP (Uplink).

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

[0021] As will be described later, the wireless communication system may include an intermediate node, an assisting node, and / or a terminal (UE) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be simply written as " / ".

[0022] 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 or an A-IoT device.

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

[0024] 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, or the like transmitted in the PUSCH or the PUCCH.

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

[0026] For Ambient IoT, for example, the following deployment scenarios and characteristics can be considered for the 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, etc. 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 the device

[0027] 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

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

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

[0030] The complexity of device A is assumed to be about the same as that of RFID (Radio frequency identification).

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

[0032] Figure 2 is a diagram illustrating Topology 1. As shown in Figure 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 communicates directly with the base station in both directions.

[0033] Figure 3 is a diagram illustrating Topology 2. As shown in Figure 3, Topology 2 is a configuration in which a base station and an ambient IoT device communicate via an intermediate node. The ambient IoT device performs bidirectional communication with the intermediate node located between the base station and the ambient IoT device. The intermediate node may be, for example, a relay, an integrated access and backhaul (IAB) node, a UE, a repeater, etc.

[0034] Fig. 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.

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

[0036] 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 an ambient IoT device and a base station.

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

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

[0039] Figure 6 illustrates Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device communicates with the UE bidirectionally. The communication related to Topology 4 may be considered as sidelink (SL) communication.

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

[0041] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE in 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. Furthermore, the A-IoT device may be used interchangeably with the A-IoT UE or the A-IoT terminal. The A-IoT device may be simply referred to as A-IoT.

[0042] 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 field from the base stations, intermediate nodes, support nodes, and other nodes via inductive coupling.

[0043] The ambient IoT device backscatters and modulates the RF signals received from the base station, the intermediate node, the support node, and other nodes by switching the reflection coefficient of the antenna of the ambient IoT device, and transmits information to the base station, the intermediate node, the support node, and other nodes. The RF signals may also be referred to as carrier waves.

[0044] 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 in FIG. 7 indicates an OFF section, which may correspond to the information (bit) "0." A sine wave signal may correspond to the information "1."

[0045] <Rel-19 SID> In the Rel-19 SID, necessary and feasible solutions for A-IoT were considered (Section 4.1 of Non-Patent Document 5). The considered solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

[0046] Additionally, several issues will be discussed for A-IoT DL and UL under the leadership of RAN 1. These include: Frame structure, synchronization and timing, and random access Numerology, bandwidth, and multiple access Waveform and modulation Channel coding DL channel / signal aspects UL channel / signal aspects Scheduling and timing implications

[0047] A-IoT has been approved as a topic for Rel. 19. In discussing A-IoT, the following points can be considered: 1. Traffic flow, 2. Device assumptions, and 3. Topology.

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

[0049] 1a. DT (device terminated) Traffic includes transmission to the A-IoT UE (DL), but not transmission from the A-IoT UE (UL). 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, which includes instructions such as commands or instructions to the A-IoT UE.

[0050] 1b. 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.

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

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

[0053] TX is an unamplified backscatter UL transmission or an amplified general UL transmission. Alternatively, an amplified backscatter UL transmission may be performed.

[0054] 2b. 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, this disclosure is not limited to FR1-FDD and may be applied to TDD, FR2, or FR3.

[0055] 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

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

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

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

[0059] 3b. Topology 2 In Topology 2, communication is performed between the base station and the A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with the intermediate node located between the base station and the A-IoT UE. Note that the base station in Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases.

[0060] For A-IoT UEs, the signal design is common to Topology 1 and Topology 2. Hereinafter, the intermediate node may be referred to as int. UE (intermediate UE). The intermediate node may also be referred to as a base station, a communication device, a network device, or a network node.

[0061] <R2D and D2R> At the RAN1#116 meeting, physical channels were considered for R2D data transmission and D2R data transmission.

[0062] R2D stands for "reader to device." D2R stands for "device to reader." A "reader" corresponds to a base station or intermediate node. A "device" corresponds to A-IoT.

[0063] R2D may be considered as DL in an A-IoT wireless communication system. R2D data transmission may be performed on a physical channel such as the physical reader to device channel (PRDCH). R2D control transmission may be performed on the same physical channel as R2D data transmission or on a different physical channel from R2D data transmission.

[0064] D2R can be considered as the UL in an A-IoT wireless communication system. D2R data transmission can be performed on a physical channel such as a physical device to reader channel (PDRCH). D2R control transmission can be performed on the same physical channel as D2R data transmission or on a physical channel separate from D2R.

[0065] R2D, R2D transmission, R2D signal, DL, and DL signal may be used interchangeably. D2R, D2R transmission, R2D signal, UL, and UL signal may be used interchangeably. R2D control transmission may be referred to as R2D control information or control information. D2R control transmission may be referred to as D2R control information or control information. Signal, data, and information may be used interchangeably.

[0066] <L1 D2R control information> It has been agreed that L1 (Layer 1) R2D control information is transmitted on PRDCH. PRDCH is a physical channel for R2D and carries the following information (data): - Upper layer payload - L1 R2D control information (if defined)

[0067] Also, for PRDCH scheduling / PDRCH scheduling, the L1 R2D control information shown in FIG. 8 is discussed.

[0068] <Considerations> As shown in FIG. 8, the L1 R2D control information may include a device ID, a device group ID, an R2D cast type, and a D2R scheduling type.

[0069] However, the A-IoT communication system does not consider a specific mechanism for performing casting. For example, a mechanism for performing unicast, multicast, and broadcast has not been considered. Therefore, the A-IoT communication system cannot perform communication in an appropriate cast type.

[0070] Furthermore, specific mechanisms for D2R scheduling have not been considered for A-IoT communication systems. For example, mechanisms for device-specific D2R, group-based D2R, and cell-based D2R have not been considered. As a result, A-IoT communication systems cannot communicate using appropriate D2R.

[0071] Therefore, in this disclosure, Proposal 1 is provided as a technique for performing communication using an appropriate cast type.

[0072] Furthermore, in this disclosure, Proposal 2 is provided as a technique for performing appropriate D2R.

[0073] Note that Proposal 1 and Proposal 2 may be applied to the L1 R2D control information shown in Figure 8. Proposal 1 and Proposal 2 may also be applied to L1 R2D control information other than the L1 R2D control information shown in Figure 8. The L1 R2D control information shown in Figure 8 may be applied to PRDCH scheduling, PDRCH scheduling, or both PRDCH and PDRCH scheduling. Proposal 1 and Proposal 2 may be applied to PRDCH scheduling, PDRCH scheduling, or both PRDCH and PDRCH scheduling.

[0074] L1 R2D control, L1 R2D control data, L1 R2D control information, control, control data, and control information may be used interchangeably. R2D data and data may be used interchangeably. Information and signaling may be used interchangeably. PRDCH may be referred to as a downlink physical channel. PDRCH may be referred to as an uplink physical channel. Device group ID may be referred to as a group ID.

[0075] <Proposal 1> Proposal 1 provides a technique for indicating cast type / device ID / group ID for PRDCH scheduling.

[0076] Proposal 1 provides options 1 to 3 for indicating a cast type / device ID / group ID for PRDCH scheduling. Proposal 1 also provides techniques for device behavior after indicating a cast type / device ID / group ID. Options 1 to 3 and device behavior will be described below.

[0077] <Proposal 1: Option 1> In Option 1 of Proposal 1, fields in the L1 R2D control information are used to indicate the cast type / device ID / group ID for PRDCH scheduling. Regarding the fields in the L1 R2D control information, the following Option 1-1 to Option 1-3 are provided.

[0078] <Proposal 1: Option 1: Option 1-1> One field is used in the L1 R2D control information to indicate a cast type / device ID / group ID for PRDCH scheduling. The field may indicate a device ID (or device specific ID), a group ID, or broadcast. For example, the L1 R2D control information may have a codepoint field (codepoint field) and indicate "Codepoint" in FIG. 9. The codepoint may indicate a device ID, a group ID, or broadcast, as shown in "Information" in FIG. 9.

[0079] For example, a device ID is mapped to the N code points indicated by arrow A9a in Fig. 9. When these code points are indicated in the code point field, unicast is indicated.

[0080] For example, a group ID is mapped to the M code points indicated by arrow A9b in Fig. 9. When these code points are indicated in the code point field, multicast is indicated.

[0081] For example, broadcast is mapped to one code point indicated by arrow A9c in Fig. 9. When this code point is indicated in the code point field, broadcast is indicated.

[0082] The reader includes, for example, the code points shown in FIG. 9 in the code point field of the L1 R2D control information and transmits it.

[0083] The device receives subsequent R2D data corresponding to the L1 R2D control information if the codepoint field indicates a device ID corresponding to the device, or indicates a group ID corresponding to the device, or indicates a broadcast.

[0084] Each device may have one or more code points, and if the indicated code point is included, the device continues subsequent operations corresponding to the L1 R2D control information (e.g., receiving R2D data).

[0085] The reader recognizes whether the R2D data is unicast, multicast, or broadcast, and sets the code point accordingly. The device does not need to recognize whether the R2D data is unicast, multicast, or broadcast before receiving it. In other words, the device only needs to recognize whether the code point field contains an ID (device ID / group ID) corresponding to the device, or whether it indicates broadcast.

[0086] The relationship between the code points and the information (the information shown in FIG. 9) may be notified to the device by higher layer signaling such as L1 R2D control information or RRC.

[0087] <Proposal 1: Option 1: Option 1-2> To indicate the cast type / device ID / group ID for PRDCH scheduling, one field X indicates the cast type and another field Y indicates the device ID / group ID in the L1 R2D control information. For example, as shown in Figure 10, field X indicates the cast type and field Y indicates the device ID / group ID.

[0088] For example, if field X in FIG. 10 indicates unicast, field Y (code point) is mapped to a device ID.

[0089] For example, if field X in FIG. 10 indicates multicast, field Y is mapped to a group ID.

[0090] For example, if field X in FIG. 10 indicates broadcast, field Y is set to either reserve or absent.

[0091] The reader includes the cast type in field X of the L1 R2D control information, and includes the device ID / group ID in field Y of the L1 R2D control information, and then transmits the information.

[0092] A device receives subsequent R2D data corresponding to the L1 R2D control information if the field X of the L1 R2D control information indicates unicast / multicast and the field Y indicates the device ID / group ID corresponding to the device.A device receives subsequent R2D data corresponding to the L1 R2D control information if the field X of the L1 R2D control information indicates broadcast.

[0093] If field X of the L1 R2D control information indicates unicast / multicast, the device assumes that field Y indicates device ID / group ID. If field X of the L1 R2D control information indicates broadcast, the device assumes that field Y is reserved or absent. If field X of the L1 R2D control information indicates broadcast, the device may not refer to field Y, which is reserved or absent.

[0094] <Proposal 1: Option 1: Option 1-3> To indicate the cast type / device ID / group ID for PRDCH scheduling, one field X indicates the cast type, another field Y indicates the device ID, and another field Z indicates the group ID in the L1 R2D control information. For example, as shown in Figure 11, field X indicates the cast type, field Y indicates the device ID, and field Z indicates the group ID.

[0095] For example, if field X in Figure 11 indicates unicast, then field Y is mapped to a device ID, and field Z is reserved or absent.

[0096] For example, if field X in Figure 11 indicates multicast, a group ID is mapped to field Z. Field Y can be reserved or absent.

[0097] For example, if field X in FIG. 11 indicates broadcast, fields Y and Z are reserved or absent.

[0098] The reader includes a cast type in field X of the L1 R2D control information, a device ID in field Y of the L1 R2D control information, and a group ID in field Z of the L1 R2D control information, and then transmits the information.

[0099] The device receives subsequent R2D data corresponding to the L1 R2D control information if field X of the L1 R2D control information indicates unicast / multicast and field Y indicates a device ID corresponding to the device / field Z indicates a group ID corresponding to the device.The device receives subsequent R2D data corresponding to the L1 R2D control information if field X of the L1 R2D control information indicates broadcast.

[0100] If field X of the L1 R2D control information indicates unicast, the device assumes that field Y indicates a device ID and that field Z is reserved or absent. If field X of the L1 R2D control information indicates unicast, the device may refer to field Y, which is assumed to indicate a device ID, and not refer to field Z, which is reserved or absent.

[0101] If field X of the L1 R2D control information indicates multicast, the device assumes that field Z indicates a group ID and that field Y is reserved or absent. If field X of the L1 R2D control information indicates multicast, the device may refer to field Z, which is assumed to indicate a group ID, and not refer to field Y, which is reserved or absent.

[0102] If field X of the L1 R2D control information indicates broadcast, the device assumes that fields Y and Z are reserved or absent. If field X of the L1 R2D control information indicates broadcast, the device does not need to refer to fields Y and Z that are reserved or absent.

[0103] <Proposal 1: Option 2> In option 2 of proposal 1, a scrambling sequence is used to indicate the cast type / device ID / group ID for PRDCH scheduling.

[0104] A different scrambling sequence is used for unicasting to each device. For example, as shown in Figure 12, sequence #a is used for unicasting to device #a, sequence #b is used for unicasting to device #b, and sequence #c is used for unicasting to device #c.

[0105] A different scrambling sequence is used for multicasting for each group of devices. For example, as shown in Figure 13, sequence #d is used for multicasting to device group #d, sequence #e is used for multicasting to device group #e, and sequence #f is used for multicasting to device group #f.

[0106] One scrambling sequence is used for broadcasting, for example, sequence #g is used for broadcasting to all devices as shown in Figure 14.

[0107] For example, the leader scrambles the L1 R2D control information using the sequence shown in Figure 12 for unicasting the L1 R2D control information to devices #a / #b / #c. For example, the leader scrambles the L1 R2D control information using the sequence shown in Figure 13 for multicasting the L1 R2D control information to group devices #d / #e / #f. For example, the leader scrambles the L1 R2D control information using the sequence shown in Figure 14 for global broadcasting of the L1 R2D control information to devices.

[0108] The device receives the L1 R2D control information using the sequence corresponding to the device, the sequence corresponding to the group device, and the sequence corresponding to the broadcast. For example, the device de-scrambles the L1 R2D control information using the sequence corresponding to the device, the sequence corresponding to the group device, and the sequence corresponding to the broadcast.

[0109] When a device receives L1 R2D control information using a sequence corresponding to the device / sequence corresponding to a group device / sequence corresponding to a broadcast, the device receives subsequent R2D data corresponding to the L1 R2D control information.

[0110] In Option 2 of Proposal 1, it is not necessary to explicitly notify the cast type / device ID / group ID in the L1 R2D control information.

[0111] The sequence corresponding to the device, the sequence corresponding to the group device, and the sequence corresponding to the broadcast may be notified to the device by higher layer signaling such as L1 R2D control information or RRC.

[0112] <Proposal 1: Option 3> In option 3 of proposal 1, a field in the L1 R2D control information and a scrambling sequence are used to indicate the cast type / device ID / group ID for PRDCH scheduling.

[0113] For example, different scrambling sequences are used for unicast, multicast, and broadcast. For example, for unicast, the same sequence #a is used for all devices. For example, for multicast, the same sequence #b is used for all groups. For example, for broadcast, sequence #c is used. Devices receive L1 R2D control information using sequences corresponding to unicast / multicast / broadcast.

[0114] The device ID / group ID is indicated in the L1 R2D control information. Regarding the indication of the device ID / group ID in the L1 R2D control information, the following options 3-1 and 3-2 are provided.

[0115] <Proposal 1: Option 3: Option 3-1> The L1 R2D control information has a field X. The field X indicates the device ID / group ID.

[0116] For example, when a device receives L1 R2D control information using a sequence corresponding to unicast (for example, sequence #a), a device ID is mapped to field X of the L1 R2D control information.

[0117] For example, when a device receives L1 R2D control information using a sequence corresponding to multicast (for example, sequence #b), a group ID is mapped to field X of the L1 R2D control information.

[0118] For example, if the device receives L1 R2D control information using a sequence corresponding to a broadcast (eg, sequence #c), field X is reserved or absent.

[0119] The reader includes the device ID / group ID in field X of the L1 R2D control information based on the cast type. For example, in the case of unicast, the reader includes the device ID in field X. For example, in the case of multicast, the reader includes the group ID in field X. For example, in the case of multicast, the reader reserves or absents field X.

[0120] The reader scrambles the L1 R2D control information with field X set based on the cast type. For example, the reader scrambles the L1 R2D control information using sequence #a in the case of unicast. For example, the reader scrambles the L1 R2D control information using sequence #b in the case of multicast. For example, the reader scrambles the L1 R2D control information using sequence #c in the case of broadcast.

[0121] When a device receives L1 R2D control information using a sequence corresponding to unicast, it assumes that a device ID is mapped to field X. When a device ID corresponding to the device is mapped to field X, the device receives subsequent R2D data corresponding to the L1 R2D control information.

[0122] When a device receives L1 R2D control information using a sequence corresponding to multicast, the device assumes that a group ID is mapped to field X. If a group ID corresponding to the device is mapped to field X, the device receives subsequent R2D data corresponding to the L1 R2D control information.

[0123] When a device receives L1 R2D control information using a sequence corresponding to a broadcast, the device receives subsequent R2D data corresponding to the L1 R2D control information. When a device receives L1 R2D control information using a sequence corresponding to a broadcast, the device assumes that field X is reserved or absent. The device does not need to refer to field X that is reserved or absent.

[0124] <Proposal 1: Option 3: Option 3-2> The L1 R2D control information has fields X and Y. Field X indicates a device ID, and field Y indicates a group ID.

[0125] For example, when a device receives L1 R2D control information using a sequence corresponding to unicast (e.g., sequence #a), a device ID is mapped to field X of the L1 R2D control information, and field Y is reserved or absent.

[0126] For example, when a device receives L1 R2D control information using a sequence corresponding to multicast (e.g., sequence #b), a group ID is mapped to field Y of the L1 R2D control information, and field X is reserved or absent.

[0127] For example, if a device receives L1 R2D control information using a sequence corresponding to a broadcast (eg, sequence #c), fields X and Y are reserved or absent.

[0128] The reader includes a device ID in field X and a group ID in field Y of the L1 R2D control information based on the cast type. For example, in the case of unicast, the reader includes a device ID in field X and reserves or leaves field Y unassigned. For example, in the case of multicast, the reader includes a group ID in field Y and reserves or leaves field X unassigned. For example, in the case of multicast, the reader reserves or leaves fields X and Y unassigned.

[0129] The reader scrambles the L1 R2D control information with fields X and Y set based on the cast type. For example, in the case of unicast, the reader scrambles the L1 R2D control information using sequence #a. For example, in the case of multicast, the reader scrambles the L1 R2D control information using sequence #b. For example, in the case of broadcast, the reader scrambles the L1 R2D control information using sequence #c.

[0130] When a device receives L1 R2D control information using a sequence corresponding to unicast, it assumes that a device ID is mapped to field X and that field Y is reserved or absent. If a device ID corresponding to the device is mapped to field X, the device receives subsequent R2D data corresponding to that L1 R2D control information. The device does not need to refer to field Y, which is reserved or absent.

[0131] When a device receives L1 R2D control information using a sequence corresponding to multicast, it assumes that a group ID is mapped to field Y and that field X is reserved or absent. If a group ID corresponding to the device is mapped to field Y, the device receives subsequent R2D data corresponding to that L1 R2D control information. The device does not need to refer to field X, which is reserved or absent.

[0132] When a device receives L1 R2D control information using a sequence corresponding to a broadcast, it receives subsequent R2D data corresponding to the L1 R2D control information. When a device receives L1 R2D control information using a sequence corresponding to a broadcast, it assumes that fields X and Y are reserved or absent. The device does not need to refer to fields X and Y that are reserved or absent.

[0133] <Proposal 1: Device Operation> If the device ID / group ID instructed (notified) by the reader matches the ID the device has, the device will keep receiving / decoding the subsequent R2D data corresponding to the instruction (notification). If the cast type instructed by the reader is broadcast, the device will keep receiving / decoding the subsequent R2D data corresponding to the instruction.

[0134] The following options 1 and 2 are provided for device behavior when the device ID / group ID indicated by the reader does not match the ID the device has and / or when the cast type indicated by the reader is not broadcast.

[0135] Proposal 1: Device Behavior: Option 1 The device stops receiving / monitoring / decoding R2D signals (eg, data) even within the time window / before the timer expires.

[0136] Proposal 1: Device Behavior: Option 2 The device keeps receiving / monitoring / decoding the R2D signal (eg, data) within the time window / until the timer expires.

[0137] The device may determine the options to apply based on the message type / format of the L1 R2D control information / R2D data, the preamble type, device type, topology, and device capabilities.

[0138] <Proposal 1: Summary> As described above, a device receives L1 R2D control information including information about unicast, multicast, and broadcast of R2D data, and determines whether to receive R2D data following the L1 R2D control information based on the L1 R2D control information. This allows the A-IoT communication system to communicate in an appropriate cast type.

[0139] <Proposal 2> Proposal 2 describes D2R scheduling. D2R scheduling and PDRCH scheduling may be used interchangeably.

[0140] In Proposal 2, the following Option 1 to Option 3 are provided for indicating device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling. Device-specific may be interpreted as device-based. Group-based may be interpreted as group-based. Cell-based may be interpreted as cell-based.

[0141] Option 1 to Option 3 will be explained below.

[0142] <Proposal 2: Option 1> In Option 1 of Proposal 2, a field in the L1 R2D control information is used to indicate device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling. Regarding the field in the L1 R2D control information, the following Option 1-1 to Option 1-3 are provided.

[0143] <Proposal 2: Option 1: Option 1-1> One field is used in the L1 R2D control information to indicate device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling. The field may indicate device ID / group ID / cell-based D2R scheduling. For example, the L1 R2D control information may have a codepoint field (codepoint field) and indicate "Codepoint" in Fig. 15. The codepoint may indicate device ID / group ID / cell-based scheduling, as shown in "Information" in Fig. 15.

[0144] For example, a device ID is mapped to the N code points indicated by an arrow A15a in Fig. 15. When these code points are indicated in the code point field, device-specific D2R scheduling is indicated.

[0145] For example, a group ID is mapped to M code points indicated by an arrow A15b in Fig. 15. When these code points are indicated in the code point field, group-based D2R scheduling is indicated.

[0146] For example, cell-based D2R scheduling is mapped to one code point indicated by an arrow A15c in Fig. 15. When this code point is indicated in the code point field, cell-based D2R scheduling is indicated.

[0147] The reader includes, for example, the code points shown in FIG. 15 in the code point field of the L1 R2D control information and transmits it.

[0148] The device transmits the PDRCH if the codepoint field indicates a device ID corresponding to the device, or indicates a group ID corresponding to the device, or indicates cell-based scheduling.

[0149] Each device may have one or more code points, and if the indicated code point is included, each device continues with subsequent operations corresponding to that L1 R2D control information (e.g., transmitting D2R data).

[0150] The reader recognizes whether the D2R scheduling is device-specific, group-based, or cell-based, and sets the code point accordingly. The device does not need to recognize whether the D2R scheduling is device-specific, group-based, or cell-based before transmitting D2R data. In other words, the device only needs to recognize whether the code point field includes an ID corresponding to the device and whether it indicates cell-based scheduling.

[0151] The relationship between the code points and the information (the information shown in FIG. 15) may be notified to the device by higher layer signaling such as L1 R2D control information or RRC.

[0152] <Proposal 2: Option 1: Option 1-2> To indicate device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling, one field X indicates the device-specific / group-based / cell-based R2D scheduling type, and another field Y indicates the device ID / group ID. For example, as shown in Figure 16, field X indicates the R2D scheduling type, and field Y indicates the device ID / group ID.

[0153] For example, if field X in FIG. 16 indicates device specificity, field Y is mapped to the device ID.

[0154] For example, if field X in FIG. 16 indicates a group base, field Y is mapped to a group ID.

[0155] For example, if field X in FIG. 16 indicates cell-based, field Y is reserved or absent.

[0156] The reader includes the R2D scheduling type in field X of the L1 R2D control information, and includes the device ID / group ID in field Y of the L1 R2D control information, and transmits the information.

[0157] The device transmits a PDRCH if field X of the L1 R2D control information indicates device-specific / group-based R2D scheduling and field Y indicates a device ID / group ID corresponding to the device. The device transmits a PDRCH if field X of the L1 R2D control information indicates cell-based R2D scheduling.

[0158] The device assumes that field Y indicates device ID / group ID if field X of the L1 R2D control information indicates device-specific / group-based R2D scheduling. The device assumes that field Y is reserved or absent if field X of the L1 R2D control information indicates cell-based R2D scheduling. The device may not refer to field Y being reserved or absent if field X of the L1 R2D control information indicates cell-based R2D scheduling.

[0159] <Proposal 2: Option 1: Options 1-3> To indicate device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling, one field X indicates the device-specific / group-based / cell-based R2D scheduling type, another field Y indicates the device ID, and another field Z indicates the group ID. For example, as shown in Figure 17, field X indicates the R2D scheduling type, field Y indicates the device ID, and field Z indicates the group ID.

[0160] For example, if field X in Figure 17 indicates device specificity, then field Y is mapped to the device ID, and field Z is reserved or absent.

[0161] For example, if field X in Figure 17 indicates a group base, then field Z is mapped to a group ID, and field Y is reserved or absent.

[0162] For example, if field X in FIG. 17 indicates cell base, fields Y and Z are reserved or absent.

[0163] The reader includes the R2D scheduling type in field X of the L1 R2D control information, includes the device ID in field Y of the L1 R2D control information, and includes the group ID in field Z of the L1 R2D control information, and then transmits the information.

[0164] The device transmits a PDRCH if field X of the L1 R2D control information indicates device-specific / group-based R2D scheduling and field Y indicates a device ID corresponding to the device / field Z indicates a group ID corresponding to the device. The device transmits a PDRCH if field X of the L1 R2D control information indicates cell-based R2D scheduling.

[0165] If field X of the L1 R2D control information indicates device-specific R2D scheduling, the device assumes that field Y indicates the device ID and field Z is reserved or absent. If field X of the L1 R2D control information indicates device-specific R2D scheduling, the device may refer to field Y and not refer to field Z, which is reserved or absent.

[0166] If field X of the L1 R2D control information indicates group-based R2D scheduling, the device assumes that field Z indicates a group ID and that field Y is reserved or absent. If field X of the L1 R2D control information indicates group-based R2D scheduling, the device may refer to field Z and not refer to field Y, which may be reserved or absent.

[0167] The device assumes that fields Y and Z are reserved or absent if field X of the L1 R2D control information indicates cell-based R2D scheduling. The device may not refer to fields Y and Z being reserved or absent if field X of the L1 R2D control information indicates cell-based R2D scheduling.

[0168] <Proposal 2: Option 2> In Option 2 of Proposal 2, a scrambling sequence is used to indicate device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling.

[0169] A different scrambling sequence is used for each device to instruct device-specific D2R scheduling. For example, as shown in Fig. 18, sequence #a is used to instruct device #a to instruct device-specific D2R scheduling. Sequence #b is used to instruct device #b to instruct device-specific D2R scheduling. Sequence #c is used to instruct device #c to instruct device-specific D2R scheduling.

[0170] A different scrambling sequence is used for each group of devices to indicate group-based D2R scheduling. For example, as shown in Fig. 19, sequence #d is used to indicate group-based D2R scheduling for device group #d. Sequence #e is used to indicate group-based D2R scheduling for device group #e. Sequence #f is used to indicate group-based D2R scheduling for device group #f.

[0171] One scrambling sequence is used to indicate cell-based D2R scheduling, for example, sequence #g is used to indicate cell-based D2R scheduling to all devices, as shown in Figure 20.

[0172] The reader scrambles the L1 R2D control information, for example, for device-specific R2D scheduling to devices #a / #b / #c, using the sequence shown in Figure 18. The reader scrambles the L1 R2D control information, for example, for group-based R2D scheduling to group devices #d / #e / #f, using the sequence shown in Figure 19. The reader scrambles the L1 R2D control information, for example, for cell-based R2D scheduling, using the sequence shown in Figure 20.

[0173] The device receives the L1 R2D control information using a sequence corresponding to the device specific (device ID), a sequence corresponding to the group base (group ID), and a sequence corresponding to the cell base. For example, the device descrambles the L1 R2D control information using the sequence corresponding to the device specific, the sequence corresponding to the group base, and the sequence corresponding to the cell base.

[0174] When a device receives L1 R2D control information using a device-specific sequence / group-based sequence / cell-based sequence, the device transmits a PDRCH.

[0175] In option 2 of Proposal 2, the R2D scheduling type / device ID / group ID does not need to be explicitly notified in the L1 R2D control information.

[0176] The device-specific corresponding sequence, the group-based corresponding sequence, and the cell-based corresponding sequence may be notified to the device by higher layer signaling such as L1 R2D control information or RRC.

[0177] <Proposal 2: Option 3> In Option 3 of Proposal 2, a field in the L1 R2D control information and a scrambling sequence are used to indicate device-specific / group-based / cell-based D2R scheduling for PDRCH scheduling.

[0178] For example, different scrambling sequences are used to indicate device-specific / group-based / cell-based D2R scheduling. For example, the same sequence #a is used for all devices to indicate device-specific D2R scheduling. For example, the same sequence #b is used for all groups to indicate group-based D2R scheduling. For example, sequence #c is used to indicate cell-based D2R scheduling. The device receives L1 R2D control information using the sequence corresponding to device-specific / group-based / cell-based.

[0179] The device ID / group ID is indicated in the L1 R2D control information. Regarding the indication of the device ID / group ID in the L1 R2D control information, the following options 3-1 and 3-2 are provided.

[0180] <Proposal 2: Option 3: Option 3-1> The L1 R2D control information has a field X. The field X indicates the device ID / group ID.

[0181] For example, when a device receives L1 R2D control information using a sequence (for example, sequence #a) corresponding to device-specific D2R scheduling, the device ID is mapped to field X of the L1 R2D control information.

[0182] For example, when a device receives L1 R2D control information using a sequence corresponding to group-based D2R scheduling (for example, sequence #b), a group ID is mapped to field X of the L1 R2D control information.

[0183] For example, if the device receives L1 R2D control information using a sequence corresponding to cell-based D2R scheduling (eg, sequence #c), field X is reserved or absent.

[0184] The reader includes the device ID / group ID in field X of the L1 R2D control information based on the R2D scheduling type. For example, the reader includes the device ID in field X for device-specific R2D scheduling. For example, the reader includes the group ID in field X for group-based R2D scheduling. For example, the reader reserves or absents field X for cell-based R2D scheduling.

[0185] The reader scrambles the L1 R2D control information with field X set based on the R2D scheduling type. For example, the reader scrambles the L1 R2D control information with sequence #a if it is device-specific, or with sequence #b if it is group-based, or with sequence #c if it is cell-based.

[0186] When a device receives L1 R2D control information using a sequence unique to the device, the device assumes that a device ID is mapped to field X. If a device ID corresponding to the device is mapped to field X, the device transmits a PDRCH.

[0187] When a device receives L1 R2D control information using a sequence corresponding to the group base, the device assumes that a group ID is mapped to field X. If a group ID corresponding to the device is mapped to field X, the device transmits a PDRCH.

[0188] When the device receives the L1 R2D control information using a sequence corresponding to the cell base, the device transmits a PDRCH. When the device receives the L1 R2D control information using a sequence corresponding to the cell base, the device assumes that the field X is reserved or absent. The device does not need to refer to the field X being reserved or absent.

[0189] <Proposal 2: Option 3: Option 3-2> The L1 R2D control information has fields X and Y. Field X indicates a device ID, and field Y indicates a group ID.

[0190] For example, when a device receives L1 R2D control information using a sequence (e.g., sequence #a) corresponding to device-specific D2R scheduling, field X of the L1 R2D control information is mapped to a device ID, and field Y is reserved or absent.

[0191] For example, when a device receives L1 R2D control information using a sequence corresponding to group-based D2R scheduling (e.g., sequence #b), a group ID is mapped to field Y of the L1 R2D control information, and field X is reserved or absent.

[0192] For example, if the device receives L1 R2D control information using a sequence corresponding to cell-based D2R scheduling (e.g., sequence #c), fields X and Y are reserved or absent.

[0193] The reader includes a device ID in field X and a group ID in field Y of the L1 R2D control information based on the R2D scheduling type. For example, for device-specific R2D scheduling, the reader includes a device ID in field X and reserves or leaves field Y unassigned. For example, for group-based R2D scheduling, the reader includes a group ID in field Y and reserves or leaves field X unassigned. For example, for cell-based R2D scheduling, the reader reserves or leaves fields X and Y unassigned.

[0194] The reader scrambles the L1 R2D control information with fields X and Y set based on the R2D scheduling type. For example, the reader scrambles the L1 R2D control information using sequence #a if it is device-specific. For example, the reader scrambles the L1 R2D control information using sequence #b if it is group-based. For example, the reader scrambles the L1 R2D control information using sequence #c if it is cell-based.

[0195] When a device receives L1 R2D control information using a sequence unique to the device, the device assumes that a device ID is mapped to field X and that field Y is reserved or absent. The device transmits a PDRCH if a device ID corresponding to the device is mapped to field X. The device does not need to refer to field Y, which is reserved or absent.

[0196] When a device receives L1 R2D control information using a sequence corresponding to a group base, the device assumes that a group ID is mapped to field Y and that field X is reserved or absent. The device transmits a PDRCH if a group ID corresponding to the device is mapped to field Y. The device does not need to refer to field X, which is reserved or absent.

[0197] When a device receives L1 R2D control information using a sequence corresponding to a cell base, the device transmits a PDRCH. When a device receives L1 R2D control information using a sequence corresponding to a cell base, the device assumes that fields X and Y are reserved or absent. The device does not need to refer to fields X and Y that are reserved or absent.

[0198] <Proposal 2: Summary> As described above, a device receives L1 R2D control information including information on device-specific transmission, group-based transmission, and cell-based transmission of PDRCH, and determines PDRCH transmission based on the L1 R2D control information. This enables the A-IoT communication system to communicate in an appropriate cast type.

[0199] <Reader> Fig. 21 is a block diagram showing an example of the configuration of a reader 10a according to an embodiment. The reader 10a includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The reader 10a communicates with the device 20 (see Fig. 22) wirelessly. The reader 10a may be an intermediate terminal or a terminal (for example, a SL terminal that communicates with the device 20).

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

[0201] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). 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 Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0202] 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 reader 10a transmits control information to the device 20 using the PDCCH and transmits downlink data signals using the PDSCH.

[0203] The reference signal included in the DL signal may include at least one of a demodulation reference signal (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 DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

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

[0205] The control unit 103 controls the communication operations of the reader 10 a, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102 .

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

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

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

[0209] Here, the control unit 103 may determine transmission of downlink control information including information regarding unicast, multicast, and broadcast of the downlink signal. The downlink signal may be R2D data. The downlink control information may be L1 R2D control information. The transmitting unit 101 may transmit the downlink control information.

[0210] The control unit 103 may include the code points described in Proposal 1 in the downlink control information. The control unit 103 may include the fields X, Y, and Z described in Proposal 1 in the downlink control information.

[0211] The control unit 103 may scramble the downlink control information based on the cast type.

[0212] Here, the control unit 103 may determine transmission of downlink control information including information regarding device-specific transmission, group-based transmission, and cell-based transmission of uplink signals. The uplink signals may be PDRCH or D2R data. Device-specific may be interpreted as device-individual or device-dedicated.

[0213] The control unit 103 may include the code points described in Proposal 2 in the downlink control information. The control unit 103 may include the fields X, Y, and Z described in Proposal 2 in the downlink control information.

[0214] The control unit 103 may scramble the downlink control information based on the D2R scheduling type, which may be scheduling of device-specific transmission, group-based transmission, or cell-based transmission of the uplink signal.

[0215] <Device Configuration> Fig. 22 is a block diagram showing an example of the configuration of a device 20 according to an embodiment. The device 20 is a device with lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, for example, an A-IoT UE. The device 20 may be considered as a device that receives power through energy harvesting. For example, the device 20 may be considered as a device that receives power through CW supplied from the base station 10 or the reader 10a.

[0216] The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with, for example, the base station 10 wirelessly. The device 20 may be, for example, an A-IoT device.

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

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

[0219] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capabilities of the device 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

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

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

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

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

[0224] 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, 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 in the resources of the PUCCH.

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

[0226] 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 Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0227] Here, the receiving unit 201 may receive downlink control information including information regarding unicast, multicast, and broadcast of the downlink signal. The downlink signal may be PRDCH or R2D data. The downlink control information may be L1 R2D control information. The control unit 203 may determine reception of the downlink signal based on the downlink control information.

[0228] The downlink control information may include the code point described in Proposal 1. The control unit 203 may determine to receive a downlink signal when the code point included in the downlink control information indicates an identifier of the device 20, indicates an identifier of a group to which the device 20 belongs, or indicates a broadcast.

[0229] The downlink control information may include the fields described in Proposal 1. The control unit 203 may determine to receive a downlink signal when the first field of the downlink control information indicates unicast and the second field indicates an identifier of the device 20, when the first field of the downlink control information indicates multicast and the second field indicates an identifier of a group to which the device 20 belongs, or when the first field of the downlink control information indicates broadcast. The first field may be Field X described in Proposal 1. The second field may be Field Y described in Proposal 1.

[0230] The downlink control information may be scrambled with a sequence based on the cast type. The control unit 203 may determine whether to receive a downlink signal based on the sequence with which the downlink control information is scrambled.

[0231] Here, the receiving unit 201 may receive downlink control information including information on device-specific transmission, group-based transmission, and cell-based transmission of uplink signals. The control unit 203 may determine transmission of uplink signals based on the downlink control information. The uplink signals may be PDRCH or D2R data. The term "device-specific" may be interpreted as being device-specific.

[0232] The downlink control information may include the code point described in Proposal 2. The control unit 203 may determine to transmit an uplink signal when the code point included in the downlink control information indicates an identifier of the device 20, indicates an identifier of a group to which the device 20 belongs, or indicates cell-based transmission.

[0233] The downlink control information may include the fields described in Proposal 2. The control unit 203 may determine to transmit an uplink signal when the first field of the downlink control information indicates apparatus-specific transmission of an uplink signal and the second field indicates an identifier of the device 20, when the first field of the downlink control information indicates group-based transmission of an uplink signal and the second field indicates an identifier of the group to which the device 20 belongs, or when the first field of the downlink control information indicates cell-based transmission.

[0234] The downlink control information may be scrambled based on a D2R scheduling type. The control unit 203 may determine the D2R scheduling type based on the sequence with which the downlink control information is scrambled. The D2R scheduling type may be scheduling for device-specific transmission, group-based transmission, and cell-based transmission of uplink signals.

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

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

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

[0238] For example, a base station, a reader, 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. 23 is a diagram showing an example of the hardware configuration of a reader and a device according to this embodiment. The above-described reader 10a 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.

[0239] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the reader 10a and the device 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

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

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

[0242] 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 these 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 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 made 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.

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

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

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

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

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

[0248] The reader 10a and the device 20 may also 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0270] <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 a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0271] 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 reader 10a described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0272] Similarly, the terminal in the present disclosure may be interpreted as a base station, in which case the reader 10a may be configured to have the functions of the device 20 described above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A communication device that receives power from energy harvesting, comprising: a receiving unit that receives downlink control information including information regarding unicast, multicast, and broadcast downlink signals; and a control unit that determines reception of the downlink signals based on the downlink control information.

2. The communication device according to claim 1, wherein the control unit determines to receive the downlink signal when the code point included in the downlink control information indicates an identifier of the communication device, indicates an identifier of a group to which the communication device belongs, or indicates the broadcast.

3. The communication device described in claim 1, wherein the control unit determines to receive the downlink signal when the first field of the downlink control information indicates unicast and the second field indicates an identifier of the communication device, when the first field indicates multicast and the second field indicates an identifier of a group to which the communication device belongs, or when the first field indicates broadcast.

4. A communications device powered by energy harvesting, comprising: a receiver that receives downlink control information including information regarding device-specific transmission, group-based transmission, and cell-based transmission of uplink signals; and a controller that determines transmission of the uplink signals based on the downlink control information.

5. The communication device described in claim 4, wherein the control unit determines to transmit the uplink signal when a code point included in the downlink control information indicates an identifier of the communication device, indicates an identifier of a group to which the communication device belongs, or indicates cell-based transmission.

6. The communication device described in claim 4, wherein the control unit determines to transmit the uplink signal when the first field of the downlink control information indicates device-specific transmission of the uplink signal and the second field indicates an identifier of the communication device, when the first field indicates group-based transmission of the uplink signal and the second field indicates an identifier of the group to which the communication device belongs, or when the first field indicates cell-based transmission.

Images