Device, wireless communication device, and wireless communication method

Abstract

This device comprises: a reception unit that receives a first signal including first control information; and a control unit that uses a specific condition as a basis to determine information indicated by at least one field included in the first control information.

Description

Device, wireless communication apparatus, and wireless communication method

[0001] The present disclosure relates to a device, a wireless communication apparatus, and a wireless communication method.

[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, it is expected that devices will receive control information and operate based on that control information, but there has been insufficient consideration of the structure of the control information received by devices, and further consideration is required.

[0006] One aspect of the present disclosure is to provide a device, a wireless communication apparatus, and a wireless communication method that can appropriately configure control information received by the device in an ambient IoT.

[0007] A device according to one aspect of the present disclosure includes a receiving unit that receives a first signal including first control information, and a control unit that determines, based on specific conditions, information indicated by at least one field included in the first control information.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure; FIG. 2 is a diagram illustrating topology 1; FIG. 3 is a diagram illustrating topology 2; FIG. 4 is a diagram illustrating topology 3 in DL support; FIG. 5 is a diagram illustrating topology 4; FIG. 6 is a diagram illustrating backscatter transmission; and FIG. 7 is a diagram illustrating L1 R2D control information to be discussed. A block diagram illustrating an example of the configuration of a base station according to an embodiment; A block diagram illustrating an example of the configuration of a device according to an embodiment; A diagram illustrating an example of the hardware configuration of a base station and a device according to the present embodiment; A diagram showing an example of the configuration of a vehicle.

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

[0010] In 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.

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

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

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

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

[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the device 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols. The frequency domain may be defined by the number of subcarriers or the number of resource blocks.

[0016] The base station 10 transmits DL signals such as control information, setting information, and data 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).

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

[0018] As will be described later, the wireless communication system may include 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 " / ".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE 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.

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

[0040] The ambient IoT device backscatters and modulates the RF signals received from the base station, 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.

[0041] FIG. 7 is a diagram illustrating backscatter transmission. FIG. 7 shows an example in which an ambient IoT device performs ON-OFF keying and transmits information. The dashed line area 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] <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)

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

[0065] <Considerations> L1 R2D control information including information such as that illustrated in FIG. 8 is transmitted from the reader to the A-IoT device via the PRDCH. This L1 R2D control information is expected to include one or more fields. For example, a certain field X has a specific size (e.g., the number of bits), is associated with specific information, and is used to notify one of candidate values ​​that can be taken as the specific information. For example, each field has a mapping between candidate values ​​that can be taken as the specific information and a code point, and the code point is set based on the mapping. This mapping may mean the "interpretation" of field X, as it indicates what value the code point of field X is to be interpreted as.

[0066] The reader, which is the sender of the L1 R2D control information, sets this field X to a code point (also called a bit pattern) that is mapped to one of the candidate values. Then, the A-IoT device, which is the sender of the L1 R2D control information, references the code point set in field X and determines a value to be associated with the code point from one of the candidate values.

[0067] For example, if the L1 R2D control information includes a field X, the field X has a size of 2 bits, the field X is associated with a coding rate, and the candidate values ​​A, B, C, and D that can be taken as the coding rate are mapped to 2-bit code points (i.e., four code points), the reader sets the 2-bit code point based on the mapping to notify one of the candidate values ​​A, B, C, and D. The A-IoT device refers to the code point set in the field X and determines the value associated with the code point from the candidate values ​​A, B, C, and D based on the mapping.

[0068] In this way, control information is notified by transmitting and receiving L1 R2D control information including fields, but the configuration of this L1 R2D control information is open to further study. For example, it is open to study what fields the L1 R2D control information includes and what size each field has. It is also open to study what kind of mapping between code points and candidate values ​​is used in each field, and what the candidate values ​​are.

[0069] For example, if the fields included in the L1 R2D control information are inappropriate, the L1 R2D control information will have too many fields, increasing the overhead of the L1 R2D control information.In addition, in this case, the fields will be insufficient, making it impossible to properly transmit information (e.g., values) to be notified.

[0070] For example, if the size of a field included in the L1 R2D control information is inappropriate, the overall size (e.g., number of bits) of the L1 R2D control information becomes excessive, increasing the overhead of the L1 R2D control information. In this case, the field size becomes insufficient, resulting in an insufficient number of code points, making it impossible to properly transmit the information (e.g., value) to be notified.

[0071] For example, if the mapping between code points and candidate values ​​for fields included in the L1 R2D control information is not appropriate, a common mapping may not be applied between the sender and receiver of the L1 R2D control information, which may result in discrepancies in the information notified.

[0072] For example, if a candidate value for a field included in the L1 R2D control information is inappropriate and there are insufficient candidate values, it may become impossible to select a value to be notified by the field. If a candidate value for a field included in the L1 R2D control information is inappropriate and there are too many candidate values, the number of mapped code points increases, the overall size (e.g., number of bits) of the L1 R2D control information becomes excessive, and the overhead of the L1 R2D control information increases.

[0073] Therefore, in this embodiment, Proposal 1 describes the configuration of the L1 R2D control information. Proposal 1-1 describes a method for defining / determining whether or not a field exists in the L1 R2D control information. Proposal 1-2 describes a method for defining / determining whether or not a field has a size in the L1 R2D control information. Proposal 1-3 describes a method for defining / determining the interpretation of a field in the L1 R2D control information. Proposal 1-4 describes a method for defining / determining candidate values ​​corresponding to fields in the L1 R2D control information.

[0074] In this embodiment, variations in handling of fields of L1 R2D control information in Proposal 2 will be described.

[0075] Note that the fields included in the L1 R2D control information may be referred to as "L1 R2D control information fields," "R2D control information fields," and "control information fields."

[0076] As mentioned above, "R2D" means a link from a reader to a device, and "D2R" means a link from a device to a reader. The reader corresponds to a BS or an intermediate UE, and the device corresponds to an A-IoT device.

[0077] In this embodiment, D2R transmission may be replaced by a signal transmitted in a D2R link, by an A-IoT device transmitting a signal in the D2R link, or by a reader receiving a signal in the D2R link. Furthermore, D2R transmission may be replaced by a PDRCH transmission. Furthermore, R2D transmission may be replaced by a signal transmitted in an R2D link, by an A-IoT device receiving a signal in the R2D link, or by a reader transmitting a signal in the R2D link. Furthermore, R2D transmission may be replaced by a PRDCH transmission.

[0078] R2D reception may correspond to the device receiving a signal / channel / information transmitted by a reader. Alternatively, R2D reception may correspond to a signal / channel / information transmitted by a reader and received by a device. Note that the reader transmitting a signal / channel / information to a device, or the transmitted signal / channel / information, may be referred to as "R2D transmission."

[0079] D2R transmission may correspond to a device transmitting a signal / channel / information to a reader. Alternatively, D2R transmission may correspond to a signal / channel / information transmitted by a device and received by a reader. Note that a reader receiving a signal / channel / information from a device, or the received signal / channel / information, may be referred to as "D2R reception."

[0080] In the following, notifications / indications may be carried in the physical (PHY) layer / Medium Access Control (MAC) layer / Radio Resource Control (RRC) layer / a new layer defined for A-IoT.

[0081] <Proposal 1> Proposal 1 describes the configuration of L1 R2D control information received on the PRDCH.

[0082] <Proposal 1-1> Proposal 1-1 describes how the presence of each L1 R2D control information field in the L1 R2D control information received on the PRDCH is defined and / or determined. In the following, nine options are shown by way of example.

[0083] Here, defining / determining the existence of a certain L1 R2D control information field X may be replaced with any of defining / determining whether or not the L1 R2D control information field X exists, defining / determining whether or not the L1 R2D control information field X is included in the L1 R2D control information, defining / determining whether or not the L1 R2D control information field X can be transmitted, defining / determining whether or not the L1 R2D control information field X can be received, defining / determining whether or not the L1 R2D control information field X can be set, or defining / determining whether or not transmission / reception of the L1 R2D control information field X is expected.

[0084] <Option 1 of Proposal 1-1> In Option 1, the presence of each L1 R2D control information field is defined in the specification and / or system. For example, the specification / system defines that R2D control information field X is always present.

[0085] In option 1, the reader transmits L1 R2D control information including an L1 R2D control information field defined as being present by the specification / system. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field defined as being present by the specification / system. The reception control here may include conversion from the code point of the L1 R2D control information field to information.

[0086] <Option 2 of Proposal 1-1> In Option 2, the presence of each L1 R2D control information field is defined for each type of A-IoT device.

[0087] For example, if the A-IoT device is of a certain type, the R2D control information field X is always present. In other words, in this case, the R2D control information field X may always be included in the L1 R2D control information transmitted to an A-IoT device of a certain type. Also, in this case, the R2D control information field X may not always be included in the L1 R2D control information transmitted to an A-IoT device of a type different from the certain type.

[0088] For example, when an A-IoT device is of a certain type, the R2D control information field X is never present. In other words, in this case, the R2D control information field X may not always be included in the L1 R2D control information transmitted to an A-IoT device of a certain type. Also, in this case, the R2D control information field X may always be included in the L1 R2D control information transmitted to an A-IoT device of a type different from the certain type.

[0089] In option 2, the reader transmits L1 R2D control information including an L1 R2D control information field defined to exist depending on the type of the A-IoT device. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field defined to exist depending on the type of the A-IoT device. The reception control here may include conversion from a code point in the L1 R2D control information field to information.

[0090] <Option 3 of Proposal 1-1> In Option 3, the presence of each L1 R2D control information field depends on the capability of the A-IoT device.

[0091] For example, if an A-IoT device supports a capability related to the R2D control information field X, the R2D control information field X is present. In other words, in this case, the R2D control information field X may be included in the L1 R2D control information transmitted to an A-IoT device that supports the capability related to the R2D control information field X. And, if the A-IoT device does not support the capability related to the R2D control information field X, the R2D control information field X is not present. In other words, in this case, the R2D control information field X may not be included in the L1 R2D control information transmitted to an A-IoT device that does not support the capability related to the R2D control information field X.

[0092] In option 3, the reader transmits L1 R2D control information including an L1 R2D control information field determined to be present based on the capability of the A-IoT device. The A-IoT device performs reception control assuming that the received L1 R2D control information includes the L1 R2D control information field determined to be present based on the capability of the A-IoT device. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0093] <Option 4 of Proposal 1-1> In option 4, the presence of each L1 R2D control information field may be determined based on R2D control information of higher layers.

[0094] For example, when upper layer parameter Y is provided, it is determined that L1 R2D control information field X is present. In other words, L1 R2D control information transmitted to an A-IoT device provided with upper layer parameter Y may include R2D control information field X. In this case, L1 R2D control information transmitted to an A-IoT device not provided with upper layer parameter Y may not include R2D control information field X.

