Apparatus, wireless communication device, and wireless communication method

Abstract

An Ambient Internet of Things (A-IoT) device includes: a control unit that divides a single data unit with a specific data processing unit into more than one segment; and a transmission unit that transmits more than one signal, each containing more than one segment.

Description

Technical Field

[0001] This disclosure relates to devices, wireless communication apparatuses, and wireless communication methods. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies are being researched to meet requirements such as high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving (for example, see Non-Patent Literature 1).

[0003] Furthermore, in 3GPP (registered trademark) version 18 (Rel-18), Ambient Internet of Things (A-IoT) is being researched (e.g., see Non-Patent Document 2). In Ambient Internet of Things, the target is devices with extremely simple structures for low-end IoT applications that operate with minimal power consumption.

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 38.300 V17.3.0 (2022-12)

[0007] Non-patent document 2: "Revised SID on Ambient IoT", RP-232404, 3GPP TSG RANMeeting #101, September 2023

[0008] Non-patent document 3: 3GPP TR 38.848 V1.0.0 (2023-09)

[0009] Non-patent document 4: 3GPP TS 36.211 V16.8.0 (2023-09)

[0010] Non-patent literature 5: "Study on solutions for Ambient IoT (Internet of Things) in NR", RP-234058, 3GPP TSG RAN Meeting #102, December 2023 Summary of the Invention

[0011] There is still room for research into the structure of data exchanged between environmental IoT devices and other wireless communication devices in communication systems that include environmental IoT devices.

[0012] One aspect of this disclosure provides an apparatus, a wireless communication device, and a wireless communication method, wherein an environmental IoT device is capable of exchanging data with other wireless communication devices in an appropriately configured manner.

[0013] The device involved in one aspect of this disclosure is an Ambient Internet of Things (A-IoT) device, comprising: a control unit that divides a single data unit having a specific data processing unit into one or more segments; and a transmission unit that transmits one or more signals, each containing one or more segments. Attached Figure Description

[0014] Figure 1 This is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure.

[0015] Figure 2 This is a diagram illustrating Topology 1.

[0016] Figure 3 This is a diagram illustrating topology 2.

[0017] Figure 4 This is a diagram illustrating topology 3 in DL-assisted programming.

[0018] Figure 5 This is a diagram illustrating topology 3 in UL-assisted programming.

[0019] Figure 6 This is a diagram illustrating topology 4.

[0020] Figure 7 This is a diagram illustrating backscattering transmission.

[0021] Figure 8 This is a diagram showing the communication flow of DT in topology 1.

[0022] Figure 9 This is a diagram illustrating the communication flow of DO-DTT in Topology 1.

[0023] Figure 10 This is a diagram showing the communication flow of DT in topology 2.

[0024] Figure 11 This is a diagram illustrating the communication flow of DO-DTT in Topology 2.

[0025] Figure 12 This is a diagram illustrating an example of the structure of a MAC PDU in TX.

[0026] Figure 13 This is a diagram representing option A of the method for obtaining the transmission schedule.

[0027] Figure 14 This is a diagram representing option B of the method for obtaining the transmission schedule.

[0028] Figure 15 This is a diagram representing an example of a time-based approach for option C of proposal a.

[0029] Figure 16 This is a diagram illustrating an example of how a MAC PDU is associated with a fixed number of transmissions.

[0030] Figure 17 This is a diagram illustrating an example indicated by PI.

[0031] Figure 18 This is a diagram illustrating an example of CRC appending per segment and per MAC PDU.

[0032] Figure 19 This is a diagram illustrating an example of the structure of a MAC PDU in RX.

[0033] Figure 20 This is a diagram representing option A of the method for obtaining the receiving schedule.

[0034] Figure 21 This is a diagram representing option B, which shows the method for obtaining the receiving schedule.

[0035] Figure 22 This is a diagram representing an example of a time-based approach for option C of proposal a.

[0036] Figure 23 This is a diagram illustrating an example of how a MAC PDU is associated with a fixed number of receptions.

[0037] Figure 24 This is a diagram illustrating an example indicated by PI.

[0038] Figure 25 This is a diagram illustrating an example of CRC appending per segment and per MAC PDU.

[0039] Figure 26 This is a block diagram illustrating an example of the structure of a base station according to an embodiment of the present disclosure.

[0040] Figure 27 This is a block diagram illustrating an example of the structure of a device involved in an embodiment of the present disclosure.

[0041] Figure 28 This is a diagram illustrating an example of the hardware structure of a base station and device involved in an embodiment of this disclosure.

[0042] Figure 29 This is a diagram illustrating an example of the structure of a vehicle according to an embodiment of this disclosure. Detailed Implementation

[0043] Hereinafter, an embodiment of the present disclosure will be described with reference to the accompanying drawings. Furthermore, the embodiment described below is an example, and the application of the present disclosure is not limited to the following embodiment.

[0044] In operating the wireless communication system according to the embodiments of this disclosure, existing technology is appropriately used. This existing technology includes, but is not limited to, existing LTE or NR. Furthermore, unless otherwise stated, the term "LTE" as used in this specification is intended to have a broad meaning encompassing LTE-Advanced and subsequent methods.

[0045] Furthermore, in the embodiments of this disclosure described below, the terms SS (synchronization signal), PSS (primary SS), SSS (secondary SS), PBCH (physical broadcast channel), PRACH (physical random access channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), and PUSCH (physical uplink shared channel) used in existing LTE systems are used. These are for ease of description, and the same signals, functions, etc., can also be referred to by other names. In addition, the above 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 explicitly written as "NR-".

[0046] Furthermore, in the embodiments of this disclosure, the duplex mode can be either TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0047] Furthermore, in the embodiments of this disclosure, the so-called "configured" wireless parameters can be either specific values ​​that are pre-configured or wireless parameters that are set from notifications from base stations, devices, terminals, etc.

[0048] (Implementation Method)

[0049] Wireless Communication Systems

[0050] Figure 1 This is a diagram illustrating an example of a wireless communication system according to an embodiment of this disclosure. (See diagram for example.) Figure 1 As shown, the wireless communication system 1 includes a base station 10 and a device 20. Figure 1In this diagram, one base station 10 and one device 20 are shown, but this is just one example; multiple base stations and devices may exist. Base stations are also referred to as BS (Base Station), gNB, etc. Device 20 can also be called a terminal (UE: User Equipment), and can be an environmental IoT device that is less complex than NB-IoT (Narrow Band Internet of Things) devices. Environmental IoT devices can also be called environmental IoT terminals, environmental IoT UEs, etc.

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

[0052] Base station 10 sends control information, setting information, data, and other DL signals to device 20 in the DL (Downlink) channel. Base station 10 receives control information, information related to the processing capabilities of device 20 (device capability (information) or A-IoT capability (information); for example, capability, device capability, A-IoT capability, A-IoT device capability, etc.), data, and other UL signals from device 20 in the UP (Uplink) channel.

[0053] The channels used in transmitting DL signals include, for example, data channels and control channels. For instance, a data channel may include a Physical Downlink Shared Channel (PDSCH), and a control channel may include a Physical Downlink Control Channel (PDCCH). For example, base station 10 uses the PDCCH to send control information to device 20 and uses the PDSCH to transmit DL data signals. Furthermore, the PDSCH is an example of a downlink shared channel or a data channel, and the PDCCH is an example of a downlink control channel. The PDCCH can also be rewritten to contain downlink control information (DCI), control information, etc., transmitted within it.

[0054] As will be described later, wireless communication systems may also include intermediate nodes, assisting nodes, and / or users (UEs) (see <Device Types and Topologies> below). Additionally, in the following, "and / or" is sometimes abbreviated as " / ".

[0055] Device 20 is a communication device with wireless communication capabilities, as described above, and can be an environmental IoT device (e.g., a sensor). Hereinafter, environmental IoT devices are also referred to as A-IoT UE.

[0056] Device 20 receives control signals, setting information, data and other DL signals from base station 10 in DL, and sends control signals, device 20 capability information, data and other UL signals to base station 10 in UL.

[0057] The channels used in transmitting UL signals include, for example, data channels and control channels. For instance, a data channel may include a Physical Uplink Shared Channel (PUSCH), and a control channel may include a Physical Uplink Control Channel (PUCCH). For example, device 20 uses the PUCCH to transmit control information and the PUSCH to transmit UL data signals. Furthermore, the PUSCH is an example of an uplink shared channel or a data channel, and the PUCCH is an example of an uplink control channel. Additionally, the PUSCH or PUCCH can be rewritten as uplink control information (UCI), control information, etc., transmitted within the PUSCH or PUCCH.

[0058] <Environmental IoT>

[0059] In Rel-18, research related to environmental IoT that is lower-end than existing NB-IoT (e.g., refer to section 10 of Non-Patent Document 4) was approved (e.g., refer to Non-Patent Document 2). In environmental IoT, the goal is to have ultra-low power consumption and ultra-low complexity devices.

[0060] In environmental IoT, for example, for associated use cases, the following introduction scenarios and characteristics can be studied.

[0061] Indoor or outdoor environment

[0062] • Base station type, for example, configuration based on macro cells / micro cells / pecimens

[0063] • The topology involved in connectivity, such as which node—base station, user device (UE), relay, or repeater—communicates with the environmental IoT devices.

[0064] • Whether the duplex mode is TDD or FDD, and whether the frequency band is a licensed or unlicensed band.

[0065] • Coexistence with UEs and network equipment in frequency bands oriented towards existing 3GPP technologies

[0066] • A conception of traffic services for sending information from / to devices.

[0067] Based on the aforementioned introduction scenarios and characteristics, the following RAN design goals can be formulated, for example.

[0068] Power consumption

[0069] • Complexity

[0070] • Coverage

[0071] Data rate

[0072] • Positioning accuracy

[0073] Based on the introduction scenario suitable for the associated use cases, the feasibility of meeting the design goals is compared and evaluated to determine the supported functions.

[0074] <Device Type and Topology>

[0075] Based on the results of the research project, TR 38.848 (Non-Patent Document 3) was approved. TR 38.848 investigates the following types of environmental IoT devices.

[0076] Device A: Device A does not have an energy storage device, does not have independent signal generation and signal amplification functions, and performs backscattering transmission.

[0077] Device B: Device B has a power storage device but does not have independent signal generation capabilities; it performs backscatter transmission. Device B uses the stored power to amplify the reflected signal.

[0078] Device C: Device C has a power storage device, an independent signal generation function, and an active RF (radio frequency) component for transmission.

[0079] Furthermore, imagine that the complexity of device A is equivalent to that of RFID (Radio Frequency Identification).

[0080] In TR 38.848, topologies 1-4 are defined in the context of environmental IoT networks.

[0081] Figure 2 This is a diagram illustrating Topology 1. For example... Figure 2 As shown, Topology 1 is the structure for communication between the base station (BS) and environmental IoT devices. The environmental IoT devices directly perform bidirectional communication with the base station.

[0082] Figure 3 This is a diagram illustrating Topology 2. For example... Figure 3 As shown, Topology 2 is a structure in which the base station and the environmental IoT device communicate via an intermediate node. The environmental IoT device performs bidirectional communication with the intermediate node configured between the base station and the environmental IoT device. The intermediate node can be, for example, a relay, an IAB (integrated access and backhaul) node, a UE, a repeater, etc.

[0083] Figure 4 This is a diagram illustrating topology 3 in DL-assisted programming. For example... Figure 4 As shown, Topology 3 is a structure that includes communication between the base station and the assistant node, communication between the assistant node and the environmental IoT device, and communication between the environmental IoT device and the base station.

[0084] Auxiliary nodes assist in deep communication. For example, such as... Figure 4 As shown, the auxiliary node receives the DL signal from the base station and transmits the received DL signal to the environmental IoT device. For UL communication, the environmental IoT device transmits the UL signal directly to the base station.

[0085] Figure 5 This is a diagram illustrating topology 3 in UL-assisted implementation. For example... Figure 5 As shown, Topology 3 is a structure that includes communication between the base station and auxiliary nodes, communication between auxiliary nodes and environmental IoT devices, and communication between environmental IoT devices and the base station.

[0086] Auxiliary nodes assist UL communication. For example, such as... Figure 5As shown, the auxiliary node receives the UL signal from the environmental IoT device and sends the received UL signal to the base station. For DL ​​communication, the environmental IoT device directly receives the DL signal from the base station.

[0087] Figure 4 as well as Figure 5 The auxiliary nodes shown can also be relays, IAB nodes, UEs, repeaters, etc.

[0088] Figure 6 This diagram illustrates Topology 4. Topology 4 is the structure for communication between the UE and the environmental IoT devices. The environmental IoT devices and the UE perform bidirectional communication. The communication involved in Topology 4 can also be understood as sidelink (SL) communication.

[0089] In addition, in the topologies 1 to 4 described above, the carrier can also be provided to the environmental IoT device from other nodes inside or outside the topology (see Section 4.2.1 of Non-Patent Document 3).

[0090] In addition to device 20, wireless communication system 1 (wireless communication network) may also include base stations, auxiliary nodes, intermediate nodes, and / or terminals (UEs of topology 4). In this specification, base stations, auxiliary nodes, intermediate nodes, and terminals may also be rewritten as networks or (network) nodes. Furthermore, A-IoT devices are sometimes simply referred to as A-IoT.

[0091] <Backscatter transmission>

[0092] Base stations, intermediate nodes, auxiliary nodes, and other nodes send RF signals to environmental IoT devices. The environmental IoT devices can be activated and receive power from the RF operating field of the base stations, intermediate nodes, auxiliary nodes, and other nodes via inductive coupling.

[0093] Environmental IoT devices switch the reflection coefficient of their antennas to perform backscatter modulation on RF signals received from base stations, intermediate nodes, auxiliary nodes, and other nodes, and then send information to these base stations, intermediate nodes, auxiliary nodes, and other nodes.

