Device, wireless communication apparatus, and wireless communication method

Abstract

To provide a device, a wireless communication apparatus, and a wireless communication method that can suppress an increase in signal collisions between devices.SOLUTION: A device is a first type device that supports an operation of determining a plurality of time resources from a received signal and selecting a transmission time resource from the plurality of time resources, and includes a control unit that determines the transmission time resource using information different from that of a second type device that does not support the operation, and a transmission unit that transmits a response signal to the received signal in the transmission time resource.SELECTED DRAWING: Figure 20

Description

[Technical Field]

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

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

[0003] Furthermore, Release 18 (Rel-18) of 3GPP (registered trademark) 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. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V17.3.0 (2022-12) [Non-patent document 2] “Revised SID on Ambient IoT”, RP-232404, 3GPP TSG RAN Meeting #101, September 2023 [Non-patent document 3] 3GPP TR 38.848 V1.0.0 (2023-09) [Non-patent document 4] 3GPP TS 36.211 V16.8.0 (2023-09) [Non-Patent Document 5] “Study on solutions for Ambient IoT (Internet of Things) in NR”, RP-234058, 3GPP TSG RAN Meeting #102, December 2023 [Non-patent document 6] “New Work Item: Solutions for Ambient IoT (Internet of Things) in NR”, RP-243326, 3GPP TSG RAN Meeting #106, December 2024 [Non-Patent Document 7] 3GPP TR 38.769 V19.0.0 (2024-12) Summary of the Invention

[0005] In random access by A-IoT devices (hereinafter simply referred to as "devices"), multiple devices transmit signals in time domain resources that are each determined by the device, which may increase the risk of signal collisions between devices.

[0006] One aspect of the present disclosure contributes to providing a device, a wireless communication apparatus, and a wireless communication method that can suppress an increase in signal collisions between devices.

[0007] A device according to one embodiment of the present disclosure is a first type device that supports an operation of determining a plurality of time resources from a received signal and selecting a transmission time resource from the plurality of time resources, and includes: a control unit that determines the transmission time resource using information different from that of a second type device that does not support the operation; and a transmission unit that transmits a response signal to the received signal in the transmission time resource. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating Topology 1. [Figure 3] FIG. 10 is a diagram illustrating Topology 2. [Figure 4] FIG. 10 is a diagram illustrating topology 3 in DL support. [Figure 5] FIG. 10 is a diagram illustrating Topology 3 in UL support. [Figure 6] FIG. 10 is a diagram illustrating Topology 4. [Figure 7] FIG. 1 is a diagram illustrating backscatter transmission. [Figure 8] 1A and 1B are diagrams illustrating examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. [Figure 9] FIG. 10 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in topology 2. [Figure 10] A diagram showing an example of an access procedure for an A-IoT device. [Figure 11] A diagram showing steps in the access procedure for an A-IoT device. [Figure 12] A diagram showing an example of a four-step (or three-step) random access procedure for an A-IoT device. [Figure 13] A diagram showing an example of a two-step random access procedure for an A-IoT device. [Figure 14] A figure showing an example of TDMA_Msg.1. [Figure 15] FIG. 10 is a diagram showing an example of Alt. 1 of Proposal 2. [Figure 16] FIG. 10 is a diagram showing an example of Alt. 2 of Proposal 2. [Figure 17] FIG. 10 is a diagram illustrating an example of Proposal 3. [Figure 18] FIG. 10 is a diagram showing an example of a variation of Proposal 3. [Figure 19] FIG. 2 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 20] FIG. 1 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure. [Figure 21] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a device according to an embodiment of the present disclosure. [Figure 22] 1 is a diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[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, device, terminal, etc. are set.

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

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

[0016] The base station 10 transmits DL signals such as control information, setting information, and data 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 intermediate nodes, assisting nodes, and / or terminals (UEs) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be written simply as " / ".

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

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

[0021] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, 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 PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or PUCCH.

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

[0023] Ambient IoT may consider, for example, the following deployment scenarios and characteristics for relevant use cases: Indoor or outdoor environment Base station type, e.g., macro / micro / pico cell-based deployment The connectivity topology, e.g., which nodes (e.g., base stations, terminals (UE), relays, and repeaters) communicate with the ambient IoT devices - Duplexing method: TDD or FDD, frequency band: licensed or unlicensed Coexistence with UE and network equipment in frequency bands for existing 3GPP technologies - Traffic assumptions for outgoing / incoming traffic from 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 type and topology> 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 and amplification functions, and performs backscattering transmission. Device B: Device B has power storage, does not have the capability of independent signal generation, and performs backscatter transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, is capable of independent signal generation, and has active RF (radio frequency) components 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] Figure 4 is a diagram illustrating Topology 3 in DL assistance. As shown in Figure 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] Figure 5 is a diagram illustrating Topology 3 in UL support. As shown in Figure 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 Figures 4 and 5 may be, for example, relays, IAB nodes, UEs, repeaters, etc.

[0036] Figure 6 is a diagram illustrating Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device performs bidirectional communication with the UE. Communication related to Topology 4 may be considered as 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 of Topology 4) in addition to the device 20. In this specification, the base station, the support node, the intermediate node, and the terminal may be read as a network or a (network) node. Also, an A-IoT device may be simply referred to as A-IoT.

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

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

[0041] FIG. 7 is a diagram illustrating backscatter transmission. FIG. 7 shows an example in which an ambient IoT device performs ON-OFF keying and transmits information. The dashed line area 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> The Rel-19 SID (Study Item Description) examined solutions necessary and feasible for A-IoT (see Section 4.1 of Non-Patent Document 5). The examined solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

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

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

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

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

[0047] In this disclosure, 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).

[0048] 2. Device Prerequisites For A-IoT UE, the following TX (transmission) and FR (frequency range) 1-FDD are assumed:

[0049] ·TX TX can be an unamplified backscatter UL transmission, an amplified backscatter UL transmission, or a general amplified UL transmission.

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

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

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

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

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

[0055] In Topology 2, communication is performed between a base station and an A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with 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 Topology 2 case may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as intermediate UE, int.UE (intermediate UE), etc.

[0056] <Device Type> Three device types are defined for A-IoT devices: Device 1, Device 2a, and Device 2b.

[0057] Device 1 (may also be referred to as Type 1) Device 1 is a device type that consumes a peak power of 1 μW or less. Device 1 has an energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million), where Z is 10 to the power of x (x is an integer greater than or equal to 0). Device 1 does not have any amplification in either DL or UL. UL transmission in Device 1 is performed by backscattering an externally provided carrier wave (CW), i.e., an unmodulated wave.

[0058] Device 2a (also referred to as Type 2a) The device 2a is a device type that consumes a peak power of several hundred μW. The device 2a has an energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the power x (x is an integer equal to or greater than 0)). The device 2a also performs DL and / or UL amplification. The UL transmission in the device 2a is performed by backscattering in a CW provided from an external device.

[0059] Device 2b (also called Type 2b) Device 2b is a device type that consumes a peak power of several hundred μW. Device 2b has energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the power x (x is an integer equal to or greater than 0)). DL and / or UL amplification is performed in device 2b. UL transmission in device 2b is performed internally within device 2b. In other words, UL transmission in device 2b does not need to be performed by backscattering in CW provided from an external source.

[0060] <Candidate Topology> Next, we describe candidate topologies for CW / R2D / D2R transmission.

[0061] Fig. 8 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. Fig. 8 shows Topology 1A, Topology 1B, Topology 1C, Topology 1D, and Topology 1E as examples of candidate topologies.

[0062] As shown in Figure 8, in topologies 1A to 1E, CW / R2D communication signals (sometimes referred to as "R2D" in Figure 8 and below) / D2R communication signals (sometimes referred to as "D2R" in Figure 8 and below) can be sent and received to A-IoT devices.

[0063] In this embodiment, DL and R2D (reader to device) may be interchangeable, and UL and D2R (device to reader) may be interchangeable, where reader corresponds to BS and / or intermediate UE, and device corresponds to A-IoT device.

[0064] In Topology 1A, the node (first BS) that transmits the CW is different from the node (second BS) that receives the D2R communication signal transmitted by the A-IoT device via backscattering, and the node that transmits the CW is the same as the node that transmits the R2D communication signal. Also, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.

[0065] In Topology 1B, the node (BS) that transmits the CW, the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.

[0066] In Topology 1C, the node transmitting the CW (CW node) is different from the node transmitting the R2D communication signal (BS). Also, in Topology 1C, the node transmitting the CW is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in Topology 1C, the node transmitting the R2D communication signal is the same as the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS, (intermediate) UE, IAB node, NCR (network-controlled repeater) node, relay node, or other type of node.