[0095] Also, for example, when the upper layer parameter Y is provided, it is determined that the L1 R2D control information field is not present. In other words, the L1 R2D control information transmitted to an A-IoT device provided with the upper layer parameter Y may not include the R2D control information field X. In this case, the L1 R2D control information transmitted to an A-IoT device not provided with the upper layer parameter Y may include the R2D control information field X.

[0096] In option 4, the reader transmits L1 R2D control information including an L1 R2D control information field determined to be present based on the R2D control information of the upper layer. The A-IoT device performs reception control assuming that the received L1 R2D control information includes the L1 R2D control information field determined to be present based on the R2D control information of the upper layer. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0097] <Option 5 of Proposal 1-1> In option 5, the presence of each L1 R2D control information field may be determined based on the scrambling ID of the PRDCH.

[0098] For example, if the PRDCH is scrambled with a scrambling ID of Y, it is determined that the L1 R2D control information field X is present. In other words, the PRDCH scrambled with a scrambling ID of Y may include the L1 R2D control information field X. Also, in this case, if the PRDCH is scrambled with a scrambling ID different from Y, the L1 R2D control information field X may not be present.

[0099] Also, for example, if the PRDCH is scrambled with a scrambling ID of Y, it is determined that the L1 R2D control information field X is not present. In other words, the PRDCH scrambled with a scrambling ID of Y may not include the L1 R2D control information field X. Also, in this example, if the PRDCH is scrambled with a scrambling ID different from Y, the L1 R2D control information field X may be present.

[0100] In option 5, the reader transmits, on the PRDCH, L1 R2D control information including an L1 R2D control information field determined to be present based on the scrambling ID of the PRDCH. Note that the transmitted PRDCH is scrambled with the scrambling ID. The A-IoT device performs reception control assuming that the received L1 R2D control information includes the L1 R2D control information field determined to be present based on the scrambling ID. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0101] <Option 6 of Proposal 1-1> In Option 6, the presence of each L1 R2D control information field may be indicated in another L1 R2D control information field. For example, the presence of L1 R2D control information field X may be indicated in L1 R2D control information field Y.

[0102] For example, if the L1 R2D control information field Y indicates a value of A, the L1 R2D control information field X is present. In other words, the L1 R2D control information including the L1 R2D control information field Y having a value of A includes the L1 R2D control information field X. Also, in this example, if the L1 R2D control information field Y indicates a value other than A, the L1 R2D control information field X may not be present. Alternatively, in this example, if the L1 R2D control information field Y is not present, the L1 R2D control information field X may not be present.

[0103] Also, for example, when the L1 R2D control information field Y indicates a value of A, the L1 R2D control information field X does not exist. In other words, the L1 R2D control information including the L1 R2D control information field Y having a value of A does not include the L1 R2D control information field X. Also, in this example, when the L1 R2D control information field Y indicates a value other than A, the L1 R2D control information field X may exist. Alternatively, in this example, when the L1 R2D control information field Y does not exist, the L1 R2D control information field X may exist.

[0104] In Option 6, the reader transmits L1 R2D control information including an L1 R2D control information field X determined to be present based on another L1 R2D control information field Y. Note that here, the L1 R2D control information field Y and the L1 R2D control information field X may be included in the same PRDCH or different PRDCHs, or may be included in the same L1 R2D control information or different L1 R2D control information. The A-IoT device performs reception control assuming that the received L1 R2D control information includes the L1 R2D control information field X determined to be present based on another L1 R2D control information field Y. Here, reception control may include conversion from a code point of the L1 R2D control information field to information.

[0105] <Option 7 of Proposal 1-1> In Option 7, the presence of each L1 R2D control information field may be based on the R2D cast type, where the R2D cast type includes unicast, where a signal is sent only to a specific A-IoT device, multicast, where a signal is sent to a group of specific A-IoT devices, and broadcast, where a signal is sent to unspecified A-IoT devices.

[0106] For example, in unicast, it is determined that the L1 R2D control information field X is present, and in multicast and / or broadcast, it is determined that the L1 R2D control information field X is not present.

[0107] Also, for example, in unicast, it is determined that the L1 R2D control information field X is not present, and in multicast and / or broadcast, it is determined that the L1 R2D control information field X is present.

[0108] The presence of each of the L1 R2D control information fields may be based on whether it is group / cell based R2D scheduling or device specific R2D scheduling.

[0109] For example, in device-specific R2D scheduling, it is determined that the L1 R2D control information field X is present, and in group / cell-based R2D scheduling, it is determined that the L1 R2D control information field X is not present.

[0110] In option 7, the reader transmits L1 R2D control information including an L1 R2D control information field determined to be present based on the cast type of the R2D. Note that the L1 R2D control information transmitted here is transmitted based on the cast type. The A-IoT device performs reception control assuming that the received L1 R2D control information includes the L1 R2D control information field determined to be present based on the cast type of the R2D. This reception control may include converting the code point of the L1 R2D control information field into information.

[0111] <Option 8 of Proposal 1-1> In option 8, the presence of each L1 R2D control information field may be based on the corresponding preamble / corresponding timing acquisition signal.

[0112] For example, if a preamble corresponding to a certain L1 R2D control information field X exists, it is determined that the L1 R2D control information field X exists. If a preamble corresponding to a certain L1 R2D control information field X does not exist, it is determined that the L1 R2D control information field X does not exist.

[0113] Also, for example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X exists, it is determined that the L1 R2D control information field X exists. For example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X does not exist, it is determined that the L1 R2D control information field X does not exist.

[0114] In option 8, the reader transmits L1 R2D control information including an L1 R2D control information field determined to be present based on the presence of a preamble / timing acquisition signal. Note that the PRDCH including the transmitted L1 R2D control information may be accompanied by a corresponding preamble / timing acquisition signal. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field determined to be present based on the presence of a received preamble / timing acquisition signal. The reception control here may include conversion of the codepoint of the L1 R2D control information field into information.

[0115] <Option 9 of Proposal 1-1> In Option 9, the presence of each L1 R2D control information field may be based on the type of message. For example, the type of message may be whether the message is an initial message or a subsequent message. The type of message may also be whether the message is important (high priority) or not (low priority).

[0116] The presence of the field may be determined by whether the message is the first message or a subsequent message in a session.

[0117] In option 9, the reader transmits L1 R2D control information including the L1 R2D control information field determined to be present based on the message type. The A-IoT device performs reception control assuming that the received L1 R2D control information includes the L1 R2D control information field determined to be present based on the message type. The reception control here may include conversion of the code point of the L1 R2D control information field to information.

[0118] A specific example of Proposal 1-1 will be described below.

[0119] The presence or absence of any of the following information fields is determined based on at least one of the options described above. Alternatively, the absence or absence of any of the following information fields is determined based on at least one of the options described above. Information on Time Domain Resource Allocation (TDRA) Information on Frequency Domain Resource Allocation (FDRA) Information on Code Domain Resource Allocation (CDRA) Information on chip duration Information on symbol duration Information on bit duration Information on how to map chips to bits Information on chip rate Information on symbol rate Information on bit rate Information on coding method Information on coding rate Information on modulation method Information on Forward Error Correction (FEC) Information on Cyclic Redundancy Check (CRC) Information on Transport Block Size (TBS) Information on repetition Information on midamble Information on cast type Information on device ID Information on device group ID D2R scheduling type Information on reader ID

[0120] In the case of broadcast, none of the above information may be present.

[0121] The L1 R2D control information field regarding the mapping method for mapping bits to chips for each bit is not present when one mapping method is determined, but may be present when a selection is made from multiple mapping methods.

[0122] For example, the L1 R2D control information field relating to a mapping method for mapping bits to chips for each bit exists in at least one of the following cases: - When PIE coding / Miller coding is supported by the capability of the A-IoT device - When PIE coding / Miller coding is indicated by higher layer control information (e.g., higher layer R2D control information) - When PIE coding / Miller coding is indicated by L1 control information (e.g., L1 R2D control information)

[0123] Furthermore, the L1 R2D control information field regarding the mapping method for mapping bits to chips for each bit is not present in at least one of the following cases: - When Manchester coding is supported by the capability of the A-IoT device - When Manchester coding is indicated by higher layer control information (e.g., higher layer R2D control information) - When Manchester coding is indicated by L1 control information (e.g., L1 R2D control information)

[0124] When mapping bits to chips for each bit, the L1 R2D control information field regarding the number of chips for each bit is not present if the number of chips for each bit is determined to be one, but may be present if a selection is made from multiple mapping methods.

[0125] The L1 R2D control information field regarding the number of chips in each bit is present in at least one of the following cases: - When PIE coding / Miller coding is supported by the capability of the A-IoT device - When PIE coding / Miller coding is indicated by higher layer control information (e.g., higher layer R2D control information) - When PIE coding / Miller coding is indicated by L1 control information (e.g., L1 R2D control information)

[0126] The L1 R2D control information field regarding the number of chips in each bit is absent in at least one of the following cases: - When Manchester coding is supported by the A-IoT device's capability - When Manchester coding is indicated by higher layer control information (e.g., higher layer R2D control information) - When Manchester coding is indicated by L1 control information (e.g., L1 R2D control information)

[0127] The L1 R2D control information field related to the midamble is absent when a midamble is not required, e.g., when synchronization can be achieved without a midamble, and is present when a midamble is required, e.g., when synchronization cannot be achieved without a midamble.

[0128] The L1 R2D control information field associated with the midamble is present in at least one of the following cases: - When PIE coding is supported by the A-IoT device's capability - When PIE coding is indicated by higher layer control information (e.g., higher layer R2D control information) - When PIE coding is indicated by L1 control information (e.g., L1 R2D control information)

[0129] The L1 R2D control information field associated with the midamble is not present in at least one of the following cases: - When Manchester coding is supported by the A-IoT device's capability - When Manchester coding is indicated by higher layer control information (e.g., higher layer R2D control information) - When Manchester coding is indicated by L1 control information (e.g., L1 R2D control information)

[0130] Note that whether or not an L1 R2D control information field associated with a midamble is present may be determined based on a time domain duration, and whether or not an L1 R2D control information field associated with a midamble is absent may be determined based on a time domain duration.

[0131] Note that "absent" may be replaced with "reserved." Note that "absent" for a certain field Z means that field Z is 0 bits. Note that "reserved" for a certain field Z means that field Z is 1 or more bits, but field Z is not used. Note that a "reserved" field Z may contain dummy information. Alternatively, a "reserved" field Z may contain information for a field different from field Z.