[0094] Figure 7 This is a diagram illustrating backscattering. In Figure 7 The image shows an example of an environmental IoT device performing ON-OFF keying and sending information. Figure 7 The area shown by the dashed line can also represent the off interval, corresponding to the information (bit) "0". A sine wave signal can also correspond to the information "1".

[0095] <Rel-19 SID>

[0096] The Rel-19 SID (Study Item Description) investigates necessary and feasible solutions for A-IoT (refer to Section 4.1 of Non-Patent Document 5). The solutions investigated include, for example, determining which functions or processes are necessary and which are unnecessary.

[0097] In addition, several issues were discussed in RAN 1 regarding the deep learning (DL) and long-range (UL) of A-IoT. One of these issues was the scheduling and timing relationships between DL and UL in A-IoT. The discussion of scheduling and timing relationships included examining the following: 1. Traffic Flow, 2. Device Assumptions, and 3. Topology.

[0098] 1. Business Flow

[0099] As a business direction for A-IoT, we are studying the following DT and DO-DTT.

[0100] DT (Device terminated)

[0101] As a traffic activity, there are transmissions (DL) to the A-IoT UE, but no transmissions (UL) originating from the A-IoT UE. In other words, there is information being sent to the A-IoT UE, but no information being sent from the A-IoT UE. DT, for example, corresponds to a command-type instruction such as an order or command sent to the A-IoT UE.

[0102] • DO-DTT (Device-Originated - Device-Terminated Triggered)

[0103] As a service, there are triggers from the network (NW) and transmissions from the A-IoT UE (UL). In other words, as a service, there is information transmitted from the A-IoT UE. DO-DTT, for example, corresponds to a sensor information reporting type that transmits sensor information collected by the A-IoT UE.

[0104] Furthermore, in this disclosure, the transmission of information corresponds to the transmission of a signal containing information or the transmission of a signal. Additionally, in this disclosure, transmission to a device X corresponds to the transmission of a signal (or information) to device X. Furthermore, transmission from a device X and transmission from a device X correspond to device X transmitting a signal (or information). Furthermore, reception from a device X corresponds to receiving a signal (or information) transmitted by receiving device X. Furthermore, reception from a device X corresponds to device X receiving a signal (or information).

[0105] 2. Equipment prerequisites

[0106] In A-IoT UE, the following TX (transmit) and FR (frequency range) 1-FDD are assumed.

[0107] TX

[0108] TX is either a backscattered UL transmission without amplifier (amplified) or a normal UL transmission with amplifier. Alternatively, a backscattered UL transmission with amplifier can also be performed.

[0109] · FR1-FDD

[0110] FR1-FDD is applied in A-IoT UEs. That is, A-IoT UEs can switch carrier frequencies between the carrier of DL and the carrier of UL. However, this disclosure is not limited to FR1-FDD, and can be applied to TDD, FR2, or FR3.

[0111] In addition, the frequency bands of each FR are as follows.

[0112] FR1: 410MHz~7.125GHz

[0113] • FR2: 24.25GHz~52.6GHz

[0114] • FR3: 7.125GHz~24.25GHz

[0115] In FR1, sub-carrier spacing (SCS) of 15kHz, 30kHz, or 60kHz can be used, with a bandwidth of 5~100MHz (BW). FR2 has a higher frequency than FR1 and can also use SCS of 60kHz or 120kHz (including 240kHz), with a bandwidth of 50~400MHz (BW).

[0116] 3. Topology

[0117] exist Figures 2-6Of the topologies shown, we are focusing on topology 1 and topology 2.

[0118] In Topology 1, UL and / or DL ​​communication occurs between the base station and the A-IoT UE without going through intermediate nodes. Additionally, the base station in Topology 1 can also correspond to a microcell.

[0119] In Topology 2, communication occurs between the base station and the A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with the intermediate node configured between the base station and the A-IoT UE. Furthermore, the base station in Topology 2 can also correspond to a macro cell. Additionally, Topology 2 can also be applied to indoor scenarios. Hereinafter, the intermediate node will also be referred to as intermediate UE, int.UE (intermediate UE), etc.

[0120] <Communication process>

[0121] The signal design for the A-IoT UE can also be designed to be common between Topology 1 and Topology 2. To make the signal design for the A-IoT UE common, the communication flows of DT and DO-DTT in Topology 1 and Topology 2 can be studied. The following four communication flows can be envisioned as the communication flows of DT and DO-DTT in Topology 1 and Topology 2.

[0122] Additionally, as shown in the four communication processes 1 to 4 below, the A-IoT UE is woken up in step 1 and receives information (or signals) in step 2. Furthermore, as shown in the communication processes 2 and 4 below, the A-IoT UE sends signals (or information) in step 3.

[0123] 1. Communication process of DT in Topology 1

[0124] Figure 8 This is a diagram showing the communication flow of DT in topology 1. Figure 8 The diagram shows the signal flow between the base station and the A-IoT UE. Additionally, Figure 8 The communication flow shown is the DT communication flow. Therefore, although there is information transmission from the base station to the A-IoT UE, there is no information transmission from the A-IoT UE to the base station.

[0125] In the communication flow of DT in Topology 1, consider the following two steps. Additionally, step 1 may involve the generation of packets at a higher layer, such as the application layer of the base station (equivalent to...). Figure 8 The “Packetarrival” indicator will be displayed.

[0126] • Step 1: The A-IoT UE is woken up by a signal such as a carrier waveform sent from the base station. The signal sent from the base station can correspond to the energy source supplying power to the A-IoT UE. The carrier waveform can also be replaced by a carrier wave.

[0127] Step 2: The A-IoT UE receives information from the base station.

[0128] Alternatively, an A-IoT UE can also be woken up by signals transmitted from outside the base station (e.g., RF signals). Here, the signals transmitted from outside the base station can correspond to an energy source that supplies power to the A-IoT UE.

[0129] 2. Communication process of DO-DTT in Topology 1

[0130] Figure 9 This is a diagram illustrating the communication flow of DO-DTT in Topology 1. Figure 9 This shows the signal flow between the base station and the A-IoT UE. Additionally, Figure 9 The communication flow shown is the DO-DTT communication flow. Therefore, there is information transmission from the base station to the A-IoT UE and information transmission from the A-IoT UE to the base station.

[0131] In the DO-DTT communication flow in Topology 1, consider the following three steps. Additionally, step 1 may involve packets generated at higher layers such as the application layer of the base station (equivalent to...). Figure 9 The “Packet arrival” indicator will begin.

[0132] • Step 1: The A-IoT UE is woken up by a signal such as a carrier waveform sent from the base station.

[0133] Step 2: The A-IoT UE receives information from the base station.

[0134] Step 3: The A-IoT UE sends a signal to the base station.

[0135] 3. Communication process of DT in Topology 2

[0136] Figure 10 This is a diagram showing the communication flow of DT in topology 2. Figure 10 This shows the signal flow between the base station, the intermediate UE (int.UE), and the A-IoT UE. Additionally, Figure 10The communication flow shown is the DT communication flow. Therefore, although there is information transmission to the A-IoT UE, there is no information transmission from the A-IoT UE.

[0137] In the communication flow of DT in Topology 2, consider the following four steps. Additionally, step 0 might involve packets generated at a higher layer, such as the application layer of the base station (equivalent to...). Figure 10 The “Packet arrival” indicator will begin.

