Device, wireless communication apparatus, and wireless communication method

Abstract

An Ambient Internet of Things (A-IoT) device comprises: 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 including one or more segments.

Description

Device, wireless communication apparatus, and wireless communication method

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

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

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

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

[0005] In a communication system including an ambient IoT device, there is room for consideration regarding the structure of data exchanged between the ambient IoT device and other wireless communication devices.

[0006] One aspect of the present disclosure provides a device, a wireless communication device, and a wireless communication method that allow an ambient IoT device to exchange appropriately configured data with other wireless communication devices.

[0007] A device according to one aspect of the present disclosure is an Ambient Internet of Things (A-IoT) device that includes 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 including the one or more segments.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating Topology 1. FIG. 2 is a diagram illustrating Topology 3 in DL assistance. FIG. 3 is a diagram illustrating Topology 3 in UL assistance. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating a communication flow of DT in Topology 1. FIG. 7 is a diagram illustrating a communication flow of DO-DTT in Topology 1. FIG. 8 is a diagram illustrating a communication flow of DT in Topology 2. FIG. 9 is a diagram illustrating a communication flow of DO-DTT in Topology 2. FIG. 10 is a diagram illustrating an example of a MAC PDU structure in TX. FIG. 11 is a diagram illustrating Option A of a method for knowing transmission scheduling. FIG. 12 is a diagram illustrating Option B of a method for knowing transmission scheduling. FIG. 13 is a diagram illustrating an example of a time-based method of Option C of Proposal a. FIG. 14 is a diagram illustrating an example where one MAC PDU is associated with a fixed number of transmissions. FIG. 15 is a diagram illustrating an example indicated by a PI. FIG. 16 is a diagram illustrating an example where CRC attachment is performed per segment and per MAC PDU. FIG. 17 is a diagram illustrating an example of a MAC PDU structure in RX. FIG. 18 is a diagram illustrating Option A of a method for knowing reception scheduling. FIG. 19 is a diagram illustrating Option B of a method for knowing reception scheduling. FIG. 20 is a diagram illustrating an example of a time-based method of Option C of Proposal a. FIG. 1 is a diagram showing an example in which one MAC PDU is associated with a fixed number of receptions; FIG. 2 is a diagram showing an example in which one MAC PDU is indicated by a PI; FIG. 3 is a diagram showing an example in which CRC attachment is performed for each segment and for each MAC PDU; FIG. 4 is a block diagram showing an example of a configuration of a base station according to an embodiment of the present disclosure; FIG. 5 is a block diagram showing an example of a configuration of a device according to an embodiment of the present disclosure; FIG. 6 is a diagram showing an example of a hardware configuration of a base station and a device according to an embodiment of the present disclosure; and FIG. 7 is a diagram showing an example of a configuration of a vehicle according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

[0016] The base station 10 transmits DL signals such as control information, setting information, and data via DL (Downlink) to the device 20. The base station 10 receives UL signals such as control information, information related to the processing capability of the device 20 (device capability (information) or A-IoT capability (information); for example, capability, device capability, A-IoT capability, A-IoT device capability, etc.), and data via UP (Uplink) from the device 20.

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

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

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

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

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

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

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

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

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

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

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

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

[0029] Fig. 2 is a diagram illustrating Topology 1. As shown in Fig. 2, Topology 1 is a configuration in which a base station (BS) and an ambient IoT device communicate with each other. The ambient IoT device directly communicates with the base station in a two-way manner.

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

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

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

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

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

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

[0036] 6 is a diagram illustrating Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device performs bidirectional communication with the UE. Communication related to Topology 4 may be considered as side link (SL) communication.

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

[0038] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE of Topology 4) in addition to the device 20. In this specification, the base station, the support node, the intermediate node, and the terminal may be read as a network or a (network) node. Also, an A-IoT device may be simply referred to as A-IoT.

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

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

[0041] FIG. 7 is a diagram illustrating backscatter transmission. FIG. 7 shows an example in which an ambient IoT device performs ON-OFF keying and transmits information. The dashed line area shown in FIG. 7 indicates an OFF section, which may correspond to information (bit) "0." A sine wave signal may correspond to information "1."

[0042] <Rel-19 SID> The Rel-19 SID (Study Item Description) examined solutions necessary and feasible for A-IoT (see Section 4.1 of Non-Patent Document 5). The examined solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

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

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

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

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

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

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

[0049] TX TX is a backscatter UL transmission without amplification or a general amplified UL transmission. Alternatively, an amplified backscatter UL transmission may be performed.

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

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

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

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

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

[0055] In Topology 2, communication is performed between a base station and an A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with an intermediate node located between the base station and the A-IoT UE. Note that the base station in the case of Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as an intermediate UE, int. UE (intermediate UE), etc.

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

[0057] As shown in the four communication flows 1. to 4. below, the A-IoT UE wakes up in step 1 and receives information (or a signal) in step 2. Also, as shown in the communication flows 2. and 4. below, the A-IoT UE transmits a signal (or information) in step 3.

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

[0059] The following two steps are assumed in the DT communication flow in Topology 1. Note that Step 1 starts when a packet is generated in an upper layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 8 ).

[0060] Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform transmitted from a base station. The signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE. The carrier waveform may be replaced with a carrier wave. Step 2: The A-IoT UE receives information from the base station.

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

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

[0063] The following three steps are assumed in the DO-DTT communication flow in Topology 1. Note that Step 1 starts when a packet is generated in a higher layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 9).

[0064] Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform sent from the base station. Step 2: The A-IoT UE receives information from the base station. Step 3: The A-IoT UE sends a signal to the base station.

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

[0066] The following four steps are assumed in the DT communication flow in Topology 2. Note that Step 0 starts when a packet is generated in an upper layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 10).

[0067] Step 0: The int. UE receives a trigger from the base station to send a signal such as a carrier waveform to the A-IoT UE, and sends a signal to the A-IoT UE based on the trigger. Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform sent from the int. UE. Step 2: The A-IoT UE receives information from the int. UE. Step X: The int. UE sends a signal to the base station.

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

[0069] The following five-step communication flow is assumed for the DO-DTT communication flow in Topology 2. Note that step 0 starts when a packet is generated in a higher layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 11).

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

[0071] In addition, in the above four communication flows 1. to 4., step 2 and step 3 may be divided into two steps (in other words, may have two sub-steps).

[0072] For example, in the communication flow of DT in Topology 1 / 2, step 2 may have the following two sub-steps (step 2A and step 2B): Step 2A: The A-IoT UE receives information A (e.g., control information or signaling) from the base station / int. UE. Step 2B: The A-IoT UE receives information B (e.g., data information or signaling) from the base station / int. UE.

[0073] Also, for example, in the communication flow of DO-DTT in Topology 1 / 2, step 3 may have the following two sub-steps (step 3A and step 3B): Step 3A: The A-IoT UE transmits signal A (e.g., control information or signal) to the base station / int. UE. Step 3B: The A-IoT UE transmits signal B (e.g., data information or signal) to the base station / int. UE.

[0074] <Things to consider> As described above, the flow of A-IoT communication includes the transmission and reception of signals in the following steps. Note that two or more of the following steps may be combined into one step. Also, at least one of the following steps may be skipped. Step 1a: Energy source signal / wake-up signal Step 1b: Synchronization signal Step 2: Signal for receiving data from the NW (signal including DL control information, DL data, or DL ​​control information and DL data) Step 1c: Carrier wave for backscattering (for example, unmodulated carrier wave) Step 3: Signal for transmitting data from the A-IoT UE

[0075] As described above, the A-IoT UE receives signals from the BS or intermediate UE, such as in step 2. The A-IoT UE also transmits signals to the BS or intermediate UE, such as in step 3.

[0076] In transmitting and receiving signals including data, data is handled in specific processing units. For example, data in specific processing units is called a transport block (TB). In the following description, signals to be transmitted and received may be replaced with channels to be transmitted and received.

[0077] The following definitions exist for TBs for legacy UEs (UEs such as NR or LTE): A TB corresponds to a MAC PCU, which includes one or more MAC subheaders, MAC-CE, MAC SDU, and padding bits. The size of a TB (transport block size (TBS)) is aligned in length in bytes. In other words, a TBS has a length that is an integer multiple of 8 bits. Each PDSCH and / or PUSCH, except for PUSCHs that do not have a UL-SCH, carries one or more TBs.

[0078] Regarding TB for A-IoT UE, the following specifications are being considered in TR (Technical Report) 38.848 and other documents: - The maximum message size is approximately 1000 bits for TX and RX. - The above specification of the maximum message size does not mean that a single PHY channel should contain the message (e.g., a message of approximately 1000 bits). In other words, the design of the TBS is not clearly defined. - The data rate that a user can experience is 0.1 kbps at minimum and 5 kbps at maximum.

[0079] As described above, although TB ​​for A-IoT UE is under consideration, the specification of transmission data for A-IoT UE is not clear. In other words, the specification of data that A-IoT UE transmits to BS or intermediate UE, for example, the specification of TB to be transmitted, is not clear.

[0080] Furthermore, as described above, although TBs for A-IoT UEs are being considered, the definition of received data for A-IoT UEs is not clear. In other words, the definition of data that an A-IoT UE receives from a BS or an intermediate UE, for example, the definition of the received TB, is not clear.