[0132] As described above, in Proposal 1-1, the presence of a field is defined / determined. This allows the field for transmitting the L1 R2D control information to be appropriately defined / determined, thereby preventing an excess of fields and reducing the overhead of the L1 R2D control information. This also prevents a shortage of fields, allowing the L1 R2D control information to be appropriately transmitted.

[0133] For example, in Proposal 1-1, the leader determines whether the L1 R2D control information includes a specific L1 R2D control information field based on a specific condition. Then, the leader transmits a PRDCH including the L1 R2D control information including the L1 R2D control information field that the leader determined to include. The A-IoT device receives the PRDCH including the L1 R2D control information. Then, the A-IoT device determines whether the L1 R2D control information includes a specific L1 R2D control information field based on a specific condition. Here, the specific condition may be a condition indicated in at least one of the above-mentioned options.

[0134] It should be noted that for each occurrence of an L1 R2D control information field in the L1 R2D control information received on the PRDCH, the presence of multiple sets of fields may be defined / determined, for example, the same options may apply to the multiple occurrences of the sets of fields, or the same conditions / rules / parameters may apply to the multiple occurrences of the sets of fields.

[0135] Note that different options may be applied to the presence of each L1 R2D control information field in the L1 R2D control information received on the PRDCH. For example, when three fields, field X, field Y, and field Z, can be included in the L1 R2D control information, option 1 may be applied to the presence of field X, option 2 may be applied to field Y, and option 3 may be applied to field Z. In cases where options are applied in this manner, for example, field X is always present according to specifications, field Y is present when the A-IoT device is of a specific type, and field Z is present when the A-IoT device supports the capability related to field Z.

[0136] <Proposal 1-2> Proposal 1-2 describes how the size of each L1 R2D control information field in the L1 R2D control information received on the PRDCH is defined and / or determined. Note that the field size may be replaced with the number of bits included in the field, the field length, the field bit length, etc. Nine options are shown below as examples.

[0137] <Option 1 of Proposal 1-2> In Option 1, the size of each L1 R2D control information field is defined in the specification and / or system. For example, the specification and / or system defines that the R2D control information field X is N bits (N is an integer equal to or greater than 1).

[0138] In option 1, the reader transmits L1 R2D control information including an L1 R2D control information field having a size defined by the specification / system. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size defined by the specification / system. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0139] <Option 2 of Proposal 1-2> In Option 2, the size of each L1 R2D control information field is defined for each type of A-IoT device. In Option 2, the size of a specific L1 R2D control information field X may be defined to be different for each type of A-IoT device. Note that Option 2 does not necessarily require the size of the L1 R2D control information field X to be different for each type of A-IoT device. In Option 2, the size of the L1 R2D control information field X may be the same for two or more types of A-IoT devices. In other words, in Option 2, the size of the control information field X may be defined independently for each type of A-IoT device. Alternatively, in Option 2, the size of the control information field X may be defined separately for each type of A-IoT device.

[0140] For example, if there are two types of A-IoT devices, Type 1 and Type 2, the R2D control information field X for Type 1 has a size of N bits (N is an integer equal to or greater than 1), and the R2D control information field X for Type 2 has a size of M bits (M is an integer equal to or greater than 1). Note that in this case, M may be different from N or may be the same as N.

[0141] In option 2, the reader transmits L1 R2D control information including an L1 R2D control information field having a size defined by the type of the A-IoT device. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size defined by the type of the A-IoT device. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0142] <Option 3 of Proposal 1-2> In Option 3, the size of each L1 R2D control information field depends on the capability of the A-IoT device. In Option 3, the size of a specific L1 R2D control information field X may vary depending on the capability of the A-IoT device. Note that Option 3 does not necessarily require the size of the L1 R2D control information field X to vary depending on the capability of the A-IoT device. In Option 3, the size of the L1 R2D control information field X may be the same between A-IoT devices with different capabilities. In other words, in Option 3, the size of the control information field X may be independent for each capability of the A-IoT device. Alternatively, in Option 3, the size of the control information field X may be differentiated for each capability of the A-IoT device.

[0143] For example, if the A-IoT device supports a capability related to the R2D control information field X, the size of the R2D control information field X is determined to be N bits. If the A-IoT device does not support a capability related to the R2D control information field X, the size of the R2D control information field X is determined to be M bits. In this case, M may be different from N or may be the same as N. Furthermore, N or M may be zero. A size of zero for a certain field X may correspond to the absence of the field X.

[0144] In option 3, the reader transmits L1 R2D control information including an L1 R2D control information field having a size determined by the capability of the A-IoT device. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size determined by the capability of the A-IoT device. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0145] <Option 4 of Proposal 1-2> In Option 4, the size of each L1 R2D control information field may be determined based on R2D control information of a higher layer. In Option 4, the size of a specific L1 R2D control information field X is determined to be a different size based on R2D control information of a higher layer. Note that Option 4 does not necessarily require the size of the L1 R2D control information field X to be different based on R2D control information of a higher layer. In Option 4, the size of the L1 R2D control information field X may be the same based on R2D control information of a higher layer. In other words, in Option 4, the size of the control information field X may be determined independently based on R2D control information of a higher layer. Alternatively, in Option 4, the size of the control information field X may be determined separately based on R2D control information of a higher layer.

[0146] For example, when a parameter A of the higher layer is specified, the size of the L1 R2D control information field X is determined to be N bits (N is an integer equal to or greater than 1). When a parameter B of the higher layer is specified, the size of the L1 R2D control information field X is determined to be M bits (M is an integer equal to or greater than 1). In this case, M may be different from N or may be the same as N.

[0147] In option 4, the reader transmits L1 R2D control information including an L1 R2D control information field having a size determined based on the R2D control information of the higher layer. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size determined based on the R2D control information of the higher layer. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0148] <Option 5 of Proposal 1-2> In Option 5, the size of each L1 R2D control information field may be determined based on the scrambling ID of the PRDCH. In Option 5, the size of a specific L1 R2D control information field X is determined to be a different size based on the scrambling ID of the PRDCH. Note that Option 5 does not necessarily require the size of the L1 R2D control information field X to be different based on the scrambling ID of the PRDCH. In Option 5, the size of the L1 R2D control information field X may be the same based on the scrambling ID of the PRDCH. In other words, in Option 5, the size of the control information field X may be determined independently based on the scrambling ID of the PRDCH. Alternatively, in Option 5, the size of the control information field X may be determined separately based on the scrambling ID of the PRDCH.

[0149] For example, if the PRDCH is scrambled with a scrambling ID of A, the size of the L1 R2D control information field X is determined to be N bits (N is an integer equal to or greater than 1). If the PRDCH is scrambled with a scrambling ID of B, the size of the L1 R2D control information field X is determined to be M bits (M is an integer equal to or greater than 1). Note that in this case, M may be different from N or may be the same as N.

[0150] In option 5, the reader transmits, on the PRDCH, L1 R2D control information including an L1 R2D control information field having a size determined based on a scrambling ID of the PRDCH. Note that the transmitted PRDCH is scrambled by the scrambling ID. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size determined based on the scrambling ID. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0151] <Option 6 of Proposal 1-2> In Option 6, the size of each L1 R2D control information field may be based on the indication of another L1 R2D control information field. In Option 6, the size of a specific L1 R2D control information field X is determined to be a different size based on the indication of another L1 R2D control information field. Note that Option 6 does not necessarily require the size of the L1 R2D control information field X to be different based on the indication of another L1 R2D control information field. In Option 6, the size of the L1 R2D control information field X may be the same based on the indication of another L1 R2D control information field. In other words, in Option 6, the size of the control information field X may be determined independently based on the indication of another L1 R2D control information field. Alternatively, in Option 6, the size of the control information field X may be determined separately based on the indication of another L1 R2D control information field.

[0152] For example, when the L1 R2D control information field Y indicates a value of A, the size of the L1 R2D control information field X is determined to be N bits. When the L1 R2D control information field Y indicates a value of B, the size of the L1 R2D control information field X is determined to be M bits. In this case, M may be different from N or may be the same as N.

[0153] In Option 6, the reader transmits L1 R2D control information including an L1 R2D control information field X having a size determined based on another L1 R2D control information field Y. Note that here, the L1 R2D control information field Y and the L1 R2D control information field X may be included in the same PRDCH or different PRDCHs, or may be included in the same L1 R2D control information or different L1 R2D control information. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field X having a size determined based on another L1 R2D control information field Y. Here, reception control may include conversion from a code point of the L1 R2D control information field to information.

[0154] <Option 7 of Proposal 1-2> In Option 7, the size of each L1 R2D control information field may be based on the cast type of the R2D. For example, in Option 7, the size of the L1 R2D control information field is different for different cast types of R2D. Note that Option 7 does not necessarily require the size of the L1 R2D control information field X to be different for different cast types of R2D. In Option 7, the size of the L1 R2D control information field X may be the same for different cast types of R2D. In other words, in Option 7, the size of the control information field X may be independent for each different cast type of R2D. Alternatively, in Option 7, the size of the control information field X may be differentiated for each different cast type of R2D.

[0155] For example, in unicast, the size of the L1 R2D control information field X is N bits, and in multicast and / or broadcast, the size of the L1 R2D control information field X is M bits, where M may be different from or equal to N.

[0156] The size of the L1 R2D control information field may be based on whether the R2D scheduling is group / cell-based or device-specific. For example, the size of the L1 R2D control information field may be different depending on whether the R2D scheduling is group / cell-based or device-specific.

[0157] In option 7, the reader transmits L1 R2D control information including an L1 R2D control information field having a size determined based on the cast type of the R2D. Note that the L1 R2D control information transmitted here is transmitted based on the cast type. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size determined based on the cast type of the R2D. This reception control may include conversion of the code point of the L1 R2D control information field into information.

[0158] <Option 8 of Proposal 1-2> In option 8, the size of each of the L1 R2D control information fields may be based on the corresponding preamble / corresponding timing acquisition signal.

[0159] For example, if a preamble corresponding to a certain L1 R2D control information field X exists, the size of the L1 R2D control information field X is determined to be N bits. If a preamble corresponding to the L1 R2D control information field X does not exist, the size of the L1 R2D control information field X is determined to be M bits. Note that in this case, M may be different from or the same as N.

[0160] Furthermore, for example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X exists, the size of the L1 R2D control information field X is determined to be N bits. For example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X does not exist, the size of the L1 R2D control information field X is determined to be M bits. Note that in this case, M may be different from N or may be the same as N.

[0161] In option 8, the reader transmits L1 R2D control information including an L1 R2D control information field having a size determined based on the presence of a preamble / timing acquisition signal. The PRDCH containing the transmitted L1 R2D control information may also be accompanied by a corresponding preamble / timing acquisition signal. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size determined based on the presence of the received preamble / timing acquisition signal. The reception control here may include converting the codepoint of the L1 R2D control information field into information.