[0138] • Step 0: The intermediate UE (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.

[0139] • Step 1: The A-IoT UE is woken up by a signal such as a carrier waveform sent from the intermediate UE (int.UE).

[0140] Step 2: The A-IoT UE receives information from the intermediate UE (int.UE).

[0141] • Step X: The intermediate UE (int.UE) sends a signal to the base station.

[0142] 4. Communication process of DO-DTT in Topology 2

[0143] Figure 11 This is a diagram illustrating the communication flow of DO-DTT in Topology 2. Figure 11 This shows the signal flow between the base station, the intermediate UE (int.UE), and the A-IoT UE. Additionally, Figure 11 The communication flow shown is the DO-DTT communication flow, therefore, there is information transmission to the A-IoT UE and information transmission from the A-IoT UE.

[0144] In the DO-DTT communication flow in Topology 2, consider the following five steps. Additionally, step 0 might involve packets generated at a higher layer, such as the application layer of the base station (equivalent to...). Figure 11 The “Packet arrival” indicator will begin.

[0145] • Step 0: The intermediate UE (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.

[0146] • Step 1: The A-IoT UE is woken up by a signal such as a carrier waveform sent from the intermediate UE (int.UE).

[0147] Step 2: The A-IoT UE receives information from the intermediate UE (int.UE).

[0148] Step 3: The A-IoT UE sends a signal to the intermediate UE (int.UE).

[0149] • Step X: The intermediate UE (int.UE) sends a signal to the base station.

[0150] Furthermore, in the four communication processes described above (1. to 4.), steps 2 and 3 can also be divided into two steps (in other words, they can also have two sub-steps).

[0151] For example, in the communication flow of DT in topology 1 / 2, step 2 can also have the following two sub-steps (step 2A and step 2B).

[0152] Step 2A: The A-IoT UE receives information A (e.g., control information or signals) from the base station / intermediate UE (int.UE).

[0153] Step 2B: The A-IoT UE receives information B (e.g., data information or signals) from the base station / intermediate UE (int.UE).

[0154] Furthermore, for example, in the DO-DTT communication flow in topology 1 / 2, step 3 may also have the following two sub-steps (step 3A and step 3B).

[0155] Step 3A: The A-IoT UE sends signal A (e.g., control information or signal) to the base station / intermediate UE (int.UE).

[0156] Step 3B: The A-IoT UE sends signal B (e.g., data information or signal) to the base station / intermediate UE (int.UE).

[0157] <Research Matters>

[0158] As described above, the communication process of A-IoT includes the transmission and reception of signals in the following steps. Additionally, two or more of the following steps may sometimes be combined into a single step. Furthermore, at least one of the following steps may sometimes be skipped.

[0159] Step 1a: Power source signal / wake-up signal

[0160] Step 1b: Synchronization signals

[0161] • Step 2: Signals for receiving data from NW (including any one of DL control information, DL data, DL control information, and DL data)

[0162] • Step 1c: Carrier used for backscattering (e.g., unmodulated carrier)

[0163] Step 3: Signals for transmitting data from the A-IoT UE

[0164] As described above, in step 2, the A-IoT UE receives signals from the BS or an intermediate UE. Furthermore, in step 3, the A-IoT UE transmits signals to the BS or an intermediate UE.

[0165] In the transmission and reception of signals containing data, each data item is processed in a specific processing unit. For example, a specific processing unit of data is called a transport block (TB). Additionally, in the following description, the transmitted / received signal can be replaced with the transmission / received channel.

[0166] Regarding TB for legacy UEs (NR or LTE UEs, etc.), the following provisions apply.

[0167] •TB corresponds to a MAC PCU that includes one or more MAC subheaders, MAC-CE, MAC SDU, and padding bits.

[0168] • Regarding the transport block size (TBS), the length is aligned to bytes. In other words, the TBS is a multiple of 8 bits in length.

[0169] • Each of the PDSCHs, except for the PUSCH which does not have a UL-SCH, carries one or more TBs.

[0170] Regarding TB for A-IoT UE, the following provisions are being studied in TR (technical report) 38.848, etc.

[0171] • The maximum message size (size) for both TX and RX is approximately 1000 bits.

[0172] The aforementioned maximum message size specification does not mean that a single PHY channel should contain that message (e.g., a message of approximately 1000 bits). In other words, the design of TBS is not yet explicitly defined.

[0173] The minimum data rate that users can perceive is 0.1kbps, and the maximum is 5kbps.

[0174] As mentioned above, although the TB (Transmission Module) for A-IoT UEs is under study, the regulations regarding the data transmitted by A-IoT UEs are still unclear. In other words, the regulations regarding the data transmitted by A-IoT UEs to BS (Browser Base Station) or intermediate UEs, such as the transmitted TB, are not yet clear.

[0175] Furthermore, as mentioned above, although the TB (Data Transfer) for A-IoT UEs is under investigation, the specifications regarding the received data used by A-IoT UEs are still unclear. In other words, the specifications regarding the data received by A-IoT UEs from BS (BS) or intermediate UEs, such as the received TB, are not yet clear.

[0176] As an example, as with conventional UEs, the following description uses one TB to correspond to one MAC PDU. However, this disclosure is not limited to this. For example, one TB may also correspond to a part of a MAC PDU. Furthermore, the transmission or reception of a physical channel may not correspond to one TB, but may correspond to a part of a MAC PDU. Hereinafter, the transmission or reception of data will be described as the transmission or reception of a MAC PDU, but this is not a limitation. In addition, in this embodiment, as an example, the data processing unit is referred to as "TB" or "MAC PDU", but this disclosure is not limited to these designations.

[0177] For example, the MAC PDU contains provisions related to at least one of the following.

[0178] • Methods for obtaining information about scheduling associated with MAC PDUs (e.g., notification methods)

[0179] • Methods for obtaining the size of the MAC PDU (e.g., notification methods)

[0180] • Methods for transforming MAC PDUs (e.g., methods for transforming MAC PDUs into formats different from MAC PDUs)

[0181] • Methods for signal processing of MAC PDUs (e.g., channel coding, CRC appending methods).

[0182] • Size of MAC PDU

[0183] For example, if any one of the above-mentioned provisions regarding the MAC PDU is unclear, data exchange with an appropriate structure cannot be performed. For example, in this case, inconsistency will occur between the data sending and receiving sides, making proper communication processing (e.g., transformation processing to the MAC PDU during reception) impossible.

[0184] When the method of scheduling associated with a MAC PDU (e.g., notification method) is unclear—for example, when it is unclear which MAC PDU's data the transmitted signal belongs to—the transmitting wireless communication device may be unable to determine which MAC PDU's data should be included in the transmitted signal. Furthermore, in this case, the receiving wireless communication device may be unable to properly retrieve the MAC PDU from the received signal. For instance, when the notification method for scheduling associated with a MAC PDU is unclear, the wireless communication device cannot determine whether blocks of data contained in multiple received signals belong to the same MAC PDU, and therefore may be unable to properly restore the MAC PDU from the blocks of data contained in multiple signals.

[0185] For example, if the method for notifying the size of the MAC PDU is unclear, the wireless communication device transmitting the signal may not be able to determine the size of the MAC PDU data contained in the transmitted signal. Furthermore, in this case, the wireless communication device receiving the signal may not be able to properly retrieve the MAC PDU from the received signal. For instance, if the method for notifying the size of the MAC PDU is unclear, the wireless communication device may not know that the MAC PDU can be reconstructed by concatenating blocks of data contained in several received signals, and therefore may be unable to properly reconstruct the MAC PDU from blocks of data contained in multiple signals.

[0186] For example, if the conversion method of the MAC PDU is unclear, the wireless communication device transmitting the signal may be unable to perform the conversion from the MAC PDU to the transmitted signal. Furthermore, in this case, the wireless communication device receiving the signal may be unable to properly retrieve the MAC PDU from the received signal. For example, if the conversion method between the MAC PDU and forms different from the MAC PDU is unclear, the wireless communication device may be unable to properly reconstruct the MAC PDU from blocks of data contained in each of multiple signals and having a form different from the MAC PDU.

[0187] For example, if the signal processing method for the MAC PDU is unclear, the wireless communication device transmitting the signal may be unable to perform the conversion from the MAC PDU to the transmitted signal. Furthermore, in this case, the wireless communication device receiving the signal may be unable to properly extract the MAC PDU from the received signal. For instance, if the channel coding and CRC appending for the MAC PDU are unclear, it may be unable to properly perform decoding corresponding to the channel coding of blocks obtained by linking data blocks contained in multiple received signals, and CRC-based error detection.

[0188] Therefore, in this embodiment, provisions regarding the MAC PDU are proposed. By setting the provisions regarding the MAC PDU to any of the proposals shown below, inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing to the MAC PDU during reception) can be performed.

[0189] Additionally, in the following explanation, TX corresponds to the transmission of the A-IoT UE, that is, the A-IoT UE transmits to the BS or an intermediate UE. Furthermore, RX corresponds to the reception of the A-IoT UE, that is, the A-IoT UE receives from the BS or an intermediate UE.

[0190] The following describes the proposals related to the MAC PDU for each of TX (that is, the transmission of the A-IoT UE) and RX (that is, the reception of the A-IoT UE).

[0191] In the following, the TX of one or more PHY channels / signals corresponds to the TX of one MAC PDU. In other words, an A-IoT UE uses more than one PHY channel or more than one signal to transmit a MAC PDU. Additionally, the PHY channel (physical layer channel) is sometimes simply referred to as a channel. Furthermore, in the following description, channel may also be replaced with signal (e.g., physical layer signal).

[0192] Furthermore, in the following, the RX of one or more PHY channels / signals corresponds to the RX of one MAC PDU. In other words, the A-IoT UE receives one MAC PDU contained in one or more PHY channels or signals.

[0193] Furthermore, the transmission of a MAC PDU (e.g., MAC PDU#X) corresponds to the transmission of a channel / signal containing a portion of MAC PDU#X, and the reception of MAC PDU#X corresponds to the reception of a channel / signal containing a portion of MAC PDU#X. Additionally, the transmitted MAC PDU#X corresponds to at least a portion of the MAC PDU#X contained in the transmitted signal, and the received MAC PDU#X corresponds to at least a portion of the MAC PDU#X contained in the received signal.

[0194] <About TX (Transmission of A-IoT UE)>

[0195] Figure 12 This is a diagram illustrating an example of the structure of a MAC PDU in TX. Figure 12 The image shows a MAC PDU divided into N (N is an integer greater than or equal to 1) blocks for transmission. The following is an example... Figure 12 As shown, sometimes the size of a MAC PDU (e.g., length, number of bits) is recorded as L_total, and the N blocks are recorded as TX-1 to TX-N, with the size of each of the N blocks recorded as L_1 to L_N. Alternatively, N and / or L_total can vary for each MAC PDU. L_1 to L_N can also be the same for each other. TX-1 to TX-N can correspond to the indices that identify the blocks of the MAC PDU.

[0196] in addition, Figure 12 The N blocks in the MAC PDU can also be recorded as segments, or replaced with other names. In the following description, a block of a MAC PDU is a block that includes at least a portion of the data of that MAC PDU.

[0197] The A-IoT UE divides (segments) the MAC PDU into N segments, TX-1 to TX-N, and sends signals containing TX-1 to TX-N to the receiving wireless communication device (e.g., BS or intermediate UE). The receiving wireless communication device receives the signals containing TX-1 to TX-N respectively and connects them in the order of TX-1 to TX-N to generate (or reconstruct) the MAC PDU.

[0198] The following are proposals a through f, which are related to MAC PDUs in TX.

[0199] <Proposal a in TX: A method for obtaining the transmission schedule of MAC PDUs>

[0200] Proposal a describes, as an example of a method for obtaining the transmission schedule of a MAC PDU, how a wireless communication device (e.g., at least one of an A-IoT UE, an intermediate UE, and a BS) obtains the transmission schedule of a new MAC PDU. In other words, it describes a method for determining whether a block of MAC PDUs contained in a certain channel / signal is a block of a new MAC PDU when a MAC PDU is transmitted through one or more channels / signals. Here, the case where a block of MAC PDUs contained in a certain channel / signal is not a block of a new MAC PDU is equivalent to a block of MAC PDUs contained in that channel / signal being a block of the same MAC PDU as a channel / signal transmitted before that channel / signal.

[0201] The MAC PDU transmission schedule can also include scheduling information for transmitting the MAC PDU.

[0202] <Option A of Proposal a in TX>

[0203] In option A, which determines the method for obtaining the transmission schedule, an indicator for the transmission schedule is set. Then, the indicator is indicated for each schedule of the channel / signal via a toggling mechanism. The indicator set here is referred to as NPI (New Packet Indicator). However, this indicator can also be associated with other names.

[0204] In option A of proposal a, when an NPI is toggled (e.g., when an NPI is switched), the toggled NPI indicates that the transmission of a new MAC PDU is scheduled. When an NPI is toggled, the transmission of a new MAC PDU can be scheduled regardless of whether the transmission of the MAC PDU prior to the NPI toggling has been completed. Additionally, if the transmission of the MAC PDU prior to the NPI toggling has not been completed, a portion of the MAC PDU prior to the NPI toggling can also be flushed. "Flush" can also be replaced with other expressions such as "discard" or "delete".

[0205] Furthermore, in option A of proposal a, in the case where the NPI is not flipped (e.g., in the case where the NPI is not switched), the unflipped NPI means scheduling the same MAC PDU as the MAC PDU sent before the unflipped NPI.

[0206] In option A of proposal a, the NPI can be included in the scheduling information (e.g., DCI, etc.) used for scheduling the transmission. For example, the A-IoT UE receives the scheduling information, refers to the NPI included in the scheduling information, determines whether to use blocks of data being transmitted by the A-IoT UE as blocks of a new MAC PDU, and based on the determination result, sends a signal containing the block of the MAC PDU.

[0207] In option A of proposal a, the NPI can be included in the transmitted channel / signal. For example, the A-IoT UE transmits a signal containing at least a portion of the MAC PDU and the NPI. Then, the BS or intermediate UE, acting as the receiving wireless communication device, refers to the NPI of the signal received from the A-IoT UE, determines whether the block of data contained in the signal is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0208] Figure 13 This is a diagram representing option A of the method for obtaining the transmission schedule. Figure 13 The horizontal axis represents the time axis. Figure 13 The example shown is of sending two MAC PDUs, MAC PDU#A and MAC PDU#B. Figure 13 TX-i (where i is an integer greater than 1 and less than N) can represent a block of a MAC PDU, or a channel / signal containing a block of a MAC PDU.

[0209] exist Figure 13 In the example, MAC PDU#B corresponds to the new MAC PDU. That is, TX-1 of MAC PDU#B is relative to the MAC PDUs sent before it up to TX-N (in... Figure 13 In the example, the block of MAC PDU#A is a new MAC PDU block. In this case, the NPI of TX-N of MAC PDU#A is 0, and the NPI of TX-1 of MAC PDU#B is 1. That is, the NPI of TX-1 of MAC PDU#B is flipped.

[0210] In addition, Figure 13 In the example, it has been sent up to TX-N of MAC PDU#A. That is to say, in Figure 13 In the example, the transmission of MAC PDU#A has been completed. (And...) Figure 13 Unlike other cases, if TX-1 to TX-k (where k is an integer greater than 1 and less than N) of MAC PDU#A is sent, the transmission of MAC PDU#A is incomplete. In this case, a portion of MAC PDU#A (e.g., the block from TX-1 to TX-k) can be flushed.

[0211] In addition, Figure 13 The example shown illustrates a flip from 0 to 1, but it is also possible to flip from 1 to 0. Furthermore, NPI is not limited to examples that flip between 0 and 1.

[0212] As in option A above, by setting the NPI to notify the MAC PDU transmission schedule, the device that obtains the NPI can know the MAC PDU transmission schedule (e.g., whether the transmitted MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data sending side and the receiving side, and enabling appropriate communication processing (e.g., transformation processing to MAC PDU during reception).

[0213] <Option B of Proposal a in TX>

[0214] In Option B, which describes the method for obtaining the transmission schedule, the NPI set to a specific value is indicated for each schedule of the channel / signal. Alternatively, in Option B, the NPI set to a specific value is indicated only for a specific schedule (the schedule of a specific channel / signal).

[0215] In option B of proposal a, when the NPI is a specific value (e.g., 1), the specific NPI value indicates that the transmission of a new MAC PDU is scheduled. When the NPI is a specific value (e.g., 1), the transmission of a new MAC PDU is scheduled regardless of whether the transmission of a MAC PDU prior to the specific NPI (e.g., 1) has been completed. Additionally, if the transmission of a MAC PDU prior to the specific NPI (e.g., 1) has not been completed, a portion of the MAC PDU prior to the specific NPI (e.g., 1) can also be flushed.

[0216] Furthermore, in option B of proposal a, if the NPI is not a specific value (e.g., not 1), an NPI of a non-specific value indicates scheduling the transmission of the same MAC PDU as the MAC PDU sent before the NPI of a non-specific value. Alternatively, in option B of proposal a, if no NPI is provided, it indicates scheduling the transmission of the same MAC PDU as the MAC PDU sent before the NPI of a non-specific value.

[0217] In option B of proposal a, the NPI can be included in the scheduling information for the transmission. For example, the A-IoT UE receives the scheduling information, refers to the NPI included in the scheduling information, determines whether to treat each block of data being transmitted as a block of a new MAC PDU, and based on the determination result, sends a signal containing the block of the MAC PDU.

[0218] In option B of proposal a, the NPI can be included in the transmitted channel / signal. For example, the A-IoT UE transmits a signal containing at least a portion of the MAC PDU and the NPI. Then, the BS or intermediate UE, acting as the receiving wireless communication device, refers to the NPI of the signal received from the A-IoT UE, determines whether the block of data contained in the signal is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0219] Figure 14 This is a diagram representing option B of the method for obtaining the transmission schedule. Figure 14 The horizontal axis represents the time axis. Figure 14 The example shown is of sending two MAC PDUs, MAC PDU#A and MAC PDU#B.

[0220] exist Figure 14 In the example, MAC PDU#B corresponds to a new MAC PDU. That is, TX-1 of MAC PDU#B is the block of the new MAC PDU relative to the blocks of MAC PDUs sent up to TX-N before it. In this case, NPI of TX-1 of MAC PDU#B represents a specific value. Figure 14 In this case, the NPI for TX-1 to TX-N of MAC PDU#A is 0, and the NPI for TX-1 of MAC PDU#B is 1. Furthermore, the NPI for TX-2 and beyond of MAC PDU#B is 0.

[0221] In addition, Figure 14 The example shown is an instance where 1 is a specific value of NPI, but the specific value can also be anything other than 1.

[0222] As in option B above, by setting the NPI to notify the MAC PDU transmission schedule, the device that obtains the NPI can know the MAC PDU transmission schedule (e.g., whether the transmitted MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data sending and receiving sides and enabling appropriate communication processing (e.g., transformation processing to MAC PDU during reception).

[0223] <Option C of Proposal a in TX>

[0224] Option C, which describes the method for obtaining the transmission schedule, is a method that does not use a specific indication (e.g., the NPI mentioned above). Option C describes a method for obtaining the schedule based on the transmission time, a method for obtaining the schedule based on the transmission time gap, and a method that sets the number of transmissions for a MAC PDU to a fixed number.

[0225] <Option C of Proposal a in TX: Time-based approach>

[0226] In time-based methods, the transmission of a MAC PDU#X is determined based on whether a specific time has elapsed since its transmission time. The decision is made whether the transmission of MAC PDU#X should continue or be transmitted as a new MAC PDU (e.g., a MACPDU different from MAC PDU#X). For example, time-based methods use a timer to track the transmission time. The timer performs the following operation: For example, an A-IoT UE causes the timer to operate as follows to determine whether the scheduling is for a new MAC PDU.

[0227] (i) If a schedule (e.g., DCI) is received while the timer is in an inactive (running) state, the schedule is for sending a new MAC PDU, and in this case, the timer starts.

[0228] (ii) If a schedule (e.g., DCI) is received while the timer is in operation, the schedule is for transmitting the same MAC PDU as in (i) above. In this case, the timer can continue to operate.

[0229] (iii) For example, when the transmission of the MAC PDU is completed (or when a schedule for the completion of the transmission of the MAC PDU is received), the timer stops and is initialized.

[0230] (iv) If a MAC PDU is not being transmitted and a specific time has elapsed since the timer started, the timer stops and is initialized. In this case, part or all of the MAC PDU is refreshed.

[0231] Figure 15 This is a diagram representing an example of a time-based approach for option C of proposal a. Figure 15 The horizontal axis represents the time axis. Figure 15 The example shown illustrates the transmission of two MAC PDUs, MAC PDU#A and MAC PDU#B. Figure 15 In the example, MAC PDU#B corresponds to the new MAC PDU.

[0232] exist Figure 15In the example, the timer starts when the scheduled reception of TX-1 of MAC PDU#A is completed. Then, the timer stops and is initialized when the transmission of TX-N of MAC PDU#A is completed (or when the reception of its corresponding scheduled transmission is completed). Afterwards, TX-1 corresponding to the scheduled transmission is the schedule for the transmission of MAC PDU#B corresponding to the new MAC PDU, so the timer starts when the scheduled reception of TX-1 of MAC PDU#B is completed.

[0233] The timer can be started or stopped during the scheduled receive time, and it can also be started or stopped during the scheduled send time.

[0234] Additionally, the BS or intermediate UE, acting as the receiving wireless communication device, can also activate the timer. For example, if the BS or intermediate UE receives a signal containing a data block from the A-IoT UE when the timer is not activated, it determines that the block is a new MAC PDU and starts the timer. Then, when the timer is activated and it receives a signal containing a data block from the A-IoT UE, it determines that the block is a MAC PDU identical to a previously received MAC PDU. Finally, when the MAC PDU reception is complete, the timer is stopped and initialized.

[0235] <Option C of Proposal a in TX: Time-gap-based approach>

[0236] In option C of proposal a in TX, it is determined whether two transmissions are transmissions of the same MAC PDU or one of the transmissions is a transmission of a new MAC PDU, based on the time interval between the scheduling of two transmissions or whether the time interval between the two transmissions is greater than a specific time.

[0237] For example, if a specific time period has elapsed after a certain transmission, the transmission schedule received after the specific time period is used for the transmission of a new MAC PDU.

[0238] If a specific time interval has not elapsed since a certain transmission, the scheduling for receiving in the state where the specific time interval has not elapsed is the same scheduling for transmitting the same MAC PDU as that transmission.

[0239] For example, an A-IoT UE determines that the schedule received after a specific time interval from the reception timing of the schedule corresponding to the last transmission of a certain MAC PDU#X is a schedule for a new MAC PDU#Y.

[0240] Alternatively, it can replace the receive timing of the schedule and be determined based on the transmission timing corresponding to the schedule. For example, an A-IoT UE determines that a transmission after a specific time interval from the last transmission timing of a certain MAC PDU#X is a transmission of a new MAC PDU#Y.

[0241] Furthermore, the BS or intermediate UE, which is the receiving side of the wireless communication device receiving the MAC PDU, can also make a determination based on the time interval. For example, the BS or intermediate UE can also determine that: from the reception timing of a certain MAC PDU#X, the reception after a specific time interval is the reception of a new MAC PDU#Y.

[0242] <Option C of Proposal a in TX: Fixed number of transmissions>

[0243] A MAC PDU can also be associated with a fixed number of transmissions. For example, a MAC PDU is always transmitted via X transmissions. X can be an integer greater than 1. Associating a MAC PDU with a fixed number of transmissions allows for the determination of whether a new MAC PDU is scheduled based on the number of transmissions.

[0244] For example, the A-IoT UE sending the MAC PDU performs transmission control, causing it to send a MAC PDU a fixed number of times. Similarly, the BS or intermediate UE receiving the MAC PDU performs reception control, causing it to receive a MAC PDU a fixed number of times. For instance, the BS or intermediate UE can also count the number of times a block is received, and when the number of receptions reaches a fixed number, determine that the next block to be received is a new MAC PDU block.

[0245] Figure 16 This is a diagram illustrating an example of how a MAC PDU is associated with a fixed number of transmissions. Figure 16 The example shown illustrates the transmission of two MAC PDUs, MAC PDU#A and MAC PDU#B. Here, MAC PDU#B corresponds to an example of a new MAC PDU.

[0246] exist Figure 16 In the example, a MAC PDU is sent a fixed number of times, 4 times. Figure 16 In the example, after block MAC PDU#A is sent 4 times, block MAC PDU#B is sent 4 times.

[0247] The number of transmissions (i.e., the value of X) can be determined by the specification or set by the NW. Alternatively, the number of transmissions can be reported by the UE's capability. Or, the number of transmissions can also be determined based on the UE's capability. For example, the NW could report a candidate number of transmissions that the UE can support based on the UE's capability, and the NW that receives the report could select at least one from the candidates.

[0248] As in option C above, by notifying the transmission schedule of a new MAC PDU without using an indicator, the wireless communication device can know the transmission schedule of the MAC PDU (e.g., whether the transmitted MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data transmitting and receiving sides and enabling appropriate communication processing (e.g., transformation processing into MAC PDUs during reception). Furthermore, since no indicator is required, signaling overhead can be reduced.

[0249] <Option D of Proposal a in TX>

[0250] In option D of proposal a in TX, the index can also be indicated per scheduling of channel / signal. Here, the index used for indication is referred to as PI (Packet Index). However, the index used for indication here can also be associated with other names.

[0251] For example, when a new MAC PDU transmission is scheduled, PI is incremented by 1. The range of PI's value is defined, and PI increments within this defined range. The defined range can be, for example, above 1 and below k (where k is an integer above 1).

[0252] In option D of proposal a, the PI can be included in the scheduling information for the transmission. For example, the A-IoT UE receives the scheduling information, refers to the PI included in the scheduling information, determines whether to include each block of data being transmitted as a block of a new MAC PDU, and based on the determination result, sends a signal containing the block of the MAC PDU.

[0253] In option D of proposal a, the PI can be included in the transmitted channel / signal. For example, the A-IoT UE transmits a signal containing at least a portion of the MAC PDU and the PI. Then, the BS or intermediate UE, acting as the receiving wireless communication device, refers to the PI of the signal received from the A-IoT UE, determines whether the block of data contained in the signal is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0254] Figure 17 This is a diagram illustrating an example indicated by PI. Figure 17 The example shown is of sending three MAC PDUs: MAC PDU#A, MAC PDU#B, and MAC PDU#C.

[0255] exist Figure 17 In the example, PI=0 is indicated in the send schedule of MAC PDU#A, PI=1 is indicated in the send schedule of MAC PDU#B, and PI=1 is indicated in the send schedule of MAC PDU#C.

[0256] PI can be either an exact index (or an actual index) or an index that performs modulo looping. For example, in the case of modulo looping, the index is indicated by a cycle of values ​​such as 1, 2, 3, 4, 1, 2, 3, 4. Or, for example, in the case of modulo looping, the index is indicated by a cycle of values ​​such as 0, 1, 2, 3, 0, 1, 2, 3.

[0257] If the PI (Primary Indicator) differs from a previous transmission, the transmission corresponding to that PI is a scheduled transmission of a new MAC PDU. Additionally, if the transmission of a MAC PDU corresponding to a previous transmission is incomplete, the MAC PDU corresponding to that previous transmission can be refreshed.

[0258] If the PI is the same as the previous transmission, the transmission corresponding to that PI is the transmission of the same MACPDU as the previous transmission.

[0259] As in option D above, by setting the PI to notify the transmission schedule of the MAC PDU, the device that obtains the PI can know the transmission schedule of the MAC PDU (e.g., whether the transmitted MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data sending side and the receiving side, and enabling appropriate communication processing (e.g., transformation processing to MAC PDU during reception).

[0260] <Proposal b in TX: A method to determine the size of a MAC PDU>

[0261] Proposal b describes a method for determining the size of a MAC PDU (e.g., a scheduled MAC PDU). This method for determining the size of a MAC PDU corresponds to the method for determining L_total, which represents the overall size of the MAC PDU.

[0262] <Option A of Proposal b in TX: Explicit Instruction>

[0263] When an explicit indication of size is made, the method of indication is not limited. For example, any at least one of the control signals, synchronization signals, and arbitrary signals received before the transmission of the MAC PDU can also indicate the exact size (or actual size) of the MAC PDU. Alternatively, higher-level parameters (e.g., preset parameters or RRC-set parameters) can determine multiple candidates for size, and any at least one of the control signals, synchronization signals, and arbitrary signals received before the transmission of the MAC PDU can indicate one of the multiple candidates.

[0264] <Option B of Proposal b in TX: Size is predetermined>

[0265] The single size of a MAC PDU can be predetermined or defined by a specification. In the latter case, a single size is always used.

[0266] <Option C of Proposal b in TX: Implicit Decision>

[0267] At the start of the scheduling for the transmission of a MAC PDU, all resources of one or more channels / signals for transmission are provided. The size of the MAC PDU is then determined based on the total amount of resources provided. For example, the size of the MAC PDU can be determined based on at least one of the following: the number of time slots provided as resources, the number of transmissions, the number of available resource elements, etc.

[0268] As in Proposal b above, by notifying the size of the MAC PDU, inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing into the MAC PDU during reception) can be performed. For example, as in Proposal b above, by notifying the size of the MAC PDU, the device sending the MAC PDU can appropriately perform MAC PDU segmentation, and the device receiving the MAC PDU can appropriately generate the MAC PDU based on more than one segment.

[0269] <Proposal c in TX: Transformation method of MAC PDU>

[0270] Proposal c describes segmentation (dividing the MAC PDU into blocks, e.g., segments) and concatenation (joining blocks to generate the MAC PDU) as methods for transforming the MAC PDU. For example, proposal c describes where and how segmentation / concatenation is performed, and how to determine which segment is scheduled. For example, proposal c describes how to indicate the size of each block obtained through segmentation of the MAC PDU. Figure 12 The L_1~L_N diagrams are explained. Furthermore, proposal c explains how to indicate the indexes of each block obtained through segmentation of the MAC PDU (...). Figure 12 The diagram shows TX-1 to TX-N. Furthermore, proposal c explains where and how the segments / cascades are performed.

[0271] <Option A of Proposal C in TX: Explicit Instruction for Each Send>

[0272] When explicit indication is given, the method of indication is not limited. For example, at least one of the control signals, synchronization signals, and arbitrary signals received before each transmission can indicate the exact size of the transmission segment and / or the index of the transmission. In the indication of the index, either an exact index or an index with modulo operation can be indicated. For example, in the case of modulo operation, the index is indicated by a cyclic value such as 1, 2, 3, 4, 1, 2, 3, 4. Or, for example, in the case of modulo operation, the index is indicated by a cyclic value such as 0, 1, 2, 3, 0, 1, 2, 3.

[0273] Additionally, if the BS or intermediate UE detects a reception failure of a channel / signal containing a block of MAC PDUs sent by the A-IoT UE, the BS or intermediate UE can refresh the received blocks of that MAC PDU, skip the remaining reception of that MAC PDU, and report the reception failure to the A-IoT UE. Refreshing the received blocks, skipping the remaining reception, and reporting the reception failure can all be performed, or at least one of them can be performed.

[0274] Furthermore, the detection of reception failure can be based on the indicated index. For example, in the case where blocks with modulo operations at indices 1, 2, 3, 4, ... are received sequentially, if 4 is detected after index 2 but 3 is not detected, the reception of the block corresponding to index 3 is detected as a failure.

[0275] Regarding the size of each segment, it can also be that higher-level parameters (e.g., preset parameters or RRC-set parameters) determine multiple candidates for the size, and at least one of the control signals, synchronization signals, and arbitrary signals received before the transmission of the MAC PDU indicates one of the multiple candidates.

[0276] <Option B of Proposal C in TX: Pre-determined>

[0277] Regarding size, the single size of a segment can be predetermined or defined by a specification. In this case, a single size is always used.

[0278] <Option C of Proposal C in TX: Implicit Decision>

[0279] Regarding segment size, at the start of the scheduling for the transmission of a MAC PDU, all resources of one or more channels / signals for transmission are provided. Then, the size of each transmission is determined based on the total amount of resources provided. For example, the segment size can be determined based on at least one of the following: the number of time slots provided as resources, the number of transmissions, the number of available resource elements, etc. In this case, the sizes of the segments of the MAC PDU can be the same. That is, it can be L_1 = L_2 = ... = L_N (= the value obtained by dividing L_total by N).

[0280] Alternatively, regarding segment size, at the start of the scheduling for the transmission of a MAC PDU, all resources of one or more channels / signals for transmission are provided. The size of each transmission is then determined based on the amount of resources provided for each transmission. For example, the segment size can be determined based on at least one of the following: the number of time slots provided as resources, the number of transmissions, the number of resource elements available. In this case, the segments of the MAC PDU can be the same or different from each other.

[0281] Furthermore, for example, regarding the segment size, the size of a MAC PDU transmission can be determined based on any of the methods in "<Proposal b in TX>" mentioned above. Then, the size of the MAC PDU determined by proposal b is equally divided into more than one segment, thereby determining the size of each segment. For example, regardless of the differences in transmission resources, the size of the MAC PDU is equally divided into more than one segment.

[0282] Regarding segment indexes, it's also possible to not indicate the index for each transmission. In this case, transmissions are performed at the index following the latest transmission. For example, if the latest transmission's index is 3, the next transmission's index is 4. In other words, transmissions are performed in index order. Alternatively, the indices can be associated with the order in which transmissions are performed.

[0283] Regarding segment indexes, each transmission resource is associated with an index. In this case, the data for the index is transmitted via that resource. That is, the data for a segment with index #k is transmitted via the transmission resource associated with index #k.

[0284] <Option D of Proposal C in TX: An example of segmentation / cascading performed via PHY>

[0285] Segmentation and / or cascading can be performed at the physical layer. For example, segmentation and / or cascading can be performed based on at least one of the following: instructions from the NW, settings from the NW, definitions in the specification, and instructions from higher layers.

[0286] The received data is linked through the physical layer. Then, the linked data is shared with the MAC layer in MAC PDU format (e.g., it is notified to or passed to the MAC layer).

[0287] For example, the data to be transmitted (e.g., MAC PDU or TB) is shared from the MAC layer to the physical layer. At the physical layer, the MAC PDU is segmented. Then, the segments obtained through segmentation are transmitted.

[0288] <Option E of Proposal c in TX: An example of segmentation / cascading executed via MAC>

[0289] Segmentation and / or cascading can be performed through the MAC layer. For example, segmentation and / or cascading can be performed based on at least one of the following: instructions from the NW, settings from the NW, definitions in the specification, and instructions from higher levels.

[0290] The received data is shared with the MAC layer. Then, multiple receivers are linked together for the MAC PDU format. Additionally, the received data shared with the MAC layer may or may not be indexed.

[0291] For example, a MAC PDU is segmented at the MAC layer. Then, each segment is shared with the physical layer for its own transmission resources.

[0292] As in Proposal c above, by knowing the information about the transformation method for the MAC PDU (size, index), inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing to the MAC PDU during reception) can be performed. For example, as in Proposal c above, by knowing the information about the transformation method for the MAC PDU, the device sending the MAC PDU can appropriately perform MAC PDU segmentation, and the device receiving the MAC PDU can appropriately generate the MAC PDU based on more than one segment.

[0293] <Proposal d in TX: Methods for signal processing of MAC PDUs (channel coding, CRC attachment methods)>

[0294] <Option A of Proposal d in TX: Execution per MAC PDU>

[0295] During transmission, channel coding / CRC appending is performed on a per MAC PDU basis. In this case, during reception, after all segments for a MAC PDU have been received, decoding of the channel coding is performed, and error detection is performed based on the appended CRC.

[0296] <Option B of Proposal d in TX: Execution for each send>

[0297] During transmission, channel coding / CRC appending is performed on a per-transmission basis. In other words, during transmission, channel coding / CRC appending is performed on a per-segment basis. In this case, during reception, the receiving wireless communication device performs channel coding decoding on a per-segment basis after receiving each segment, and performs error detection on a per-segment basis based on the CRC appended on each segment.

[0298] Alternatively, CRC appending can be performed on a segment-by-segment basis and on a per-MAC PDU basis. With CRC appending performed on a segment-by-segment basis and on a per-MAC PDU basis, error detection can be performed on a segment-by-segment basis during reception, and a CRC check can be performed on the MAC PDU after a segment for a MAC PDU has been received.

[0299] Furthermore, channel coding can also be performed segment by segment and per MAC PDU. In the case where channel coding is performed segment by segment and per MAC PDU, decoding can also be performed segment by segment during reception, and decoding of the MAC PDU can be performed after a segment for a MAC PDU has been received.

[0300] Figure 18 This is a diagram illustrating examples of CRC appending performed on each segment and on each MAC PDU. Figure 18 The diagram shows the addition of a CRC to each block (TX-1~TX-N) of the transmitted MAC PDU, and the addition of a CRC to the MAC PDU.

[0301] <Option C of Proposal d in TX: Do not execute>

[0302] In option C of proposal d, channel coding and CRC appending are not performed. In this case, transmission can also be performed based on sequence. Alternatively, CRC appending can be performed without channel coding. Or, channel coding can be performed without CRC appending.

[0303] As in Proposal d above, by knowing the specifications of the MAC PDU signal processing method, inconsistencies between the data transmitting and receiving sides can be avoided, and appropriate communication processing (e.g., conversion processing to MAC PDU during reception) can be performed. For example, as in Proposal c above, by knowing the specifications of the MAC PDU signal processing method, the device transmitting the MAC PDU can appropriately perform MAC PDU segmentation, and the device receiving the MAC PDU can appropriately generate the MAC PDU based on more than one segment.

[0304] <Proposal e in TX: Size of MAC PDU (e.g., should it be aligned to bytes?)>

[0305] <Option A of Proposal e in TX: Transmission of each channel / signal is byte-aligned>

[0306] For example, imagine that the result of dividing the size of the MAC PDU by the number of segments is aligned in bytes. That is, imagine that the number of bits in the result of dividing the size of the MAC PDU by the number of segments is an integer multiple of 8 bits. In other words, imagine that the number of bits in each segment is an integer multiple of 8 bits.

[0307] The size of each transmission can also be calculated using the TBS determination mechanism. The TBS determination mechanism includes 8 8N-bit quantization using N bits (N being an integer greater than 1), and / or methods for selecting TBS from candidates aligned to bytes, etc.

[0308] <Option B of Proposal e in TX: Transmission of each channel / signal can be byte-aligned or not>

[0309] For example, if a MAC PDU uses multiple segments of equal size, it is assumed that dividing the size of the MAC PDU by the number of segments will result in a positive integer. This positive integer value corresponds to the segment size (e.g., the number of bits). In this case, it is assumed that the number of bits obtained by dividing the size of the MAC PDU by the number of segments is not limited to being an integer multiple of 8 bits.

[0310] The size of each transmission is calculated using the TBS (Tracking Baseline Scale) mechanism. However, the TBS mechanism does not include a 8x ... 8N-bit quantization, where N bits (N is an integer greater than or equal to 1) are used for quantization.

[0311] <Proposal f in TX: Regarding the size of the MAC PDU>

[0312] Regarding data size, any of the following can be applied.

[0313] • Data sizes can be the same in A-IoT UE transmissions. In other words, the sizes of the transmitted segments can be the same.

[0314] • Data sizes can be the same or different in A-IoT UE transmissions. In other words, the sizes of the transmitted segments can be the same or different.

[0315] The data size corresponds to the segment size. The segment size can be the same as the proposal shown in <Proposal c in TX> above.

[0316] As explained above, by specifying any of the proposals for the MAC PDU for TX, inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing to the MAC PDU during reception) can be performed.