[0081] For example, in the following description, one TB corresponds to one MAC PDU, as in a conventional UE. However, the present disclosure is not limited to this. For example, one TB may correspond to a portion of the MAC PDU. Furthermore, transmission or reception of one physical channel may not correspond to one TB, but may correspond to a portion of the MAC PDU. Hereinafter, transmission or reception of data will be described as transmission or reception of a MAC PDU, but this is not limiting. Furthermore, in this embodiment, for example, the data processing unit will be referred to as a "TB" and a "MAC PDU," but the present disclosure is not limited to these terms.

[0082] For example, the MAC PDU specification includes specifications for at least one of the following: - A method for knowing scheduling for the MAC PDU (e.g., a notification method) - A method for knowing the size of the MAC PDU (e.g., a notification method) - A MAC PDU conversion method (e.g., a method for converting between the MAC PDU and a format other than the MAC PDU) - A signal processing method for the MAC PDU (e.g., a channel coding method, a CRC attachment method) - The size of the MAC PDU

[0083] For example, if at least one of the above MAC PDU specifications is unclear, data with an appropriate structure cannot be exchanged, which may result in a discrepancy between the data sender and receiver, making it impossible to properly perform communication processing (e.g., conversion processing into MAC PDU at reception).

[0084] If the method for knowing the scheduling for the MAC PDU (e.g., the notification method) is unclear, for example, if it is unclear which MAC PDU data the data of a transmitted signal belongs to, a wireless communication device transmitting a signal may not be able to determine which MAC PDU data should be included in the transmitted signal. Furthermore, in this case, a wireless communication device receiving a signal may not be able to properly acquire the MAC PDU from the received signal. For example, if the method for notifying the scheduling for the MAC PDU is unclear, the wireless communication device may not be able to determine whether blocks of data included in multiple received signals belong to the same MAC PDU, and therefore may not be able to properly restore the MAC PDU from the blocks of data included in multiple signals.

[0085] For example, if the method for notifying the MAC PDU size is unclear, a wireless communication device transmitting a signal may not be able to grasp the size of the MAC PDU data to be included in the transmitted signal. Furthermore, in this case, a wireless communication device receiving a signal may not be able to properly obtain the MAC PDU from the received signal. For example, if the method for notifying the MAC PDU size is unclear, the wireless communication device may not be able to properly restore the MAC PDU from the data blocks included in the multiple signals, because it is unclear how many data blocks included in the multiple signals that need to be concatenated to restore the MAC PDU.

[0086] For example, if the MAC PDU conversion method is unclear, a wireless communication device transmitting a signal may not be able to convert the MAC PDU into the signal to be transmitted. In this case, a wireless communication device receiving a signal may not be able to properly retrieve the MAC PDU from the received signal. For example, if the conversion method between a MAC PDU and a format other than the MAC PDU is unclear, the wireless communication device may not be able to properly restore the MAC PDU from a block of data that is included in each of multiple signals and has a format other than the MAC PDU.

[0087] For example, if the signal processing method for a MAC PDU is unclear, a wireless communication device transmitting a signal may not be able to convert the MAC PDU into a signal to be transmitted. Furthermore, in this case, a wireless communication device receiving a signal may not be able to properly obtain a MAC PDU from the received signal. For example, if the channel coding and CRC attachment for a MAC PDU are unclear, a block obtained by concatenating blocks of data included in multiple received signals may not be able to be properly decoded for channel coding or to perform CRC error detection.

[0088] Therefore, in this embodiment, a definition for MAC PDU is proposed. By defining MAC PDU in accordance with one of the following proposals, it is possible to avoid discrepancies between the data transmitting side and the data receiving side, and to appropriately perform communication processing (e.g., conversion processing into MAC PDU at reception).

[0089] In the following description, TX corresponds to the transmission of the A-IoT UE, i.e., the A-IoT UE transmitting to the BS or intermediate UE, and RX corresponds to the reception of the A-IoT UE, i.e., the A-IoT UE receiving from the BS or intermediate UE.

[0090] Below, we will explain the proposals for MAC PDUs for TX (i.e., A-IoT UE transmitting) and RX (i.e., A-IoT UE receiving) respectively.

[0091] In the following, TX of one or more PHY channels / signals corresponds to TX of one MAC PDU. In other words, an A-IoT UE transmits one MAC PDU using one or more PHY channels or one or more signals. Note that a PHY channel (a physical layer channel) may be simply referred to as a channel. In the following description, a channel may be replaced with a signal (e.g., a physical layer signal).

[0092] In the following, the RX of one or more PHY channels / signals corresponds to the RX of one MAC PDU, i.e., the A-IoT UE receives one MAC PDU included in one or more PHY channels or one or more signals.

[0093] In the following description, the transmission of a certain MAC PDU (e.g., MAC PDU#X) corresponds to the transmission of a channel / signal including a portion of MAC PDU#X, and the reception of MAC PDU#X corresponds to the reception of a channel / signal including a portion of MAC PDU#X. Furthermore, a transmitted MAC PDU#X corresponds to a MAC PDU#X at least a portion of which is included in the transmitted signal, and a received MAC PDU#X corresponds to a MAC PDU#X at least a portion of which is included in the received signal.

[0094] <Regarding TX (A-IoT UE Transmission)> Figure 12 is a diagram showing an example of the configuration of a MAC PDU in TX. Figure 12 shows one MAC PDU divided into N blocks for transmission (N is an integer equal to or greater than 1). Hereinafter, as shown in Figure 12, the size of the MAC PDU (e.g., length, number of bits) may be written as L_total, the N blocks may be written as TX-1 to TX-N, and the sizes of the N blocks may be written as L_1 to L_N. Note that N and / or L_total may be different for each MAC PDU. L_1 to L_N may be the same. TX-1 to TX-N may correspond to indices that identify each block of the MAC PDU.

[0095] 12 may be referred to as segments or may be replaced with other names. In the following description, a block of a MAC PDU is a block that includes at least a portion of data of the MAC PDU.

[0096] The A-IoT UE divides (segments) the MAC PDU into N pieces, TX-1 to TX-N, and transmits signals each including TX-1 to TX-N to a receiving wireless communication device (e.g., a BS or an intermediate UE). The receiving wireless communication device receives each of the signals including TX-1 to TX-N and generates (or restores) a MAC PDU by concatenating the signals in the order of TX-1 to TX-N.

[0097] Proposals a to f regarding MAC PDU in TX will be explained below.

[0098] <Proposal a in TX: Method for Knowing MAC PDU Transmission Scheduling> Proposal a describes, as an example of a method for knowing the MAC PDU transmission scheduling, how a wireless communication device (e.g., at least one of an A-IoT UE, an intermediate UE, and a BS) knows the transmission scheduling of a new MAC PDU. In other words, this describes a method for knowing whether a MAC PDU block included in a certain channel / signal is a new MAC PDU block when the MAC PDU is transmitted over one or more channels / signals. Here, a case where a MAC PDU block included in a certain channel / signal is not a new MAC PDU block corresponds to a case where the block included in the certain channel / signal is the same MAC PDU block as a channel / signal transmitted earlier than the certain channel / signal.

[0099] The MAC PDU transmission scheduling may include scheduling information for transmitting the MAC PDU.

[0100] <Option A of Proposal a in TX> In Option A of the method of knowing transmission scheduling, an indicator for transmission scheduling is provided. Then, an indicator is indicated for each channel / signal scheduling by a toggling mechanism of the indicator. The indicator provided here is referred to as NPI (ner packet indicator). However, another name may be associated with the indicator provided here.

[0101] In Option A of Proposal a, when the NPI is toggled (e.g., when the NPI is switched), the toggled NPI indicates that a new MAC PDU is scheduled for transmission. When the NPI is toggled, the new MAC PDU may be scheduled for transmission regardless of whether the transmission of the MAC PDU before the NPI is toggled is complete. Note that if the transmission of the MAC PDU before the NPI is toggled is not complete, some of the MAC PDU before the NPI is toggled may be flushed. The word "flush" may be replaced with another term such as "discard" or "delete."

[0102] Also, in Option A of Proposal a, when the NPI is not toggled (e.g., when the NPI is not switched), the non-toggled NPI indicates that the same MAC PDU is scheduled as the MAC PDU transmitted before the non-toggled NPI.

[0103] In Option A of Proposal a, the NPI may be included in scheduling information (e.g., DCI, etc.) that schedules transmissions. For example, the A-IoT UE receives the scheduling information, references the NPI included in the scheduling information, determines whether to convert a block of data in each transmission of the A-IoT UE into a block of a new MAC PDU, and transmits a signal including the block of a MAC PDU based on the determination result.

[0104] In Option A of Proposal a, the NPI may be included in the transmitted channel / signal. For example, an A-IoT UE transmits a signal including at least a part of a MAC PDU and the NPI. Then, the receiving wireless communication device, a BS or an intermediate UE, refers to the NPI of the signal received from the A-IoT UE, determines whether the data block included in the signal is a new MAC PDU block, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0105] Figure 13 is a diagram showing option A of the method for determining transmission scheduling. The horizontal axis in Figure 13 represents the time axis. Figure 13 shows an example in which two MAC PDUs, MAC PDU #A and MAC PDU #B, are transmitted. TX-i (i is an integer between 1 and N) in Figure 13 may represent one block of MAC PDU, or may represent a channel / signal including one block of MAC PDU.