[0067] In Topology 1D, the node (BS) that transmits the R2D communication signal is the same as the node that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, R in R2D is the same as R in D2R.

[0068] In Topology 1E, the node (first BS) that transmits the R2D communication signal is different from the node (second BS) that receives the D2R communication signal generated and transmitted by the A-IoT device. In other words, R in R2D is different from R in D2R.

[0069] Fig. 9 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 2. Fig. 9 shows Topology 2A, Topology 2B, Topology 2C, Topology 2D, and Topology 2E as examples of candidate topologies.

[0070] As shown in Figure 9, in topologies 2A to 2E, CW / R2D communication signals (referred to as "R2D" in Figure 9) / D2R communication signals (referred to as "D2R" in Figure 9) can be sent and received to A-IoT devices.

[0071] In Topology 2A, the node transmitting the CW (first intermediate UE) is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (second intermediate UE), and the node transmitting the CW is the same as the node transmitting the R2D communication signal. Also, the node transmitting the R2D communication signal is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.

[0072] In Topology 2B, the node that transmits the CW (intermediate UE), the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.

[0073] In Topology 2C, the node transmitting the CW (CW node) is different from the node transmitting the R2D communication signal (intermediate UE). Also, in Topology 1C, the node transmitting the CW is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in Topology 1C, the node transmitting the R2D communication signal is the same as the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR node / relay node / other type of node.

[0074] In Topology 2D, the node (intermediate UE) that transmits the R2D communication signal is the same as the node that receives the D2R communication signal generated and transmitted by the A-IoT device, i.e., R in R2D is the same as R in D2R.

[0075] In Topology 2E, the node (first intermediate UE) that transmits the R2D communication signal is different from the node (second intermediate UE) that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, R in R2D is different from R in D2R.

[0076] <Terminology> Here, we will explain the terms used in relation to the A-IoT mentioned above.

[0077] A-IoT device or device: a device included in an A-IoT system, having any of the multiple device types as described above.

[0078] Reader: D2R receiver The leader can be either a BS or a UE. The leader UE can be called an intermediate UE. The R2D transmitter and D2R receiver may be the same node or different nodes.

[0079] ·R2D: Abbreviation for Reader-to-Device Link. PRDCH: Physical R2D channel. D2R: Abbreviation for Device-to-Reader Link. PDRCH: Physical D2R channel.

[0080] ·DT traffic: Abbreviation for Device Terminated traffic. ·DT traffic is, for example, traffic that sends commands from a leader to a device and ends at the device.

[0081] ·DO-DTT traffic: Device Originated-Device Terminated Trigger ·DO-DTT traffic is, for example, "inventory" traffic.

[0082] · The timing acquisition signal / preamble / midamble / postamble / synchronization signal can be replaced with each other.

[0083] <Rel-19 compliant WID> A new WID (Work Item Description) "New Work Item: Solutions for Ambient IoT (Internet of Things) in NR" (RP-243326) (Non-Patent Document 6) was approved in Rel-19. This WID shows the guidelines for promoting the standardization of A-IoT technology in NR, and Chapter 4 is described as follows.

[0084] General scope Definitions provided in TR 38.848, TR 38.769, and decisions in the RAN working group in Rel-19 SI in the RAN WG are incorporated into this WI, and the following are exclusive general scopes: A. The overall goal is to standardize the following ambient IoT devices: Device 1: Peak power consumption ~1 μW, energy storage, RF envelope detector receiver, initial sampling frequency offset (SFO) up to 10 X ppm, no amplification of R2D and D2R within the device, D2R transmission of the device is backscattered against a carrier provided externally B. Deployment scenario 1 using topology 1 according to D1T1-B The licensed spectrum in C.FR1 operates in a frequency division duplex (FDD) scheme, with R2D being used in the downlink (DL) spectrum and D2R and CW being used in the uplink (UL) spectrum. D. Spectrum deployment in the band for NR and standalone spectrum deployment, A-IoT base station (BS) is installed indoors E. Traffic types DO-DTT, DT for rUC1 (indoor inventory) and rUC4 (indoor command) Waveform 1 carrier transmission only, no hopping, for the following cases based on F.TR 38.769 Regarding cases 1 to 4 of D1T1-B G.Proximity determination only according to Solution 1 of TR 38.769 (Un)availability of devices via H.TR 38.769 direction 1 only