[0317] <Regarding RX (Reception of A-IoT UE)>

[0318] Figure 19 This is a diagram illustrating an example of the structure of a MAC PDU in RX. Figure 19 The image shows a MAC PDU divided into N (N is an integer greater than or equal to 1) receive blocks. The following is an example... Figure 19 As shown, sometimes the size of a MAC PDU (e.g., length, number of bits) is recorded as L_total, and the N blocks are recorded as RX-1 to RX-N, with the size of each of the N blocks recorded as L_1 to L_N. Alternatively, N and / or L_total can vary for each MAC PDU. L_1 to L_N can also be the same for each other. RX-1 to RX-N can correspond to the indices that identify the blocks of the MAC PDU.

[0319] in addition, Figure 19 The N blocks in the code can be recorded as segments or replaced with other names. In the following description, a block of a MAC PDU is a block that includes at least a portion of the data of that MAC PDU.

[0320] The wireless communication device (e.g., BS or intermediate UE) transmitting signals to the A-IoT UE divides (segments) the MAC PDU into N segments, RX-1 to RX-N, and transmits signals containing RX-1 to RX-N to the A-IoT UE. The A-IoT UE receives the signals containing RX-1 to RX-N respectively and connects them in the order of RX-1 to RX-N to generate (or reconstruct) the MAC PDU.