[0106] In the example of Figure 13, MAC PDU#B corresponds to a new MAC PDU. That is, TX-1 of MAC PDU#B is a new MAC PDU block for the previously transmitted MAC PDU block up to TX-N (MAC PDU#A in the example of Figure 13). 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 toggled.

[0107] In the example of Fig. 13, MAC PDU#A has been transmitted up to TX-N. That is, in the example of Fig. 13, transmission of MAC PDU#A is completed. Although different from the example of Fig. 13, when MAC PDU#A TX-1 through TX-k (k is an integer greater than or equal to 1 and less than N) are transmitted, transmission of MAC PDU#A is not completed. In this case, part of MAC PDU#A (for example, the block from TX-1 through TX-k) may be flushed.

[0108] 13 shows an example in which the NPI is toggled from 0 to 1, but it may also be toggled from 1 to 0. Furthermore, the NPI is not limited to being toggled between 0 and 1.

[0109] As in the above Option A, an NPI is provided to notify the MAC PDU transmission scheduling, so that a device that acquires the NPI can know the MAC PDU transmission scheduling (e.g., whether or not the MAC PDU to be transmitted is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the data receiving side, and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception).

[0110] <Option B of Proposal a in TX> In Option B of the method for knowing transmission scheduling, the NPI to be set to a specific value is indicated for each scheduling of a channel / signal. Alternatively, in Option B of the method for knowing transmission scheduling, the NPI to be set to a specific value is indicated only for a specific scheduling (scheduling of a specific channel / signal).

[0111] In Option B of Proposal a, when the NPI is a specific value (e.g., 1), the specific value of the NPI indicates that a new MAC PDU is scheduled for transmission. When the NPI is a specific value (e.g., 1), the new MAC PDU is scheduled for transmission regardless of whether the transmission of the MAC PDU before the NPI with the specific value (e.g., 1) has been completed. Note that if the transmission of the MAC PDU before the NPI with the specific value (e.g., 1) has not been completed, some of the MAC PDUs before the NPI with the specific value (e.g., 1) may be flushed.

[0112] Also, in Option B of Proposal a, if the NPI is not a specific value (e.g., not 1), the non-specific NPI indicates that the same MAC PDU as the MAC PDU transmitted before the non-specific NPI is scheduled for transmission. Alternatively, in Option B of Proposal a, if no NPI is provided, it indicates that the same MAC PDU as the MAC PDU transmitted before the non-specific NPI is scheduled for transmission.

[0113] In Option B of Proposal a, the NPI may be included in scheduling information for scheduling transmissions. For example, an A-IoT UE receives scheduling information, references the NPI included in the scheduling information, determines whether to convert a block of data in each transmission into a new MAC PDU block, and transmits a signal including the MAC PDU block based on the determination result.

[0114] In Option B of Proposal A, the NPI may be included in the transmitted channel / signal. For example, an A-IoT UE transmits a signal including at least a part of a MAC PDU and the NPI. Then, the receiving wireless communication device, a BS or an intermediate UE, refers to the NPI of the signal received from the A-IoT UE, determines whether the data block included in the signal is a new MAC PDU block, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0115] Fig. 14 is a diagram showing option B of the method for determining transmission scheduling. The horizontal axis in Fig. 14 represents time. Fig. 14 shows an example in which two MAC PDUs, MAC PDU#A and MAC PDU#B, are transmitted.

[0116] In the example of Figure 14, MAC PDU#B corresponds to a new MAC PDU. That is, TX-1 of MAC PDU#B is a new MAC PDU block compared to the previously transmitted MAC PDU block up to TX-N. In this case, the NPI of TX-1 of MAC PDU#B indicates a specific value. In the example of Figure 14, the NPIs of TX-1 to TX-N of MAC PDU#A are 0, and the NPI of TX-1 of MAC PDU#B is 1. Furthermore, the NPIs of TX-2 and onward of MAC PDU#B are 0.

[0117] In the example of FIG. 14, 1 is the specific value of the NPI, but the specific value may be a value other than 1.

[0118] As in the above-described Option B, an NPI is provided to notify the MAC PDU transmission scheduling, so that a device that acquires the NPI can know the MAC PDU transmission scheduling (e.g., whether or not the MAC PDU to be transmitted is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the data receiving side, and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception).

[0119] <Option C of Proposal a in TX> Option C of the method for determining transmission scheduling is a method that does not use a specific indication (for example, the above-mentioned NPI). Option C describes a method for determining scheduling based on the time of transmission time, a method for determining scheduling based on the time gap of transmission time, and a method for fixing the number of transmissions for one MAC PDU.

[0120] <Option C of Proposal a in TX: Time-based Method> In the time-based method, whether to continue the transmission of a MAC PDU#X or to transmit a new MAC PDU (e.g., a MAC PDU different from MAC PDU#X) is determined based on whether a specific time has elapsed since the transmission time of the transmission of a certain MAC PDU#X. For example, in the time-based method, a timer that measures the transmission time is used. The timer operates as follows. For example, the A-IoT UE operates the timer as follows to determine whether the scheduling is for a new MAC PDU.

[0121] (i) If a scheduling (e.g., DCI) is received while the timer is not running, the scheduling is for the transmission of a new MAC PDU, and in this case, the timer starts.

[0122] (ii) If a scheduling request (e.g., a DCI) is received while the timer is running, the scheduling request is for the transmission of the same MAC PDU as the MAC PDU in (i) above. Note that in this case, the timer may continue to run.

[0123] (iii) For example, when the transmission of a MAC PDU is completed (or when a scheduling for the transmission of a MAC PDU is received), the timer is stopped and initialized.

[0124] (iv) If a specific time has elapsed since the timer started while transmission of a MAC PDU is not completed, the timer is stopped and reset, and in this case, part or all of the MAC PDU is flushed.

[0125] Figure 15 is a diagram showing an example of the time-based method of option C of proposal a. The horizontal axis in Figure 15 represents the time axis. Figure 15 shows an example in which two MAC PDUs, MAC PDU#A and MAC PDU#B, are transmitted. In the example of Figure 15, MAC PDU#B corresponds to a new MAC PDU.

[0126] In the example of Fig. 15, the timer starts upon reception of the scheduling of TX-1 of MAC PDU#A. Then, upon completion of transmission of TX-N of MAC PDU#A (or upon completion of reception of the scheduling corresponding thereto), the timer stops and is initialized. After that, since TX-1 corresponding to the scheduled transmission is a scheduling for transmission of MAC PDU#B corresponding to a new MAC PDU, the timer starts upon reception of the scheduling of TX-1 of MAC PDU#B.

[0127] The timer may start, stop, or perform other operations at the timing of receiving the scheduling, or may start, stop, or perform other operations at the timing of transmitting data corresponding to the scheduling.

[0128] The BS or intermediate UE, which is the wireless communication device on the receiving side, may operate the timer. For example, when the BS or intermediate UE receives a signal including a data block from the A-IoT UE while the timer is not running, it determines that the block is a new MAC PDU block and starts the timer. Then, when the BS or intermediate UE receives a signal including a data block from the A-IoT UE while the timer is running, it determines that the block is the same MAC PDU block as the MAC PDU received up to that point. Then, when reception of the MAC PDU is complete, it stops and initializes the timer.

[0129] <Option C of Proposal a in TX: Time Gap Based Method> In Option C of Proposal a in TX, it is determined whether two transmissions are transmissions of the same MAC PDU or whether one transmission is a new MAC PDU based on the time interval between the scheduling of two transmissions or whether the time interval between two transmissions is greater than or equal to a certain time.

[0130] For example, if a certain time interval has elapsed after a transmission, the transmission scheduling received after the certain time interval has elapsed is for the transmission of a new MAC PDU.

[0131] If a specific time interval has not elapsed since a certain transmission, the scheduling received before the specific time interval has elapsed is a scheduling for transmitting the same MAC PDU as the transmission.

[0132] For example, the A-IoT UE determines that the scheduling received after a specific time interval has elapsed from the timing of receiving the scheduling corresponding to the last transmission of a certain MAC PDU#X is a scheduling for a new MAC PDU#Y.

[0133] Note that the determination may be made based on the transmission timing of the transmission corresponding to the scheduling, instead of the reception timing of the scheduling. For example, the A-IoT UE determines that the transmission after a specific time period has elapsed since the transmission timing of the last transmission of a certain MAC PDU#X is the transmission of a new MAC PDU#Y.

[0134] Alternatively, a BS or an intermediate UE, which is a wireless communication device on the receiving side that receives a MAC PDU, may make a determination based on a time gap. For example, the BS or the intermediate UE may determine that a reception of a MAC PDU #Y after a specific time interval has elapsed since the reception of a certain MAC PDU #X is a reception of a new MAC PDU #Y.

[0135] <Option C of Proposal a in TX: Method of Fixing the Number of Transmissions> One MAC PDU may be associated with a fixed number of transmissions. For example, one MAC PDU is always transmitted by X transmissions, where X may be an integer equal to or greater than 1. By associating one MAC PDU with a fixed number of transmissions, whether or not a new MAC PDU should be scheduled is determined based on the number of transmissions.

[0136] For example, an A-IoT UE that transmits a MAC PDU may perform transmission control so that one MAC PDU is transmitted at a fixed number of times. A BS or intermediate UE that receives a MAC PDU may perform reception control so that one MAC PDU is received at a fixed number of times. For example, the BS or intermediate UE may count the number of times a block is received, and when the number of times reaches the fixed number, determine that the next block to be received is a block of a new MAC PDU.

