Device and communication method

Abstract

This device has a lower level of complexity than a Narrow Band-Internet of Things (NB-IoT) device, and includes: a control unit that competes with a plurality of devices to acquire one resource provided to the plurality of devices, or, acquires one of a plurality of resources provided to the plurality of devices with or without competing with the plurality of devices; and a transmission unit that uses the acquired resource to transmit a signal.

Description

Device and communication method

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

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

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

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

[0005] However, in ambient IoT, the behavior of signal transmission has not been sufficiently studied, and further study is required.

[0006] One aspect of the present disclosure is to provide a device and a communication method that can transmit signals appropriately.

[0007] A device according to one aspect of the present disclosure is a device of lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, and includes a control unit that competes with a plurality of devices to acquire a resource provided to the plurality of devices, or acquires one of a plurality of resources provided to the plurality of devices, either by competing with the plurality of devices or without competition, and a transmission unit that transmits a signal using the acquired resource.

[0008] 1 is a diagram illustrating an example of a configuration of a wireless communication system according to an embodiment. FIG. 1 is a diagram illustrating Topology 1. FIG. 2 is a diagram illustrating Topology 3 in DL support. FIG. 3 is a diagram illustrating Topology 3 in UL support. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating a DT communication flow in Topology 1. FIG. 7 is a diagram illustrating a DO-DTT communication flow in Topology 1. FIG. 8 is a diagram illustrating a DT communication flow in Topology 2. FIG. 9 is a diagram illustrating a DO-DTT communication flow in Topology 2. FIG. 10 is a diagram illustrating a DO-DTT communication flow in Topology 1. FIG. 11 is a diagram illustrating Proposal 1: Option 1a. FIG. 12 is a diagram illustrating Proposal 1: Option 1b. FIG. 12 is a diagram illustrating Proposal 1: Option 1b. FIG. 13 is a diagram illustrating Proposal 1: Option 1b. FIG. 14 is a diagram illustrating Proposal 1: Option 2a. FIG. 15 is a diagram illustrating Proposal 1: Option 2a. FIG. 16 is a diagram illustrating Proposal 1: Option 2a. FIG. 17 is a diagram illustrating Proposal 1: Option 2a. 1 is a diagram explaining Proposal 1: Option 2a. 2 is a diagram explaining Proposal 1: Option 2a. 3 is a diagram explaining Proposal 1: Option 2b. 4 is a diagram explaining Proposal 1: Option 2b. 5 is a diagram explaining Proposal 1: Option 2b. 6 is a diagram explaining Proposal 1: Option 2b. 7 is a diagram explaining Proposal 1: Option 2b. 8 is a diagram explaining Proposal 1: Option 2b. 9 is a diagram explaining Proposal 2: Option 1a. 10 is a diagram explaining Proposal 2: Option 1b. 11 is a diagram explaining Proposal 2: Option 2a. 12 is a diagram explaining Proposal 2: Option 2b. 13 is a diagram explaining Proposal 3: Option 1. 14 is a diagram explaining Proposal 3: Option 2. 15 is a diagram explaining Proposal 3: Option 3. 16 is a diagram explaining Proposal 7: Option 1. 17 is a diagram explaining Proposal 7: Option 2. 18 is a diagram explaining Proposal 7: Option 3. 19 is a diagram explaining Proposal 7: Option 4. 10 is a diagram explaining variations.It is a block diagram showing an example of the configuration of a base station according to an embodiment. It is a block diagram showing an example of the configuration of a device according to an embodiment. It is a diagram showing an example of the hardware configuration of a base station and a device according to an embodiment. It is a diagram showing an example of the configuration of a vehicle.

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

[0010] In the operation of the wireless communication system according to the embodiment of the present disclosure, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, existing LTE. Furthermore, the term "LTE" as used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) 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 referred to 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 and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station or a terminal including a device are set.

[0014] <System Configuration> Fig. 1 is a diagram showing an example of the configuration of a wireless communication system according to an embodiment. As shown in Fig. 1, the wireless communication system includes a base station 10 and a device 20. Although Fig. 1 shows one base station 10 and one device 20, this is an example, and there may be a plurality of each. The device 20 may be an ambient IoT device.

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

[0016] The base station 10 transmits a synchronization signal and system information to the device 20. The base station 10 transmits a control signal and data to the device 20 via DL (Downlink). The base station 10 receives a control signal and data from the device 20 via UL (Uplink).

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

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

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

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

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

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

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

[0024] TR 38.848 defines the following topologies 1 to 4 for ambient IoT networks.

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

[0026] 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, or a repeater.

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

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

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

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

[0031] The support node shown in Figures 4 and 5 may send out a carrier wave for the ambient IoT device to generate backscatter. The support node may be, for example, a relay, an IAB node, a UE, or a repeater.

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

[0033] 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 (Section 4.2.1 of Non-Patent Document 3).

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

[0035] 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 its own antenna, and transmits information to the base station, intermediate node, support node, and other nodes.

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

[0037] Hereinafter, a network may include a base station, a support node, an intermediate node, and a terminal (UE in Topology 4). Hereinafter, the base station, the support node, the intermediate node, the relay, and the terminal may be referred to as network nodes. Ambient IoT may be referred to as A-IoT. An A-IoT device may be referred to as A-IoT UE.