[0321] The following are proposals a through f, which are related to MAC PDUs in the RX.

[0322] <Proposal a in RX: A method for obtaining the transmission schedule of MAC PDUs>

[0323] Proposal a illustrates, as an example of a method for obtaining the reception schedule of a MAC PDU, how a wireless communication device (e.g., at least one of an A-IoT UE, an intermediate UE, and an intermediate BS) obtains the reception schedule of a new MAC PDU. In other words, it describes a method for determining whether a block of MAC PDUs contained in a certain channel / signal is a block of a new MAC PDU when receiving a MAC PDU through one or more channels / signals. Here, the case where a block of MAC PDUs contained in a certain channel / signal is not a block of a new MAC PDU is equivalent to the case where the block contained in that channel / signal is a block of the same MAC PDU as a channel / signal received before that channel / signal.

[0324] The MAC PDU receive schedule can also include scheduling information for receiving MAC PDUs.

[0325] <Option A of Proposal a in RX>

[0326] In option A, which describes the method for obtaining the receive schedule, an indicator for the receive schedule is set. Then, the indicator is indicated for each schedule of the channel / signal via a toggling mechanism. The indicator set here is referred to as NPI (New Packet Indicator). However, this indicator can also be associated with other names.

[0327] In option A of proposal a, when the NPI is flipped (e.g., when the NPI is switched), the flipped NPI indicates that the reception of the new MAC PDU is scheduled. When the NPI is flipped, the reception of the new MAC PDU can be scheduled regardless of whether the reception of the MAC PDU prior to the NPI flip has been completed. Additionally, if the reception of the MAC PDU prior to the NPI flip has not been completed, a portion of the MAC PDU prior to the NPI flip can also be flushed. "Flush" can also be replaced with other expressions such as "discard" or "delete".

[0328] Furthermore, in option A of proposal a, in the case where the NPI is not flipped (e.g., in the case where the NPI is not switched), the unflipped NPI indicates that the same MAC PDU was scheduled as the MAC PDU received before the unflipped NPI.

[0329] In option A of proposal a, the NPI can be included in the scheduling information (e.g., DCI, etc.) used for receiving the data. For example, when an A-IoT UE receives the scheduling information, it refers to the NPI included in the scheduling information to determine whether each block of data received by the A-IoT UE is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0330] In option A of proposal a, the NPI can be included in the received channel / signal. For example, the BS, acting as the transmitting wireless communication device, or the intermediate UE, transmits a signal containing at least a portion of the MAC PDU and the NPI. Then, the A-IoT UE refers to the NPI of the signal received from the transmitting wireless communication device, determines whether the block of data contained in the signal is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0331] Figure 20 This is a diagram representing option A of the method for obtaining the receiving schedule. Figure 20 The horizontal axis represents the time axis. Figure 20 The example shown is receiving two MAC PDUs, MAC PDU#A and MAC PDU#B. Figure 20 RX-i (where i is an integer greater than 1 and less than N) can represent either a block of a MAC PDU or a channel / signal containing a block of a MAC PDU.

[0332] exist Figure 20 In the example, MAC PDU#B corresponds to the new MAC PDU. That is, RX-1 of MAC PDU#B is relative to the MAC PDUs received before it up to RX-N (in... Figure 20 In the example, the block of MAC PDU#A is a new MAC PDU block. In this case, the NPI of RX-N of MAC PDU#A is 0, and the NPI of RX-1 of MAC PDU#B is 1. That is, the NPI of RX-1 of MAC PDU#B is flipped.

[0333] In addition, Figure 20 In the example, data is received up to RX-N of MAC PDU#A. That is, in Figure 20 In the example, the reception of MAC PDU#A has been completed. (And...) Figure 20 Unlike other cases, if RX-1 to RX-k of MAC PDU#A (where k is an integer greater than 1 and less than N) are received, the reception of MAC PDU#A is incomplete. In this case, a portion of MAC PDU#A (e.g., the block from RX-1 to RX-k) can be flushed.

[0334] In addition, Figure 20 The example shown illustrates a flip from 0 to 1, but it is also possible to flip from 1 to 0. Furthermore, NPI is not limited to examples that flip between 0 and 1.

[0335] As in option A above, by setting the NPI to notify the MAC PDU reception schedule, the device that obtains the NPI can know the MAC PDU reception schedule (e.g., whether the received MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data sending and receiving sides and enabling appropriate communication processing (e.g., transformation processing to MAC PDU during reception).

[0336] <Option B of Proposal a in RX>

[0337] In option B of the method for obtaining the receive schedule, the NPI set to a specific value is indicated for each schedule of the channel / signal. Alternatively, in option B of the method for obtaining the receive schedule, the NPI set to a specific value is indicated only for a specific schedule (the schedule of a specific channel / signal).

[0338] In option B of proposal a, when the NPI is a specific value (e.g., 1), the specific NPI value indicates that the reception of a new MAC PDU is scheduled. When the NPI is a specific value (e.g., 1), the reception of the new MAC PDU is scheduled regardless of whether the reception of the MAC PDU preceding the specific NPI (e.g., 1) has been completed. Additionally, if the reception of the MAC PDU preceding the specific NPI (e.g., 1) has not been completed, a portion of the MAC PDU preceding the specific NPI (e.g., 1) can also be flushed.

[0339] Furthermore, in option B of proposal a, if the NPI is not a specific value (e.g., not 1), an NPI of a non-specific value indicates that the reception of the same MAC PDU as the MAC PDU received before the NPI of a non-specific value is scheduled. Alternatively, in option B of proposal a, if no NPI is provided, it indicates that the reception of the same MAC PDU as the MAC PDU sent before the state where no NPI is provided is scheduled.

[0340] In option B of proposal a, the NPI can be included in the scheduling information for receiving data. For example, when an A-IoT UE receives scheduling information, it refers to the NPI included in the scheduling information, determines whether each block of data being received is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0341] In option B of proposal a, the NPI can be included in the received channel / signal. For example, the BS, acting as the transmitting wireless communication device, or the intermediate UE, transmits a signal containing at least a portion of the MAC PDU and the NPI. Then, the A-IoT UE refers to the NPI of the signal received from the transmitting wireless communication device, determines whether the block of data contained in the signal is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0342] Figure 21 This is a diagram representing option B, which shows the method for obtaining the receiving schedule. Figure 21 The horizontal axis represents the time axis. Figure 21 The example shown is receiving two MAC PDUs, MAC PDU#A and MAC PDU#B.