[0137] 16 shows an example in which one MAC PDU is associated with a fixed number of transmissions. In this example, two MAC PDUs, MAC PDU#A and MAC PDU#B, are transmitted. Here, MAC PDU#B corresponds to an example of a new MAC PDU.

[0138] In the example of Fig. 16, one MAC PDU is transmitted a fixed number of times, 4. In the example of Fig. 16, after the block of MAC PDU#A is transmitted four times, the block of MAC PDU#B is transmitted four times.

[0139] The number of transmissions (i.e., the value of X) may be specified by a specification or may be set by the NW. Alternatively, the number of transmissions may be reported by the UE capability. Alternatively, the number of transmissions may be determined based on the UE capability. For example, the UE capability may report candidates for the number of transmissions that the UE can support, and the NW that receives the report may determine at least one of the candidates.

[0140] By using a method for notifying the transmission scheduling of a new MAC PDU without using an indicator, as in the above Option C, the wireless communication device can know the transmission scheduling of the MAC PDU (e.g., whether or not the MAC PDU to be transmitted is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the receiving side and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception). Furthermore, since an indicator is not required, signaling overhead can be reduced.

[0141] <Option D of Proposal a in TX> In Option D of Proposal a in TX, an index may be indicated for each channel / signal scheduling. Here, the index used for the indication is written as PI (Packet Index). However, the index used for the indication here may be associated with another name.

[0142] For example, when a new MAC PDU is scheduled for transmission, the PI is incremented by 1. A range of PI values ​​is defined, and the PI is incremented within the defined range. The defined range may be, for example, 1 to k (k is an integer equal to or greater than 1).

[0143] In Option D of Proposal a, the PI may be included in scheduling information for scheduling transmissions. For example, an A-IoT UE receives scheduling information, references the PI included in the scheduling information, determines whether to convert a block of data in each transmission into a new MAC PDU block, and transmits a signal including the MAC PDU block based on the determination result.

[0144] In Option D of Proposal a, the PI may be included in the transmitted channel / signal. For example, an A-IoT UE transmits a signal including at least a part of a MAC PDU and the PI. Then, the receiving wireless communication device, a BS or an intermediate UE, refers to the PI of the signal received from the A-IoT UE, determines whether the data block included in the signal is a new MAC PDU block, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0145] Fig. 17 is a diagram showing an example of instructions by PI, in which three MAC PDUs, MAC PDU#A, MAC PDU#B, and MAC PDU#C, are transmitted.

[0146] In the example of FIG. 17, PI=0 is indicated in the transmission scheduling of MAC PDU#A, PI=1 is indicated in the transmission scheduling of MAC PDU#B, and PI=1 is indicated in the transmission scheduling of MAC PDU#C.

[0147] PI may be an exact index (or actual index) or a modulo index, e.g., when modulo is used, the indexes are rotated as follows: 1, 2, 3, 4, 1, 2, 3, 4, etc. Alternatively, when modulo is used, the indexes are rotated as follows: 0, 1, 2, 3, 0, 1, 2, 3, etc.

[0148] If the PI is different from the previous transmission, the transmission corresponding to the PI is a transmission for scheduling a new MAC PDU, and if the transmission of the MAC PDU corresponding to the previous transmission has not been completed, the MAC PDU corresponding to the previous transmission may be flushed.

[0149] If the PI is the same as the previous transmission, the transmission corresponding to that PI is a transmission of the same MAC PDU as the previous transmission.

[0150] As in the above-described Option D, a PI is provided to notify the MAC PDU transmission scheduling, so that a device that acquires the PI can know the MAC PDU transmission scheduling (e.g., whether or not the MAC PDU to be transmitted is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the data receiving side, and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception).

[0151] <Proposal b in TX: Method for Knowing the MAC PDU Size> Proposal b describes a method for knowing the size of a MAC PDU (e.g., a scheduled MAC PDU). The method for knowing the MAC PDU size corresponds to the method for knowing L_total, which indicates the size of the entire MAC PDU.

[0152] <Option A of Proposal b in TX: Explicit Indication> When the size is explicitly indicated, the method of indication is not limited. For example, at least one of a control signal, a synchronization signal, and an arbitrary signal received before the transmission of a MAC PDU may indicate the exact size (or actual size) of the MAC PDU. Alternatively, a parameter of a higher layer (e.g., a pre-configured parameter or an RRC-configured parameter) may determine multiple size candidates, and at least one of a control signal, a synchronization signal, and an arbitrary signal received before the transmission of a MAC PDU may indicate one of the multiple candidates.

[0153] Option B of Proposal b in TX: Size is Predetermined A single size for the MAC PDU may be predetermined or defined by the specification, in which case a single size is always used.

[0154] Option C of Proposal b in TX: Implicit Determination: At the start of 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 provided resources. For example, the size of the MAC PDU may be determined based on at least one of the number of slots provided as resources, the number of transmissions, the number of available resource elements, etc.

[0155] By notifying the MAC PDU size as in the above proposal b, it is possible to avoid discrepancies between the data transmitting side and the receiving side, and to appropriately perform communication processing (e.g., conversion processing into a MAC PDU upon reception). For example, by notifying the MAC PDU size as in the above proposal b, a device transmitting a MAC PDU can appropriately segment the MAC PDU, and a device receiving a MAC PDU can appropriately generate a MAC PDU from one or more segments.

[0156] <Proposal c in TX: MAC PDU Conversion Method> Proposal c describes MAC PDU conversion methods, including segmentation, which divides a MAC PDU into blocks (e.g., segments), and concatenation, which concatenates blocks to generate a MAC PDU. For example, proposal c describes where and how segmentation / concatenation is performed, and how to know which segments are scheduled. For example, proposal c describes how to indicate the size of each block (L_1 to L_N shown in FIG. 12) obtained by MAC PDU segmentation. Proposal c also describes how to indicate the index of each block (TX-1 to TX-N shown in FIG. 12) obtained by MAC PDU segmentation. Proposal c also describes where and how segmentation / concatenation is performed.

[0157] <Option A of Proposal c in TX: Explicit Indication for Each Transmission> When explicit indication is performed, the method of indication is not limited. For example, at least one signal, such as a control signal, a synchronization signal, or an arbitrary signal received before each transmission, may indicate the exact size of the segmentation of the transmission and / or the index of the transmission. When indicating the index, the exact index may be indicated, or an index obtained by modulo arithmetic may be indicated. For example, when modulo arithmetic is applied, the index may be indicated by cyclic values ​​such as 1, 2, 3, 4, 1, 2, 3, 4, etc. Alternatively, when modulo arithmetic is applied, the index may be indicated by cyclic values ​​such as 0, 1, 2, 3, 0, 1, 2, 3, etc.

[0158] If the BS or intermediate UE detects a failure in reception of a channel / signal including a block of a MAC PDU transmitted by an A-IoT UE, the BS or intermediate UE may flush the received block of the MAC PDU, skip reception of the remaining MAC PDU, and report the reception failure to the A-IoT UE. The flushing of the received block, the skipping of reception of the remaining MAC PDU, and the reporting of the reception failure may all be performed, or at least one of them may be performed.

[0159] The detection of a reception failure may be performed based on the indicated index. For example, in a case where blocks with modulo arithmetic indexes 1, 2, 3, 4, 1, ... are received in order, if index 4 is detected after index 2 but index 3 is not, it is detected that the reception of the block corresponding to index 3 has failed.

[0160] Regarding the size of each segment, a parameter of a higher layer (e.g., a pre-configured parameter or an RRC-configured parameter) may determine multiple size candidates, and at least one signal, such as a control signal, a synchronization signal, or an arbitrary signal, received before transmission of the MAC PDU may indicate one of the multiple candidates.

[0161] Option B of Proposal c in TX: Pre-determined: For size, a single size of the segment may be pre-determined or defined by the specification, in which case a single size is always used.

[0162] <Option C of Proposal c in TX: Implicit Determination> Regarding the segment size, at the start of 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 total amount of provided resources. For example, the segment size may be determined based on at least one of the number of slots provided as resources, the number of transmissions, the number of available resource elements, etc. In this case, the sizes of each segment of the MAC PDU may be the same. That is, L_1 = L_2 = ... = L_N (= L_total divided by N).

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

[0164] Furthermore, for example, the size of a segment may be determined based on one of the methods in "<Proposal b for TX>" above. Then, the size of each segment is determined by equally dividing the MAC PDU size determined by proposal b into one or more segments. For example, regardless of differences in each transmission resource, the size of the MAC PDU is equally divided into one or more segments.

[0165] Regarding the segment index, the index does not need to be specified for each transmission. In this case, the transmission of the index next to the index of the most recent transmission is executed. For example, if the index of the most recent transmission is 3, the index of the next transmission will be 4. In other words, transmissions are executed in the order of the indexes. Alternatively, the indexes are associated with the order in which the transmissions were executed.

[0166] For a segment index, each transmission resource is associated with the index, and data of the index is transmitted on that resource, i.e., data of a segment with index #k is transmitted on the transmission resource associated with index #k.

[0167] <Option D of Proposal c in TX: Example in which Segmentation / Concatenation is Performed in PHY> Segmentation and / or concatenation may be performed by the physical layer. For example, segmentation and / or concatenation may be performed based on at least one of an instruction from the network, a configuration from the network, a definition in a specification, and an instruction from a higher layer.