[0162] <Option 9 of Proposal 1-2> In option 9, the size of each of the L1 R2D control information fields may be based on the type of message.

[0163] The size of the field may be determined depending on whether the message is the first message or a subsequent message in a session.

[0164] In option 9, the reader transmits L1 R2D control information including an L1 R2D control information field having a size determined based on the message type. The A-IoT device performs reception control assuming that the received L1 R2D control information includes an L1 R2D control information field having a size determined based on the message type. The reception control here may include conversion of the code point of the L1 R2D control information field to information.

[0165] Note that a single size of the field may be determined based on at least one of the above options, or a maximum value of the size of the field may be defined and / or determined, or a minimum value of the size of the field may be defined and / or determined, or minimum and maximum values ​​may be defined and / or determined, or the number and / or values ​​of possible field sizes may be defined and / or determined, based on at least one of the above options.

[0166] For example, if a maximum value for the size of field X is determined, the size of field X of the control information to be transmitted is equal to or less than the maximum value. The manner in which the size of field X of the control information to be transmitted is defined / determined as equal to or less than the maximum value may be based on, for example, at least one of the options described above. That is, the maximum value for the size of the field is defined / determined based on, for example, at least one of the options described above, and further, the manner in which the size of the field is defined / determined as equal to or less than the maximum value may be based on, for example, at least one of the options described above.

[0167] Alternatively, the size of the field may be fixed, and the size of the significant bits (number of significant bits) in the field may be defined / determined based on at least one of the options described above. For example, the size of the field may be fixed to X bits, and the size of the significant bits Y (Y is an integer greater than or equal to 1 and less than or equal to X) may be defined / determined based on at least one of the options described above.

[0168] Specific examples are described below.

[0169] The size of any of the fields of the following information is determined based on at least one of the options mentioned above: Information about TDRA Information about FDRA Information about CDRA Information about chip interval Information about symbol interval Information about bit interval Information about how chips are mapped to bits Information about chip rate Information about symbol rate Information about bit rate Information about coding method Information about coding rate Information about modulation method Information about FEC Information about CRC Information about TBS Information about repetition Information about midamble Information about cast type Information about device ID Information about device group ID D2R scheduling type Information about reader ID

[0170] The size of any of the fields in the following information may be determined based on a value indicating a range of possible values ​​(for example, the maximum and / or minimum value of the range of possible values). The size of any of the fields in the following information may also be determined based on multiple candidate values. TDRA FDRA CDRA Chip interval Symbol interval Bit interval Method of mapping chips to bits Chip rate Symbol rate Bit rate Coding method Coding rate Modulation method FEC method FEC coding rate CRC length TBS Number of repetitions Information related to midamble Cast type Device ID Device group ID D2R scheduling type Reader ID

[0171] The size of the FDRA information is determined based on the bandwidth of the R2D / D2R system.

[0172] In at least one of the following cases: when different coding schemes / different modulation schemes are supported by the capability of the A-IoT device, when different coding schemes / different modulation schemes are indicated by higher layer control information, and when different coding schemes / different modulation schemes are indicated by L1 control information, the size of any of the following may be different: A field for information about the chip interval A field for information about the symbol interval A field for information about the bit interval A field for information about how to map chips to bits A field for information about the chip rate A field for information about the symbol rate A field for information about the bit rate A field for information about the coding rate

[0173] The A-IoT device may receive L1 R2D control information having different sizes. The different size patterns may be specified by a specification, may depend on the capability of the A-IoT device, or may depend on the type of the A-IoT device. For example, there are three patterns of sizes for the L1 R2D control information: X bits, Y bits, and Z bits. The A-IoT device may receive L1 R2D control information having any of the sizes of the three patterns.

[0174] As described above, in Proposal 1-2, the size is defined / determined. This allows the size of the field for transmitting the L1 R2D control information to be appropriately defined / determined, thereby preventing the field size from becoming excessively large and reducing the overhead of the L1 R2D control information. Alternatively, this allows the field size to be prevented from becoming insufficient, thereby enabling the L1 R2D control information to be appropriately transmitted.

[0175] For example, in Proposal 1-2, the leader determines the size of a specific L1 R2D control information field included in the L1 R2D control information based on a specific condition. Then, the leader transmits a PRDCH including L1 R2D control information, which includes an L1 R2D control information field having the determined size. The A-IoT device receives the PRDCH including the L1 R2D control information. Then, the A-IoT device determines the size of a specific L1 R2D control information field included in the L1 R2D control information based on a specific condition. Here, the specific condition may be a condition indicated in at least one of the above-mentioned options.

[0176] Note that different options may be applied to the sizes of the L1 R2D control information fields in the L1 R2D control information received on the PRDCH. For example, when three fields, field X, field Y, and field Z, can be included in the L1 R2D control information, option 1 may be applied to the size of field X, option 2 may be applied to the size of field Y, and option 3 may be applied to the size of field Z. In such a case where three options are applied, for example, the size of field X is defined by specifications, the size of field Y is determined depending on the type of A-IoT device, and the size of field Z depends on the capability of the A-IoT device regarding field Z.

[0177] <Proposal 1-3> Proposal 1-3 explains how the interpretation of the L1 R2D control information field in the L1 R2D control information received on the PRDCH is defined and / or determined.

[0178] Here, interpretation means, for example, mapping between the code point of a field and the indicated value / information. For example, if information indicating one of four values, A, B, C, and D, is indicated by a field X having a size of 2 bits, interpretation means mapping between the four code points of field X, "00," "01," "10," and "11," and A, B, C, and D. Note that the code points are not limited to being indicated by bit patterns, and may be indicated by integers corresponding to the bit patterns.

[0179] Note that different interpretations mean different mappings. For example, different mappings for a certain field X means that the values / information mapped to at least one of the code points that field X can take are different from each other. For example, the mapping when the four code points "00", "01", "10", and "11" are mapped to A, B, C, and D, respectively, is different from the mapping when the four code points "00", "01", "10", and "11" are mapped to D, C, B, and A, respectively. Such cases of different mappings correspond to cases of different interpretations.

[0180] Also, for example, in the case where one of eight integer values ​​from "0" to "7" is indicated by a field X having a size of 2 bits, the following exemplary mappings are different from one another: - Mapping where four code points "00", "01", "10", and "11" are mapped to "0", "1", "2", and "3", respectively - Mapping where four code points "00", "01", "10", and "11" are mapped to "4", "5", "6", and "7", respectively - Mapping where four code points "00", "01", "10", and "11" are mapped to "2", "3", "4", and "5", respectively - Mapping where three code points "00", "01", and "10" are mapped to "0", "1", and "2", respectively, and no value is mapped to "11".

[0181] In the following description, interpretations α, β, etc. indicate mapping between the code point of a field and the indicated value / information. Also, in the following description, interpretations α and β may be the same interpretation or different interpretations. Also, in the following, nine options are shown as examples.

[0182] <Option 1 of Proposal 1-3> In Option 1, the interpretation of each L1 R2D control information field is defined in the specification and / or system. For example, the specification and / or system defines that the interpretation of R2D control information field X is a certain interpretation α (mapping α).

[0183] In option 1, the reader transmits L1 R2D control information including an L1 R2D control information field with a code point set based on a specification / system-defined interpretation. The A-IoT device controls reception of the L1 R2D control information field based on a specification / system-defined interpretation. The control of reception here may include conversion of the code point of the L1 R2D control information field to information.

[0184] <Option 2 of Proposal 1-3> In Option 2, the interpretation of each L1 R2D control information field is defined for each type of A-IoT device. In Option 2, the interpretation of a specific L1 R2D control information field X may be defined as a different interpretation for each type of A-IoT device. Note that Option 2 does not necessarily require the interpretation of the L1 R2D control information field X to be different for each type of A-IoT device. In Option 2, the interpretation of the L1 R2D control information field X may be the same for two or more types of A-IoT devices. In other words, in Option 2, the interpretation of the control information field X may be defined independently for each type of A-IoT device. Alternatively, in Option 2, the interpretation of the control information field X may be defined separately for each type of A-IoT device.

[0185] For example, if there are two types of A-IoT devices, type α and type β, the R2D control information field X for type α is interpreted as interpretation α (mapping α), and the R2D control information field X for type β is interpreted as interpretation β (mapping β). Note that in this case, the interpretation α may be different from the interpretation β or may be the same as the interpretation β.

[0186] In option 2, the reader transmits L1 R2D control information including an L1 R2D control information field with a code point set based on the interpretation depending on the type of the A-IoT device. The A-IoT device controls reception of the L1 R2D control information field based on the interpretation defined by the type of the A-IoT device. The control of reception here may include conversion from the code point of the L1 R2D control information field to information.

[0187] <Option 3 of Proposal 1-3> In Option 3, the interpretation of each L1 R2D control information field depends on the capability of the A-IoT device. In Option 3, the interpretation of a specific L1 R2D control information field X may differ depending on the capability of the A-IoT device. Note that Option 3 does not necessarily require the interpretation of the L1 R2D control information field X to differ depending on the capability of the A-IoT device. In Option 3, the interpretation of the L1 R2D control information field X may be the same between different capabilities of the A-IoT device. In other words, in Option 3, the interpretation of the control information field X may be independent for each capability of the A-IoT device. Alternatively, in Option 3, the interpretation of the control information field X may be differentiated for each capability of the A-IoT device.

[0188] For example, if the A-IoT device supports a capability related to the R2D control information field X, the interpretation of the R2D control information field X is determined to be interpretation α. ​​If the A-IoT device does not support a capability related to the R2D control information field X, the interpretation of the R2D control information field X is determined to be interpretation β.

[0189] In option 3, the reader transmits L1 R2D control information including an L1 R2D control information field in which a code point is set based on an interpretation determined by the capability of the A-IoT device. The A-IoT device controls reception of the L1 R2D control information field based on the interpretation determined by the capability of the A-IoT device. The control of reception here may include conversion from the code point of the L1 R2D control information field to information.

[0190] <Option 4 of Proposal 1-3> In Option 4, the interpretation of each L1 R2D control information field may be determined based on R2D control information of a higher layer. In Option 4, the interpretation of a specific L1 R2D control information field X is determined to be a different interpretation based on R2D control information of a higher layer. Note that Option 4 does not necessarily require the interpretation of L1 R2D control information field X to be different based on R2D control information of a higher layer. In Option 4, the interpretation of L1 R2D control information field X may be the same based on R2D control information of a higher layer. In other words, in Option 4, the interpretation of control information field X may be determined independently based on R2D control information of a higher layer. Alternatively, in Option 4, the interpretation of control information field X may be determined separately based on R2D control information of a higher layer.