[0343] exist Figure 21In the example, MAC PDU#B corresponds to a new MAC PDU. That is, RX-1 of MAC PDU#B is the block of the new MAC PDU relative to the block of MAC PDUs received up to RX-N before it. In this case, NPI of RX-1 of MAC PDU#B represents a specific value. Figure 21 In this case, the NPI of RX-1 to RX-N of MAC PDU#A is 0, and the NPI of RX-1 of MAC PDU#B is 1. In addition, the NPI of RX-2 and beyond of MAC PDU#B is 0.

[0344] In addition, Figure 21 The example shown is an instance where 1 is a specific value of NPI, but the specific value can also be anything other than 1.

[0345] As in option B above, by setting the NPI to notify the MAC PDU reception schedule, the device that acquires the NPI can know the MAC PDU reception schedule (e.g., whether the received MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data sending and receiving sides and enabling appropriate communication processing (e.g., transformation processing to MAC PDU during reception).

[0346] <Option C of Proposal a in RX>

[0347] Option C, which describes the method for obtaining the receive schedule, is a method that does not use a specific indication (e.g., the NPI mentioned above). Option C describes a method for obtaining the schedule based on the time of reception, a method for obtaining the schedule based on the time interval of reception, and a method that sets the number of receptions for sending a MAC PDU to a fixed number.

[0348] <Option C of Proposal a in RX: Time-based approach>

[0349] In time-based methods, the reception of a MAC PDU#X is determined based on whether a specific time has elapsed since the reception time of that MAC PDU#X was received, to decide whether the reception of MAC PDU#X should be continued or treated as a new MAC PDU (e.g., a MAC PDU different from MAC PDU#X). For example, time-based methods use a timer to track the reception time. The timer performs the following operation: For example, an A-IoT UE causes the timer to operate as follows to determine whether the scheduling is for a new MAC PDU.

[0350] (i) If a schedule (e.g., DCI) is received while the timer is inactive, the schedule is for receiving a new MACPDU, and in this case, the timer is started.

[0351] (ii) If a schedule (e.g., DCI) is received while the timer is in the running state, the schedule is for receiving the same MAC PDU as in (i) above. In this case, the timer may continue to operate.

[0352] (iii) For example, when the reception of the MAC PDU is completed (or when a schedule for the reception of the MAC PDU is received is received), the timer stops and is initialized.

[0353] (iv) If the reception of a MAC PDU is incomplete, and a specific time has elapsed since the timer started, the timer stops and is initialized. In this case, part or all of the MAC PDU is refreshed.

[0354] Figure 22 This is a diagram representing an example of a time-based approach for option C of proposal a. Figure 22 The horizontal axis represents the time axis. Figure 22 The example shown illustrates the transmission of two MAC PDUs, MAC PDU#A and MAC PDU#B. Figure 22 In the example, MAC PDU#B corresponds to the new MAC PDU.

[0355] exist Figure 22 In the example, the timer starts when scheduled reception occurs on RX-1 of MAC PDU#A. Then, when reception of RX-N of MAC PDU#A is complete (or, when reception of its corresponding scheduled reception is complete), the timer stops and is initialized. Afterwards, RX-1 corresponding to the scheduled reception is the scheduler for reception of MAC PDU#B corresponding to the new MAC PDU, therefore, the timer starts when scheduled reception occurs on RX-1 of MAC PDU#B.

[0356] The timer can be started or stopped during the scheduled receive time, or it can be started or stopped during the receive time corresponding to the schedule.

[0357] Additionally, the BS or intermediate UE, acting as the transmitting wireless communication device, can also activate the timer. For example, if the BS or intermediate UE, in a state where the timer is not activated, sends a signal to the A-IoT UE to transmit a block containing data, and determines that the block is a new MAC PDU, then starts the timer. Then, if, in a state where the timer is activated, the BS or intermediate UE sends a signal to the A-IoT UE to transmit a block containing data, it determines that the block is a block of the same MAC PDU as a previously received MAC PDU. Finally, upon completion of the MAC PDU transmission, the timer is stopped and initialized.

[0358] <Option C of Proposal a in RX: Time-gap-based approach>

[0359] In option C of proposal a in RX, it is determined whether two receptions are for the same MAC PDU or one of them is for a new MAC PDU, based on the time interval between the scheduling of two receptions or whether the time interval between the two receptions is greater than a specific time.

[0360] For example, if a specific time interval has elapsed after a certain reception, the scheduling of receptions after the specific time interval is used for the reception of new MAC PDUs.

[0361] If a certain time interval has not elapsed after a certain reception, the scheduling for receiving in the state of not having elapsed the specific time interval is the scheduling for receiving the same MAC PDU as that reception.

[0362] For example, an A-IoT UE determines that: after a specific time interval has elapsed since the last reception of a MAC PDU#X, the reception schedule is for a new MAC PDU#Y.

[0363] Alternatively, it can replace the reception timing of the scheduled reception and make the determination based on the reception timing corresponding to the scheduled reception. For example, an A-IoT UE determines that: a reception after a specific time interval from the last reception timing of a certain MAC PDU#X is a reception of a new MAC PDU#Y.

[0364] Furthermore, the BS or intermediate UE, which is the transmitting side of the MAC PDU, can also make a determination based on the time interval. For example, the BS or intermediate UE can also determine that a transmission after a specific time interval from the transmission timing of a certain MAC PDU#X is the transmission of a new MAC PDU#Y.

[0365] <Option C of Proposal a in RX: Fixed Receive Count Method>

[0366] A MAC PDU can also be associated with a fixed number of receptions. For example, a MAC PDU is always received through X receptions. Furthermore, X can be an integer greater than 1. Associating a MAC PDU with a fixed number of receptions allows for the determination of whether a new MAC PDU is scheduled based on the number of receptions.

[0367] For example, the A-IoT UE receiving the MAC PDU performs transmission control, causing it to receive a MAC PDU a fixed number of times. Furthermore, the BS or intermediate UE transmitting the MAC PDU performs transmission control, causing it to transmit a MAC PDU a fixed number of times. For example, the BS or intermediate UE can also count the number of times a block is transmitted, and when the transmission count reaches a fixed number, determine that the next block to be transmitted is a new MAC PDU block.

[0368] Figure 23 This is a diagram illustrating an example of how a MAC PDU is associated with a fixed number of receptions. Figure 23 The example shown illustrates receiving two MAC PDUs, MAC PDU#A and MAC PDU#B. Here, MAC PDU#B corresponds to an example of a new MAC PDU.

[0369] exist Figure 23 In this example, a MAC PDU is received a fixed number of times (4 times). Figure 23 In the example, after block MAC PDU#A was received 4 times, block MAC PDU#B was received 4 times.

[0370] The number of receptions (i.e., the value of X) can be determined by the specification or set by the NW. Alternatively, the number of receptions can be reported by the UE's capability. Or, the number of receptions can also be determined based on the UE's capability. For example, the NW that receives the report can choose at least one candidate number of receptions that the UE can support.

[0371] As in option C above, by notifying the transmission schedule of a new MAC PDU without using an indicator, the wireless communication device can know the transmission schedule of the MAC PDU (e.g., whether the transmitted MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data transmitting and receiving sides and enabling appropriate communication processing (e.g., transformation processing into MAC PDUs during reception). Furthermore, since no indicator is required, signaling overhead can be reduced.

[0372] <Option D of Proposal a in RX>

[0373] In option D of proposal a in RX, the index can also be indicated per scheduling of channel / signal. Here, the index used for indication is referred to as PI (Packet Index). However, the index used for indication here can also be associated with other names.

[0374] For example, when a new MAC PDU is scheduled for reception, PI is incremented by 1. The range of PI's value is defined, and PI increments within this defined range. The defined range can be, for example, above 1 and below k (where k is an integer above 1).

[0375] In option D of proposal a, the PI can be included in the scheduling information (e.g., DCI, etc.) used for receiving the data. For example, when an A-IoT UE receives the scheduling information, it refers to the PI included in the scheduling information to determine whether each block of data received by the A-IoT UE is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0376] In option D of proposal a, the PI can be included in the received channel / signal. For example, the BS, acting as the transmitting wireless communication device, or the intermediate UE, transmits a signal containing at least a portion of the MAC PDU and the PI. Then, the A-IoT UE refers to the PI of the signal received from the transmitting wireless communication device, determines whether the block of data contained in the signal is a block of a new MAC PDU, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0377] Figure 24 This is a diagram illustrating an example indicated by PI. Figure 24 The image shows the three MAC PDUs that receive MAC PDU#A, MAC PDU#B, and MAC PDU#C.

[0378] exist Figure 24In the example, PI=0 is indicated in the receive schedule of MAC PDU#A, PI=1 is indicated in the receive schedule of MAC PDU#B, and PI=1 is indicated in the receive schedule of MAC PDU#C.

[0379] PI can be either an exact index (or an actual index) or an index that performs modulo looping. For example, in the case of modulo looping, the index is indicated by a cycle of values ​​such as 1, 2, 3, 4, 1, 2, 3, 4. Or, for example, in the case of modulo looping, the index is indicated by a cycle of values ​​such as 0, 1, 2, 3, 0, 1, 2, 3.

[0380] If the PI (Portable Receiver) differs from a previous reception, the reception corresponding to that PI is scheduled for a new MAC PDU. Additionally, if the reception of a MAC PDU corresponding to a previous reception is incomplete, the MAC PDU corresponding to that previous reception can be refreshed.

[0381] If the PI is the same as the previous reception, the reception corresponding to that PI is the reception of the same MACPDU as the previous reception.

[0382] As in option D above, by setting the PI to notify the MAC PDU reception schedule, the device that obtains the PI can know the MAC PDU reception schedule (e.g., whether the received MAC PDU is a new MAC PDU), thereby avoiding inconsistencies between the data sending side and the receiving side, and enabling appropriate communication processing (e.g., transformation processing to MAC PDU during reception).

[0383] <Proposal b in RX: A method to determine the size of a MAC PDU>

[0384] Proposal b describes a method for determining the size of a MAC PDU (e.g., a scheduled MAC PDU). This method for determining the size of a MAC PDU corresponds to the method for determining L_total, which represents the overall size of the MAC PDU.

[0385] <Option A of Proposal b in RX: Explicit Directive>

[0386] When explicitly indicating the size, the method of indication is not limited. For example, any at least one of the control signals, synchronization signals, and arbitrary signals received before the MAC PDU is received can also indicate the exact size (or actual size) of the MAC PDU. Alternatively, higher-level parameters (e.g., preset parameters or RRC-set parameters) can also determine multiple candidates for the size, and any at least one of the control signals, synchronization signals, and arbitrary signals received before the MAC PDU is received can indicate one of the multiple candidates.

[0387] <Option B of Proposal b in RX: Size is predetermined>

[0388] The single size of a MAC PDU can be predetermined or defined by a specification. In the latter case, a single size is always used.

[0389] <Option C of Proposal b in RX: Implicit Decision>

[0390] At the start of the reception scheduling for a MAC PDU, all resources of one or more channels / signals for reception are provided. The size of the MAC PDU is then determined based on the total amount of resources provided. For example, the size of the MAC PDU can be determined based on at least one of the following: the number of time slots provided as resources, the number of receptions, the number of available resource elements, etc.

[0391] As in Proposal b above, by notifying the size of the MAC PDU, inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing into the MAC PDU during reception) can be performed. For example, as in Proposal b above, by notifying the size of the MAC PDU, the device sending the MAC PDU can appropriately perform MAC PDU segmentation, and the device receiving the MAC PDU can appropriately generate the MAC PDU based on more than one segment.

[0392] <Proposal c in RX: Transformation method of MAC PDU>

[0393] Proposal c describes segmentation (dividing the MAC PDU into blocks, e.g., segments) and concatenation (linking blocks to generate the MAC PDU) as methods for transforming the MAC PDU. For example, proposal c describes where and how segmentation / concatenation is performed, and how to determine which segment is scheduled. For example, proposal c describes how to indicate the size of each block obtained through segmentation of the MAC PDU. Figure 19The L_1~L_N diagrams are explained. Furthermore, proposal c explains how to indicate the indexes of each block obtained through segmentation of the MAC PDU (...). Figure 19 The diagram shows RX-1 to RX-N. Furthermore, proposal c explains where and how the segments / cascades are performed.

[0394] <Option A of Proposal c in RX: Explicit instruction for each received>

[0395] When explicit indication is given, the method of indication is not limited. For example, at least one of the control signals, synchronization signals, and arbitrary signals received before each reception can indicate the exact size of the received segment and / or the index of the reception. In the indication of the index, either an exact index or an index with modulo operation can be indicated. For example, in the case of modulo operation, the index is indicated by a cyclic value such as 1, 2, 3, 4, 1, 2, 3, 4. Or, for example, in the case of modulo operation, the index is indicated by a cyclic value such as 0, 1, 2, 3, 0, 1, 2, 3.

[0396] Additionally, if the A-IoT UE detects a reception failure of a channel / signal containing a block of MAC PDUs sent by the BS or an intermediate UE, the A-IoT UE can refresh the received blocks of that MAC PDU, skip the remaining reception of that MAC PDU, and report the reception failure to the BS or intermediate UE. Refreshing the received blocks, skipping the remaining reception, and reporting the reception failure can all be performed, or at least one of them can be performed.

[0397] Furthermore, the detection of reception failure can be based on the indicated index. For example, in the case where blocks with modulo operations at indices 1, 2, 3, 4, ... are received sequentially, if 4 is detected after index 2 but 3 is not detected, the reception of the block corresponding to index 3 is detected as a failure.