[0168] The received data is concatenated at the physical layer, and the concatenated data is then shared (e.g., signaled or transmitted) to the MAC layer in the format of a MAC PDU.

[0169] For example, data to be transmitted (e.g., MAC PDUs or TBs) is shared from the MAC layer to the physical layer, where segmentation is performed on the MAC PDUs, and the resulting segments are then transmitted.

[0170] <Option E of Proposal c in TX: Example in which Segmentation / Concatenation is Performed in MAC> Segmentation and / or concatenation may be performed by the MAC layer. For example, segmentation and / or concatenation may be performed based on at least one of an instruction from the NW, a configuration from the NW, a definition in a specification, and an instruction from a higher layer.

[0171] The received data is shared to the MAC layer, and multiple received data are concatenated to form a MAC PDU. Note that the received data shared to the MAC layer may or may not have an index.

[0172] For example, a MAC PDU is segmented at the MAC layer, and each segment is then shared with the physical layer for each transmission resource.

[0173] As in the above proposal c, by knowing information (size, index) related to the MAC PDU conversion method, it is possible to avoid discrepancies between the data transmitting side and the receiving side, and to appropriately perform communication processing (e.g., conversion processing into a MAC PDU at reception). For example, by knowing information related to the MAC PDU conversion method as in the above proposal c, a device transmitting a MAC PDU can appropriately segment the MAC PDU, and a device receiving a MAC PDU can appropriately generate a MAC PDU from one or more segments.

[0174] <Proposal d in TX: Signal Processing Method for MAC PDU (Method of Channel Coding and CRC Attachment)> <Option A of Proposal d in TX: Execution for Each MAC PDU> In transmission, channel coding / CRC attachment is performed for each MAC PDU. In this case, in reception, after all segments for one MAC PDU are received, decoding for the channel coding is performed and error detection is performed based on the attached CRC.

[0175] <Option B of Proposal d in TX: Execution for Each Transmission> In transmission, channel coding / CRC attachment is performed for each transmission. In other words, in transmission, channel coding / CRC attachment is performed for each segment. In this case, in reception, after receiving each segment, the wireless communication device on the receiving side performs decoding for the channel coding for each segment, and performs error detection for each segment based on the CRC attached to each segment.

[0176] Note that CRC addition may be performed for each segment and for each MAC PDU. In the case where CRC addition is performed for each segment and for each MAC PDU, upon reception, error detection may be performed for each segment based on the CRC added for each segment, and after a segment for one MAC PDU is received, a CRC check may be performed on the MAC PDU.

[0177] Furthermore, channel coding may be performed for each segment and for each MAC PDU. In the case where channel coding is performed for each segment and for each MAC PDU, decoding may be performed for each segment upon reception, and after a segment for one MAC PDU is received, decoding for the MAC PDU may be performed.

[0178] Fig. 18 shows an example in which a CRC is added to each segment and each MAC PDU. Fig. 18 shows that a CRC is added to each block (TX-1 to TX-N) of the MAC PDU to be transmitted, and also to the MAC PDU.

[0179] <Option C of Proposal d in TX: Not Implemented> In Option C of Proposal d, channel coding and CRC attachment are not implemented. In this case, transmission may be performed on a sequence basis. Note that CRC attachment may be performed without channel coding. Alternatively, channel coding may be performed without CRC attachment.

[0180] As in the above proposal d, by knowing the specification of the signal processing method for MAC PDU, it is possible to avoid discrepancies between the data transmitting side and the receiving side, and to appropriately perform communication processing (e.g., conversion processing into MAC PDU at reception).For example, as in the above proposal c, by knowing the specification of the signal processing method for MAC PDU, a device transmitting a MAC PDU can appropriately segment the MAC PDU, and a device receiving a MAC PDU can appropriately generate a MAC PDU from one or more segments.

[0181] <TX Proposal e: MAC PDU size (e.g., whether to byte-align or not)> <TX Proposal e Option A: Transmission of each channel / signal is byte-aligned> For example, it is assumed that the result of dividing the MAC PDU size by the number of segments is byte-aligned. That is, it is assumed that the number of bits of the result of dividing the MAC PDU size by the number of segments is an integer multiple of 8 bits. That is, it is assumed that the number of bits of each segment is an integer multiple of 8 bits.

[0182] The size of each transmission may be calculated using a TBS determination mechanism, such as 8N-bit quantization, where quantization is performed using 8*N bits (N is an integer greater than or equal to 1), and / or a method for selecting a TBS from byte-aligned candidates.

[0183] <Option B of Proposal e in TX: Transmission of each channel / signal may or may not be byte-aligned> For example, if multiple segments for a MAC PDU have the same size, the result of dividing the MAC PDU size by the number of segments is assumed to be a positive integer. This positive integer value corresponds to the size (e.g., number of bits) of the segment. In this case, it is assumed that the number of bits resulting from dividing the MAC PDU size by the number of segments is not limited to an integer multiple of 8 bits.

[0184] The size of each transmission is calculated by a TBS determination mechanism, except that the TBS determination mechanism does not include 8N-bit quantization, where quantization is performed by 8*N bits (N is an integer greater than or equal to 1).

[0185] <Proposal f in TX: Regarding MAC PDU size> Any of the following may be applied to the data size. - The data size may be the same in the transmission of the A-IoT UE. In other words, the sizes of the transmitted segments may be the same. - The data size may be the same or different in the transmission of the A-IoT UE. In other words, the sizes of the transmitted segments may be the same or different.

[0186] The data size corresponds to the segment size, which may be the same as the proposal shown in <Proposal c in TX> above.

[0187] As described above, by specifying one of the MAC PDU proposals for TX, it is possible to avoid discrepancies between the data transmitting side and the data receiving side, and to appropriately perform communication processing (e.g., conversion processing into MAC PDU at reception).

[0188] <Regarding RX (A-IoT UE Reception)> Figure 19 is a diagram showing an example of the configuration of a MAC PDU in RX. Figure 19 shows one MAC PDU divided into N blocks for reception (N is an integer equal to or greater than 1). Hereinafter, as shown in Figure 19, the size of the MAC PDU (e.g., length, number of bits) may be written as L_total, the N blocks may be written as RX-1 to RX-N, and the sizes of the N blocks may be written as L_1 to L_N. Note that N and / or L_total may be different for each MAC PDU. L_1 to L_N may be the same. RX-1 to RX-N may correspond to indexes that identify each block of the MAC PDU.

[0189] 19 may be referred to as segments or may be replaced with other names. In the following description, a block of a MAC PDU is a block that includes at least a portion of data of the MAC PDU.

[0190] A transmitting wireless communication device (e.g., a BS or an intermediate UE) that transmits a signal to an A-IoT UE divides (segments) a MAC PDU into N pieces, RX-1 to RX-N, and transmits each signal including RX-1 to RX-N to the A-IoT UE. The A-IoT UE receives each signal including RX-1 to RX-N and generates (or restores) a MAC PDU by concatenating the signals in the order of RX-1 to RX-N.

[0191] Proposals a to f regarding MAC PDU in RX will be explained below.

[0192] <Proposal a in RX: Method for Knowing MAC PDU Transmission Scheduling> Proposal a describes, as an example of a method for knowing the MAC PDU reception scheduling, how a wireless communication device (e.g., at least one of an A-IoT UE, an intermediate UE, and a BS) knows the reception scheduling of a new MAC PDU. In other words, this describes a method for knowing whether a MAC PDU block included in a certain channel / signal is a new MAC PDU block when a MAC PDU is received over one or more channels / signals. Here, a case where a MAC PDU block included in a certain channel / signal is not a new MAC PDU block corresponds to a case where the block included in the certain channel / signal is the same MAC PDU block as a channel / signal received earlier than the certain channel / signal.

[0193] The MAC PDU reception scheduling may include scheduling information for receiving the MAC PDU.

[0194] <Option A of Proposal a in RX> In Option A of the method of knowing reception scheduling, an indicator for reception scheduling is provided. Then, an indicator is indicated for each channel / signal scheduling by a toggling mechanism of the indicator. The indicator provided here is referred to as NPI (ner packet indicator). However, another name may be associated with the indicator provided here.

[0195] In Option A of Proposal a, when the NPI is toggled (e.g., when the NPI is switched), the toggled NPI indicates that a new MAC PDU is scheduled for reception. When the NPI is toggled, the new MAC PDU may be scheduled for reception regardless of whether reception of the MAC PDU before the NPI is toggled is complete. Note that if reception of the MAC PDU before the NPI is toggled is not complete, some of the MAC PDUs before the NPI is toggled may be flushed. The word "flush" may be replaced with another term such as "discard" or "delete."

[0196] Also, in Option A of Proposal a, when the NPI is not toggled (e.g., when the NPI is not switched), the non-toggled NPI indicates that the same MAC PDU is scheduled as the MAC PDU received before the non-toggled NPI.

[0197] In Option A of Proposal a, the NPI may be included in scheduling information (e.g., DCI, etc.) that schedules reception. For example, the A-IoT UE receives the scheduling information, references the NPI included in the scheduling information, determines whether each block of data received by the A-IoT UE is a block of a new MAC PDU, and concatenates the blocks to generate a MAC PDU based on the determination result.