[0191] For example, when a parameter A of the higher layer is indicated, the interpretation of the L1 R2D control information field X is determined to be interpretation α, and when a parameter B of the higher layer is indicated, the interpretation of the L1 R2D control information field X is determined to be interpretation β.

[0192] In option 4, the reader transmits L1 R2D control information including an L1 R2D control information field in which a code point is set based on an interpretation determined based on the R2D control information of the higher layer. The A-IoT device controls reception of the L1 R2D control information field based on the interpretation determined based on the R2D control information of the higher layer. The control of reception here may include conversion from the code point of the L1 R2D control information field to information.

[0193] <Option 5 of Proposals 1-3> In Option 5, the interpretation of each L1 R2D control information field may be determined based on the scrambling ID of the PRDCH. In Option 5, the interpretation of a specific L1 R2D control information field X is determined to be different based on the scrambling ID of the PRDCH. Note that Option 5 does not necessarily require the interpretation of the L1 R2D control information field X to be different based on the scrambling ID of the PRDCH. In Option 5, the interpretation of the L1 R2D control information field X may be the same based on the scrambling ID of the PRDCH. In other words, in Option 5, the interpretation of the control information field X may be determined independently based on the scrambling ID of the PRDCH. Alternatively, in Option 5, the interpretation of the control information field X may be determined differently based on the scrambling ID of the PRDCH.

[0194] For example, if the PRDCH is scrambled with a scrambling ID of A, the interpretation of the L1 R2D control information field X is determined to be interpretation α. ​​If the PRDCH is scrambled with a scrambling ID of B, the interpretation of the L1 R2D control information field X is determined to be interpretation β.

[0195] In option 5, the reader transmits, on the PRDCH, L1 R2D control information including an L1 R2D control information field whose code point is set based on an interpretation based on a scrambling ID of the PRDCH. Note that the transmitted PRDCH is scrambled by the scrambling ID. The A-IoT device controls reception of the L1 R2D control information field based on the interpretation determined based on the scrambling ID. This reception control may include conversion of the code point of the L1 R2D control information field into information.

[0196] <Option 6 of Proposals 1-3> In Option 6, the interpretation of each L1 R2D control information field may be based on the indication of another L1 R2D control information field. In Option 6, the interpretation of a specific L1 R2D control information field X is determined to be a different interpretation based on the indication of another L1 R2D control information field Y. Note that Option 6 does not necessarily require the interpretation of L1 R2D control information field X to be different based on the indication of another L1 R2D control information field. In Option 6, the interpretation of L1 R2D control information field X may be the same based on the indication of another L1 R2D control information field. In other words, in Option 6, the interpretation of control information field X may be determined independently based on the indication of another L1 R2D control information field. Alternatively, in Option 6, the interpretation of control information field X may be determined separately based on the indication of another L1 R2D control information field.

[0197] For example, if the L1 R2D control information field Y indicates a value of A, the interpretation of the L1 R2D control information field X is determined to be interpretation α. ​​If the L1 R2D control information field Y indicates a value of B, the interpretation of the L1 R2D control information field X is determined to be interpretation β.

[0198] In Option 6, the reader transmits L1 R2D control information including an L1 R2D control information field X in which a code point is set based on an interpretation determined based on another L1 R2D control information field Y. Note that here, the L1 R2D control information field Y and the L1 R2D control information field X may be included in the same PRDCH or different PRDCHs, or may be included in the same L1 R2D control information or different L1 R2D control information. The A-IoT device controls reception of the L1 R2D control information field X based on the interpretation determined based on the other L1 R2D control information field Y.

[0199] <Option 7 of Proposals 1-3> In Option 7, the interpretation of each L1 R2D control information field may be based on the cast type of the R2D. For example, in Option 7, the interpretation of the L1 R2D control information field is different for different cast types of R2D. Note that Option 7 does not necessarily require that the interpretation of the L1 R2D control information field X be different for different cast types of R2D. In Option 7, the interpretation of the L1 R2D control information field X may be the same for different cast types of R2D. In other words, in Option 7, the interpretation of the control information field X may be independent for each different cast type of R2D. Alternatively, in Option 7, the interpretation of the control information field X may be differentiated for each different cast type of R2D.

[0200] For example, in unicast, the interpretation of the L1 R2D control information field X is interpretation α, and in multicast and / or broadcast, the interpretation of the L1 R2D control information field X is interpretation β.

[0201] The interpretation of the L1 R2D control information field may be based on whether the R2D scheduling is group / cell-based or device-specific. For example, the interpretation of the L1 R2D control information field may differ depending on whether the R2D scheduling is group / cell-based or device-specific.

[0202] In option 7, the reader transmits L1 R2D control information including an L1 R2D control information field in which a code point is set based on an interpretation determined based on the cast type of the R2D. Note that the L1 R2D control information transmitted here is transmitted based on the cast type. The A-IoT device performs reception control of the L1 R2D control information field based on the interpretation determined based on the cast type of the R2D. This reception control may include conversion of the code point of the L1 R2D control information field to information.

[0203] <Option 8 of Proposals 1-3> In option 8, the interpretation of each of the L1 R2D control information fields may be based on the corresponding preamble / corresponding timing acquisition signal.

[0204] For example, if a preamble corresponding to a certain L1 R2D control information field X exists, the interpretation of the L1 R2D control information field X is determined to be interpretation α. ​​If a preamble corresponding to the L1 R2D control information field X does not exist, the interpretation of the L1 R2D control information field X is determined to be interpretation β.

[0205] Also, for example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X exists, the interpretation of the L1 R2D control information field X is determined to be interpretation α. ​​For example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X does not exist, the interpretation of the L1 R2D control information field X is determined to be interpretation β.

[0206] In option 8, the reader transmits L1 R2D control information including an L1 R2D control information field with a code point set based on an interpretation determined based on the presence of a preamble / timing acquisition signal. Note that a corresponding preamble / timing acquisition signal may be added to the PRDCH containing the L1 R2D control information transmitted here. The A-IoT device performs reception control assuming that the L1 R2D control information field is included based on an interpretation determined based on the presence of a received preamble / timing acquisition signal. The reception control here may include conversion of the code point of the L1 R2D control information field into information.

[0207] <Option 9 of Proposals 1-3> In option 9, the interpretation of each of the L1 R2D control information fields may be based on the type of message.

[0208] The interpretation of the field may be determined by whether the message is the first message or a subsequent message in a session.

[0209] In option 9, the reader transmits L1 R2D control information including an L1 R2D control information field with a code point set based on an interpretation determined based on the message type. The A-IoT device controls reception of the L1 R2D control information field based on the interpretation determined based on the message type. The control of reception here may include conversion of the code point of the L1 R2D control information field to information.

[0210] <Option 10 of Proposals 1-3> In Option 10, the interpretation of each L1 R2D control information field is based on the value of a specific field. For example, in Option 10, the interpretation of the L1 R2D control information field differs based on the value of a specific field. Note that Option 10 does not necessarily require that the interpretation of L1 R2D control information field X differ for different values ​​of a specific field. In Option 10, the interpretation of L1 R2D control information field X may be the same for different values ​​of a specific field. In other words, in the options, the interpretation of control information field X may be independent for different values ​​of a specific field. Alternatively, in Option 7, the interpretation of control information field X may be differentiated for different values ​​of a specific field.

[0211] For example, if field A is set to all "0"s or all "1"s, then field B is interpreted as interpretation X; otherwise, field B is interpreted as interpretation Y.

[0212] In option 10, the reader transmits L1 R2D control information including an L1 R2D control information field in which a code point is set based on an interpretation determined based on a value of a certain field (e.g., a code point). The A-IoT device controls reception of the L1 R2D control information field based on the interpretation determined based on the value of a certain field (e.g., a code point). The reception control here may include conversion from the code point of the L1 R2D control information field to information.

[0213] Specific examples are described below.

[0214] The interpretation of any of the following information fields is determined based on at least one of the options mentioned above: Information about TDRA Information about FDRA Information about CDRA Information about chip interval Information about symbol interval Information about bit interval Information about how chips are mapped to bits Information about chip rate Information about symbol rate Information about bit rate Information about coding scheme Information about coding rate Information about modulation scheme Information about FEC Information about CRC Information about TBS Information about repetition Information about midamble Information about cast type Information about device ID Information about device group ID D2R scheduling type Information about reader ID

[0215] The interpretation of the FDRA information may differ for different A-IoT device types. For example, for backscatter D2R transmission, the FDRA indicates the frequency shift of the backscatter. For active D2R transmission, the FDRA indicates the frequency resource for the active D2R transmission.

[0216] As described above, in Proposals 1-3, the interpretation is defined / determined. As a result, the interpretation of the field for transmitting the L1 R2D control information can be appropriately defined / determined, so that a common interpretation is applied between the transmitter and receiver of the L1 R2D control information, and it is possible to avoid discrepancies in the information to be notified.

[0217] For example, in Proposals 1-3, the leader determines an interpretation of a specific L1 R2D control information field included in the L1 R2D control information based on a specific condition. Then, the leader transmits a PRDCH including L1 R2D control information, the PRDCH including the L1 R2D control information, the L1 R2D control information field having a code point set based on the determined interpretation. The A-IoT device receives the PRDCH including the L1 R2D control information. Then, the A-IoT device determines an interpretation of the specific L1 R2D control information field included in the L1 R2D control information based on a specific condition, and controls reception of the specific L1 R2D control information field based on the determined interpretation. Here, the specific condition may be a condition indicated in at least one of the above-mentioned options.

[0218] Note that different options may be applied to the interpretation of each L1 R2D control information field in the L1 R2D control information received on the PRDCH. For example, when three fields, field X, field Y, and field Z, can be included in the L1 R2D control information, option 1 may be applied to the interpretation of field X, option 2 may be applied to the interpretation of field Y, and option 3 may be applied to the interpretation of field Z. In such a case where three options are applied, for example, the interpretation of field X is defined by the specifications, the interpretation of field Y is determined depending on the type of the A-IoT device, and the interpretation of field Z depends on the capability of the A-IoT device regarding field Z.

[0219] <Proposal 1-4> Proposal 1-4 describes how each candidate value of the L1 R2D control information field in the L1 R2D control information received on the PRDCH is defined and / or determined.

[0220] It should be noted that the candidate values ​​of the L1 R2D control information field X correspond to candidate values ​​notified by the L1 R2D control information field X. For example, the candidate values ​​of the L1 R2D control information field X correspond to candidate values ​​mapped to code points that the L1 R2D control information field X can take. For example, if the size of field X is 2 bits and there are four code points, the number of candidate values ​​may be a maximum of four. It should be noted that if there are N code points (N is an integer equal to or greater than 1), the number of candidate values ​​may be N or less than N.