[0398] Regarding the size of each segment, it can also be that higher-level parameters (e.g., preset parameters or RRC-set parameters) determine multiple candidates for the size, and at least one of the control signals, synchronization signals, and arbitrary signals received before the MAC PDU is received indicates one of the multiple candidates.

[0399] <Option B of Proposal C in RX: Pre-determined>

[0400] Regarding size, the single size of a segment can be predetermined or defined by a specification. In this case, a single size is always used.

[0401] <Option C of Proposal c in RX: Implicit Decision>

[0402] Regarding segment size, at the start of the reception scheduling for a MAC PDU, all resources of one or more channels / signals for reception are provided. Then, the size of each transmission is determined based on the total amount of resources provided. For example, the segment size can be determined based on at least one of the following: the number of time slots provided as resources, the number of receptions, the number of available resource elements, etc. In this case, the sizes of the segments of the MAC PDU can be the same. That is, it can be L_1 = L_2 = ... = L_N (= L_total divided by N).

[0403] Alternatively, regarding segment size, at the start of the reception scheduling for a MAC PDU, all resources of one or more channels / signals for reception are provided. The size of each reception segment is then determined based on the amount of resources provided for each reception. For example, the segment size can be determined based on at least one of the following: the number of time slots provided as resources, the number of receptions, the number of available resource elements, etc. In this case, the segments of the MAC PDU can be the same size or different size from each other.

[0404] Furthermore, for example, regarding the segment size, the size of a transmitted MAC PDU can be determined based on any of the methods in "<Proposal b in RX>" mentioned above. Then, the size of the MAC PDU determined by proposal b is equally divided into more than one segment. For example, regardless of the differences between the receiving resources, the size of the MAC PDU is equally divided into more than one segment.

[0405] Regarding segment indexes, it's also possible to not indicate the index for each receive. In this case, the receive is performed at the index following the latest receive. For example, if the latest receive has an index of 3, the next receive would have an index of 4. In other words, receives are performed in index order. Alternatively, the indices can be associated with the order in which the receives are performed.

[0406] Regarding segment indexes, each receiving resource is associated with an index. In this case, the data for the index is received through that resource. That is, the data for a segment with index #k is received through the sending resource associated with index #k.

[0407] <Option D of Proposal c in RX: An example of segmentation / cascading performed via PHY>

[0408] Segmentation and / or cascading can be performed at the physical layer. For example, segmentation and / or cascading can be performed based on at least one of the following: instructions from the NW, settings from the NW, definitions in the specification, and instructions from higher layers.

[0409] The received data is linked through the physical layer. Then, the linked data is shared with the MAC layer in MAC PDU format.

[0410] For example, the data to be transmitted (e.g., MAC PDU or TB) is shared from the MAC layer to the physical layer. At the physical layer, the MAC PDU is segmented. Then, the segments obtained through segmentation are transmitted.

[0411] <Option E of Proposal c in RX: An example of segmentation / cascading executed via MAC>

[0412] Segmentation and / or cascading can be performed through the MAC layer. For example, segmentation and / or cascading can be performed based on at least one of the following: instructions from the NW, settings from the NW, definitions in the specification, and instructions from higher levels.

[0413] The received data is shared with the MAC layer. Then, multiple receivers are linked together for the MAC PDU format. Additionally, the received data shared with the MAC layer may or may not be indexed.

[0414] For example, a MAC PDU is segmented at the MAC layer. Then, each segment is shared with the physical layer for its own transmission resources.

[0415] As in Proposal c above, by knowing the information about the transformation method for the MAC PDU (size, index), inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing to the MAC PDU during reception) can be performed. For example, as in Proposal c above, by knowing the information about the transformation method for the MAC PDU, the device sending the MAC PDU can appropriately perform MAC PDU segmentation, and the device receiving the MAC PDU can appropriately generate the MAC PDU based on more than one segment.

[0416] <Proposal d in RX: Methods for signal processing of MAC PDUs (channel coding, CRC attachment methods)>

[0417] <Option A of Proposal d in RX: Execution per MAC PDU>

[0418] During transmission, channel coding / CRC appending is performed on a per MAC PDU basis. In this case, during reception, after all segments for a MAC PDU have been received, decoding of the channel coding is performed, and error detection is performed based on the appended CRC.

[0419] <Option B of Proposal d in RX: Execution for each send>

[0420] During transmission, channel coding / CRC appending is performed on a per-transmission basis. In other words, during transmission, channel coding / CRC appending is performed on a per-segment basis. In this case, during reception, the receiving wireless communication device performs channel coding decoding on a per-segment basis after receiving each segment, and performs error detection on a per-segment basis based on the CRC appended on each segment.

[0421] Alternatively, CRC appending can be performed on a segment-by-segment basis and on a per-MAC PDU basis. With CRC appending performed on a segment-by-segment basis and on a per-MAC PDU basis, error detection can be performed on a segment-by-segment basis during reception, and a CRC check can be performed on the MAC PDU after a segment for a MAC PDU has been received.

[0422] Furthermore, channel coding can also be performed segment by segment and per MAC PDU. In the case where channel coding is performed segment by segment and per MAC PDU, decoding can also be performed segment by segment during reception, and decoding of the MAC PDU can be performed after a segment for a MAC PDU has been received.

[0423] Figure 25 This is a diagram illustrating examples of CRC appending performed on each segment and on each MAC PDU. Figure 25 The diagram shows the addition of a CRC to each block (RX-1~RX-N) of the transmitted MAC PDU, and the addition of a CRC to the MAC PDU.

[0424] <Option C of Proposal d in RX: Do not execute>

[0425] In option C of proposal d, channel coding and CRC appending are not performed. In this case, transmission can also be performed based on sequence. Alternatively, CRC appending can be performed without channel coding. Or, channel coding can be performed without CRC appending.

[0426] As in Proposal d above, by knowing the specifications of the MAC PDU signal processing method, inconsistencies between the data transmitting and receiving sides can be avoided, and appropriate communication processing (e.g., conversion processing to MAC PDU during reception) can be performed. For example, as in Proposal c above, by knowing the specifications of the MAC PDU signal processing method, the device transmitting the MAC PDU can appropriately perform MAC PDU segmentation, and the device receiving the MAC PDU can appropriately generate the MAC PDU based on more than one segment.

[0427] <Proposal e in RX: Size of MAC PDU (e.g., should it be aligned to bytes?)>

[0428] <Option A of Proposal e in RX: Transmission of each channel / signal is byte-aligned>

[0429] For example, imagine that the result of dividing the size of the MAC PDU by the number of segments is aligned in bytes. That is, imagine that the number of bits in the result of dividing the size of the MAC PDU by the number of segments is an integer multiple of 8 bits. In other words, imagine that the number of bits in each segment is an integer multiple of 8 bits.

[0430] The size of each transmission can also be calculated using the TBS determination mechanism. The TBS determination mechanism includes 8 8N-bit quantization using N bits (N being an integer greater than 1), and / or methods for selecting TBS from candidates aligned to bytes, etc.

[0431] <Option B of Proposal e in RX: Transmission of each channel / signal can be byte-aligned or not>

[0432] For example, if a MAC PDU uses multiple segments of equal size, it is assumed that dividing the size of the MAC PDU by the number of segments will result in a positive integer. This positive integer value corresponds to the segment size (e.g., the number of bits). In this case, it is assumed that the number of bits obtained by dividing the size of the MAC PDU by the number of segments is not limited to being an integer multiple of 8 bits.

[0433] The size of each transmission is calculated using the TBS (Tracking Baseline Scale) mechanism. However, the TBS mechanism does not include a 8x ... 8N-bit quantization, where N bits (N is an integer greater than or equal to 1) are used for quantization.

[0434] <Proposal f in RX: Regarding the size of the MAC PDU>

[0435] Regarding data size, any of the following can be applied.

[0436] • Data sizes can be the same in A-IoT UE reception. In other words, the sizes of the segments being transmitted can be the same.

[0437] • Data sizes can be the same or different in the A-IoT UE reception. In other words, the sizes of the transmitted segments can be the same or different.

[0438] The data size corresponds to the segment size. The segment size can be the same as the proposal shown in <Proposal c in RX> above.

[0439] As explained above, by specifying any one of the proposals for the MAC PDU for RX, inconsistencies between the data sending and receiving sides can be avoided, and appropriate communication processing (e.g., transformation processing to MAC PDU during reception) can be performed.

[0440] Furthermore, in the above, the specifications for each of TX (transmission of the A-IoT UE) and RX (reception of the A-IoT UE) can be the same or different from each other. For example, the method for notifying the transmission schedule of a new MAC PDU in TX and the method for notifying the reception schedule of a new MAC PDU in RX can be the same (e.g., the same option) or different (e.g., different options). Additionally, an implicit instruction can be given to the other party based on an explicit instruction in either TX or RX.

[0441] Furthermore, in the aforementioned proposals, it is assumed that the TX of one or more PHY channels / signals corresponds to the TX of one MAC PDU, and the RX of one or more PHY channels / signals corresponds to the RX of one MAC PDU, but this disclosure is not limited thereto. For example, this disclosure can also be applied to situations where the TX of one or more PHY channels / signals corresponds to the TX of one or more MAC PDUs, and the RX of one or more PHY channels / signals corresponds to the RX of one or more MAC PDUs. Additionally, for example, this disclosure can also be applied to situations where the TX of one PHY channel / signal corresponds to the TX of one MAC PDU, and the RX of one PHY channel / signal corresponds to the RX of one MAC PDU.

[0442] Next, the structures of base station 10 and device 20 will be described. Furthermore, the structures of base station 10 and device 20 described below illustrate one example of the functions associated with this embodiment. Base station 10 and device 20 may also have functions not shown. Moreover, the functional divisions and / or names of functional units are not limited as long as the function performs the operations involved in this embodiment.

[0443] <Base station structure>

[0444] Figure 26 This is a block diagram illustrating an example of the structure of a base station 10 according to an embodiment. Base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 10 communicates wirelessly with device 20 (see reference 103). Figure 27 The base station 10 can also be an intermediate node, an auxiliary node, or a terminal (the terminal of the SL that communicates with the device 20).

[0445] The transmitting unit 101 transmits a downlink (DL) signal to the device 20. For example, the transmitting unit 101 transmits the DL signal under the control of the control unit 103.

[0446] The DL signal may include, for example, downlink data signals and control information (e.g., DCI (Downlink Control Information)). Furthermore, the DL signal may include scheduling information related to signal transmission by device 20 (e.g., UL authorization). Additionally, the DL signal may also include higher-layer control information (e.g., RRC (Radio Resource Control) control information). Furthermore, the DL signal may also include reference signals.

[0447] The channels used for transmitting DL signals may include, for example, data channels and control channels. For instance, 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, base station 10 uses the PDCCH to transmit control information and the PDSCH to transmit downlink data signals for device 20.

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

[0449] The receiving unit 102 receives uplink (UL) signals transmitted from the device 20. For example, the receiving unit 102 receives UL signals under the control of the control unit 103.

[0450] The control unit 103 controls the communication operations of the base station 10, which includes the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102. For example, the control unit 103 performs operations other than transmission and reception as described in the above embodiments (in addition, these operations may also be performed by the reception unit 102 and / or the transmission unit 101).

[0451] For example, control unit 103 acquires data and control information from higher layers and outputs it to transmitting unit 101. Furthermore, control unit 103 outputs data and control information received from receiving unit 102 to higher layers.

[0452] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or UL signals based on signals received from the device 20 (e.g., data and control information) and / or data and control information obtained from higher layers. Information related to the allocated resources may be included in the control information sent to the device 20.

[0453] As an example of resource allocation used in the transmission and reception of UL signals, the control unit 103 sets the PUCCH resources. Information related to the PUCCH setting, such as the PUCCH cell timing pattern (PUCCH setting information), can be notified to the device 20 via RRC.

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

[0455] For example, the receiving unit 102 of base station 10 (an example of a wireless communication device) receives more than one signal from device 20, each containing more than one segment. Then, control unit 103 connects the more than one segment to generate a single data unit with a specific data processing unit.

[0456] For example, the control unit 103 of base station 10 (an example of a wireless communication device) divides a single data unit with a specific data processing unit into more than one segment. The transmitting unit 101 transmits to device 20 more than one signal, each containing more than one segment.

[0457] <Equipment Structure>

[0458] Figure 27 This is a block diagram illustrating an example of the structure of the device 20 according to the embodiment. The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with the base station 10 wirelessly, for example. The device 20 may also be, for example, an A-IoT UE.

[0459] The receiving unit 201 receives the 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.

[0460] The transmitting unit 202 transmits a 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.

[0461] The UL signal may include, for example, uplink data signals and control information (e.g., UCI (Uplink Control Information)). For instance, it may include information related to the processing capabilities of device 20 (e.g., A-IoT capability). Furthermore, the UL signal may also include reference signals.

[0462] The channels used in transmitting UL signals may include data channels and control channels. For example, the data channel may include PUSCH (Physical Uplink Shared Channel), and the control channel may include PUCCH (Physical Uplink Control Channel). For example, device 20 uses PUCCH to send control information to base station 10 and uses PUSCH to transmit uplink data signals.

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

[0464] The control unit 203 controls the communication operations of the device 20, which includes the receiving processing in the receiving unit 201 and the transmitting processing in the transmitting unit 202. For example, the control unit 203 performs operations other than transmitting and receiving as described in the above embodiments (in addition, these operations may also be performed by the receiving unit 201 and / or the transmitting unit 202).

[0465] For example, control unit 203 acquires data and control information from higher layers and outputs it to transmitting unit 202. Furthermore, control unit 203 may output data and control information received from receiving unit 201 to higher layers, for example.

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

[0467] The control unit 203 configures the PUCCH resources based on the configuration information received from the base station 10 (e.g., configuration information such as the PUCCH cell timing mode notified via RRC and / or DCI). The control unit 203 determines the PUCCH resources used in transmitting the information fed back to the base station 10. The transmitting unit 202, under the control of the control unit 203, transmits the information fed back to the base station 10 using the PUCCH resources determined by the control unit 203.