[0198] In Option A of Proposal a, the NPI may be included in the received channel / signal. For example, a transmitting wireless communication device, such as a BS or an intermediate UE, transmits a signal including at least a part of a MAC PDU and the NPI. The A-IoT UE then refers to the NPI of the signal received from the transmitting wireless communication device to determine whether the data block included in the signal is a new MAC PDU block, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0199] Figure 20 is a diagram showing option A of the method for determining reception scheduling. The horizontal axis in Figure 20 represents the time axis. Figure 20 shows an example in which two MAC PDUs, MAC PDU #A and MAC PDU #B, are received. RX-i (i is an integer between 1 and N) in Figure 20 may represent one block of MAC PDU, or may represent a channel / signal including one block of MAC PDU.

[0200] In the example of Figure 20, MAC PDU#B corresponds to a new MAC PDU. That is, RX-1 of MAC PDU#B is a new MAC PDU block for the previously received MAC PDU block up to RX-N (MAC PDU#A in the example of Figure 20). 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 toggled.

[0201] In the example of Fig. 20, MAC PDU#A up to RX-N has been received. That is, in the example of Fig. 20, reception of MAC PDU#A is complete. Unlike the example of Fig. 20, if MAC PDU#A from RX-1 to RX-k (k is an integer greater than or equal to 1 and less than N) has been received, reception of MAC PDU#A is not complete. In this case, part of MAC PDU#A (for example, the block from RX-1 to RX-k) may be flushed.

[0202] 20 shows an example in which the NPI is toggled from 0 to 1, but it may also be toggled from 1 to 0. Furthermore, the NPI is not limited to being toggled between 0 and 1.

[0203] As in the above Option A, an NPI is provided to notify the MAC PDU reception scheduling, so that a device that acquires the NPI can know the MAC PDU reception scheduling (e.g., whether or not the received MAC PDU is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the data receiving side, and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception).

[0204] <Option B of Proposal a in RX> In Option B of the method for knowing the reception scheduling, the NPI to be set to a specific value is indicated for each scheduling of a channel / signal, or in Option B of the method for knowing the reception scheduling, the NPI to be set to a specific value is indicated only for a specific scheduling (scheduling of a specific channel / signal).

[0205] In Option B of Proposal a, when the NPI is a specific value (e.g., 1), the specific value indicates that a new MAC PDU is scheduled for reception. When the NPI is a specific value (e.g., 1), the new MAC PDU is scheduled for reception regardless of whether reception of the MAC PDUs prior to the NPI having the specific value (e.g., 1) has been completed. Note that if reception of the MAC PDUs prior to the NPI having the specific value (e.g., 1) has not been completed, some of the MAC PDUs prior to the NPI having the specific value (e.g., 1) may be flushed.

[0206] Also, in Option B of Proposal a, if the NPI is not a specific value (e.g., not 1), the non-specific NPI indicates that the same MAC PDU as the MAC PDU received before the non-specific NPI is scheduled for reception. Alternatively, in Option B of Proposal a, if no NPI is provided, it indicates that the same MAC PDU as the MAC PDU transmitted before the state in which no NPI is provided is scheduled for reception.

[0207] In Option B of Proposal a, the NPI may be included in the scheduling information for scheduling reception. For example, the A-IoT UE receives the scheduling information, refers to the NPI included in the scheduling information, determines whether each received data block is a new MAC PDU block, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0208] In Option B of Proposal A, the NPI may be included in the received channel / signal. For example, a transmitting wireless communication device, such as a BS or an intermediate UE, transmits a signal including at least a portion of a MAC PDU and the NPI. The A-IoT UE then refers to the NPI of the signal received from the transmitting wireless communication device to determine whether the data block included in the signal is a new MAC PDU block, and concatenates the blocks based on the determination result to generate a MAC PDU.

[0209] Fig. 21 is a diagram showing option B of the method for determining reception scheduling. The horizontal axis in Fig. 21 represents time. Fig. 21 shows an example in which two MAC PDUs, MAC PDU #A and MAC PDU #B, are received.

[0210] In the example of Figure 21, MAC PDU#B corresponds to a new MAC PDU. That is, RX-1 of MAC PDU#B is a new MAC PDU block relative to the previously received MAC PDU blocks up to RX-N. In this case, the NPI of RX-1 of MAC PDU#B indicates a specific value. In the example of Figure 21, the NPIs of RX-1 to RX-N of MAC PDU#A are 0, and the NPI of RX-1 of MAC PDU#B is 1. Furthermore, the NPIs of RX-2 and onward of MAC PDU#B are 0.

[0211] In the example of FIG. 21, 1 is the specific value of the NPI, but the specific value may be a value other than 1.

[0212] As in the above-mentioned Option B, an NPI is provided to notify the MAC PDU reception scheduling, so that a device that acquires the NPI can know the MAC PDU reception scheduling (e.g., whether or not the received MAC PDU is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the data receiving side, and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception).

[0213] <Option C of Proposal a in RX> Option C of the method for determining reception scheduling is a method that does not use a specific indication (for example, the above-mentioned NPI). Option C describes a method for determining scheduling based on the time base of reception time, a method for determining scheduling based on the time gap of reception time, and a method for fixing the number of receptions for transmitting one MAC PDU.

[0214] <Option C of Proposal a in RX: Time-based Method> In the time-based method, based on whether a specific time has elapsed since the reception of a certain MAC PDU#X, it is determined whether to continue receiving MAC PDU#X or to receive a new MAC PDU (e.g., a MAC PDU different from MAC PDU#X). For example, in the time-based method, a timer that measures the reception time is used. The timer operates as follows. For example, the A-IoT UE operates the timer as follows to determine whether the scheduling is for a new MAC PDU.

[0215] (i) If a scheduling (e.g., DCI) is received while the timer is not running, the scheduling is for receiving a new MAC PDU, and in this case, the timer starts.

[0216] (ii) If a scheduling request (e.g., a DCI) is received while the timer is running, the scheduling request is for receiving the same MAC PDU as the MAC PDU in (i) above. Note that in this case, the timer may continue to run.

[0217] (iii) For example, when reception of a MAC PDU is completed (or when a scheduling for completion of reception of a MAC PDU is received), the timer is stopped and initialized.

[0218] (iv) If a specific time has elapsed since the timer started while reception of a MAC PDU is not complete, the timer is stopped and then reset, and part or all of the MAC PDU is flushed.

[0219] Figure 22 is a diagram showing an example of the time-based method of Option C of Proposal a. The horizontal axis in Figure 22 represents the time axis. Figure 22 shows an example in which two MAC PDUs, MAC PDU#A and MAC PDU#B, are transmitted. In the example of Figure 22, MAC PDU#B corresponds to a new MAC PDU.

[0220] In the example of Fig. 22, the timer starts when scheduling of RX-1 for MAC PDU#A is received. Then, when reception of RX-N for MAC PDU#A is completed (or when reception of the corresponding scheduling is completed), the timer stops and is initialized. After that, since RX-1 corresponding to the scheduled reception is scheduled for reception of MAC PDU#B corresponding to a new MAC PDU, the timer starts when scheduling of RX-1 for MAC PDU#B is received.

[0221] The timer may start, stop, or perform other operations at the timing of receiving the scheduling, or may start, stop, or perform other operations at the timing of receiving the scheduling.

[0222] Note that the BS or intermediate UE, which is the transmitting wireless communication device, may operate the timer. For example, when the BS or intermediate UE transmits a scheduling to transmit a signal including a data block to the A-IoT UE while the timer is not running, the BS or intermediate UE determines that the block is a new MAC PDU block and starts the timer. Then, when the BS or intermediate UE transmits a scheduling to transmit a signal including a data block to the A-IoT UE while the timer is running, the BS or intermediate UE determines that the block is the same MAC PDU block as the MAC PDU received up to that point. Then, when the transmission of the MAC PDU is completed, the timer is stopped and initialized.

[0223] <Option C of Proposal a in RX: Time Gap Based Method> In Option C of Proposal a in RX, it is determined whether two receptions are of the same MAC PDU or whether one reception is of a new MAC PDU based on the time interval between the scheduling of two receptions or whether the time interval between two receptions is greater than or equal to a specific time.

[0224] For example, if a specific time interval has elapsed after a certain reception, the scheduling of the reception after the specific time interval has elapsed is for the reception of a new MAC PDU.

[0225] If a specific time interval has not elapsed since a certain reception, scheduling for reception before the specific time interval has elapsed is scheduling for receiving the same MAC PDU as the reception.

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

[0227] Note that the determination may be based on the reception timing of a reception corresponding to the scheduling, instead of the reception timing of the scheduling. For example, the A-IoT UE determines that a reception after a specific time period has elapsed since the reception timing of the last reception of a certain MAC PDU #X is a reception of a new MAC PDU #Y.

[0228] Alternatively, a BS or an intermediate UE, which is a wireless communication device on the transmitting side that transmits a MAC PDU, may make a determination based on a time gap. For example, the BS or the intermediate UE may determine that a transmission after a specific time interval has elapsed since the transmission timing of a certain MAC PDU #X is a transmission of a new MAC PDU #Y.

[0229] <Option C of Proposal a in RX: Method of Fixing the Number of Receptions> One MAC PDU may be associated with a fixed number of receptions. For example, one MAC PDU is always received by X receptions, where X may be an integer equal to or greater than 1. By associating one MAC PDU with a fixed number of receptions, whether or not a new MAC PDU should be scheduled is determined based on the number of receptions.