[0221] The candidate values ​​may be defined, for example, by a range of values ​​or by a set of values.

[0222] Regarding the mapping between code points and candidate values, at least one of the following options a and b may be applied.

[0223] Option a: Code points are mapped to any integer value within a range of values ​​from a minimum value to a maximum value. For example, if there are N+1 code points from 0 to N, then the code points are mapped to N+1 integer values ​​from X to X+N, ranging from a minimum value of X to a maximum value of X+N.

[0224] Option b: Code points are mapped to a specific set of values, e.g. code points 0, 1, 2, ... are mapped to X, Y, Z, ...

[0225] As described above, the candidate values ​​may be represented by a range of candidate values, or by a minimum and a maximum value that indicate the range of candidate values. The range of candidate values ​​may also be represented by a reference value for the range (e.g., the minimum or maximum value of the range) and a step size from the reference value. For example, if the reference value for the range is "1" and the step size is "+2," the candidate values ​​are 1, 3, 5, and 7.

[0226] Alternatively, the candidate values ​​may be represented by a set of candidate values.

[0227] Furthermore, the candidate values ​​are not limited to numerical values, and for example, candidates for the coding method, modulation method, etc. to be applied may be associated with the candidate values.

[0228] The candidate values ​​may be replaced by a range of values, a minimum value, or a maximum value.

[0229] Below, nine options are shown, taking as examples the case where the candidate values ​​are represented by a range of candidate values ​​and the case where the candidate values ​​are represented by a set of candidate values. Note that the range of candidate values ​​may be simply referred to as a "range (of values)," and the set of candidate values ​​may be simply referred to as a "candidate value."

[0230] <Option 1 of Proposal 1-4> In Option 1, the range of possible values ​​for each L1 R2D control information field is defined in the specification and / or system. For example, the range of values ​​for R2D control information field X is defined in the specification and / or system.

[0231] Also, in option 1, each candidate value of the L1 R2D control information field is defined in the specification and / or system. For example, candidate values ​​of the R2D control information field X are defined in the specification and / or system.

[0232] <Option 2 of Proposal 1-4> In Option 2, the range of candidate values ​​for each L1 R2D control information field is defined for each type of A-IoT device. In Option 2, the range of values ​​for a specific L1 R2D control information field X may be defined as a different range for each type of A-IoT device. Note that Option 2 does not necessarily require the range of values ​​for the L1 R2D control information field X to be different for each type of A-IoT device. In Option 2, the range of values ​​for the L1 R2D control information field X may be the same for two or more types of A-IoT devices. In other words, in Option 2, the range of values ​​for the control information field X may be defined independently for each type of A-IoT device. Alternatively, in Option 2, the range of values ​​for the control information field X may be defined separately for each type of A-IoT device.

[0233] For example, if there are two types of A-IoT devices, type α and type β, the range of values ​​of the R2D control information field X for type α is A to B (A and B are, for example, real numbers), and the range of values ​​of the R2D control information field X for type β is C to D (C and D are, for example, real numbers). In this case, A may be different from C or may be the same as C. Furthermore, B may be different from D or may be the same as D.

[0234] Here, range P and range Q being different from each other means that at least one of the following is true: - The minimum value of range P is different from the minimum value of range Q. - The maximum value of range P is different from the maximum value of range Q. - The number of candidates included in range P is different from the number of candidates included in range Q. - At least one of the candidate values ​​included in range P is not included in range Q.

[0235] Furthermore, in Option 2, each candidate value of the L1 R2D control information field is defined for each type of A-IoT device. In Option 2, a candidate value of a certain L1 R2D control information field X may be defined as a different candidate value for each type of A-IoT device. Note that Option 2 does not necessarily require that the candidate value of the L1 R2D control information field X be different for each type of A-IoT device. In Option 2, the candidate value of the L1 R2D control information field X may be the same for two or more types of A-IoT devices. In other words, in Option 2, the candidate value of the control information field X may be defined independently for each type of A-IoT device. Alternatively, in Option 2, the candidate value of the control information field X may be defined separately for each type of A-IoT device.

[0236] For example, if there are two types of A-IoT devices, type α and type β, the candidate values ​​of the R2D control information field X for type α are A, B, and C (A, B, and C are, for example, real numbers), and the candidate values ​​of the R2D control information field X for type β are D, E, and F (D, E, and F are, for example, real numbers). In this case, A, B, and C may be different from D, E, and F, respectively, or at least one of A, B, and C may be the same as at least one of D, E, and F.

[0237] Here, candidate value P and candidate value Q being different from each other means, for example, that at least one of the values ​​included in candidate value P is not included in candidate value Q. Note that candidate value P and candidate value Q each indicate a set of candidate values.

[0238] <Option 3 of Proposals 1-4> In Option 3, the range of candidate values ​​for each L1 R2D control information field depends on the capability of the A-IoT device. In Option 3, the value range of a specific L1 R2D control information field X may differ depending on the capability of the A-IoT device. Note that Option 3 does not necessarily require that the value range of the L1 R2D control information field X differ depending on the capability of the A-IoT device. In Option 3, the value range of the L1 R2D control information field X may be the same between different capabilities of the A-IoT device. In other words, in Option 3, the value range of the control information field X may be independent for each capability of the A-IoT device. Alternatively, in Option 3, the value range of the control information field X may be distinguished for each capability of the A-IoT device.

[0239] For example, if an A-IoT device supports a capability related to the R2D control information field X, the range of values ​​for the R2D control information field X is range P. In other words, in this case, a value determined from range P is included in the R2D control information field X of the L1 R2D control information transmitted to an A-IoT device that supports the capability related to the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from range P is included in the R2D control information field X. On the other hand, if an A-IoT device does not support the capability related to the R2D control information field X, the range of values ​​for the R2D control information field X is range Q. In other words, in this case, a value determined from range Q is included in the R2D control information field X of the L1 R2D control information transmitted to an A-IoT device that does not support the capability related to the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from range Q is included in the R2D control information field X.

[0240] Furthermore, in Option 3, each candidate value of the L1 R2D control information field depends on the capability of the A-IoT device. In Option 3, the candidate value of a certain L1 R2D control information field X may differ depending on the capability of the A-IoT device. Note that Option 3 does not necessarily require that the candidate value of the L1 R2D control information field X differ depending on the capability of the A-IoT device. In Option 3, the candidate value of the L1 R2D control information field X may be the same between different capabilities of the A-IoT device. In other words, in Option 3, the candidate value of the control information field X may be independent for each capability of the A-IoT device. Alternatively, in Option 3, the candidate value of the control information field X may be distinguished for each capability of the A-IoT device.

[0241] For example, if an A-IoT device supports a capability related to the R2D control information field X, the candidate value for the value of the R2D control information field X is candidate value P. In other words, in this case, a value determined from among candidate values ​​P is included in the R2D control information field X in the L1 R2D control information transmitted to an A-IoT device that supports the capability related to the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from among candidate values ​​P is included in the R2D control information field X. Then, if an A-IoT device does not support the capability related to the R2D control information field X, the range of values ​​for the R2D control information field X is candidate value Q. In other words, in this case, a value determined from among candidate values ​​Q is included in the R2D control information field X in the L1 R2D control information transmitted to an A-IoT device that does not support the capability related to the R2D control information field X. Specifically, a code point corresponding to the value determined from among candidate values ​​Q is included in the R2D control information field X.

[0242] <Option 4 of Proposal 1-4> In Option 4, the range of candidate values ​​for each L1 R2D control information field may be determined based on higher layer R2D control information. In Option 4, the value range of a specific L1 R2D control information field X is determined to be a different range of values ​​based on higher layer R2D control information. Note that Option 4 does not necessarily require the value range of the L1 R2D control information field X to be different based on higher layer R2D control information. In Option 4, the value range of the L1 R2D control information field X may be the same based on higher layer R2D control information. In other words, in Option 4, the value range of the control information field X may be independently determined based on higher layer R2D control information. Alternatively, in Option 4, the value range of the control information field X may be separately determined based on higher layer R2D control information.

[0243] For example, when a parameter A of the higher layer is specified, the range of values ​​of the L1 R2D control information field X is determined to be range P. When a parameter B of the higher layer is specified, the range of values ​​of the L1 R2D control information field X is determined to be range Q. In this case, range P may be different from range Q or may be the same as range Q.

[0244] In option 4, each candidate value of the L1 R2D control information field may be determined based on R2D control information in a higher layer. In option 4, candidate values ​​of a certain L1 R2D control information field X are determined to be different candidate values ​​based on R2D control information in a higher layer. Note that option 4 does not necessarily require that candidate values ​​of the L1 R2D control information field X be different based on R2D control information in a higher layer. In option 4, the candidate values ​​of the L1 R2D control information field X may be the same based on R2D control information in a higher layer. In other words, in option 4, candidate values ​​of the control information field X may be independently determined based on R2D control information in a higher layer. Alternatively, in option 4, candidate values ​​of the control information field X may be separately determined based on R2D control information in a higher layer.

[0245] For example, when a parameter A of the higher layer is specified, the candidate value of the L1 R2D control information field X is determined to be candidate value P. When a parameter B of the higher layer is specified, the candidate value of the L1 R2D control information field X is determined to be candidate value Q. In this case, candidate value P may be different from candidate value Q or may be the same as candidate value Q.

[0246] <Option 5 of Proposals 1-4> In Option 5, the range of values ​​available for each of the L1 R2D control information fields may be determined based on the scrambling ID of the PRDCH. In Option 5, the range of values ​​for a specific L1 R2D control information field X is determined to be a range of values ​​that differ based on the scrambling ID of the PRDCH. Note that Option 5 does not necessarily require the range of values ​​for the L1 R2D control information field X to differ based on the scrambling ID of the PRDCH. In Option 5, the range of values ​​for the L1 R2D control information field X may be the same based on the scrambling ID of the PRDCH. In other words, in Option 5, the range of values ​​for the control information field X may be determined independently based on the scrambling ID of the PRDCH. Alternatively, in Option 5, the range of values ​​for the control information field X may be determined separately based on the scrambling ID of the PRDCH.

[0247] For example, if the PRDCH is scrambled with a scrambling ID of A, it is determined that the range of values ​​of the L1 R2D control information field X is range P. In this case, a value determined from range P is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from range P is included in the R2D control information field X. And, if the PRDCH is scrambled with a scrambling ID of B, it is determined that the range of values ​​of the L1 R2D control information field X is range Q. In this case, a value determined from range Q is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from range Q is included in the R2D control information field X.