[0038] <Rel-19 Study Item Description (SID)> The Rel-19 SID examined necessary and feasible solutions for A-IoT (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.

[0039] Additionally, several issues for the DL and UL of A-IoT will be discussed under the leadership of RAN 1. Among the issues discussed are DL and UL multiple access, scheduling, and timing relationships in A-IoT. In discussing scheduling and timing relationships, the following 1. traffic flow, 2. device assumptions, and 3. topology can be considered.

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

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

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

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

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

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

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

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

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

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

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

[0051] 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 may be referred to as int. UE (intermediate UE).

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

[0053] As shown in the four communication flows 1 to 4 below, the A-IoT UE wakes up in step 1 and receives information in step 2. The information received by the A-IoT UE may be interpreted as a signal.

[0054] Also, as shown in the communication flows in 2 and 4 below, the A-IoT UE transmits a signal in step 3. The signal transmitted by the A-IoT UE may be interpreted as information.

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

[0056] The communication flow of DT in Topology 1 is assumed to involve the following two steps:

[0057] Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform transmitted from the base station (step 1 is not shown). The carrier waveform may be replaced with a carrier wave. Step 2: The A-IoT UE receives information from the base station.

[0058] Step 1 is initiated, for example, when a packet occurs in the application layer of the base station (corresponding to "Packet arrival" shown in Figure 8) (the same applies to step 1 described in Figures 9, 10, and 11).

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

[0060] The A-IoT UE may be woken up by a signal (e.g., an RF signal) transmitted from a source other than a base station, where the signal may correspond to an energy source that provides energy to the A-IoT UE. The carrier waveform may be replaced with a carrier wave.

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

[0062] The DO-DTT communication flow in Topology 1 is assumed to involve the following three steps:

[0063] Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform transmitted from the base station (step 1 is not shown). Step 2: The A-IoT UE receives information from the base station. Step 3: The A-IoT UE transmits a signal to the base station.

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

[0065] The communication flow of DT in Topology 2 is assumed to involve the following four steps:

[0066] Step 0: The int. UE receives a trigger from the base station to send a signal such as a carrier waveform to the A-IoT UE, and sends a signal to the A-IoT UE based on the trigger (step 0 is not shown). Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform sent from the int. UE (step 1 is not shown). Step 2: The A-IoT UE receives information from the base station via the int. UE. Step X: The int. UE sends a signal to the base station.

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

[0068] In the DO-DTT communication flow in Topology 2, the following five-step communication flow is assumed.

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

[0070] DO-DTT Communication Flow in Topology 1 The following communication flow may be assumed for DO-DTT communication flow.

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

[0072] The communication flow of DO-DTT in Topology 1 assumes the following steps: Step 1a: The A-IoT UE receives an energy source signal / wake-up signal. Step 1b: The A-IoT UE receives a signal for synchronization. Step 2: The A-IoT UE receives a signal for data RX (DL control / DL data / DL control & DL data) from the network. Step 1c: The A-IoT UE receives a carrier wave for backscatter without modulation from the network. Step 3: The A-IoT UE transmits a signal for data TX to the network.

[0073] It should be noted that some steps may be combined into one step, and some steps may be skipped.

[0074] In FIG. 12, the communication flow of DO-DTT in topology 1 has been described, but in the communication flow of DO-DTT in topology 2, steps 1a, 1b, and 1c are added in the same manner.

[0075] <Analysis> Considering use cases such as inventory, it is assumed that the information transmitted in step 2 is effective to be transmitted to a group of A-IoT UEs. Note that the base station may or may not recognize the A-IoT UEs belonging to the group of A-IoT UEs. For example, it is assumed that at least a part of the signal transmitted in step 2 is effective to be transmitted by broadcast or multicast (groupcast).

[0076] However, 3GPP has not fully considered how to transmit information to a group of A-IoT UEs, and A-IoT UEs may not be able to transmit signals properly.

[0077] For example, in a use case such as inventory, a network such as a base station / int. UE may provide resource information such as time domain resources / frequency domain resources / code domain resources to multiple A-IoT UEs and instruct them to transmit signals using the provided resources. However, insufficient consideration is given to operations such as providing and deriving resource information for transmission signals in step 3, and the A-IoT UE may not be able to transmit signals appropriately.

[0078] Therefore, in this disclosure, in Proposals 1 to 8, we provide technologies that allow A-IoT UEs to transmit signals appropriately.

[0079] In the following proposal, the combination of step 1b and step 2 in the DO-DTT communication flow may be referred to as step 2. The combination of step 1a, step 1b, and step 2 in the DO-DTT communication flow may be referred to as step 2. If step 2 is skipped in the DO-DTT communication flow, step 1b may be referred to as step 2. If step 2 is skipped in the DO-DTT communication flow, step 1a and step 1b may be referred to as step 2.

[0080] Note that "may be step 2" may also mean "step 2 may be replaced", for example, "the combination of step 1b and step 2 may be step 2" may mean "step 2 may be replaced with the combination of step 1b and step 2". The following proposal may also be applied to the DT communication flow. For example, it is assumed that the A-IoT UE performs any transmission in the DT communication flow.

[0081] The time domain resource, the frequency domain resource, and the code domain resource may be referred to as a time resource, a frequency resource, and a code resource. The information indicated (notified) by physical layer signaling may be indicated by, for example, Downlink Control Information (DCI). The information indicated by higher layer signaling may be indicated by, for example, Radio Resource Control (RRC).

[0082] <Proposal 1> Proposal 1 proposes a technology for allocating transmission signal resources to multiple A-IoT UEs.

[0083] In the communication flow of DO-DTT in Topology 1 and Topology 2, the A-IoT UE receives information from the network (base station / int. UE) (step 2) and transmits a signal to the network (step 3). The information received in step 2 triggers the transmission in step 3. Note that in this disclosure, the base station and int. UE may be interchangeable.

[0084] Regarding the resources such as time domain resources / frequency domain resources / code domain resources of the signal in step 3, the following options 1a, 1b, 2a and 2b are proposed.

[0085] <Proposal 1: Option 1a> One time / frequency / code domain resource is provided (given) to one group of A-IoT UEs.

[0086] Figure 13 illustrates Proposal 1: Option 1a. As shown in Figure 13, one time / frequency / code domain resource is provided to one group of A-IoT UEs. For example, one resource is shared by multiple (one group) A-IoT UEs #1, #2, ... #N. Therefore, the resource is used by the group of A-IoT UEs in a contention-based manner.

[0087] In the case of <Proposal 1: Option 1a>, the information in step 2 (resource information) may be broadcast to any A-IoT UE or multicast to a group of A-IoT UEs.

[0088] <Proposal 1: Option 1b> One time / frequency / code domain resource is provided to one A-IoT UE. In other words, multiple A-IoT UEs are each provided with individual resources. Note that one resource may be assigned to an A-IoT UE by individual A-IoT UE signaling.

[0089] Figures 14-20 are diagrams illustrating Proposal 1: Option 1b. As shown in Figures 14-20, multiple time / frequency / code domain resources are provided to each of multiple (one group) A-IoT UEs.

[0090] For example, in Figure 14, one of the four resources is provided to A-IoT UE #1 of the four A-IoT UEs, one of the four resources is provided to A-IoT UE #2 of the four A-IoT UEs, one of the four resources is provided to A-IoT UE #3 of the four A-IoT UEs, and one of the four resources is provided to A-IoT UE #4 of the four A-IoT UEs.

[0091] Multiple A-IoT UEs use the provided resources for signaling in step 3. From the system (network) perspective, different resources are used by different A-IoT UEs in a contention-free manner.

[0092] Each of the multiple A-IoT UEs may derive different resources based on, for example, different pre-configured A-IoT UE-specific parameters. Derivation may be interpreted as obtaining, selecting, or determining. Furthermore, derivation, obtaining, selecting, and determining may be interpreted as interchangeable terms.

[0093] For example, the resource information may be unicast individually to each of the multiple A-IoT UEs in step 2. For example, the resource information may be unicast individually to each of the multiple A-IoT UEs in the DL control information in step 2. Note that information other than the DL control information in step 2 may be received by broadcast or multicast.

[0094] Note that Figure 14 shows an example in which resources of different A-IoT UEs are time division multiplexed (TDM). Figure 15 shows an example in which resources of different A-IoT UEs are frequency division multiplexed (FDM). Figure 16 shows an example in which resources of different A-IoT UEs are code division multiplexed (CDM). Figure 17 shows an example in which resources of different A-IoT UEs are TDM and FDM. Figure 18 shows an example in which resources of different A-IoT UEs are TDM and CDM. Figure 19 shows an example in which resources of different A-IoT UEs are FDM and CDM. Figure 20 shows an example in which resources of different A-IoT UEs are TDM, FDM and CDM.

[0095] <Proposal 1: Option 2a> Multiple time / frequency / code domain resources are provided to a group of A-IoT UEs, and the multiple resources are allocated to the multiple A-IoT UEs in a contention-based manner.

[0096] For example, in <Proposal 1: Option 2a>, the number of resources allocated to A-IoT UEs is less than the number of A-IoT UEs. For example, 10 resources are allocated to 100 A-IoT UEs. Therefore, in <Proposal 1: Option 2a>, multiple resources are allocated to multiple A-IoT UEs in a contention-based manner.

[0097] Figures 21 to 27 are diagrams illustrating Proposal 1: Option 2a. As shown in Figures 21 to 27, multiple time / frequency / code domain resources are provided to multiple (one group) A-IoT UEs.

[0098] For example, in Figure 21, four resources are provided to N (N>4) A-IoT UEs #1, #2, #3, ..., #N. In other words, the four resources are shared by N A-IoT UEs #1, #2, #3, ..., #N. Therefore, the four resources are allocated to N A-IoT UEs #1, #2, #3, ..., #N in a contention-based manner.

[0099] The A-IoT UE may randomly select and use one resource for transmission.

[0100] The A-IoT UE may select one resource to use for transmission based on at least one of defined rules, A-IoT UE-specific / common parameters instructed (provided) by the network, and parameters defined in the A-IoT UE, such as the A-IoT UE's identity.

[0101] The information of the multiple resources may be broadcast or multicast to multiple A-IoT UEs, for example, in step 2.

[0102] Note that Figure 21 shows an example where resources of different A-IoT UEs are TDM'd. Figure 22 shows an example where resources of different A-IoT UEs are FDM'd. Figure 23 shows an example where resources of different A-IoT UEs are CDM'd. Figure 24 shows an example where resources of different A-IoT UEs are TDM'd and FDM'd. Figure 25 shows an example where resources of different A-IoT UEs are TDM'd and CDM'd. Figure 26 shows an example where resources of different A-IoT UEs are FDM'd and CDM'd. Figure 27 shows an example where resources of different A-IoT UEs are TDM'd, FDM'd and CDM'd.

[0103] Proposal 1: Option 2b: Multiple time / frequency / code domain resources are provided to a group of A-IoT UEs. The resources are allocated to the A-IoT UEs in a contention-free manner. The resources may also be allocated to the A-IoT UEs by common signaling.

[0104] For example, in <Proposal 1: Option 2b>, the number of resources allocated to A-IoT UEs is equal to or greater than the number of A-IoT UEs. For example, 10 resources are allocated to 10 A-IoT UEs. Therefore, in <Proposal 1: Option 2b>, multiple resources are allocated to multiple A-IoT UEs in a contention-free manner.

[0105] Figures 28-34 are diagrams illustrating Proposal 1: Option 2b. As shown in Figures 28-34, multiple time / frequency / code domain resources are provided to each of multiple (one group) A-IoT UEs.

[0106] For example, in Figure 28, one of the four resources is provided to A-IoT UE #1 of the four A-IoT UEs. One of the four resources is provided to A-IoT UE #2 of the four A-IoT UEs. One of the four resources is provided to A-IoT UE #3 of the four A-IoT UEs. One of the four resources is provided to A-IoT UE #4 of the four A-IoT UEs. Therefore, the four resources are allocated to the four A-IoT UEs in a contention-free manner.

[0107] The A-IoT UE may determine one resource to use for transmission based on at least one of the defined rules, A-IoT UE specific / common parameters instructed by the network, and A-IoT UE defined parameters such as the A-IoT UE ID. The rules in <Proposal 1: Option 2b> differ from the rules in <Proposal 1: Option 2a> in that they allocate resources specific to the A-IoT UE.

[0108] The information of the multiple resources may be broadcast or multicast to multiple A-IoT UEs, for example, in step 2.

[0109] Note that Figure 28 shows an example where resources of different A-IoT UEs are TDM'd. Figure 29 shows an example where resources of different A-IoT UEs are FDM'd. Figure 30 shows an example where resources of different A-IoT UEs are CDM'd. Figure 31 shows an example where resources of different A-IoT UEs are TDM'd and FDM'd. Figure 32 shows an example where resources of different A-IoT UEs are TDM'd and CDM'd. Figure 33 shows an example where resources of different A-IoT UEs are FDM'd and CDM'd. Figure 34 shows an example where resources of different A-IoT UEs are TDM'd, FDM'd and CDM'd.

[0110] <Proposal 1: Variation> The A-IoT UE may derive the resources from information received in step 2, predefined information, or information indicated in physical layer or higher layer signaling different from the above information (e.g., pre-configured information).

[0111] A time resource may be defined based on the start and number of time units, such as symbols or slots.

[0112] A frequency resource may be defined based on the start and number of frequency units, such as subcarriers or resource blocks (RBs).

[0113] The code resource may be defined based on a base sequence length, a base sequence index, a cyclic shift, and an orthogonal cover code index (OCC index).

[0114] The time relationship of step 3 may be defined as an offset with respect to step 2 or step 1. For example, the start position (start time) of the signal transmitted in step 3 may be defined as an offset with respect to the reception start position or reception end position of the information received in step 2, or an offset with respect to the reception start position or reception end position of the signal received in step 1.

[0115] <Proposal 1: Summary> As explained above, an A-IoT UE competes with multiple A-IoT UEs to acquire a single resource provided to multiple A-IoT UEs (a group of A-IoT UEs). This operation allows the A-IoT UE to transmit step 3 (transmit the signal in step 3) using the resource acquired through competition, and to transmit the signal appropriately.

[0116] The A-IoT UE competes with multiple A-IoT UEs to acquire one of the multiple resources provided to multiple A-IoT UEs. This operation allows the A-IoT UE to transmit in step 3 using the resource acquired through competition and transmit signals appropriately.

[0117] The A-IoT UE acquires one of the resources provided to the multiple A-IoT UEs without contention with the multiple A-IoT UEs. This operation allows the A-IoT UE to transmit in step 3 using the acquired resource without contention and transmit signals appropriately.

[0118] <Proposal 2> Proposal 2 proposes a technique for allocating contiguous and non-contiguous resources.

[0119] In the cases of <Proposal 1: Option 2a> and <Proposal 1: Option 2b>, multiple time / frequency / code domain resources are provided to one group of A-IoT UEs. Regarding the resources provided to one group of A-IoT UEs, the following options 1a, 1b, 2a, 2b, and 3 are proposed.

[0120] <Proposal 2: Option 1a> Contiguous time resources are allocated to the A-IoT UE.

[0121] Figure 35 illustrates Proposal 2: Option 1a. As shown in Figure 35, consecutive time resources are allocated to A-IoT UEs. Each time resource may contain the same number of time units or may contain different numbers of time units.

[0122] <Proposal 2: Option 1b> Non-contiguous time resources are allocated to the A-IoT UE.

[0123] Figure 36 illustrates Proposal 2: Option 1b. As shown in Figure 36, non-contiguous time resources are allocated to A-IoT UEs. Each time resource may include the same number of time units or may include different numbers of time units.

[0124] The gap in time resources may be predefined or may be indicated (eg, preconfigured) in physical layer or higher layer signaling.

[0125] <Proposal 2: Option 2a> Contiguous frequency resources are allocated to A-IoT UEs.

[0126] Figure 37 illustrates Proposal 2: Option 2a. As shown in Figure 37, contiguous frequency resources are allocated to A-IoT UEs. Each frequency resource may include the same number of frequency units or may include different numbers of frequency units.

[0127] <Proposal 2: Option 2b> Non-contiguous frequency resources are allocated to A-IoT UEs.

[0128] Figure 38 illustrates Proposal 2: Option 2b. As shown in Figure 38, non-contiguous frequency resources are allocated to A-IoT UEs. Each frequency resource may include the same number of frequency units or may include a different number of frequency units.

[0129] The frequency resource gaps may be predefined or indicated (eg, preconfigured) in physical layer or higher layer signaling.

[0130] <Proposal 2: Option 3> Multiple code resources are allocated to the A-IoT UE, which may be multiple sequences / cyclic shifts / orthogonal cover codes.

[0131] <Proposal 2: Variation> As explained in Proposal 1, the resources of multiple A-IoT UEs can be a combination of TDM / FDM / CDM. The following resources may be allocated to multiple A-IoT UEs:

[0132] Same time domain resources + different frequency domain resources / code domain resources Same time domain resources + same frequency domain resources + different code domain resources Same time domain resources + same code domain resources + different frequency domain resources Same frequency domain resources + different time domain resources / code domain resources Same frequency domain resources + same code domain resources + different time domain resources Same code domain resources + different time domain resources / frequency domain resources

[0133] Note that Figure 28 shows an example in which different time domain resources and the same frequency domain resources are assigned to multiple A-IoT UEs, while Figure 29 shows an example in which the same time domain resources and different frequency domain resources are assigned to multiple A-IoT UEs.

[0134] <Proposal 2: Summary> As explained above, the A-IoT UE uses continuous resources to transmit in step 3. This operation allows the A-IoT UE to transmit in step 3 using continuous resources, enabling it to transmit signals appropriately.

[0135] The A-IoT UE uses non-contiguous resources to transmit in step 3. This operation allows the A-IoT UE to transmit in step 3 using non-contiguous resources and transmit signals appropriately.

[0136] <Proposal 3> Proposal 3 proposes a technique for identifying (distinguishing) multiple resources.

[0137] In the case of Proposal 1: Option 2b, multiple time / frequency / code domain resources are provided to a group of A-IoT UEs and allocated in a contention-free manner. To distinguish between the multiple resources, indexes are assigned to the multiple resources. Regarding indexing, the following options 1, 2, and 3 are proposed:

[0138] <Proposal 3: Option 1> Figure 39 is a diagram explaining Proposal 3: Option 1. As shown in Figure 39, one resource allocated to one A-IoT UE is represented by one index. The indexes are counted from three dimensions (time, frequency, and code). For example, index #1, #2, ..., #8 are counted for three-dimensional resources in the time domain, frequency domain, and code domain. The order in which the indexes are assigned may be based on a to f below.

[0139] a. First the time domain, then the frequency domain, then the code domain b. First the time domain, then the code domain, then the frequency domain c. First the frequency domain, then the time domain, then the code domain d. First the frequency domain, then the code domain, then the time domain e. First the code domain, then the time domain, then the frequency domain f. First the code domain, then the frequency domain, then the time domain

[0140] The index may be provided in step 2 of the communication flow. The index may be provided by the network in physical layer or higher layer signaling.

[0141] An index may be determined based on at least one of a defined rule, an A-IoT UE specific / common parameter instructed by the network, and a parameter predefined for the A-IoT UE, such as the ID of the A-IoT UE.

[0142] If only one or two dimensions of the time / frequency / code domain resource are supported, the index may be counted from only one or two dimensions.

[0143] <Proposal 3: Option 2> Figure 40 is a diagram explaining Proposal 3: Option 2. As shown in Figure 40, one resource allocated to one A-IoT UE is represented by three indexes. One index is counted from one dimension. For example, for each resource, Time index #1 and #2 are counted for the time domain. For each resource, Freq index #1 and #2 are counted for the frequency domain. For each resource, Code index #1 and #2 are counted for the code domain.

[0144] The index for each dimension may be provided in step 2 of the communication flow. The index for each dimension may be provided by the network in signaling at the physical layer or higher layer.

[0145] The index for each dimension may be determined based on at least one of a defined rule, an A-IoT UE specific / common parameter instructed by the network, and a parameter predefined for the A-IoT UE, such as the A-IoT UE ID.

[0146] If only one or two dimensions of the time / frequency / code domain resource are supported, the index may be counted from only one or two dimensions.

[0147] <Proposal 3: Option 3> Figure 41 is a diagram explaining Proposal 3: Option 3. As shown in Figure 41, one resource allocated to one A-IoT UE is represented by two indexes. One of the two indexes is counted from the first dimension, and the other index is counted from the second dimension.

[0148] The dimensions of the two indexes may be based on the following a to c. An example of a is shown in Figure 41.

[0149] a. One index for the time and frequency domains and one index for the code domain

[0150] The order in which the indexes for the time domain and the frequency domain are assigned may be based on the following a1 and a2: a1. Time domain first, then frequency domain a2. Frequency domain first, then time domain

[0151] b. One index for the time domain and code domain, and one index for the frequency domain

[0152] The order in which the indexes for the time domain and the code domain are assigned may be based on the following b1 and b2: - b1. Time domain first, then code domain - b2. Code domain first, then time domain

[0153] c. One index for the frequency domain and code domain, and one index for the time domain

[0154] The order in which the indexes for the frequency domain and the code domain are assigned may be based on the following c1 and c2: - c1. Frequency domain first, then code domain - c2. Code domain first, then frequency domain

[0155] The indexes in the first and second dimensions may be provided in step 2 of the communication flow. The indexes in the first and second dimensions may be provided by the network in physical layer or higher layer signaling.

[0156] The indexes in the first and second dimensions may be determined based on at least one of defined rules, A-IoT UE specific / common parameters instructed by the network, and parameters predefined for the A-IoT UE, such as the A-IoT UE ID.

[0157] <Proposal 3: Summary> As explained above, resources are assigned indexes and the resources allocated to A-IoT UEs are differentiated. This configuration allows the A-IoT UE to transmit in step 3 using differentiated resources, enabling it to transmit signals appropriately.

[0158] <Proposal 4> Proposal 4 proposes a technique for selecting between multiple resources.

[0159] In the case of Proposal 1: Option 2a, multiple time / frequency / code domain resources are provided to a group of A-IoT UEs and allocated in a contention-based manner. The following options 1, 2, and 3 are proposed for resource selection in the contention-based manner.

[0160] <Proposal 4: Option 1> Regarding resource distinction, <Proposal 3: Option 1> is used. That is, one resource is represented by one index, and the index is counted from three dimensions (time, frequency, and code). Note that if only one or two dimensions of the time / frequency / code domain resource are supported, the index may be counted from only one or two dimensions.

[0161] One index may be randomly selected by the A-IoT UE.

[0162] An index may be selected by the A-IoT UE by applying several defined rules. The rules may take into account A-IoT UE-specific / common parameters instructed by the network or parameters defined in the A-IoT UE, such as the A-IoT UE ID. These rules / parameters may result in various resources, and the A-IoT UE may randomly select one resource from these resources. That is, the A-IoT UE may determine Y indexes from X indexes notified by the base station based on at least one of A-IoT UE-specific / common parameters instructed by the network and parameters predefined in the A-IoT UE, such as the A-IoT UE ID, and then randomly select one index from the Y indexes.

[0163] An index may be determined based on at least one of a defined rule, an A-IoT UE specific / common parameter instructed by the network, and a parameter predefined in the A-IoT UE, such as the A-IoT UE ID, etc. These rules and parameters result in a resource.

[0164] <Proposal 4: Option 2> Regarding resource distinction, <Proposal 3: Option 2> is used. That is, one resource allocated to one A-IoT UE is represented by three indexes, and each index is counted from one dimension. Note that if only one or two dimensions of time / frequency / code domain resources are supported, the indexes may be counted from only one or two dimensions.

[0165] In each dimension, one index may be randomly selected by the A-IoT UE.

[0166] For each dimension, an index may be selected by the A-IoT UE by applying several defined rules. The rules may take into account A-IoT UE-specific / common parameters instructed by the network or parameters defined in the A-IoT UE, such as the A-IoT UE ID. These rules / parameters may result in various resources, and the A-IoT UE may randomly select one resource from these resources. That is, for each dimension, the A-IoT UE may determine Y indexes from X indexes notified by the base station based on at least one of A-IoT UE-specific / common parameters instructed by the network and parameters predefined in the A-IoT UE, such as the A-IoT UE ID, and then randomly select one index from the Y indexes.

[0167] In each dimension, an index may be determined based on at least one of a defined rule, an A-IoT UE specific / common parameter instructed by the network, and a parameter predefined for the A-IoT UE, such as the A-IoT UE's ID, resulting in a resource.

[0168] <Proposal 4: Option 3> Regarding resource distinction, <Proposal 3: Option 2> is used, i.e., one resource allocated to one A-IoT UE is represented by two indexes, one of which is counted from the first dimension and the other from the second dimension.

[0169] In the first and second dimensions, one index may be randomly selected by the A-IoT UE.

[0170] In the first and second dimensions, the A-IoT UE may select a resource by applying several defined rules. The rules may take into account A-IoT UE-specific / common parameters instructed by the network or parameters defined in the A-IoT UE, such as the A-IoT UE's ID. These rules / parameters may result in various resources, and the A-IoT UE may randomly select one resource from these resources. That is, for each index determination, the A-IoT UE may determine Y indexes from X indexes notified by the base station based on at least one of A-IoT UE-specific / common parameters instructed by the network and parameters predefined in the A-IoT UE, such as the A-IoT UE's ID, and then randomly select one index from the Y indexes.

[0171] In the first and second dimensions, an index may be determined based on at least one of a defined rule, an A-IoT UE specific / common parameter instructed by the network, and a parameter predefined for the A-IoT UE, such as the A-IoT UE ID, etc. These rules and parameters result in a resource.

[0172] <Proposal 4: Summary> As explained above, the A-IoT UE uses the index to select (specify) the resources to be used for transmission in step 3. This operation enables the A-IoT UE to transmit in step 3 using the resources selected using the index, and to transmit signals appropriately.

[0173] <Proposal 5> Proposal 5 proposes technologies for the carrier waveform / modulation / coding method / scrambled RNTI used for A-IoT UE transmission (signal transmission in Step 3).

[0174] In the cases of <Proposal 1: Option 1a> and <Proposal 1: Option 2a>, i.e., when resources are used in a contention-based manner, the carrier waveform / modulation / coding scheme / scrambling RNTI used for A-IoT UE transmission is predefined or provided by cell-common / group-common parameters, where RNIT is an abbreviation for Radio Network Temporary Identifier.

[0175] In the cases of <Proposal 1: Option 1b> and <Proposal 1: Option 2b>, i.e., when resources are used in a contention-free manner, the carrier waveform / modulation / coding scheme / scrambling RNTI used for A-IoT UE transmission is provided by A-IoT UE-specific parameters.

[0176] Note that when resources are used in a contention-free manner, the carrier waveform / modulation / coding scheme / scrambling RNTI used for A-IoT UE transmission may be predefined or provided by cell-common / group-common parameters.

[0177] <Proposal 5: Summary> As explained above, the A-IoT UE determines, according to a predetermined rule, the carrier waveform / modulation / coding scheme / scrambling RNTI to be used for signal transmission in step 3. This operation enables the A-IoT UE to transmit in step 3 based on the carrier waveform / modulation / coding scheme / scrambling RNTI determined according to the predetermined rule, and to transmit signals appropriately.

[0178] <Proposal 6> Proposal 6 proposes a technique for preamble transmission in signal transmission in step 3.

[0179] In the case of <Proposal 1: Option 1a> and <Proposal 1: Option 2a>, i.e., when resources are used in a contention-based manner, the transmission from the A-IoT UE (transmission of step 3) may be divided into two steps. For example, step 3 may be divided into the following steps 3a and 3b.

[0180] Step 3a: The A-IoT UE transmits a preamble. Step 3b: The A-IoT UE transmits a signal (UL data).

[0181] The above-described suggestions may be applied to steps 3a and 3b.

[0182] The preamble sequence of step 3a may be specific to the A-IoT UE, for example, the preamble sequence of step 3a may include the ID of the A-IoT UE.

[0183] If the preamble sequence in step 3a is A-IoT UE specific, the carrier waveform / modulation / coding scheme / scrambling RNTI used for transmission in step 3b is provided by A-IoT UE specific parameters, although the carrier waveform / modulation / coding scheme / scrambling RNTI may still be predefined or provided by cell-common / group-common parameters.

[0184] Otherwise (if the preamble sequence in step 3a is not A-IoT UE specific), the carrier waveform / modulation / coding scheme / scrambling RNTI used for the transmission in step 3b is provided by predefined or cell-common / group-common parameters.

[0185] In the case of <Proposal 1: Option 1a>, i.e., when one resource is provided to multiple A-IoT UEs, the time / frequency / code domain resources in step 3a and step 3b have a predefined relationship, for example, there may be a predefined / specified offset between the resources in step 3a and step 3b.

[0186] In the case of <Proposal 1: Option 2a>, i.e., when multiple time / frequency / code domain resources are provided to multiple A-IoT UEs, the time / frequency / code domain resources in step 3a and step 3b have a predefined relationship, where one resource in step 3a is paired with one resource in step 3b. The A-IoT UE uses the resource pair for transmission in step 3a and step 3b.

[0187] For example, if resources are indexed as described in Proposal 3, resources with the same index may be used in step 3a and step 3b, i.e., the resources in step 3b may be automatically determined from the resources in step 3a, or there may be a predefined / specified offset between the resources in step 3a and step 3b.

[0188] <Proposal 6: Summary> As explained above, step 3 of the communication flow is divided into two steps, 3a and 3b, and the A-IoT UE transmits a preamble in step 3a. This operation allows the A-IoT UE to transmit signals appropriately.

[0189] <Proposal 7> Proposal 7 proposes a technology to reduce (reduce) transmission collisions in step 3 of A-IoT UE.

[0190] In the cases of <Proposal 1: Option 1a> and <Proposal 1: Option 2a>, i.e., when resources are used in a contention-based manner, the A-IoT UE transmits step 3 (signal) with probability x. In other words, the A-IoT UE does not transmit step 3 with probability 1-x. When the A-IoT UE transmits step 3, it determines the resources and performs transmission based on each proposal described above.

[0191] In one possible implementation in the A-IoT UE, the A-IoT UE randomly generates (selects) a number from N numbers, 0, 1, ..., (N-1), and transmits step 3 based on the generated number, where N is a natural number greater than or equal to 2.

[0192] For example, if the number generated from 0, 1, ..., (N-1) is 0 (or m), the A-IoT UE transmits step 3. If the generated number is not 0, the A-IoT UE does not transmit step 3. In this case, the probability x that the A-IoT UE transmits step 3 is 1 / N.

[0193] If the A-IoT UE fails to transmit step 3 (if the generated number is not 0 and step 3 was not transmitted), it waits for other information in step 2. That is, it may attempt to receive information related to other resource allocation from the base station. The other information is information for transmitting step 3. The A-IoT UE receives the other information and executes transmission of step 3 (attempts to transmit step 3 again).

[0194] If the A-IoT UE fails to transmit step 3, it may perform the transmission of step 3 based on options 1 to 4 below.

[0195] <Proposal 7: Option 1> Figure 42 is a diagram explaining Proposal 7: Option 1. The A-IoT UE transmits step 3 with probability x each time it receives information from step 2. In other words, the A-IoT UE does not transmit step 3 with probability 1-x each time it receives information from step 2. The range of values ​​generated by the A-IoT UE is the same for each reception of step 2, and is 0, 1, ..., (N-1).

[0196] The A-IoT UE receives information from step 2 until it transmits step 3 (until the transmission of step 3 is successful).

[0197] <Proposal 7: Option 2> Figure 43 is a diagram for explaining Proposal 7: Option 2. When the A-IoT UE receives the information in Step 2 for the first time, it transmits Step 3 with probability x. In other words, when the A-IoT UE receives the information in Step 2 for the first time, it does not transmit Step 3 with probability 1 - x.

[0198] Thereafter, each time the A-IoT UE receives the information in Step 2, it transmits Step 3 with probability y (y > x). In other words, each time the A-IoT UE receives the information in Step 2, it does not transmit Step 3 with probability 1 - y.

[0199] The range of values generated by the A-IoT UE is 0, 1, …, (N - 1) when it receives the information in Step 2 for the first time. Thereafter, the range of values generated by the A-IoT UE is the same for each reception of the information in Step 2 and is 0, 1, …, (M - 1) (M < N). Note that the above probability y becomes 1 / M.

[0200] The A-IoT UE receives the information in Step 2 until it transmits Step 3 (until the transmission of Step 3 is successful).

[0201] <Proposal 7: Option 3> Figure 44 is a diagram for explaining Proposal 7: Option 3. When the A-IoT UE receives the information in Step 2 for the first time, it transmits Step 3 with probability x. In other words, when the A-IoT UE receives the information in Step 2 for the first time, it does not transmit Step 3 with probability 1 - x.

[0202] Thereafter, each time the A-IoT UE receives the information in Step 2, it transmits Step 3 with probability x + (n - 1)i (n is the number of times the information is received, i is a constant). In other words, each time the A-IoT UE receives the information in Step 2, it does not transmit Step 3 with probability 1 - {x + (n - 1)i}.

[0203] The range of values ​​generated by the A-IoT UE is 0, 1, ..., (N-1) when it first receives the information in step 2. After that, the range of values ​​generated by the A-IoT UE gradually decreases with each reception of step 2. For example, the value of N may be decreased by j (Nj, N-2j, ...).

[0204] The A-IoT UE receives information from step 2 until it transmits step 3 (until the transmission of step 3 is successful).

[0205] <Proposal 7: Option 4> Figure 45 is a diagram explaining Proposal 7: Option 4. In <Proposal 7: Option 4>, when the A-IoT UE receives the information of step 2 for the first time, it randomly generates a number from 0, 1, ..., (N-1). If the generated number is 0 (or m), the A-IoT UE transmits step 3. In other words, if the generated number is not 0, the A-IoT UE does not transmit step 3. The A-IoT UE stores the number "L" (L ≠ 0) generated when it receives the information of step 2 for the first time in a memory unit.

[0206] After that, the A-IoT UE subtracts 1 (or a specific integer value) from the number "L" stored in the memory unit each time it receives the information of step 2. When the subtracted value becomes 0, the A-IoT UE transmits step 3.

[0207] <Proposal 7: Variation 1> The information in step 2 may include information that distinguishes (identifies) the scheduling round. In other words, the information in step 2 distinguishes whether it is for the same scheduling round as the previous step 2.

[0208] A scheduling round refers to scheduling for the transmission and / or reception of a specific piece of information until all A-IoT UEs in a group complete signal transmission (step 3 signal transmission). For example, the network instructs 100 A-IoT UEs to transmit signals using 10 resources. In this case, the network repeats the information transmission in step 2 10 times, and each of the 100 A-IoT UEs performs the signal transmission in step 3, 10 at a time. These 10 information transmissions in step 2 and 10 signal transmissions in step 3 constitute one scheduling round. The A-IoT UE distinguishes the scheduling round based on the scheduling round distinguishing information included in the step 2 information, and determines whether the previously received step 2 information is information from the same scheduling round. If the received step 2 information indicates a new scheduling round, the A-IoT UE resets the probability and the number to be generated to their initial values ​​(e.g., resets parameters such as x, N, and L to their initial values).

[0209] The information of step 2 may include information indicating the number of times information is transmitted in one scheduling round. In other words, the information of step 2 distinguishes the number of times information is transmitted in one scheduling round.

[0210] For example, in the above example, the information in step 2 includes information indicating whether it is the first (initial) information transmission or the second information transmission among the ten information transmissions in step 2 within one scheduling round. The A-IoT UE determines whether the information it receives is the 'first' information based on the information indicating the number of information transmissions included in the information in step 2 (see <Proposal 7: Option 2>, <Proposal 7: Option 3>, and <Proposal 7: Option 4>).

[0211] <Proposal 7: Variation 2> If the transmission in step 3 is successful, the A-IoT UE may reset the probability and the number to be generated to their initial values ​​(for example, parameters such as x, N, and L may be reset to their initial values).

[0212] "Success" may mean that the A-IoT UE successfully performs the transmission, or that the A-IoT UE receives an ACK from the network at the PHY layer, or that the A-IoT UE receives an ACK from the network at a higher layer.

[0213] <Proposal 7: Variation 3> For a scheduling round of an A-IoT UE group, the network may transmit P pieces of step 2 information.

[0214] The parameters x, N, y, M, i, j, m, and L described in <Proposal 7: Option 1> to <Proposal 7: Option 1> may be provided by physical layer or higher layer signaling, or may be defined in a specification.

[0215] <Proposal 7: Summary> As explained above, when an A-IoT UE receives information from step 2, it determines transmission in step 3 based on a predetermined probability. This operation allows the A-IoT UE to reduce transmission collisions in step 3.

[0216] <Proposal 8> Proposal 8 proposes a technology to reduce (reduce) transmission collisions in step 3 of A-IoT UE.

[0217] In the cases of <Proposal 1: Option 1a> and <Proposal 1: Option 2a>, i.e., when resources are used in a contention-based manner, the transmissions of the A-IoT UEs in step 3 may collide.

[0218] If the A-IoT UE receives other information from Step 2 after the successful transmission of Step 3, it may perform the following operations in Options 1 and 2. For the meaning of "success", see <Proposal 7: Variation 2>.

[0219] <Proposal 8: Option 1> If there is data in the UL buffer, the A-IoT UE performs transmission in step 3. The transmission in step 3 may be transmission based on each of the proposals above.

[0220] <Proposal 8: Option 2> As explained in <Proposal 7: Variation 1>, the information in step 2 is distinguished whether it is for the same scheduling round as the previous step 2 or not.

[0221] If an A-IoT UE successfully transmits step 3 for information on a certain step 2 and then receives information on another step 2 in the same scheduling round as the certain step 2, it will not transmit step 3 for the information on the other step 2.

[0222] After successfully transmitting step 3 for information on a certain step 2, if the A-IoT UE receives information on another step 2 in a different (newer) scheduling round from the certain step 2, it transmits step 3 for the information on the other step 2.

[0223] <Proposal 8: Summary> As explained above, after the A-IoT UE has successfully transmitted step 3, it determines whether to transmit step 3 based on whether it has received the information for step 2 in the same scheduling round as the information for step 2 that triggered the transmission of step 3. This operation allows the A-IoT UE to transmit signals appropriately.

[0224] <Variations> Figure 46 is a diagram illustrating variations. In each of the above proposals, frequency hopping may be applied to determining frequency resources for A-IoT UEs.

[0225] Massive connectivity is one of the target scenarios for 6G. In massive connectivity, contention-based uplink transmission is a potential solution. The applicability of the proposal is not limited to A-IoT, but may also be used in other massive connectivity scenarios.

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

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

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

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

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

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

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

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

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

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

[0236] Here, the control unit 103 may provide one resource to multiple devices 20. The resource is a resource for multiple devices 20 to transmit signals, and may be, for example, a time / frequency / code domain resource. The signals transmitted by the multiple devices 20 may be signals in step 3 of the A-IoT communication flow.

[0237] The control unit 103 may provide a plurality of resources to a plurality of devices 20. The number of the plurality of resources may be less than the number of the plurality of devices 20. The number of the plurality of devices 20 may be equal to or greater than the number of the plurality of devices 20.

[0238] The control unit 103 may assign an index to a resource for transmitting a signal by the device 20. The control unit 103 may assign an index based on the method described in <Proposal 3>.

[0239] <Device Configuration> Fig. 48 is a block diagram showing an example of the configuration of the device 20 according to the embodiment. The device 20 is a device with lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, and is, for example, an A-IoT UE.

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

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

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

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

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

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

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

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

[0248] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ-ACK, channel state information (CSI), or a scheduling request (SR). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted in the resources of the PUCCH.

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

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

[0251] Here, the control unit 203 may acquire one resource provided to multiple devices by competing with the multiple devices. The control unit 203 may acquire one of multiple resources provided to multiple devices by competing with the multiple devices. The control unit 203 may acquire one of multiple resources provided to multiple devices without competing with the multiple devices. The resource may be a resource for signal transmission in step 3 of the A-IoT communication flow. The resource may be a time / frequency / code domain resource.

[0252] The transmitting unit 202 may transmit a signal using the resource acquired by the control unit 203. The signal may be the signal of step 3 in the A-IoT communication flow.

[0253] The control unit 203 may acquire one of a plurality of resources that is less than the number of devices by competing with the plurality of devices, or may acquire one of a plurality of resources that is equal to or greater than the number of devices without competing with the plurality of devices.

[0254] The control unit 203 may acquire one of a plurality of resources equal to or greater than the number of devices based on at least one of a defined rule and a defined parameter. The parameter may be, for example, an A-IoT UE-specific / common parameter instructed by the network. The parameter may be a parameter defined in the A-IoT UE, such as an A-IoT UE ID.

[0255] The control unit 203 may randomly acquire one of a plurality of resources that is less than the number of devices, or may randomly acquire one of a plurality of resources that is equal to or greater than the number of devices.

[0256] The control unit 203 may use the index assigned to the resource to determine (designate) the resource of the signal to be transmitted.

[0257] Here, the receiving unit 201 may receive information from a network. The information may be information of step 2 in the A-IoT communication flow.

[0258] The control unit 203 may determine to transmit a signal based on a predetermined probability when the receiving unit 201 receives information. The signal may be the signal of step 3 in the A-IoT communication flow.

[0259] The control unit 203 may determine whether to transmit a signal using the same probability each time the receiving unit 201 receives information. The control unit 203 may set a higher probability of determining whether to transmit a signal when receiving information for the second or subsequent times than a higher probability of determining whether to transmit a signal when receiving information for the first time. The control unit 203 may increase the probability of transmitting a signal each time information is received. The information may be received within the same scheduling round.

[0260] The control unit 203 may determine to transmit a signal based on a number randomly selected from a predetermined range of numbers such as 0, 1, ..., (N-1). For example, the control unit 203 may determine to transmit a signal when the selected number is 0 (or may be m).

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

[0262] <Hardware Configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0263] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

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

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

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

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