[0230] For example, an A-IoT UE that receives a MAC PDU may perform transmission control so as to receive one MAC PDU at a fixed number of times. Also, a BS or intermediate UE that transmits a MAC PDU may perform transmission control so as to transmit one MAC PDU at a fixed number of times. For example, the BS or intermediate UE may count the number of times a block is transmitted, and when the number of transmissions reaches the fixed number, determine that the next block to be transmitted is a block of a new MAC PDU.

[0231] 23 shows an example in which one MAC PDU is associated with a fixed number of receptions. In this example, two MAC PDUs, MAC PDU#A and MAC PDU#B, are received. Here, MAC PDU#B corresponds to an example of a new MAC PDU.

[0232] In the example of Fig. 23, one MAC PDU is received a fixed number of times, i.e., four times, after the block of MAC PDU#A is received four times, the block of MAC PDU#B is received four times.

[0233] The number of receptions (i.e., the value of X) may be specified by a specification or may be set by the network. Alternatively, the number of receptions may be reported by the UE capability. Alternatively, the number of receptions may be determined based on the UE capability. For example, the UE capability may report candidates for the number of receptions that the UE can support, and the network that receives the report may determine at least one of the candidates.

[0234] By using a method for notifying the transmission scheduling of a new MAC PDU without using an indicator, as in the above Option C, the wireless communication device can know the transmission scheduling of the MAC PDU (e.g., whether or not the MAC PDU to be transmitted is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the receiving side and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception). Furthermore, since an indicator is not required, signaling overhead can be reduced.

[0235] <Option D of Proposal a in RX> In Option D of Proposal a in RX, an index may be indicated for each channel / signal scheduling. Here, the index used for the indication is written as PI (Packet Index). However, the index used for the indication here may be associated with another name.

[0236] For example, when a new MAC PDU is scheduled for reception, the PI is incremented by 1. A range of PI values ​​is defined, and the PI is incremented within the defined range. The defined range may be, for example, 1 to k (k is an integer equal to or greater than 1).

[0237] In Option D of Proposal a, the PI may be included in scheduling information (e.g., DCI, etc.) that schedules reception. For example, the A-IoT UE receives the scheduling information, references the PI included in the scheduling information, determines whether each block of data received by the A-IoT UE is a block of a new MAC PDU, and based on the determination result, concatenates the blocks to generate a MAC PDU.

[0238] In Option D of Proposal a, the PI may be included in the received channel / signal. For example, a transmitting wireless communication device, such as a BS or an intermediate UE, transmits a signal including at least a portion of a MAC PDU and the PI. The A-IoT UE then refers to the PI in the signal received from the transmitting wireless communication device to determine whether a block of data included 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.

[0239] Fig. 24 is a diagram showing an example of indication by PI, in which three MAC PDUs, MAC PDU#A, MAC PDU#B, and MAC PDU#C, are received.

[0240] In the example of FIG. 24, PI=0 is indicated in the reception scheduling of MAC PDU#A, PI=1 is indicated in the reception scheduling of MAC PDU#B, and PI=1 is indicated in the reception scheduling of MAC PDU#C.

[0241] PI may be an exact index (or actual index) or a modulo index, e.g., when modulo is used, the indexes are rotated as follows: 1, 2, 3, 4, 1, 2, 3, 4, etc. Alternatively, when modulo is used, the indexes are rotated as follows: 0, 1, 2, 3, 0, 1, 2, 3, etc.

[0242] If the PI is different from the previous reception, the reception corresponding to the PI is the reception of a new MAC PDU for scheduling. Note that if the reception of the MAC PDU corresponding to the previous reception is not completed, the MAC PDU corresponding to the previous reception may be flushed.

[0243] If the PI is the same as the previous reception, the reception corresponding to that PI is the same MAC PDU as the previous reception.

[0244] As in the above-described Option D, a PI is provided to notify the MAC PDU reception scheduling, so that a device that acquires the PI can know the MAC PDU reception scheduling (e.g., whether or not the received MAC PDU is a new MAC PDU), thereby preventing discrepancies from occurring between the data transmitting side and the data receiving side, and enabling appropriate communication processing (e.g., conversion processing into a MAC PDU upon reception).

[0245] <Proposal b in RX: Method for Knowing the MAC PDU Size> Proposal b describes a method for knowing the size of a MAC PDU (e.g., a scheduled MAC PDU). The method for knowing the MAC PDU size corresponds to the method for knowing L_total, which indicates the size of the entire MAC PDU.

[0246] <Option A of Proposal b in RX: Explicit Indication> When explicit size indication is performed, the method of indication is not limited. For example, at least one signal, such as a control signal, a synchronization signal, or an arbitrary signal received before reception of a MAC PDU, may indicate the exact size (or actual size) of the MAC PDU. Alternatively, a parameter of a higher layer (e.g., a pre-configured parameter or an RRC-configured parameter) may determine multiple size candidates, and at least one signal, such as a control signal, a synchronization signal, or an arbitrary signal received before reception of a MAC PDU, may indicate one of the multiple candidates.

[0247] Option B of Proposal b in RX: Size is Predetermined A single size for the MAC PDU may be predetermined or defined by the specification, in which case a single size is always used.

[0248] Option C of Proposal b in RX: Implicit Determination: At the start of scheduling for reception of 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 provided resources. For example, the size of the MAC PDU may be determined based on at least one of the number of slots provided as resources, the number of receptions, the number of available resource elements, etc.

[0249] By notifying the MAC PDU size as in the above proposal b, it is possible to avoid discrepancies between the data transmitting side and the receiving side, and to appropriately perform communication processing (e.g., conversion processing into a MAC PDU upon reception). For example, by notifying the MAC PDU size as in the above proposal b, a device transmitting a MAC PDU can appropriately segment the MAC PDU, and a device receiving a MAC PDU can appropriately generate a MAC PDU from one or more segments.

[0250] <Proposal c in RX: MAC PDU Conversion Method> Proposal c describes MAC PDU conversion methods, including segmentation, which divides a MAC PDU into blocks (e.g., segments), and concatenation, which concatenates blocks to generate a MAC PDU. For example, proposal c describes where and how segmentation / concatenation are performed, and how to know which segments are scheduled. For example, proposal c describes how to indicate the size of each block (L_1 to L_N shown in FIG. 19) obtained by MAC PDU segmentation. Proposal c also describes how to indicate the index of each block (RX-1 to RX-N shown in FIG. 19) obtained by MAC PDU segmentation. Proposal c also describes where and how segmentation / concatenation are performed.

[0251] <Option A of Proposal c in RX: Explicit Indication for Each Reception> When explicit indication is performed, the method of indication is not limited. For example, at least one signal, such as a control signal, a synchronization signal, or an arbitrary signal received before each reception, may indicate the exact size of the segmentation for that reception and / or the index for that reception. When indicating the index, the exact index may be indicated, or an index obtained by modulo arithmetic may be indicated. For example, when modulo arithmetic is performed, the index may be indicated by cyclic values ​​such as 1, 2, 3, 4, 1, 2, 3, 4, etc. Alternatively, when modulo arithmetic is performed, the index may be indicated by cyclic values ​​such as 0, 1, 2, 3, 0, 1, 2, 3, etc.

[0252] If the A-IoT UE detects a failure in reception of a channel / signal including a block of a MAC PDU transmitted by a BS or an intermediate UE, the A-IoT UE may flush the received block of the MAC PDU, skip reception of the remaining MAC PDU, and report the reception failure to the BS or the intermediate UE. The flushing of the received block, the skipping of reception of the remaining MAC PDU, and the reporting of the reception failure may all be performed, or at least one of them may be performed.

[0253] The detection of a reception failure may be performed based on the indicated index. For example, in a case where blocks with modulo arithmetic indexes 1, 2, 3, 4, 1, ... are received in order, if index 4 is detected after index 2 but index 3 is not detected, it is detected that reception of the block corresponding to index 3 has failed.

[0254] Regarding the size of each segment, a parameter of a higher layer (e.g., a pre-configured parameter or an RRC-configured parameter) may determine multiple size candidates, and at least one signal, such as a control signal, a synchronization signal, or an arbitrary signal, received before reception of the MAC PDU may indicate one of the multiple candidates.

[0255] Option B of proposal c in RX: Pre-determined: For size, a single size of the segments may be pre-determined or defined by the specification, in which case a single size is always used.

[0256] <Option C of Proposal c in RX: Implicit Determination> Regarding the segment size, at the start of scheduling for reception of 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 provided resources. For example, the segment size may be determined based on at least one of the number of slots provided as resources, the number of receptions, the number of available resource elements, etc. In this case, the sizes of each segment of the MAC PDU may be the same. That is, L_1 = L_2 = ... = L_N (= L_total divided by N).

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

[0258] Furthermore, for example, regarding the size of a segment, the size of a transmission of a certain MAC PDU may be determined based on any of the methods in the above "<Proposal b in RX>." Then, the size of the MAC PDU determined by proposal b is evenly divided into one or more segments. For example, regardless of differences in each reception resource, the size of the MAC PDU is evenly divided into one or more segments.

[0259] Regarding the segment index, the index does not need to be specified for each reception. In this case, reception of the index next to the most recently received index is executed. For example, if the most recently received index is 3, the next received index will be 4. In other words, reception is executed in the order of the indexes. Alternatively, the indexes are associated with the order in which reception was executed.

[0260] For a segment index, each receiving resource is associated with the index, and data of the index is received on that resource. That is, data of a segment with index #k is received on the transmission resource associated with index #k.