[0248] In option 5, each candidate value of the L1 R2D control information field may be determined based on a scrambling ID of the PRDCH. In option 5, candidate values ​​of a certain L1 R2D control information field X are determined to be different candidate values ​​based on the scrambling ID of the PRDCH. Note that option 5 does not necessarily require that candidate values ​​of the L1 R2D control information field X be different based on the scrambling ID of the PRDCH. In option 5, candidate values ​​of the L1 R2D control information field X may be the same based on the scrambling ID of the PRDCH. In other words, in option 5, candidate values ​​of the control information field X may be determined independently based on the scrambling ID of the PRDCH. Alternatively, in option 5, candidate values ​​of the control information field X may be determined separately based on the scrambling ID of the PRDCH.

[0249] For example, if the PRDCH is scrambled with a scrambling ID of A, the candidate value of the L1 R2D control information field X is determined to be candidate value P. In this case, a value determined from among candidate values ​​P is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from among candidate values ​​P is included in the R2D control information field X. Then, if the PRDCH is scrambled with a scrambling ID of B, the candidate value of the L1 R2D control information field X is determined to be candidate value Q. In this case, a value determined from among candidate values ​​Q is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from among candidate values ​​Q is included in the R2D control information field X.

[0250] <Option 6 of Proposals 1-4> In Option 6, the range of values ​​available for each of the L1 R2D control information fields may be determined based on the indication of another L1 R2D control information field. In Option 6, the value range of a specific L1 R2D control information field X is determined to be a different value range based on the indication of another L1 R2D control information field. Note that Option 6 does not necessarily require the value range of the L1 R2D control information field X to be different based on the indication of another L1 R2D control information field. In Option 6, the value range of the L1 R2D control information field X may be the same based on the indication of another L1 R2D control information field. In other words, in Option 6, the value range of the control information field X may be determined independently based on the indication of another L1 R2D control information field. Alternatively, in Option 6, the value range of the control information field X may be determined separately based on the indication of another L1 R2D control information field.

[0251] For example, when the L1 R2D control information field Y indicates a value A, it is determined that the range of values ​​of the L1 R2D control information field X is range P. In this case, a value determined from range P is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from range P is included in the R2D control information field X. Furthermore, when the L1 R2D control information field Y indicates a value B, it is determined that the range of values ​​of the L1 R2D control information field X is range Q. In this case, a value determined from range Q is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from range Q is included in the R2D control information field X.

[0252] In Option 6, each candidate value of the L1 R2D control information field may be based on the indication of another L1 R2D control information field. In Option 6, the candidate value of a specific L1 R2D control information field X is determined to be a different candidate value based on the indication of another L1 R2D control information field. Note that Option 6 does not necessarily require the candidate value of L1 R2D control information field X to be different based on the indication of another L1 R2D control information field. In Option 6, the candidate value of L1 R2D control information field X may be the same based on the indication of another L1 R2D control information field. In other words, in Option 6, the candidate value of control information field X may be independently determined based on the indication of another L1 R2D control information field. Alternatively, in Option 6, the candidate value of control information field X may be separately determined based on the indication of another L1 R2D control information field.

[0253] For example, when the L1 R2D control information field Y indicates a value A, the candidate value of the L1 R2D control information field X is determined to be candidate value P. In this case, a value determined from among candidate values ​​P is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from among candidate values ​​P is included in the R2D control information field X. Furthermore, when the L1 R2D control information field Y indicates a value B, the candidate value of the L1 R2D control information field X is determined to be candidate value Q. In this case, a value determined from among candidate values ​​Q is included in the R2D control information field X. Specifically, in this case, a code point corresponding to the value determined from among candidate values ​​Q is included in the R2D control information field X.

[0254] <Option 7 of Proposals 1-4> In Option 7, the range of possible values ​​for each of the L1 R2D control information fields may be based on the cast type of the R2D. For example, in Option 7, the range of values ​​for the L1 R2D control information field is different for different cast types of R2D. Note that Option 7 does not necessarily require the range of values ​​for the L1 R2D control information field X to be different for different cast types of R2D. In Option 7, the range of values ​​for the L1 R2D control information field X may be the same for different cast types of R2D. In other words, in Option 7, the range of values ​​for the control information field X may be independent for each different cast type of R2D. Alternatively, in Option 7, the range of values ​​for the control information field X may be distinguished for each different cast type of R2D.

[0255] For example, in unicast, the range of values ​​of the L1 R2D control information field X is range P, and in multicast and / or broadcast, the range of values ​​of the L1 R2D control information field X is range Q.

[0256] The range of values ​​for the L1 R2D control information field may be based on whether the R2D scheduling is group / cell-based or device-specific. For example, the range of values ​​for the L1 R2D control information field may differ depending on whether the R2D scheduling is group / cell-based or device-specific.

[0257] In Option 7, each candidate value of the L1 R2D control information field may be based on the cast type of the R2D. For example, in Option 7, the candidate values ​​of the L1 R2D control information field are different for different cast types of the R2D. Note that Option 7 does not necessarily require that the candidate values ​​of the L1 R2D control information field X be different for different cast types of the R2D. In Option 7, the candidate values ​​of the L1 R2D control information field X may be the same for different cast types of the R2D. In other words, in Option 7, the candidate values ​​of the control information field X may be independent for each different cast type of the R2D. Alternatively, in Option 7, the candidate values ​​of the control information field X may be differentiated for each different cast type of the R2D.

[0258] For example, in unicast, the candidate value of the L1 R2D control information field X is candidate value P, and in multicast and / or broadcast, the candidate value of the L1 R2D control information field X is candidate value Q.

[0259] The candidate values ​​of the L1 R2D control information field may be based on whether the R2D scheduling is group / cell-based or device-specific. For example, the candidate values ​​of the L1 R2D control information field may differ depending on whether the R2D scheduling is group / cell-based or device-specific.

[0260] <Option 8 of Proposals 1-4> In option 8, the range of possible values ​​for each L1 R2D control information field may be based on the corresponding preamble / corresponding timing acquisition signal.

[0261] For example, if a preamble corresponding to a certain L1 R2D control information field X exists, it is determined that the value range of the L1 R2D control information field X is range P. If a preamble corresponding to the L1 R2D control information field X does not exist, it is determined that the value range of the L1 R2D control information field X is range Q.

[0262] Furthermore, for example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X exists, the range of values ​​of the L1 R2D control information field X is determined to be range P. For example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X does not exist, the range of values ​​of the L1 R2D control information field X is determined to be range Q.

[0263] In option 8, each candidate value for the L1 R2D control information field may be based on the corresponding preamble / corresponding timing acquisition signal.

[0264] For example, if a preamble corresponding to a certain L1 R2D control information field X exists, the candidate value of the L1 R2D control information field X is determined to be candidate value P. If a preamble corresponding to the L1 R2D control information field X does not exist, the candidate value of the L1 R2D control information field X is determined to be candidate value Q.

[0265] Furthermore, for example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X exists, the candidate value of the L1 R2D control information field X is determined to be candidate value P. For example, if a timing acquisition signal corresponding to a certain L1 R2D control information field X does not exist, the candidate value of the L1 R2D control information field X is determined to be candidate value Q.

[0266] <Option 9 of Proposals 1-4> In option 9, each candidate value of the L1 R2D control information field may be based on the type of message.

[0267] The possible values ​​for the field may be determined by whether the message is the first message or a subsequent message in a session.

[0268] It should be noted that the range of values ​​for the field may be determined based on at least one of the above-mentioned options, or the maximum value of the range of values ​​for the field may be defined and / or determined, or the minimum value of the range of values ​​for the field may be defined and / or determined, or the minimum and maximum values ​​may be defined and / or determined based on at least one of the above-mentioned options.

[0269] It should be noted that two or more of the above options may be applied. For example, different options may be applied to the maximum and minimum values ​​of a field's value range. For example, option 1 may be applied to the minimum value of the value range, and option 2 may be applied to the maximum value. In this case, the minimum value may be defined in the specification / system, and the maximum value may be determined by the type of A-IoT device.

[0270] Alternatively, the number and / or values ​​of possible possible values ​​for the field may be defined and / or determined based on at least one of the options discussed above.

[0271] Note that there may be unused code points, which may be treated as reserved.

[0272] Specific examples are described below.

[0273] The value range or candidate values ​​for any of the fields of the following information are determined based on at least one of the options mentioned above: Information about TDRA Information about FDRA Information about CDRA Information about chip interval Information about symbol interval Information about bit interval Information about how chips are mapped to bits Information about chip rate Information about symbol rate Information about bit rate Information about coding method Information about coding rate Information about modulation method Information about FEC Information about CRC Information about TBS Information about repetition Information about midamble Information about cast type Information about device ID Information about device group ID D2R scheduling type Information about reader ID

[0274] In at least one of the following cases: when a different coding scheme / different modulation scheme / different FEC is supported by the capability of the A-IoT device, when a different coding scheme / different modulation scheme / different FEC is indicated by higher layer control information, and when a different coding scheme / different modulation scheme / different FEC is indicated by L1 control information, any of the following may be different: At least one of the minimum, maximum and candidate values ​​of the chip interval At least one of the minimum, maximum and candidate values ​​of the symbol interval At least one of the minimum, maximum and candidate values ​​of the bit interval At least one of the minimum, maximum and candidate values ​​of the chip to bit mapping method At least one of the minimum, maximum and candidate values ​​of the chip rate At least one of the minimum, maximum and candidate values ​​of the symbol rate At least one of the minimum, maximum and candidate values ​​of the bit rate At least one of the minimum, maximum and candidate values ​​of the coding rate At least one of the minimum, maximum and candidate values ​​of the FEC coding rate

[0275] As described above, in Proposals 1-4, the range of values / candidate values ​​of the L1 R2D control information field are defined / determined. This allows the range of values / candidate values ​​of the field for transmitting the L1 R2D control information to be appropriately defined / determined, thereby preventing the range of values / candidate values ​​of the field from becoming excessively large, thereby reducing the overhead of the L1 R2D control information. Furthermore, this allows the range of values / candidate values ​​of the field to be avoided from becoming insufficient, thereby enabling the L1 R2D control information to be appropriately transmitted.

[0276] For example, in Proposal 1-4, the reader determines a candidate value for a specific L1 R2D control information field included in the L1 R2D control information based on a specific condition. Then, the reader transmits a PRDCH including L1 R2D control information, which includes an L1 R2D control information field having a code point associated with one of the determined candidate values. The A-IoT device receives the PRDCH including the L1 R2D control information. Then, the A-IoT device determines a candidate value for the specific L1 R2D control information field based on a specific condition, and performs reception control of the specific L1 R2D control information field based on the determined candidate value. Here, the reception control includes a process of identifying which candidate value the specific L1 R2D control information field corresponds to. Furthermore, here, the specific condition may be a condition indicated in at least one of the options described above.