[0085] Within a general scope, the following objectives are set: RAN1 range: PRDCH and PDRCH are the only physical channels in R2D and D2R, respectively. R2D and D2R signals Multiplexing / multiple connections in R2D are only TDMA (Time Division Multiple Access), while D2R is only TDMA and FDMA (Frequency Division Multiple Access). R2D only supports OOK (on-off keying)-4 modulation and provides one solution for CP processing, while D2R backscatter only supports OOK and BPSK (binary phase shift keying) modulation. R2D transmission only supports Manchester line code in TR 38.769 D2R transmission supports: Manchester line code or no line code in TR 38.769 (choose one) ·Corresponding small frequency shift method according to Option TR 38.769 R2D does not support FEC (forward error correction). D2R supports only convolutional coding with a generating polynomial according to TS 36.212 (unless RAN1 decides to use other generating polynomials according to RAN1#120bis). PRDCH and PDRCH support transmission without CRC (cyclic redundancy check) and support transmission with CRC according to the generating polynomials of 6-bit CRC and 16-bit CRC in TS 38.212 (unless RAN1 decides to use other generating polynomials according to RAN1#120bis). The decision of which CRC length to use or to use no CRC is made by RAN1. D2R supports physical layer repeated transmission (repetition). R2D does not support physical layer repeated transmission.

[0086] <Access Procedure for A-IoT Devices> In an A-IoT communication session, the access procedure for an A-IoT device (hereinafter also simply referred to as a device) is executed. As access procedures for A-IoT devices, two approaches, namely a two-step approach and a four-step approach, are being considered.

[0087] Figure 10 is a diagram showing an example of the access procedure for an A-IoT device. Figure 10 shows the signal exchange between one leader and one device. The horizontal axis of Figure 10 represents the time axis. Figure 10 shows an exchange including a two-step access procedure and a four-step access procedure.

[0088] In the two-step access procedure, the reader sends an A-IoT paging message. The A-IoT paging message corresponds to the first R2D transmission in an A-IoT communication session. The device that receives the A-IoT paging message sends a message called A-IoT Msg1 to the reader. In the two-step access procedure, A-IoT Msg1 contains information that identifies the device (e.g., device ID). A-IoT Msg1 may be considered a device ID report. The reader that receives A-IoT Msg1 sends a message called A-IoT Msg2 to the device. For example, the reader that receives A-IoT Msg1 sends A-IoT Msg2 addressed to the device identified by the device ID included in A-IoT Msg1. A-IoT Msg2 contains information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The two-step access procedure is then completed.

[0089] In the four-step access procedure, the reader sends an A-IoT paging message. A device that receives the A-IoT paging message sends a message called A-IoT Msg1 to the reader. In the four-step access procedure, A-IoT Msg1 contains a random ID. A-IoT Msg1 may be considered a random ID report. The reader that receives A-IoT Msg1 sends a message called A-IoT Msg2 to the device. For example, the A-IoT reader sends A-IoT Msg2, which contains the random ID contained in A-IoT Msg1. A-IoT Msg2 contains information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The device receives A-IoT Msg2 and sends A-IoT Msg3 to the reader. For example, if the random ID of the received A-IoT Msg2 matches the random ID of the sent A-IoT Msg1, the device sends A-IoT Msg3 to the reader. In the four-step access procedure, A-IoT Msg3 contains information that identifies the device (e.g., device ID). A-IoT Msg3 may be considered a device ID report. A reader that receives A-IoT Msg3 sends a response (e.g., R2D response). The four-step access procedure is then completed. However, in the four-step access procedure, a reader that receives A-IoT Msg3 does not have to send a response (e.g., R2D response).

[0090] For example, in an "inventory" use case such as checking the presence of an A-IoT device, each communication session includes only the above two-step access procedure or four-step access procedure. Note that the "inventory" use case is not limited to checking the presence of an A-IoT device.

[0091] For example, in the "inventory + command" use case, which includes checking the presence of an A-IoT device and issuing instructions to the A-IoT device, as shown in Figure 10, each communication session involves sending an R2D command message and a D2R response after the above two-step or four-step access procedure.

[0092] In addition, in exchanges including the access procedures shown in Figure 10, etc., a contention-based access procedure such as slotted-ALOHA may be applied at least to A-IoT Msg1.

[0093] In an A-IoT communication session, one A-IoT page may be sent to multiple devices. After receiving one A-IoT page, the multiple devices may continue with subsequent transmission / reception in the communication session. Note that the subsequent transmission / reception in the device may be at least one of sending A-IoT Msg1, receiving A-IoT Msg2, sending A-IoT Msg3, receiving an R2D response, receiving an R2D command message, and sending a D2R response, as shown in Figure 10.

[0094] In addition, in the exchanges including the access procedures shown in Figure 10 etc., A-IoT Paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3 may be abbreviated as Paging, Msg1, Msg2, Msg3, respectively. Furthermore, A-IoT Paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3 may be associated with names different from these names.

[0095] The message type may be any of A-IoT paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3, R2D response, R2D command message, and D2R response. The R2D response may be omitted. The message type may be interchangeably referred to as message. The message may be interchangeably referred to as signal or information. For example, message transmission / reception may be interchangeably referred to as signal transmission / reception. The R2D command message may be referred to as R2D data.

[0096] The following description will mainly focus on an example of a four-step access procedure and "inventory+command" communication. However, the present disclosure is not limited to this. The present disclosure may be applied to a two-step access procedure or to "inventory" communication. An example of "inventory+command" communication corresponds to an example in which a four-step access procedure is followed by transmission / reception of an R2D command message and a D2R response.

[0097] Also, in the following description, one or more steps (e.g., processes) may be omitted (or skipped). For example, as described above, in the case of a two-step approach, the transmission / reception of A-IoT Msg3 may be omitted. Also, as described above, in the case of "inventory" communication, the R2D command message and D2R response may be omitted.

[0098] It should be noted that any of the above message types may be transmitted by unicast, multicast, broadcast, or groupcast.

[0099] <Procedures based on the agreement> Rel-19 considers inventory and command use cases as well as DO-DTT and DT traffic, and for these use cases / traffic types, steps 1 and 2 below are considered.

[0100] 1. Inventory only Step A: The reader sends an A-IoT page to the device. Step B: The device sends its device ID to the reader (via Random Access (RA) or without RA).

[0101] 2. Inventory and command Step A: The reader sends an A-IoT page to the device. Step B: The device sends its device ID to the reader (via Random Access (RA) or without RA). Step C1: The reader sends data to the device (e.g., R2D command). Step C2: The corresponding device sends data (e.g., feedback) to the reader. Note that it is unclear whether step C2 is optional.

[0102] FIG. 11 is a related diagram in TR 38.769 (Non-Patent Document 7).

[0103] <Random Access (RA) based on agreements> Regarding random access, the following steps 1 and 2 are being considered:

[0104] 1. 4 steps (or 3 steps) (see Figure 12) A-IoT Msg1: The device sends its ID to the reader. The ID is a random ID generated by the device. The size of the random ID is fixed, 16 bits. A-IoT Msg2: The reader echoes the ID received in Msg1. A-IoT Msg3: The device sends its device ID and / or other upper layer data (upon upper layer request). If the device receives Msg2 containing the same random ID as Msg1, it considers the conflict resolution successful. "Msg4" (i.e., subsequent R2D transmissions after a D2R transmission) does not always need to be sent with random access. "Msg4" can be considered to handle Msg3 transmission failures (due to various reasons).

[0105] Step 2.2 (See Figure 13) A-IoT Msg1: The device transmits its device ID and / or other upper layer data (as requested by the upper layer). A random ID (fixed 16 bits) may additionally be included in Msg1. A-IoT Msg2: If Msg1 contains a random ID, the reader echoes the ID received in Msg1.

[0106] In addition, at the 3GPP RAN2#126 and #127 meetings, the following procedures were agreed upon in relation to the above procedures.

[0107] [3GPP RAN2#126 Agreement on "4-Step" RA] 1. A-IoT Msg1: The device sends its ID to the reader. The ID is a random ID generated by the device (how it is generated is undetermined, e.g. randomly or based on the device ID). The ID size is undetermined. This does not exclude other information agreed upon in RAN1. 2. A-IoT Msg2: The reader echoes the ID received in Msg1. Msg2 may contain further information based on the agreement of RAN1. 3. A-IoT Msg3: The device sends its device ID and / or other upper layer data (as requested by the upper layer). 4. If the device receives Msg2 containing the same random ID as Msg1, it considers the contention resolution successful. RAN2 assumes that the size of the random ID in Msg1 is sufficient for contention resolution purposes. 5. "Msg4" (i.e., subsequent R2D transmissions after a D2R transmission) does not always need to be transmitted via random access. "Msg4" can be considered to handle Msg3 transmission failures (due to various reasons). The use / existence of "Msg4" can be further discussed. RAN2 does not use the term "Msg4" for further discussion of random access.

[0108] [3GPP RAN2#126 Agreement on 2-Step CB RA] 1. A-IoT Msg1: The device sends its device ID and / or other higher layer data (as required by the higher layer). It is undetermined what the device ID will be. It is undetermined whether an additional random ID is required. This does not preclude other information agreed upon in RAN1. 2. A-IoT Msg2: The reader may echo some information from Msg1. It is undetermined what that some information is. The usage / existence of "Msg2" can be further discussed.

[0109] [3GPP RAN2#127 Agreement (3-step CBRA)] For 3-step CBRA (Contention-Based Random Access) support, the fixed random ID size is 16 bits. The ID is generated randomly. -Indication of D2R failure / success will be considered. It is not yet decided whether the indication of D2R failure / success will be implicitly or explicitly indicated, and in what cases it will be required. It is also not yet decided whether the indication of D2R failure / success will only be applied in some cases.

[0110] [3GPP RAN2#127 Agreement (2-step CBRA)] For 2-step CBRA, the RAN2 specification supports Msg2. Whether it is required is up to the reader. It is not yet decided when it is required. For 2-step CBRA (when Msg2 is required), the random ID (fixed 16 bits) is also included in A-IoT Msg1 and echoed in A-IoT Msg2. If there are devices that only support 2-step RA, it is not yet decided whether other optimizations will be required for such devices. In contention-free access, A-IoT devices will directly send higher layer data (e.g., device ID) in the first D2R message after being triggered (i.e., skipping contention resolution Msg1 / 2). It remains to be determined whether short AS IDs will also be included in the message, and what type of IDs will be included for scheduling purposes. · It is yet to be determined if the leader will assign AS IDs for scheduling purposes.

[0111] <Collision avoidance algorithm> In contention-based random access, the following mechanism may be used to avoid collisions between devices: Note that in the following description, Msg1 may be written as Msg.1. Q algorithm TDMA of Msg.1 (hereinafter sometimes referred to as TDMA_Msg.1)

[0112] In the Q algorithm, the device determines whether to respond to the R2D A-IoT paging message based on the counter Q. Note that the R2D A-IoT paging message may be referred to as the R2D_A-IoT paging message.

[0113] In TDMA_Msg.1, one R2D_A-IoT message determines M (M is an integer greater than 1) time domain resources for transmitting Msg.1, and the device selects one time domain resource from the multiple time domain resources and transmits Msg.1 using the selected resource. Note that one R2D_A-IoT message determining M time domain resources for transmitting Msg.1 may correspond to determining M time domain resources for transmitting Msg.1 based on information (or instructions) included in one R2D_A-IoT message and / or the transmission / reception timing of one R2D_A-IoT message. Furthermore, one time domain resource is one resource having a specific time width. The specific time width may be predefined, instructed by the reader, or set by a parameter of a higher layer. One time domain resource may be expressed as a slot, a frame, a symbol, or the like, and one time domain resource may correspond to at least one of two or more slots, two or more frames, and two or more symbols.

[0114] However, depending on the device's capability, there may be devices that cannot support TDMA_Msg.1. Devices that cannot support TDMA_Msg.1 only support one time domain resource for Msg.1 transmission determined from one R2D_A-IoT paging message. In other words, there may be devices in the A-IoT system that only support one time domain resource for Msg.1 transmission determined from one R2D_A-IoT paging message.

[0115] Even when considering devices that cannot support TDMA_Msg.1 as described above, it may be possible for the reader to use TDMA_Msg.1. For example, a device that does not support TDMA_Msg.1 transmits on the first time domain resource determined from the R2D_A-IoT paging message. The first time domain resource may be the earliest time domain resource.

[0116] Figure 14 is a diagram showing an example of TDMA_Msg.1. Figure 14 shows an example of an R2D_A-IoT paging message (A-IoT paging in Figure 14) between a reader and a device, and an example of time domain resources for transmitting Msg.1 determined from the R2D_A-IoT paging message. The horizontal axis in Figure 14 represents the time axis.

[0117] In Figure 14, if a device supports TDMA_Msg.1, one R2D_A-IoT message determines four time domain resources for transmitting Msg.1. In Figure 14, the four time domain resources determined from the R2D_A-IoT paging message #1 are written as resource #1 to resource #4. In the example of Figure 14, a device that supports TDMA_Msg.1 selects one time domain resource from the four time domain resources and transmits Mg.1 on the selected resource. Also in Figure 14, if a device does not support TDMA_Msg.1, it transmits Msg.1 on the first time domain resource determined from the R2D_A-IoT paging message.

[0118] In the example of Figure 14, when a device that supports TDMA_Msg.1 responds to R2D_A-IoT paging message #1, it selects one time domain resource from resource #1 to resource #4 and transmits Msg.1 on the selected resource. Also, in the example of Figure 14, when a device that does not support TDMA_Msg.1 responds to R2D_A-IoT paging message #1, it transmits Msg.1 on resource #1, which corresponds to the first time domain resource determined from the R2D_A-IoT paging message.

[0119] Here, multiple paging messages are transmitted for the same A-IoT traffic. Each paging message may be defined to have a different name and / or a different message. For example, in FIG. 14, A-IoT paging #1 to A-IoT paging #3 are transmitted for the same A-IoT traffic, and each of A-IoT paging #1 to A-IoT paging #3 may be defined to have a different name and / or a different message.

[0120] In the Q algorithm, the following four steps, Step 1 to Step 4, are executed.

[0121] Step 1: The value of Q is indicated in the R2D_A-IoT paging message.

[0122] Step 2: The device sets the initial value C0 of the counter to a value randomly selected from 0 to P, where P=2 Q Obtained at -1.

[0123] Step 3: Each time the device receives an R2D_A-IoT paging message, it decrements the counter by 1. That is, the counter value at time i is decremented by C i Then, the counter value C at time i i and the counter C at the time i-1 just before that i-1 The relationship between i =C i-1 - Meets 1.

[0124] Step 4: When the counter reaches 0, e.g., counter C i = 0, the device responds to the R2D_A-IoT paging message. Responding to the R2D_A-IoT paging message corresponds to the device sending Msg.1.

[0125] In step 1 above, the value of Q is indicated in the R2D_A-IoT paging message, and in step 2, the device sets the initial value C0 of the counter to P=2. Q The R2D_A-IoT paging message indicates the range of candidate values ​​for the initial value of the counter C0. Note that both Q and P indicate the range of candidate values ​​for the initial value of the counter C0.

[0126] The Q algorithm having the four steps described above allows for the following variations:

[0127] In a variation of step 1, the value of Q may be a fixed value. Alternatively, in a variation of step 1, the value of Q may be implicitly determined based on one or more other parameters, which may be, for example, parameters included in a message other than the R2D_A-IoT paging message.

[0128] In a variation of step 2, the value of P may be indicated in the R2D_A-IoT paging message. Alternatively, in a variation of step 2, the value of P may be fixed. Alternatively, in a variation of step 2, the value of P may be implicitly determined based on one or more other parameters. Note that in a variation of step 2, since the value of P is indicated (or determined), the value of Q does not need to be indicated (or determined).

[0129] In a variation of step 3, each time the device receives an R2D_A-IoT paging message, it decrements the counter by D, where D is an integer greater than or equal to 1. That is, the counter value at time i is decremented by C i Then, the counter value C at time i i and the counter C at the time i-1 just before that i-1 The relationship between i =C i-1- Satisfies D, where D may be the number M of time domain resources for transmitting Msg.1 determined based on one R2D_A-IoT paging message.

[0130] In a variation of step 4, if the counter reaches E, for example, counter C i = E, the device responds to the R2D_A-IoT paging message. Note that E is an integer equal to or greater than 0. Responding to the R2D_A-IoT paging message is equivalent to the device sending Msg.1. The device may also respond to the R2D_A-IoT paging message when the counter is equal to or less than E.

[0131] In paging variations, the content of the first R2D_A-IoT paging message may be different from the content of R2D_A-IoT paging messages after the first R2D_A-IoT paging message.

[0132] In a variation of step 3 and / or step 4, the serial number of the R2D_A-IoT paging message is indicated in the R2D_A-IoT paging message, and if the indicated serial number is the same as the initial value C0 of the counter, the device responds to the R2D_A-IoT paging message. Note that responding to the R2D_A-IoT paging message corresponds to the device sending Msg.1. Note that in this variation, it is not necessary to decrement the counter value by 1 each time the device receives an R2D_A-IoT paging message, as in step 3 above.

[0133] <Considerations> In this embodiment, the following points are assumed. The reader handles both devices that support TDMA_Msg.1 and devices that do not support TDMA_Msg.1. For example, the reader communicates with and provides services to both devices that support TDMA_Msg.1 and devices that do not support TDMA_Msg.1. All devices decide whether to respond to the R2D_A-IoT paging message based on the Q algorithm. M time domain resources for Msg.1 transmission are determined from one R2D_A-IoT paging message, where M can be an integer greater than 1. Devices that do not support TDMA_Msg.1 will transmit Msg.1 in the first time domain resource determined from the R2D_A-IoT paging message. A device that supports TDMA_Msg.1 selects one time domain resource from the M time domain resources and transmits Msg.1 on the selected resource.

[0134] For example, in a device that does not support TDMA_Msg.1, Msg.1 is transmitted at a specific time after the R2D_A-IoT paging message. That is, the first time domain resource determined from the R2D_A-IoT paging message corresponds to a specific time after the R2D_A-IoT paging message. Here, the specific time is defined by Tmin, which indicates a minimum time, and Tmax, which indicates a maximum time. For example, the specific time is included in the time between Tmin after receiving the R2D_A-IoT paging message and Tmax after receiving the R2D_A-IoT paging message. Alternatively, the specific time starts at a start timing T hours after receiving the R2D_A-IoT paging message.

[0135] Under the above assumptions, among the M time domain resources for transmitting Msg.1, devices that support TDMA_Msg.1 can transmit using time domain resources other than the first time domain resource, whereas the first time domain resource can be used by both devices that support TDMA_Msg.1 and devices that do not support TDMA_Msg.1. In other words, among the M time domain resources for transmitting Msg.1, the collision probability of the first time domain resource is higher than the collision probability of the time domain resources other than the first time domain resource. On the other hand, if the collision probability of the first time domain resource is reduced, signal collisions between devices that support TDMA_Msg.1 will increase in the time domain resources other than the first time domain resource. Therefore, it is desirable to adjust the collision probability of multiple time domain resources, including the first time domain resource.

[0136] Therefore, in this embodiment, a method for suppressing an increase in signal collisions between devices will be described. For example, when multiple devices using different methods for determining time domain resources each determine a time domain resource for signal transmission, the increase in signal collisions between the devices is suppressed by adjusting the time domain resources so that the determined time domain resources do not overlap between the devices.

[0137] In this embodiment, "R2D," "R2D signal," "R2D message," and "R2D message type" may be interchangeable. Also, in this embodiment, "D2R," "D2R signal," "D2R message," and "D2R message type" may be interchangeable.

[0138] The items described in the following proposals may be combined as appropriate as long as no contradictions arise.

[0139] In the following suggestions, the options may be combined as appropriate.

[0140] In the proposals below, different options may be applied on a case-by-case basis.

[0141] In the following proposal, the indication / configuration may be transmitted by physical (PHY) layer control information or higher layer payload (e.g., MAC (Medium Access Control) layer control information, Msg0 (paging), Msg2 (RAR (Random Access Response)), Msg4, unicast data, etc.).

[0142] In the following proposals, the instructions on the R2D may have the same meaning as above.

[0143] In the following proposal, the indication / configuration may be transmitted by the PRDCH or the R2D timing acquisition signal (preamble / midamble / postamble) / synchronization signal.

[0144] In the following proposal, a slot may be a 1 ms time interval (i.e., one slot in OFDM) or a slot in slotted ALOHA, or any other time domain unit consisting of one or more symbols.

[0145] In the following proposal, a symbol may be one OFDM symbol, M chips for OOK, or one modulation symbol for PSK / FSK.

[0146] In the following proposals, different alternatives / options may apply to R2D and D2R.

[0147] In the suggestions below, different alternatives / options may apply depending on the device type.

[0148] In the following proposals, different alternatives / options may apply to different connection topologies.

[0149] In the following proposal, different alternatives / options may be applied to different R2D / D2R channels (PRDCH: PHY channel for R2D control, PDRCH: PHY channel for D2R control).

[0150] In the following proposal, different alternatives / options may apply for different R2D / D2R information / formats / commands (R2D data, R2D control, R2D system information, R2D information triggering contention-based access, D2R data, D2R control, D2R ACK / NACK response, D2R response in contention-based access (Msg1 / Msg3)).

[0151] Hereinafter, "CW / R2D / D2R transmission" may also be referred to as communication in a wireless communication system including a device, communication of a device, communication with a device, communication involving a device, etc.

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

[0153] <Premise of proposal> In this embodiment, the above-mentioned Q algorithm is used as a premise.

[0154] Furthermore, in this embodiment, TDMA_Msg.1 is used as a premise. In TDMA_Msg.1, one R2D_A-IoT message determines M (M is an integer greater than 1) time domain resources for transmitting Msg.1, and the device selects one time domain resource from the multiple time domain resources and transmits Msg.1 using the selected resource.

[0155] In this embodiment, there are two types of devices: device type X and device type Y.

[0156] Device type X is a device that does not support TDMA_Msg.1. Device type X transmits Msg.1 in one time domain resource for Msg.1 transmission determined from one R2D_A-IoT paging message, where the one determined time domain resource corresponds to the first time domain resource of M time domain resources for Msg.1 transmission.

[0157] For example, in a device that does not support TDMA_Msg.1, Msg.1 is transmitted at a specific time after the R2D_A-IoT paging message. That is, the first time domain resource determined from the R2D_A-IoT paging message corresponds to a specific time after the R2D_A-IoT paging message. Here, the specific time is defined by a minimum time Tmin and a maximum time Tmax. For example, the specific time is included between the time Tmin has elapsed since receiving the R2D_A-IoT paging message and the time Tmax has elapsed since receiving the R2D_A-IoT paging message. Alternatively, the specific time starts at a start timing T hours after receiving the R2D_A-IoT paging message.

[0158] Device type Y is a device that supports TDMA_Msg.1. Device type Y selects one time domain resource from the M time domain resources and transmits Msg.1 in the selected resource.

[0159] <Proposal 1> In Proposal 1, different values ​​of Q or different values ​​of P are used in the Q algorithm for device type X and device type Y. In other words, the values ​​of Q or P are used independently for device type X and device type Y. Since the values ​​of Q and P are both parameters that determine the range of candidate values ​​for the initial value of the counter, in Proposal 1, the range of candidate values ​​for the initial value of the counter of device type X is determined independently from the range of candidate values ​​for the initial value of the counter of device type Y in the Q algorithm.

[0160] For example, a larger Q factor is used for device type X and a smaller Q factor is used for device type Y. Illustratively, the Q factor for device type X may be larger than the Q factor for device type Y.

[0161] In Proposal 1, the following operations of Steps 1 to 4 are performed as an example of an extended Q algorithm. Note that Step 2 is divided into Step 2-1 and Step 2-2 depending on the device type.

[0162] Step 1: Two values ​​of Q are indicated in the R2D_A-IoT paging message. The two values ​​of Q are referred to as Q1 and Q2. Both values ​​may be explicitly indicated. Alternatively, one of the two values ​​may be explicitly indicated, and the other may be associated with the indicated value. For example, one of the indicated values ​​may be obtained by performing a specific operation on the other value. The specific operation may be, for example, adding an offset, multiplying a coefficient, etc.

[0163] Step 2-1: Device type X sets the initial value of the counter to a value randomly selected from the range of 0 to P1. P1 is, for example, P1=2. Q1 It is represented as -1.

[0164] Step 2-2: Device type Y sets the initial value of the counter to a value randomly selected from the range of 0 to P2. For example, P2=2 Q2 It is represented as -1.

[0165] Step 3: Each time the device receives an R2D_A-IoT paging message, it decrements the counter by one.

[0166] Step 4: When the counter reaches 0, the device responds to the R2D_A-IoT paging message. Responding to the R2D_A-IoT paging message corresponds to the device sending Msg.1.

[0167] In Proposal 1, any of the variations of the Q algorithm described above may be applied.

[0168] For example, when the variation of the Q algorithm described above is applied to step 1, at least one of the values ​​of Q1 and Q2 may be a fixed value. Alternatively, at least one of the values ​​of Q1 and Q2 may be implicitly determined based on one or more other parameters. Note that the one or more other parameters may be, for example, parameters included in a message other than the R2D_A-IoT paging message.

[0169] For example, when the variation of the Q algorithm described above is applied to step 2 (steps 2-1 and 2-2), at least one of the values ​​of P1 and P2 may be indicated in the R2D_A-IoT paging message. Alternatively, at least one of the values ​​of P1 and P2 may be fixed. Alternatively, at least one of the values ​​of P1 and P2 may be implicitly determined based on one or more other parameters. Note that if the value of P1 is indicated (or fixed), the value of Q1 does not have to be indicated (or fixed), and if the value of P2 is indicated (or fixed), the value of Q2 does not have to be indicated (or fixed).

[0170] For example, if the variation of the Q algorithm described above is applied to step 3, each time a device receives an R2D_A-IoT paging message it decrements the counter value by D, where D is an integer greater than or equal to 1. The value of D may be different for each device type. For example, device type X decrements the counter value by D1 each time it receives an R2D_A-IoT paging message, and device type Y decrements the counter value by D2 each time it receives an R2D_A-IoT paging message, where D1 and D2 are each integers greater than or equal to 1 and may be different from each other.

[0171] For example, if the variation of the Q algorithm described above is applied to step 4, when the counter reaches E, e.g., counter C i = E, the device responds to the R2D_A-IoT paging message. E is an integer equal to or greater than 0. The value of E may differ for each device type. For example, for device type X, when the counter reaches E1, for example, counter C i = E1, the device type Y responds to the R2D_A-IoT paging message, and when the counter becomes E2, for example, the counter C i = E2, the R2D_A-IoT responds to the paging message. Note that E1 and E2 are each an integer greater than or equal to 1, and E1 and E2 may be different from each other.

[0172] According to Proposal 1, the probability that device type X transmits in a certain time domain resource is 1 / P1, and the probability that device type Y transmits in a certain time domain resource is 1 / (P2×M). By setting P1 and P2 to different values, the collision probability of time domain resources can be adjusted between time domain resources, thereby suppressing an increase in signal collisions between devices. For example, by setting P1 and P2 to different values, the collision probability of time domain resources can be made approximately equal between multiple time domain resources.

[0173] <Proposal 2> In Proposal 2, different time domain resources are determined from the R2D_A-IoT paging message for transmitting Msg.1 for device type X and device type Y. In other words, independent time domain resources are determined from the R2D_A-IoT paging message for transmitting Msg.1 for device type X and device type Y. For example, the time domain resources determined from the R2D_A-IoT paging message for device type X may be different from the time domain resources determined from the R2D_A-IoT paging message for device type Y.

[0174] In Proposal 2, device type X transmits within a specific time window after the R2D_A-IoT paging message or at a timing T after the R2D_A-IoT paging message. Here, the specific time window is defined by Tmin, which indicates a minimum time, and Tmax, which indicates a maximum time. For example, the specific time window is the time between the time Tmin has elapsed since receiving the R2D_A-IoT paging message and the time Tmax has elapsed since receiving the R2D_A-IoT paging message. Hereinafter, the specific window defined by Tmin, which indicates a minimum time, and Tmax, which indicates a maximum time, will be referred to as time window [Tmin, Tmax].

[0175] In Proposal 2, for device type Y, any of the following Alternatives (Alt.) may be applied:

[0176] <Alt.1 of Proposal 2> In Alt.1 of Proposal 2, M time domain resources for Msg.1 transmission are determined from one R2D_A-IoT paging message, where the first of the M time domain resources is within a time window [Tmin, Tmax] after the R2D_A-IoT paging message or after time T after the R2D_A-IoT paging message, i.e., the first of the M time domain resources is the same as the time domain resource used by device type X.

[0177] In Alt. 1 of Proposal 2, device type Y does not select the first time domain resource for transmitting Msg. 1. For example, in Alt. 1 of Proposal 2, device type Y selects one time domain resource from the M-1 time domain resources other than the first time domain resource.

[0178] Figure 15 is a diagram showing an example of Alt.1 of Proposal 2. Figure 15 shows an example of an R2D_A-IoT paging message (A-IoT paging in Figure 15) between a reader and a device, and an example of time domain resources for transmitting Msg.1 determined from the R2D_A-IoT paging message. The horizontal axis in Figure 15 represents the time axis.

[0179] In Figure 15, if a device supports TDMA_Msg.1, one R2D_A-IoT message determines four time domain resources for transmitting Msg.1. In Figure 15, the four time domain resources determined from the R2D_A-IoT paging message #1 are written as resource #1 to resource #4. In the example of Figure 15, a device that supports TDMA_Msg.1 selects one time domain resource from three of the four time domain resources, excluding the first time domain resource, and transmits Mg.1 on the selected resource. Also, in Figure 15, if a device does not support TDMA_Msg.1, it transmits Msg.1 on the first time domain resource determined from the R2D_A-IoT paging message.

[0180] In the example of Figure 15, when a device that supports TDMA_Msg.1 responds to R2D_A-IoT paging message #1, it selects one time domain resource from resources #2 to #4, excluding resource #1, and transmits Mg.1 on the selected resource. Also, in the example of Figure 15, when a device that does not support TDMA_Msg.1 responds to R2D_A-IoT paging message #1, it transmits Mg.1 on resource #1, which corresponds to the first time domain resource determined from the R2D_A-IoT paging message. In this case, collision is avoided between one device that supports TDMA_Msg.1 and one device that does not support TDMA_Msg.1, at least on resource #1.

[0181] The reader may instruct whether the device type Y may select the first time domain resource for transmitting Msg.1. For example, the reader may instruct via the R2D whether the device type Y may select the first time domain resource for transmitting Msg.1, or may instruct in an R2D_A-IoT paging message whether the device type Y may select the first time domain resource for transmitting Msg.1. If the reader instructs that the device type Y may select the first time domain resource for transmitting Mg.1, the device type Y selects one time domain resource from the M time domain resources including the first time domain resource. If the reader does not instruct that the device type Y may select the first time domain resource for transmitting Mg.1, the device type Y selects one time domain resource from the M-1 time domain resources other than the first time domain resource. Note that the case where the reader does not instruct that the device type Y may select the first time domain resource for transmitting Mg.1 may correspond to the case where the reader instructs that the device type Y should not select the first time domain resource for transmitting Mg.1.

[0182] <Alt.2 of Proposal 2> In Alt.2 of Proposal 2, M time domain resources for Msg.1 transmission are determined from one R2D_A-IoT paging message, where the first of the M time domain resources is within a time window [Tmin', Tmax'] after the R2D_A-IoT paging message or after time T' after the R2D_A-IoT paging message. That is, the first of the M time domain resources may be different from the time domain resource used by device type X.

[0183] In Alt. 2 of Proposal 2, device type Y selects one time domain resource from M time domain resources other than the time domain resources used by device type X, where the M time domain resources do not include the time domain resources used by device type X.

[0184] Figure 16 is a diagram showing an example of Alt.2 of Proposal 2. Figure 16 shows an example of an R2D_A-IoT paging message (A-IoT paging in Figure 16) between a reader and a device, and an example of time domain resources for transmitting Msg.1 determined from the R2D_A-IoT paging message. The horizontal axis in Figure 16 represents the time axis.

[0185] In the example of FIG. 16, the time domain resource used by device type X is one time domain resource starting from time T of the R2D_A-IoT paging message. The one time domain resource starting from time T of the R2D_A-IoT paging message is resource #1. Also in the example of FIG. 16, the time domain resource used by device type Y is three time domain resources starting from time T' of the R2D_A-IoT paging message. The three time domain resources starting from time T' of the R2D_A-IoT paging message are resource #2 to resource #4. Here, T, which determines the time domain resource of device type X, is different from T', which determines the time domain resource of device type Y. For example, the relationship T'≧T+(duration of one time domain resource) holds.

[0186] In Figure 16, if a device supports TDMA_Msg.1, that is, if it is device type Y, the device selects one time domain resource from the three time domain resources starting from time T' of the R2D_A-IoT paging message and transmits Mg.1 in the selected resource. Also in Figure 16, if a device does not support TDMA_Msg.1, that is, if it is device type X, it transmits Mg.1 in one time domain resource starting from time T of the R2D_A-IoT paging message. In this case, collision is avoided between one device that supports TDMA_Msg.1 and one device that does not support TDMA_Msg.1 in one time domain resource starting from time T of the R2D_A-IoT paging message.

[0187] In addition, in Alt.2 of Proposal 2, the same value may be specified for Tmin' and Tmin. The same value may be specified for Tmax' and Tmax. The same value may be specified for T' and T. In such an indication of the same value, the first time domain resource among the M time domain resources may be the same as the time domain resource used by device type X.

[0188] <Alt.3 of Proposal 2> In Alt. 3 of Proposal 2, X time domain resources for Msg.1 transmission are determined from one R2D_A-IoT paging message, where the first of the M time domain resources is within a time window [Tmin, Tmax] after the R2D_A-IoT paging message or after time T after the R2D_A-IoT paging message, i.e., the first of the M time domain resources is the same as the time domain resource used by device type X.

[0189] In Alt. 3 of Proposal 2, device type Y selects one time domain resource from M time domain resources, where in Alt. 3 of Proposal 2, the probability of selecting the first time domain resource is different from the probability of selecting each of the M−1 time domain resources other than the first time domain resource. For example, the probability of selecting the first time domain resource is lower than the probability of selecting each of the M−1 time domain resources other than the first time domain resource.

[0190] For example, the probability of selecting the first time-domain resource P f P f = 1 / α × M, where P is the probability of selecting each of the M − 1 time-domain resources other than the first one. N P N ={1-1 / (α×M)} / (M-1), where α is a coefficient for adjusting the probability, and may be a value equal to or greater than 1, or may be a value greater than 0, for example.

[0191] Note that the probability of selecting the first time domain resource may be indicated by another device (e.g., a reader) or may be indicated by the R2D. For example, the probability of selecting the first time domain resource may be included in the R2D_A-IoT paging message. In the above example, the probability of selecting the first time domain resource is represented by α, but the probability of selecting the first time domain resource may be represented by another value (e.g., an offset value added to or subtracted from the probability instead of the coefficient α).

[0192] Note that one candidate value of α may be 1. When α=1, the M time domain resources are selected with equal probability.

[0193] According to Proposal 2, the collision probability of time domain resources can be adjusted between time domain resources, which can prevent an increase in signal collisions between devices. For example, the collision probability of time domain resources can be made approximately equal between multiple time domain resources.

[0194] Note that Proposal 2 described above may be used together with Proposal 1. For example, when Proposal 1 and Alt. 2 of Proposal 2 are combined, Proposal 1 allows different Q values ​​or different P values ​​to be used for device type X and device type Y in the Q algorithm, and when device type Y responds to an R2D_A-IoT paging message, device type Y selects one time domain resource from M time domain resources other than the time domain resources used by device type X.

[0195] Furthermore, when Proposal 1, in which P1 and P2 are used in the Q algorithm, is combined with Alt. 2 of Proposal 2, the probability that device type X transmits in a certain time domain resource is 1 / P1, and the probability that device type Y transmits in a certain time domain resource is 1 / (P2 × M). In this case, by appropriately setting P1, P2, and M, the collision probability of time domain resources can be adjusted between time domain resources, thereby suppressing an increase in signal collisions between devices. For example, the collision probability of time domain resources can be made approximately equal between multiple time domain resources.

[0196] <Proposal 3> In Proposal 3, different R2D_A-IoT paging messages trigger random access for device type X and device type Y. For example, the R2D_A-IoT paging message that triggers random access for device type X is different from the R2D_A-IoT paging message that triggers random access for device type Y. The R2D_A-IoT paging message that triggers random access for device type X is specified independently from the R2D_A-IoT paging message that triggers random access for device type Y.

[0197] In the following, for illustrative purposes, the two R2D_A-IoT paging messages are denoted as R2D_A-IoT paging message x and R2D_A-IoT paging message y. R2D_A-IoT paging message x triggers random access for device type X, and R2D_A-IoT paging message y triggers random access for device type Y.

[0198] Figure 17 is a diagram showing an example of Proposal 3. Figure 17 shows device #1 receiving R2D_A-IoT paging message x from leader #1, and device #2 receiving R2D_A-IoT paging message y from leader #2. R2D_A-IoT paging message x and R2D_A-IoT paging message y correspond to A-IoT paging x and A-IoT paging y in Figure 17, respectively.

[0199] Note that Figure 17 does not intend that the R2D_A-IoT paging message x and the R2D_A-IoT paging message y are transmitted at the same time. The R2D_A-IoT paging message x and the R2D_A-IoT paging message y may be transmitted at different times. Also, Figure 17 shows an example in which the reader that transmits the R2D_A-IoT paging message x and the reader that transmits the R2D_A-IoT paging message y are different, but the reader that transmits the R2D_A-IoT paging message x and the reader that transmits the R2D_A-IoT paging message y may be the same. In other words, one reader may transmit the R2D_A-IoT paging message x and the R2D_A-IoT paging message y.

[0200] When an R2D_A-IoT paging message x is received, device type X responds to the paging message, and device type Y does not respond. Note that when an R2D_A-IoT paging message x is received, both device types X and Y may respond.

[0201] When an R2D_A-IoT paging message y is received, device type Y responds to the paging message and device type X does not respond.

[0202] In Proposal 3, the counter decrement performed by the Q algorithm may be performed for R2D_A-IoT paging message x and R2D_A-IoT paging message y. For example, the counter decrement for at least one of device type X and device type Y is performed for R2D_A-IoT paging message x and R2D_A-IoT paging message y.

[0203] Alternatively, in Proposal 3, the counter decrement performed in the Q algorithm may be performed only for the associated paging message (e.g., either R2D_A-IoT paging message x or R2D_A-IoT paging message y). For example, the counter decrement for device type X is performed for R2D_A-IoT paging message x but not for R2D_A-IoT paging message y. For example, the counter decrement for device type Y is performed for R2D_A-IoT paging message y but not for R2D_A-IoT paging message x.

[0204] A time domain resource for one Msg.1 transmission is determined from the R2D_A-IoT paging message x, and two or more Msg.1 time resources are determined from the R2D_A-IoT paging message y.

[0205] The paging message type may be indicated in the R2D payload of L1 (layer 1) and / or higher layers.

[0206] The paging message type may be one of two types, for example, an R2D_A-IoT paging message x that triggers random access for device type X, or an R2D_A-IoT paging message y that triggers random access for device type Y.

[0207] The paging message type may be implicitly determined instead of being explicitly indicated. For example, the paging message type may be implicitly determined by the number of Msg.1 time domain resources indicated in the paging message. For example, if one time domain resource is indicated in the R2D_A-IoT paging message, the R2D_A-IoT paging message is determined to be R2D_A-IoT paging message x. For example, if two or more time domain resources are indicated in the R2D_A-IoT paging message, the R2D_A-IoT paging message is determined to be R2D_A-IoT paging message y.

[0208] Based on the paging ID, the paging message type may be implicitly determined.

[0209] While the above example shows two types of paging message, the present disclosure is not limited to this. The paging message type may be one of three types: R2D_A-IoT paging message x that triggers random access for device type X; R2D_A-IoT paging message y that triggers random access for device type Y; and R2D_A-IoT paging message z that triggers random access for both device type X and device type Y. Both device type X and device type Y may respond to R2D_A-IoT paging message z that triggers random access for both device type X and device type Y. In both device type X and device type Y, the counter decrement performed by the Q algorithm may be performed for R2D_A-IoT paging message z.

[0210] <Variation of Proposal 3> In a variation of Proposal 3, as an extension of the Q algorithm, the serial number of the R2D_A-IoT paging message is indicated in the R2D_A-IoT paging message, and if the indicated serial number is the same as the initial value C0 of the counter, the device responds to the R2D_A-IoT paging message. In addition, in a variation of Proposal 3, the value of the initial value C0 of the applicable counter is different for device type X and device type Y.

[0211] In a variation of proposal 3, one of the following options applies to the set of values ​​for C0 for device type X and device type Y, respectively:

[0212] <Option 1 of variation of Proposal 3> In option 1, separate sets of C0 values ​​are applied to device type X and device type Y. The set of C0 values ​​for device type X is set separately from the set of C0 values ​​for device type Y. For example, set #A of C0 values ​​is applicable only to device type X, and set #B of C0 values ​​is applicable only to device type Y. Note that set #A of C0 values ​​= {a1, a2,} and set #B of C0 values ​​= {b1, b2,}. Device type X selects the initial value C0 of the counter from the set of C0 values ​​for device type X. Device type Y selects the initial value C0 of the counter from the set of C0 values ​​for device type Y. For example, if the set of C0 values ​​for device type X is a set of odd numbers and the set of C0 values ​​for device type Y is a set of even numbers, C0 is always odd for device type X and always even for device type Y.

[0213] Figure 18 is a diagram showing an example of a variation of Proposal 3. Figure 18 shows device #1 and device #2 receiving an R2D_A-IoT paging message from reader #1. Note that A-IoT paging #a1 in Figure 18 is referred to as R2D_A-IoT paging message #a1, A-IoT paging #b1 is referred to as R2D_A-IoT paging message #b1, and A-IoT paging #a2 is referred to as R2D_A-IoT paging message #a2. Note that a1, b1, and a2 correspond to the serial numbers of the R2D_A-IoT paging messages. The serial numbers correspond to identification numbers that identify the R2D_A-IoT paging messages. a1 and a2 are serial numbers included in the above set #A, and b1 is a serial number included in the above set #B.

[0214] In the example of Figure 18, device #1 is device type X and device #2 is device type Y. When option 1 of the variation of proposal 3 is applied, only device #1 can respond to A-IoT paging message #a1 and A-IoT paging message #a2 because the serial numbers a1 and a2 indicated by R2D_A-IoT paging messages #a1 and #a2 are included in the set #A of C0 values ​​applicable only to device type X. For example, if device #1 sets the value of C0 of the counter to a2, device #1 responds to A-IoT paging message #a2. Note that in this case, device #1 does not respond to A-IoT paging message #a1.

[0215] Also, in the example of Figure 18, when option 1 of the variation of proposal 3 is applied, only device #2 can respond to A-IoT paging message #b1 because the serial number b1 indicated by R2D_A-IoT paging message #b1 is included in set #B of C0 values ​​that are applicable only to device type Y. For example, if device #2 sets the value of C0 of the counter to b1, device #2 will respond to A-IoT paging message #b1.

[0216] <Option 2-1 of Proposal 3 Variation> In option 2-1, C0 value set #A is applicable only to device type X, and C0 value set #B is applicable to both device type X and device type Y. Note that C0 value set #A = {a1, a2,} and C0 value set #B = {b1, b2,}. Note that at least one value included in either C0 value set #A or set #B may or may not be included in the other set.

[0217] Option 2-1 will be explained with reference to Figure 18. In option 2-1, set #A is applicable only to device type X, and set #B is applicable to both device type X and device type Y, so in the example of Figure 18, device #1 of device type X can respond to R2D_A-IoT paging messages #a1, #b1, and #a2, and device #2 of device type Y can respond to R2D_A-IoT paging message #b1.

[0218] <Option 2-2 of Proposal 3 Variation> In option 2-2, C0 value set #A is applicable only to device type Y, and C0 value set #B is applicable to both device type X and device type Y. Note that C0 value set #A = {a1, a2,} and C0 value set #B = {b1, b2,}. Note that at least one value included in either C0 value set #A or set #B may or may not be included in the other set.

[0219] Option 2-2 will be explained with the aid of Figure 18. In option 2-2, set #A is applicable only to device type Y, and set #B is applicable to both device type X and device type Y, so in the example of Figure 18, device #1 of device type X can respond to R2D_A-IoT paging message #b1, and device #2 of device type Y can respond to R2D_A-IoT paging messages #a1, #b1, and #a2.

[0220] <Option 3 of variation of proposal 3> In option 3, the probability of selecting one C0 from value sets #A and #B differs between device type X and device type Y. For example, if set #A and set #B contain the same C0 value, the probability of selecting the same C0 may differ between device type X and device type Y. Alternatively, if set #A and set #B contain 10 C0 values, the probability of selecting each of the 10 values ​​may differ between device type X and device type Y. Alternatively, the multiple values ​​contained in each of sets #A and #B may include values ​​that are easy for a device to select and values ​​that are difficult for a device to select, and the values ​​that are easy for a device to select may differ between device type X and device type Y, and the values ​​that are difficult for a device to select may differ between device type X and device type Y.

[0221] According to Proposal 3, the collision probability of time domain resources can be adjusted between time domain resources, thereby suppressing an increase in signal collisions between devices. For example, the R2D_A-IoT paging message transmitted by the reader may be determined so as not to select a time domain resource for which it is desired to relatively reduce the collision probability. For example, to reduce the collision probability of time domain resources available to device type X and device type Y, an R2D_A-IoT paging message that only one of device type X and device type Y can respond may be transmitted.

[0222] In the above-described embodiment, Msg1 transmission, Msg3 transmission, and step 2 transmission are given as examples of D2R transmission, but the present disclosure is not limited to these.

[0223] In the above-described embodiment, device type Y determines one time domain resource using information different from that of device type X, and transmits Msg.1 for the R2D_A-IoT paging message using the determined time domain resource. Here, device Y is a type of device that supports the operation of determining multiple time domain resources from the R2D_A-IoT paging message and selecting one time domain resource from the multiple time domain resources, while device type X is a type of device that does not support this operation. Here, for example, in proposal 1, the information different from device type X is the value of P or Q in the Q algorithm. Also, for example, in proposal 2, the information different from device type X is information regarding the time domain resource determined from the R2D_A-IoT paging message (e.g., the position of the time domain resource, whether the time domain resource can be selected, and the probability of selection). Also, for example, in proposal 3, the information different from device type X is the R2D_A-IoT paging message that differs between device type X and device type Y.

[0224] For example, in the case of Proposal 1 described above, in the Q algorithm, different values ​​of Q or P are used for device type X and device type Y. In this case, device type Y uses a different P or Q than device type X to decide whether to respond to the R2D_A-IoT paging message.

[0225] For example, in the case of Proposal 2 described above, among the multiple time domain resources determined from the R2D_A-IoT paging message, device type Y is set to have a lower probability of selecting a time domain resource that overlaps with a time domain resource that device type X can use to transmit Msg.1 than a time domain resource that does not overlap with a time domain resource that device type X can use to transmit Msg.1. For example, in the case of Alt. 1 of Proposal 2, a time domain resource that overlaps with a time domain resource that device type X can use to transmit Mg.1 is not selected. In the case of Alt. 2 of Proposal 2, the time domain resource that device type X can use to transmit Mg.1 does not overlap with the multiple time domain resources selectable by device type Y. In other words, in the cases of Alt. 1 and Alt. 2 of Proposal 2, the probability that device type Y will select a time domain resource that overlaps with a time domain resource that device type X can use to transmit Msg.1 may be zero.

[0226] For example, in the case of Proposal 3 above, device type Y may determine multiple time domain resources from the R2D_A-IoT paging message differently from device type X.

[0227] <Device configuration> 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 the present 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 the present embodiment.

[0228] <Base station configuration> 19 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 a device 20 (see FIG. 20) wirelessly. The base station 10 may be a terminal (an intermediate UE communicating with the device 20) or a CW node.

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

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

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

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

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

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

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

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

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

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

[0239] For example, when the base station 10 (an example of a wireless communication device) communicates with a device type Y, the transmitter 101 transmits an R2D_A-IoT paging message (an example of a transmission signal) to the device type Y. The receiver 102 receives Msg.1 (an example of a response signal) in response to the R2D_A-IoT paging message in a time domain resource determined by the device type Y using information different from that of the device type X.

[0240] Also, for example, the communication unit may use the above time resources to perform communication involving A-IoT devices.

[0241] <Device configuration> 20 is a block diagram showing an example of a configuration of a device 20 according to an embodiment. The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with, for example, a base station 10 wirelessly. The device 20 may be a terminal (for example, an intermediate UE) or a CW node.

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

[0243] The transmitter 202 transmits the UL signal to the base station 10. For example, the transmitter 202 transmits the UL signal under the control of the controller 203.

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

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

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

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

[0248] For example, the control unit 203 acquires information such as data and control information from a higher 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 higher layer.

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

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

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

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

[0253] For example, if the device 20 is the above-mentioned device type Y, the control unit 203 determines the time domain resource using information different from that for device type X. The communication unit transmits Msg.1 (an example of a response signal) in response to the R2D_A-IoT paging message (an example of a received signal) in the determined time domain resource.

[0254] The information that differs from device type X is, for example, at least one of the values ​​of P or Q in the Q algorithm, information regarding the time domain resource determined from the R2D_A-IoT paging message (e.g., the position of the time domain resource, whether the time domain resource can be selected, and the probability of selection), and the R2D_A-IoT paging message that differs between device type X and device type Y.

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

[0256] <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 hardware and / or 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 connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

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

[0258] For example, a base station, a device, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 21 is a diagram showing an example of the hardware configuration of a base station and a device according to the embodiment. The above-described base station 10 and device 20 may be physically configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

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

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

[0262] Furthermore, the processor 1001 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 103 of the base station 10 and the control unit 203 of the device 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be 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 be transmitted from a network via a telecommunications line.

[0263] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable 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.

[0264] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy 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.

[0265] 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, or a communication module. 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.

[0266] The input device 1005 is an input device (for example, 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 (for example, 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 (for example, a touch panel).

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

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

[0269] <Information notification, signaling> The notification of information is not limited to the embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0270] <Applicable systems> The embodiments described in this 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), 6G (6th generation mobile communication system), 7G (7th generation mobile communication system), 8G (8th generation mobile communication system), 9G (9th generation mobile communication system), 10G (10th generation mobile communication system), 11G (11th generation mobile communication system), 12G (12th generation mobile communication system), 13G (13th generation mobile communication system), 14G (14th generation mobile communication system), 15G (15th generation mobile communication system), 16G (16th generation mobile communication system), 17G (17th generation mobile communication system), 18G (18th generation mobile communication system), 19G (19th generation mobile communication system), 20G (20th generation mobile communication system), 21G (2 th The present invention may be applied to at least one of a system using a next-generation mobile communication system (6G), an xth-generation mobile communication system (xG) (xG (x is, for example, an integer or decimal point)), Future Radio Access (FRA), new Radio (NR), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), or other appropriate system, and a next-generation system extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0271] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed 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.

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

[0273] <Input / output direction> Information, etc. (see the section on information and signals) 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.

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

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

[0276] <Variations of form, etc.> Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, 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).

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

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

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

[0280] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0281] Note that terms explained 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.

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

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

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

[0285] <Base station> In this 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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0286] 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 divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

[0288] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

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

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

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

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

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

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

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

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

[0297] 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 information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

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

[0299] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

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

[0303] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices 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)).

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