[0261] <Option D of Proposal c in RX: Example in which Segmentation / Concatenation is Performed in PHY> Segmentation and / or concatenation may be performed by the physical layer. For example, segmentation and / or concatenation may be performed based on at least one of an instruction from the network, a configuration from the network, a definition in a specification, and an instruction from a higher layer.

[0262] The received data is concatenated at the physical layer, and the concatenated data is then shared to the MAC layer in the format of a MAC PDU.

[0263] For example, data to be transmitted (e.g., MAC PDUs or TBs) is shared from the MAC layer to the physical layer, where segmentation is performed on the MAC PDUs, and the resulting segments are then transmitted.

[0264] <Option E of Proposal c in RX: Example in which Segmentation / Concatenation is Performed in MAC> Segmentation and / or concatenation may be performed by the MAC layer. For example, segmentation and / or concatenation may be performed based on at least one of an instruction from the NW, a configuration from the NW, a definition in a specification, and an instruction from a higher layer.

[0265] The received data is shared to the MAC layer, and multiple received data are concatenated to form a MAC PDU. Note that the received data shared to the MAC layer may or may not have an index.

[0266] For example, a MAC PDU is segmented at the MAC layer, and each segment is then shared with the physical layer for each transmission resource.

[0267] As in the above proposal c, by knowing information (size, index) related to the MAC PDU conversion method, it is possible to avoid discrepancies between the data transmitting side and the receiving side, and to appropriately perform communication processing (e.g., conversion processing into a MAC PDU at reception). For example, by knowing information related to the MAC PDU conversion method as in the above proposal c, a device transmitting a MAC PDU can appropriately segment the MAC PDU, and a device receiving a MAC PDU can appropriately generate a MAC PDU from one or more segments.

[0268] <Proposal d in RX: Signal Processing Method for MAC PDU (Method of Channel Coding and CRC Attachment)> <Option A of Proposal d in RX: Execution for Each MAC PDU> In transmission, channel coding / CRC attachment is performed for each MAC PDU. In this case, in reception, after all segments for one MAC PDU are received, decoding for the channel coding is performed and error detection is performed based on the attached CRC.

[0269] <Option B of Proposal d in RX: Execution for Each Transmission> In transmission, channel coding / CRC attachment is performed for each transmission. In other words, in transmission, channel coding / CRC attachment is performed for each segment. In this case, in reception, after receiving each segment, the wireless communication device on the receiving side performs decoding for the channel coding for each segment, and performs error detection for each segment based on the CRC attached to each segment.

[0270] Note that CRC addition may be performed for each segment and for each MAC PDU. In the case where CRC addition is performed for each segment and for each MAC PDU, upon reception, error detection may be performed for each segment based on the CRC added for each segment, and after a segment for one MAC PDU is received, a CRC check may be performed on the MAC PDU.

[0271] Furthermore, channel coding may be performed for each segment and for each MAC PDU. In the case where channel coding is performed for each segment and for each MAC PDU, decoding may be performed for each segment upon reception, and after a segment for one MAC PDU is received, decoding for the MAC PDU may be performed.

[0272] 25 is a diagram showing an example in which a CRC is added to each segment and each MAC PDU, in which a CRC is added to each block (RX-1 to RX-N) of the MAC PDU to be transmitted, and also to the MAC PDU.

[0273] <Option C of Proposal d in RX: Not Implemented> In Option C of Proposal d, channel coding and CRC attachment are not implemented. In this case, transmission may be performed on a sequence basis. Note that CRC attachment may be performed without channel coding. Alternatively, channel coding may be performed without CRC attachment.

[0274] As in the above proposal d, by knowing the specification of the signal processing method for MAC PDU, it is possible to avoid discrepancies between the data transmitting side and the receiving side, and to appropriately perform communication processing (e.g., conversion processing into MAC PDU at reception).For example, as in the above proposal c, by knowing the specification of the signal processing method for MAC PDU, a device transmitting a MAC PDU can appropriately segment the MAC PDU, and a device receiving a MAC PDU can appropriately generate a MAC PDU from one or more segments.

[0275] <Proposal e in RX: MAC PDU size (e.g., whether to byte-align or not)> <Option A of proposal e in RX: Transmission of each channel / signal is byte-aligned> For example, it is assumed that the result of dividing the MAC PDU size by the number of segments is byte-aligned. That is, it is assumed that the number of bits of the result of dividing the MAC PDU size by the number of segments is an integer multiple of 8 bits. That is, it is assumed that the number of bits of each segment is an integer multiple of 8 bits.

[0276] The size of each transmission may be calculated using a TBS determination mechanism, such as 8N-bit quantization, where quantization is performed using 8*N bits (N is an integer greater than or equal to 1), and / or a method for selecting a TBS from byte-aligned candidates.

[0277] <Option B of Proposal e in RX: Transmission of each channel / signal may or may not be byte-aligned> For example, if multiple segments for a MAC PDU have the same size, the result of dividing the MAC PDU size by the number of segments is assumed to be a positive integer. This positive integer value corresponds to the size (e.g., number of bits) of the segment. In this case, it is assumed that the number of bits resulting from dividing the MAC PDU size by the number of segments is not limited to an integer multiple of 8 bits.

[0278] The size of each transmission is calculated by a TBS determination mechanism, except that the TBS determination mechanism does not include 8N-bit quantization, where quantization is performed by 8*N bits (N is an integer greater than or equal to 1).

[0279] <Proposal f in RX: Regarding MAC PDU size> Any of the following may be applied to the data size. - The data size may be the same among the receptions of the A-IoT UE. In other words, the sizes of the transmitted segments may be the same. - The data size may be the same or different among the receptions of the A-IoT UE. In other words, the sizes of the transmitted segments may be the same or different.

[0280] The data size corresponds to the size of the segment, which may be the same as the proposal shown in <Proposal c in RX> above.

[0281] As described above, by specifying one of the MAC PDU proposals for RX, it is possible to avoid discrepancies between the data transmitting side and the data receiving side, and to appropriately perform communication processing (e.g., conversion processing into MAC PDU at reception).

[0282] In the above description, the specifications for TX (transmission of the A-IoT UE) and RX (reception of the A-IoT UE) may be the same or different. For example, the method for notifying the transmission scheduling of a new MAC PDU in TX and the method for notifying the reception scheduling of a new MAC PDU in RX may be the same (e.g., the same option) or different (e.g., different options). Furthermore, an instruction for either TX or RX may be implicitly given based on an explicit instruction for the other.

[0283] In the above proposals, it has been described 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 the present disclosure is not limited to this. For example, the present disclosure may be applied to a case 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. Furthermore, for example, the present disclosure may be applied to a case 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.

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

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

[0286] The transmitter 101 transmits a downlink (DL) signal to the device 20. For example, the transmitter 101 transmits the DL signal under the control of the controller 103.

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

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

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

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

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

[0292] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

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

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

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

[0296] For example, the receiver 102 of the base station 10 (an example of a wireless communication device) receives one or more signals, each including one or more segments, from the device 20. The controller 103 then concatenates the one or more segments to generate a single data unit having a specific data processing unit.

[0297] For example, the control unit 103 of the base station 10 (an example of a wireless communication device) divides a single data unit having a specific data processing unit into one or more segments, and the transmission unit 101 transmits one or more signals, each including one or more segments, to the device 20.

[0298] <Device Configuration> Fig. 27 is a block diagram showing an example of the configuration 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, for example, the base station 10 wirelessly. The device 20 may be, for example, an A-IoT UE.

[0299] The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal under the control of the control unit 203.

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

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

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

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

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

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

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

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

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

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

[0310] For example, the control unit 203 of the device 20 divides a single data unit having a specific data processing unit into one or more segments, and the transmission unit 202 transmits one or more signals each including one or more segments.

[0311] Also, for example, the receiving unit 201 of the device 20 receives one or more signals, each including one or more segments. The control unit 203 concatenates the one or more segments to generate a single data unit having a specific data processing unit.

[0312] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

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

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

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

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

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

[0318] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0334] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0335] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0336] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

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

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

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

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

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

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

[0344] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0346] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

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

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

[0350] Fig. 29 shows an example configuration of a vehicle 2001. As shown in Fig. 29, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

[0352] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

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

[0355] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

[0357] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0358] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

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

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

[0361] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

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

[0363] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

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

[0365] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

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

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

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

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

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

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

[0372] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0373] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0374] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

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

[0376] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0377] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0378] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

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

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

[0381] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

[0383] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

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

[0385] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0386] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

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

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

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

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

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

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

Claims

1. 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 including the one or more segments.

2. The device of claim 1, wherein the transmitter transmits to and / or receives from a receiver of the signal information indicating whether the segment contains data of a new data unit.

3. The device of claim 1, wherein whether the segment contains data of a new data unit is determined based on a transmission time of a signal containing the segment.

4. The device of claim 1, wherein the size of the segments and / or the size of the data units is indicated explicitly or implicitly.

5. A wireless communication device comprising: a receiver that receives one or more signals, each of which includes one or more segments, from an Ambient Internet of Things (A-IoT) device; and a controller that concatenates the one or more segments to generate a single data unit having a specific data processing unit.

6. A wireless communication method in which an Ambient Internet of Things (A-IoT) device divides a single data unit having a specific data processing unit into one or more segments, and transmits one or more signals each containing the one or more segments.

Images