[0277] Note that different options may be applied to the value range / candidate values ​​of each L1 R2D control information field in the L1 R2D control information received on the PRDCH. For example, when three fields, field X, field Y, and field Z, may be included in the L1 R2D control information, option 1 may be applied to the value range / candidate values ​​of field X, option 2 may be applied to the value range / candidate values ​​of field Y, and option 3 may be applied to the value range / candidate values ​​of field Z. In a case where three options are applied in this way, for example, the value range / candidate values ​​of field X are defined by specifications, the value range / candidate values ​​of field Y are determined depending on the type of the A-IoT device, and the value range / candidate values ​​of field Z depend on the capability of the A-IoT device for field Z.

[0278] In the above-mentioned Proposal 1, one field may indicate multiple pieces of L1 R2D control information. For example, a code point A in a certain field may indicate that the L1 R2D control information X is N and the L1 R2D control information Y is J. A code point B in the certain field may indicate that the L1 R2D control information X is M and the L1 R2D control information Y is K.

[0279] For example, one field X may indicate information about a chip rate and information about a symbol rate. For example, a code point A in field X may indicate that the chip rate is N and the symbol rate is J. A code point B in the field may indicate that the chip rate is M and the L1 symbol rate is K. Here, N and M are each one of the candidate values ​​for the chip rate. J and K are each one of the candidate values ​​for the symbol rate.

[0280] Here are some examples:

[0281] For example, two or more of the following information / parameters may be indicated together in one field: Information on the modulation method Information on the coding method Information on how to map chips to bits Information on the chip interval Information on the symbol interval Information on the bit interval Information on the chip rate Information on the symbol rate Information on the bit rate Information on the coding rate Information on the FEC method Information on the FEC coding rate

[0282] Furthermore, at least two or more of the following three types of information may be collectively indicated in one field: Information about TDRA Information about FDRA Information about CDRA

[0283] Furthermore, at least one of the following three types of information and information about repetition may be indicated together in one field: Information about TDRA Information about FDRA Information about CDRA

[0284] Furthermore, at least one of the following three types of information and information related to the TBS may be indicated together in one field: Information related to the TDRA Information related to the FDRA Information related to the CDRA

[0285] Furthermore, at least one of the following three types of information and information related to TDRA may be indicated together in one field: Information related to chip duration Information related to symbol duration Information related to bit duration

[0286] As described above, in Proposal 1, the leader determines, based on a specific condition, information indicated by a specific L1 R2D control information field included in the L1 R2D control information. Then, the leader transmits a PRDCH including L1 R2D control information that includes the determined L1 R2D control information field. The A-IoT device receives the PRDCH including the L1 R2D control information. Then, the A-IoT device determines, based on a specific condition, information indicated by a specific L1 R2D control information field included in the L1 R2D control information. Here, determining the information indicated by the L1 R2D control information field includes at least one of determining the presence of the L1 R2D control information field, determining the size of the L1 R2D control information field, determining the interpretation (e.g., mapping) of the L1 R2D control information field, and determining candidate values ​​for the L1 R2D control information field. Also, here, the specific condition may be at least one of a specification / system definition, an A-IoT device type, an A-IoT device capability (e.g., capability), higher layer R2D control information, another L1 R2D control information field, identification information used for scrambling the PRDCH (e.g., scrambling ID), a cast type, a preamble / timing acquisition signal, and a message type.

[0287] Note that similar options may be applied to Proposals 1-1 to 1-4. For example, if Option 2 is applied to Proposal 1-1 and the existence of Field X is defined for each type of A-IoT device, Option 2 may also be applied to Proposal 1-2 and the size of Field X may also be defined for each type of A-IoT device.

[0288] Furthermore, different options may be applied to the above-described Proposals 1-1 to 1-4. For example, Option 2 may be applied to Proposal 1-1, in which the presence of Field X is defined for each type of A-IoT device, and Option 3 may be applied to Proposal 1-2, in which the size of Field X depends on the capability of the A-IoT device.

[0289] <Proposal 2> In proposal 2, reserved bits or reserved codepoints in the L1 R2D control information field are reused to indicate other information.

[0290] In cases where parameters / information are dictated by higher layers, default values ​​are applied to the A-IoT device before the higher layer information is received by the A-IoT device.

[0291] For example, a reserved bit or a reserved codepoint in the L1 R2D control information field may be used for information transmission in a four-step contention-based access procedure. An example of a four-step contention-based access procedure will now be described.

[0292] In step 1 of the four-step contention-based access procedure, the A-IoT device sends its ID to the reader as message 1 (Msg1), which may be a random ID generated by the A-IoT device.

[0293] In step 2, the reader echoes the ID received in Msg1 as message 2 (Msg2).

[0294] In procedure 3, the A-IoT device sends the device ID and / or other upper layer data as message 3 (Msg3).

[0295] In procedure 4, the leader performs R2D transmission after D2R transmission in procedure 3. However, R2D transmission in procedure 4 does not necessarily have to be performed.

[0296] For Msg3PDRCH in the above-mentioned four-step contention-based access procedure, the scheduling information of that Msg3PDRCH is transmitted by the higher layer information in Msg2. The scheduling information is, for example, at least a part of the information shown below. Information on TDRA Information on FDRA Information on CDRA Information on chip interval Information on symbol interval Information on bit interval Information on how to map chips to bits Information on chip rate Information on symbol rate Information on bit rate Information on coding method Information on coding rate Information on modulation method Information on FEC Information on CRC Information on TBS Information on repetition Information on midamble Information on cast type Information on device ID Information on device group ID D2R scheduling type Information on reader ID

[0297] The intermediate UE may report the support status of each of the above-mentioned proposals and each option of each proposal to a network (e.g., a base station) as capability information. The base station may configure / instruct the intermediate UE based on the report of the capability information from the intermediate UE.

[0298] In the present disclosure, A / B may mean at least one of A and B. In the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0299] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

[0300] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0301] The physical layer signaling may be, for example, downlink control information (DCI).

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

[0303] <Configuration of Base Station> Fig. 9 is a block diagram showing an example of the configuration of a base station 10 according to an embodiment. The base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 10 communicates with the device 20 (see Fig. 10) wirelessly. The base station 10 may be a CW node or a terminal (for example, an intermediate node communicating with the device 20). The intermediate node may be referred to as an intermediate UE.

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

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

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

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

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

[0309] The control unit 103 controls the communication operations of the base station 10, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102. For example, the control unit 103 performs operations other than the transmission and reception described in the above embodiment (note that these operations may be performed by the reception unit 102 and / or the transmission unit 101).

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

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

[0312] The control unit 103 configures PUCCH resources as an example of allocation of resources 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.

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

[0314] For example, the control unit 103 of the base station 10 (an example of a wireless communication device) determines information indicated by at least one field included in L1 R2D control information (an example of first control information) based on a specific condition. The transmission unit 101 transmits a PRDCH (an example of a first signal) including the L1 R2D control information. Here, the specific condition may be at least one of a specification / system definition, a type of the device 20, a capability of the device 20 (e.g., capability), R2D control information of a higher layer (an example of second control information), another L1 R2D control information field (an example of second control information), identification information used for scrambling the PRDCH (e.g., scrambling ID), a cast type of the PRDCH (an example of a transmission method of the first signal), a preamble / timing acquisition signal (an example of a second signal), and a message type. In addition, determining the information indicated by the L1 R2D control information field includes at least one of determining the presence of the L1 R2D control information field, determining the size of the L1 R2D control information field, determining the interpretation (e.g., mapping) of the L1 R2D control information field, and determining candidate values ​​for the L1 R2D control information field.

[0315] <Device Configuration> Fig. 10 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, and is, for example, an A-IoT UE or an A-IoT device. The device 20 may be considered to be a device that receives power from energy harvesting. For example, the device 20 may be considered to be a device that receives power from the base station 10 or a CW supplied from the base station 10.

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

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

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

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

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

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

[0322] The control unit 203 controls communication operations of the device 20, including reception processing in the receiving unit 201 and transmission processing in the transmitting unit 202. For example, the control unit 203 performs operations other than the transmission and reception described in the above embodiment (note that these operations may be performed by the receiving unit 201 and / or the transmitting unit 202).

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

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

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

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

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

[0328] For example, the receiving unit 201 of the device 20 receives a PRDCH (an example of a first signal) including L1 R2D control information (an example of first control information). The control unit 203 determines information indicated by at least one field included in the L1 R2D control information based on a specific condition. Here, the specific condition may be at least one of a specification / system definition, a type of the device 20, a capability of the device 20 (e.g., capability), R2D control information of a higher layer (an example of second control information), another L1 R2D control information field (an example of second control information), identification information used for scrambling the PRDCH (e.g., scrambling ID), a cast type of the PRDCH (an example of a transmission method of the first signal), a preamble / timing acquisition signal (an example of a second signal), and a message type. In addition, determining the information indicated by the L1 R2D control information field includes at least one of determining the presence of the L1 R2D control information field, determining the size of the L1 R2D control information field, determining the interpretation (e.g., mapping) of the L1 R2D control information field, and determining candidate values ​​for the L1 R2D control information field.

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

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

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

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

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

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

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

[0336] 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. 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 terminal 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.

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

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

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

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

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

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

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

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

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

[0346] <Base Station Operation> In the following, a base station may be read as an intermediate node. A specific operation described as being performed by a base station in the present disclosure may also be performed by its upper node in some cases. It is clear that in a network consisting of one or more network nodes having a base station, 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 is not limited to these). While 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0365] Furthermore, a 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 terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A device comprising: a receiving unit that receives a first signal including first control information; and a control unit that determines information indicated by at least one field included in the first control information based on specific conditions.

2. The device of claim 1, wherein the specific condition is at least one of the type of the device, the capability of the device, second control information different from the first control information, identification information used to scramble the first signal, the transmission method of the first signal, the second signal added to the first signal, and the transmission type of the first control information.

3. The device according to claim 1, wherein the control unit determines, based on the specific condition, at least one of whether the first control information includes a specific field and the size of the specific field.

4. The device according to claim 1, wherein the control unit determines what a first value included in a specific field indicates based on the specific condition.

5. A wireless communication device comprising: a control unit that determines information indicated by at least one field included in first control information based on specific conditions; and a transmission unit that transmits a first signal including the first control information.

6. A wireless communication method, comprising: a device receiving a first signal including first control information; and determining information indicated by at least one field included in the first control information based on a specific condition.

Images