[0468] Furthermore, the channels used in transmitting DL signals and UL signals are not limited to the examples described above. For instance, the channels used in transmitting DL signals and UL signals may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). RACH, for example, can be used for transmitting DCIs that include RA-RNTI (Random Access Radio Network Temporary Identifier).

[0469] Here, the receiving unit 201 and the transmitting unit 202 (which can also be collectively referred to as the communication unit) communicate with the network such as the base station 10.

[0470] For example, the control unit 203 of device 20 divides a single data unit with a specific data processing unit into more than one segment. The transmitting unit 202 transmits more than one signal, each containing more than one segment.

[0471] Furthermore, for example, the receiving unit 201 of device 20 receives more than one signal, each containing more than one segment. The control unit 203 connects more than one segment to generate a single data unit with a specific data processing unit.

[0472] The above provides an explanation of this disclosure. Furthermore, the division of items in the above explanation is not essential in this disclosure; items described in two or more items may be combined as needed, and items described in one item may be applied to items described in other items (as long as there is no contradiction).

[0473] <Hardware structure, etc.>

[0474] The block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., wired, wireless, etc.) connecting two or more physically or logically separate devices, and implementing it using these multiple devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0475] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural unit) that implements the sending function is called a transmitting unit or a transmitter. Both are described above, and the implementation method is not particularly limited.

[0476] For example, the base station, device, etc. in one embodiment of this disclosure can also function as a computer for processing the wireless communication method of this disclosure. Figure 28 This diagram illustrates an example of the hardware structure of the base station and device involved in the implementation. The base station 10 and device 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0477] Additionally, in the following description, the term "device" can be replaced with circuit, device, unit, etc. The hardware structure of base station 10 and device 20 can be configured to include one or more of the devices shown in the figure, or it can be configured to exclude some of the devices.

[0478] Regarding the various functions in base station 10 and device 20, specific software (programs) are read into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication based on communication device 1004, or controls at least one of reading out and writing data in memory 1002 and storage device 1003, thereby achieving the following:

[0479] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may also be implemented by the processor 1001.

[0480] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 103 of the base station 10 and the control unit 203 of the device 20 can also be implemented by control programs stored in the memory 1002 and operated by the processor 1001; similarly, other functional blocks can be implemented. The various processes described above have been explained as being executed by one processor 1001, but they can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented using more than one chip. Additionally, the program can be transmitted from a network via an electrical communication line.

[0481] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: ROM (Read-Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory). The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0482] Storage 1003 is a computer-readable recording medium, and may be comprised of at least one of the following: CD-ROM (Compact Disc ROM) or other optical discs; hard disk drives; flexible discs; optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs); smart cards; flash memory (e.g., cards, sticks, key drives); floppy disks; magnetic stripes; etc. Storage 1003 may also be referred to as an auxiliary storage device. The aforementioned storage medium may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0483] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 can also be implemented using the communication device 1004.

[0484] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED light, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., touch panel).

[0485] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured using a single bus or different buses between the devices.

[0486] Furthermore, the base station 10 and the device 20 can also be configured with hardware including microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), etc., and can also implement some or all of the functional blocks through such hardware. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0487] <Information notification and signaling>

[0488] The notification of information is not limited to the implementation methods described in this disclosure, and can also be performed by other methods. For example, the notification of information can also be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Media Access Control) signaling, broadcast information (MIB (Master Information Block)), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling can also be referred to as RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0489] <Application Systems>

[0490] The implementations described in this disclosure can also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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 At least one of 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), systems utilizing other suitable systems, and next-generation systems derived from them through enhancement, modification, creation, or specification. Furthermore, multiple systems may be combined (e.g., a combination of LTE and at least one of LTE-A with 5G, etc.) for application.

[0491] <Processing procedures, etc.>

[0492] The processing procedures, timing, flowcharts, etc., of the various methods / implementations described in this disclosure may be rearranged as long as they do not contradict each other. For example, for the methods described in this disclosure, an illustrative order is used to indicate the elements of various steps, but the order in which they are indicated is not limited.

[0493] <Base Station Operation>

[0494] In this disclosure, specific operations purported to be performed by a base station may sometimes be performed by its upper node, depending on the circumstances. Clearly, in a network consisting of one or more network nodes having a base station, various operations for communication with a terminal can also be performed by at least one of the base station and other network nodes besides the base station (e.g., consider MME or S-GW, but not limited to these). In the above, other network nodes besides the base station are exemplified as one case; it could also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0495] <Direction of input / output>

[0496] Information (see the items under "Information, Signals") can also be output from higher (or lower) layers to lower (or higher) layers. It can also be input and output via multiple network nodes.

[0497] <Processing of input and output information>

[0498] Input and output information can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0499] <Judgment Method>

[0500] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (Boolean: true or false), or by a numerical comparison (e.g., a comparison with a specific value).

[0501] <Changes in methods, etc.>

[0502] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, notification of specific information (e.g., a "It is X" notification) is not limited to explicit notification, but can also be done implicitly (e.g., without notifying the recipient of that specific information).

[0503] The present disclosure has been described in detail above, but it will be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented with modifications and variations without departing from the spirit and scope defined by the claims. Therefore, the description in this disclosure is for illustrative purposes and is not intended to be restrictive in any way.

[0504] <Software>

[0505] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0506] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of transmission medium.

[0507] <Information, Signals>

[0508] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0509] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and the symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as a carrier frequency, cell, frequency carrier, etc.

[0510] <Systems, Networks>

[0511] The terms “system” and “network” are used interchangeably in this disclosure.

[0512] <Parameters, Channel Name>

[0513] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by an index.

[0514] The names used for the parameters described above are not limiting names in any respect. Furthermore, the mathematical expressions using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0515] <Base Station>

[0516] In this disclosure, the terms "base station (BS)," "wireless 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" are used interchangeably. There are also instances where terms such as macro cell, small cell, femtocell, and picocell are used to refer to base stations.

[0517] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0518] In this disclosure, the information sent by the base station to the terminal can also be rewritten as the base station instructing the terminal to perform information-based control and operation.

[0519] <Mobile Station>

[0520] In this disclosure, the terms “Mobile Station (MS),” “user terminal,” “user equipment (UE),” and “terminal” are used interchangeably.

[0521] There are also instances where a mobile station is 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, hand set, user agent, mobile client, client, or several other appropriate terms.

[0522] <Base station / Mobile station>

[0523] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a communication device, etc. Furthermore, at least one of the base station and the mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object whose speed of movement is arbitrary. This also includes situations where the mobile body is stationary. Examples of mobile bodies include vehicles, transport vehicles, automobiles, autonomous two-wheelers, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (boats and other watercraft), airplanes, rockets, artificial satellites, drones (registered trademark), multi-rotor aircraft, quadcopter aircraft, balloons, and objects mounted on them, and are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operating commands. It can be a means of transportation (e.g., vehicles, airplanes, etc.), a mobile body that moves unmanned (e.g., drones, autonomous vehicles, etc.), or a robot (humanized or unmanned). In addition, at least one of the base station and the mobile station also includes a device that is not necessarily mobile during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0524] Furthermore, the base station in this disclosure can also be rewritten as a terminal. For example, embodiments of this disclosure can also be applied to structures where communication between the base station and the terminal is replaced by communication between multiple terminals (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, it can also be configured such that the device 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can also be rewritten as terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be rewritten as side channel.

[0525] Similarly, the terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the aforementioned device 20.

[0526] Figure 29 An example of the structure of vehicle 2001 is shown. For example... Figure 29 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various methods / implementations described in this disclosure can also be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0527] The drive unit 2002 is configured, for example, as an engine, a motor, or a combination of an engine and a motor. The steering unit 2003 is configured to include at least a steering wheel (also called a handlebar) and to steer at least one of the front and rear wheels based on the operation of the steering wheel by the user.

[0528] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. The electronic control unit 2010 receives signals from various sensors 2021-2029 of the vehicle 2001. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

[0529] The signals from various sensors 2021 to 2029 include current signals from current sensor 2021 that senses the current of the motor, speed signals of the front and rear wheels obtained by speed sensor 2022, air pressure signals of the front and rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depress amount signals obtained by accelerator pedal sensor 2029, brake pedal depress amount signals obtained by brake pedal sensor 2026, gear shift lever operation signals obtained by gear shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0530] The information service unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, as well as one or more ECUs that control these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0531] The information service unit 2012 may include input devices (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) that accept input from the outside, and output devices (e.g., display, speaker, LED light, touch panel, etc.) that implement output to the outside.

[0532] The driver assistance system unit 2030 comprises various devices used to provide functions such as preventing accidents or reducing the driver's workload, including millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the driver assistance system unit 2030 sends and receives various information via a communication module 2013 and implements driver assistance or autonomous driving functions.

[0533] The communication module 2013 can communicate with the microprocessor 2031 and the constituent elements of the vehicle 2001 via the communication port. For example, the communication module 2013 sends and receives data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheel 2007, rear wheel 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, and memory (ROM, RAM) 2032 and sensors 2021-29 in the vehicle 2001 via the communication port 2033.

[0534] The communication module 2013 can be controlled by the microprocessor 2031 of the electronic control unit 2010 and is a communication device capable of communicating with external devices. For example, it can send and receive various types of information wirelessly with external devices. The communication module 2013 can be located either inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0535] The communication module 2013 can also wirelessly transmit to an external device at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2029 described above, information obtained based on these signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2029, and the information service unit 2012 can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 2013 can also include information based on the aforementioned input.

[0536] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle 2001. The information service unit 2012 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received through the communication module 2013 (or data / information decoded from the PDSCH).

[0537] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be utilized by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided by the vehicle 2001.

[0538] <Meaning and Explanation of Terms>

[0539] The terms "determining" and "determining" as used in this disclosure encompass a wide variety of actions. For example, "determining" and "determining" can include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining. Furthermore, "determining" and "determining" can include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory). Additionally, "determining" and "determining" can include actions such as resolving, selecting, choosing, establishing, and comparing. That is, "judgment" and "decision" can include situations where certain actions are regarded as having been "judged" or "decided". In addition, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc.

[0540] The terms “connected,” “coupled,” or any variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connection or combination between elements can be physical, logical, or a combination thereof. For example, “connected” can also be rewritten as “access.” In the context of this disclosure, it is possible to consider two elements being mutually “connected” or “coupled” using at least one or more wires, cables, or printed electrical connections, and as several non-limiting and non-exclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (both visible and invisible) region.

[0541] <Reference Signal>

[0542] The reference signal can also be simply referred to as RS (Reference Signal), or it can be called a pilot depending on the standard applied.

[0543] <The meaning of "based on">

[0544] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0545] <"First", "Second">

[0546] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be used, or that the first element must precede the second element in some form.

[0547] <Unit>

[0548] Alternatively, the term "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0549] <Open format>

[0550] In this disclosure, the terms "include," "including," and variations thereof, as well as the term "comprising," refer to inclusion. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0551] <Time units such as TTI, frequency units such as RB, and radio frame structure>

[0552] A wireless frame can also consist of one or more frames in the time domain. These frames can also be referred to as subframes in the time domain. Furthermore, a subframe can also consist of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0553] A parameter set can also be a set of communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, a parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0554] In the time domain, a time slot can also be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can also be a time unit based on a set of parameters.

[0555] A time slot can also comprise multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (or PUSCH) mapping type B.

[0556] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also be referred to by their respective other names.

[0557] For example, a subframe can also be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0558] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0559] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0560] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0561] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in LTE Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0562] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0563] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also include one or more consecutive subcarriers. The number of subcarriers included in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers included in an RB can also be determined based on the parameter set.

[0564] Furthermore, the time domain of an RB can also include one or more symbols, or it can be the length of a time slot, a mini-time slot, a subframe, or a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0565] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0566] Furthermore, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0567] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of that carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0568] A BWP can also include a UL BWP and a DL BWP. For a UE, one or more BWPs can also be set within a single carrier.

[0569] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Furthermore, the terms "cell," "carrier," etc., used in this disclosure may be replaced with "BWP."

[0570] The structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0571] <Maximum Transmit Power>

[0572] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0573] <Article>

[0574] In this disclosure, for example, in cases where articles are added through translation, such as in English (a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0575] <"Differences">

[0576] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0577] Industrial availability

[0578] One aspect of this disclosure is useful for wireless communication systems.

[0579] Explanation of reference numerals in the attached figures

[0580] 10 Base station; 20 Equipment; 101, 202 Transmitting units; 102, 201 Receiving units; 103, 203 Control units.

Claims

1. A device, which is an environmental Internet of Things (A-IoT) device, comprising: The control unit divides a single data unit with a specific data processing unit into one or more segments; and The transmitting unit transmits one or more signals, each containing one or more of the aforementioned segments.

2. The device according to claim 1, wherein, The transmitting unit sends information to the receiving destination of the signal indicating whether the segment contains data of a new data unit, and / or receives the information from the receiving destination of the signal.

3. The device according to claim 1, wherein, Whether a segment contains new data units is determined based on the transmission time of the signal containing the segment.

4. The device according to claim 1, wherein, The size of the segment and / or the size of the data unit is indicated explicitly or implicitly.

5. A wireless communication device, comprising: The receiving unit receives one or more signals, each containing one or more segments, from environmental IoT devices, i.e., A-IoT devices; and The control unit connects one or more segments to generate a single data unit with a specific data processing unit.

6. A wireless communication method, wherein, Environmental IoT devices, or A-IoT devices, divide a single data unit with a specific data processing unit into more than one segment; and The A-IoT device sends one or more signals, each containing one or more segments.

Images