[0268] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the device 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

[0270] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0271] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

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

[0273] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

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

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

[0276] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0277] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

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

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

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

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

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

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

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

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

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

[0287] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

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

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

[0291] <Base Station> In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0292] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

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

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

[0297] Furthermore, the base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the device 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

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

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

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

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

[0303] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

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

[0305] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

[0308] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0309] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

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

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

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

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

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

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

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

[0317] Open Format: When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0318] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

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

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

[0324] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

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

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

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

[0328] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0329] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

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

[0331] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0333] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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

[0336] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.

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

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

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

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

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

Claims

1. A device of lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, comprising: a control unit that competes with a plurality of devices to acquire a resource provided to the plurality of devices, or acquires one of a plurality of resources provided to the plurality of devices, either by competing with the plurality of devices or without competition; and a transmission unit that transmits a signal using the acquired resource.

2. The device according to claim 1, wherein the control unit acquires one of the plurality of resources that is less than the number of the plurality of devices by competing with the plurality of devices, or acquires one of the plurality of resources that is equal to or greater than the number of the plurality of devices without competing with the plurality of devices.

3. The device according to claim 2, wherein the control unit acquires one of the plurality of resources, the number of which is equal to or greater than the number of the plurality of devices, based on at least one of a defined rule and a defined parameter.

4. The device according to claim 2, wherein the control unit randomly acquires one of the plurality of resources, the number of which is less than the number of the plurality of devices.

5. The device according to claim 1, wherein each of the plurality of resources, the number of which is equal to or greater than the number of the plurality of devices, is assigned an index.

6. A communication method for a device with lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, comprising: acquiring a resource provided to a plurality of devices by competing with the plurality of devices; or acquiring one of a plurality of resources provided to the plurality of devices by competing with the plurality of devices or without competing with the plurality of devices; and transmitting a signal using the acquired resource.

Images