[0305] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

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

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

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

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

[0310] <Means> In the configurations of each of the above devices, the "means" may be replaced with a "section", "circuit", "device", etc.

[0311] <Open format> In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive in the same manner as the term "comprising". Further, the term "or" used in the present disclosure is intended not to be an exclusive disjunction.

[0312] <Time units such as TTI, frequency units such as RB, 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 referred to as 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) independent of numerology.

[0313] Numerology may be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. Numerology 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 configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

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

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

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

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

[0318] 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. However, the definition of TTI is not limited to this.

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

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

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

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

[0323] A resource block (RB) is a resource allocation unit in the time domain and 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 also be determined based on numerology.

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

[0325] 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, or the like.

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

[0327] 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 given BWP and numbered within that BWP.

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

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

[0330] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, 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. may be changed in various ways.

[0331] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

[0333] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Industrial Applicability]

[0334] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0335] 10 base station 20 devices 101,202 Transmitter 102,201 Receiver 103,203 Control unit

Claims

1. 1. A first type of device that supports determining a plurality of time resources from a received signal and selecting a transmission time resource from the plurality of time resources, the device comprising: a control unit that determines the transmission time resource using information different from that of a second type of device that does not support the operation; a transmitter that transmits a response signal to the received signal in the transmission time resource; 1. A device comprising:

2. the control unit determines an initial value of a counter value from a first range, decrements the counter value by N each time the control unit receives the reception signal, and determines the transmission time resource when the counter value becomes 0; the first range differs between the first type of device and the second type of device; The device of claim 1 .

3. the control unit determines one selected from the plurality of time resources determined from the received signal as the transmission time resource; Among the plurality of time resources, a time resource that overlaps with a specific time resource that the second type device can use to transmit the response signal is set to have a lower probability of being selected than a time resource that does not overlap with the specific time resource. The device of claim 1 .

4. the control unit determines the plurality of resources from a first received signal, and determines one of the plurality of time resources as the transmission time resource; the first received signal is different from a second received signal that the second type of device uses to determine the transmission time resource; The device of claim 1 .

5. 1. A wireless communications apparatus for communicating with a first type of device that supports determining a plurality of time resources from a received signal and selecting a transmission time resource from the plurality of time resources, the wireless communications apparatus comprising: a transmitter that transmits a transmission signal; a receiving unit that receives a response signal to the transmission signal in the transmission time resource determined using information different from that of a second type device that does not support the operation; A wireless communication device comprising:

6. a first type of device supporting operations of determining a plurality of time resources from a received signal and selecting a transmission time resource from the plurality of time resources, the first type of device comprising: determining the transmission time resource using information different from a second type of device that does not support the operation; transmitting a response signal to the received signal in the determined transmission time resource; Wireless communication method.

Images