Improved SDT uplink transmission

Abstract

The disclosure inter alia relates to an apparatus. The apparatus may comprise at least one processor. The apparatus may further comprise at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus to perform receiving, from a network node, a frequency-domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the network node. The instructions, when executed by the at least one processor, may further cause the apparatus to perform performing the uplink transmission to the network node based on the received frequency-domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus. The instructions, when executed by the at least one processor, may further cause the apparatus to perform indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus.

Description

[0001] Improved SDT Uplink Transmission

[0002] TECHNOLOGICAL FIELD

[0003] Various example embodiments relate to wireless communication networks, in particular to performing an uplink transmission as part of a Small Data Transmission (SDT) procedure in such networks.

[0004] BACKGROUND

[0005] Small Data Transmission (SDT) is a wireless communication networks procedure used in particular for Internet of Things (loT) applications. The SDT procedure supports data transmission in an inactive communication state, e.g. without transitioning to a Radio Resource Control (RRC) connected state. Such data transmission may be beneficial in particular for infrequent and / or small data transmissions as they may occur in various loT applications. Examples of wireless communication networks comprise cellular networks such as networks operating according to Long Term Evolution (LTE), 5G or 6G radio access technology. 5G radio access technology may also be referred to as New Radio (NR) access technology. The 3rd Generation Partnership Project, 3GPP, develops standards for LTE, 5G / NR and 6G. One of the topics discussed within 3GPP is how to further improve SDT uplink transmission techniques, e.g. for loT applications in 6G.

[0006] SUMMARY OF SOME EXAMPLE EMBODIMENTS

[0007] In an SDT uplink transmission, it may be desirable for a user equipment (UE) to transmit an uplink report in as few transmissions as possible, in particular in a single transmission. In this way, the SDT procedure may be completed quickly, thereby reducing an amount of power consumed by the UE. In addition, by completing the SDT procedure with fewer transmissions, potential excess network resources may be saved.

[0008] However, a size of the data transmission may not be known to the network beforehand. In particular, while a size of an loT data transmission may be relatively small, this size may vary. As a result, the network may over allocate or under allocate network resources for the data transmission. While an under allocation may result in multiple transmissions being required to transmit the data, an over allocation may waste network resources and result in the transmission to last longer than necessary. As a consequence in both cases, the power consumption in particular of the UE may increase. Further, in particular in geographical areas and / or during times of relatively weak radio coverage a UE may be required to transmit a relatively large number of data packets for a given amount of data due to limitations inherent in uplink transmissions in such scenarios, which may likewise increase the power consumption of the UE.

[0009] In view of the above, certain embodiments of the disclosure may have the effect of enabling an improved SDT uplink transmission, e.g. for loT applications in 6G. In particular, certain embodiments of the disclosure may reduce, e.g. minimize, a number of uplink transmissions required for transmitting a certain amount of data, in particular to a single transmission, thereby saving network resources and reducing, e.g. minimizing, an amount of power consumed by an apparatus performing the uplink transmission. According to a first example aspect, there is disclosed an apparatus. The apparatus may comprise at least one processor. The apparatus may further comprise at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus to perform receiving, from a network node, a frequency-domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the network node. The instructions, when executed by the at least one processor, may further cause the apparatus to perform performing the uplink transmission to the network node based on the received frequency-domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus. The instructions, when executed by the at least one processor, may further cause the apparatus to perform indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus.

[0010] The apparatus according to the first example aspect may be or may comprise a user equipment (UE).

[0011] According to a second example aspect, there is disclosed an apparatus. The apparatus may comprise at least one processor. The apparatus may further comprise at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus to perform transmitting, to a user equipment, a frequency-domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the apparatus. The instructions, when executed by the at least one processor, may further cause the apparatus to perform receiving the uplink transmission from the user equipment. The instructions, when executed by the at least one processor, may further cause the apparatus to perform receiving, from the user equipment, an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed. The instructions, when executed by the at least one processor, may further cause the apparatus to perform, based on the indication, determining at least one of: a duration of the uplink transmission; a length of the uplink transmission; an end of the uplink transmission; a number of symbols of the uplink transmission; a number of slots of the uplink transmission; a number of Transmission Time Intervals, TTIs, of the uplink transmission; or a Transport Block Size, TBS, of the uplink transmission.

[0012] The apparatus according to the second example aspect may be or may comprise a network entity such as, e.g., a network node.

[0013] Any of the disclosed devices (e.g., the apparatus according to the first example aspect and / or the apparatus according to the second example aspect) may be a stationary device or a mobile device.

[0014] A user equipment (an example of the apparatus according to the first example aspect) may in particular be a terminal device, e.g. a mobile device such as a smartphone, a tablet, a wearable, a smartwatch, a low power device, an loT device, an IIoT device, a vehicle, a truck, a drone, an airplane, or the like. A user equipment may in particular be capable of communicating with (transmitting and / or receiving signals and / or data to / from) one or more other user equipments and / or with one or more network nodes, such as a base station of a wireless communication network. Generally, a user equipment may be any device enabled for communication with a wireless communication network and / or with another user equipment. A network node (an example of the apparatus according to the second example aspect) may be understood as a wireless communication station installed at a fixed or mobile location and may in particular be or comprise an entity of a radio access network of a wireless communication system. For instance, a network node may be, comprise, or be part of a base station of a wireless communication network of any generation (e.g. a gNB, eNodeB, NodeB, BTS or the like) of a 3 GPP standard. Generally, a network node may be or comprise a hardware or software component implementing a certain functionality. In an example, a network node may be an entity as defined by 3 GPP 5G or NR standard (also referred to as gNB). Accordingly, while a network node may be understood to be implemented in or be a single device or module, a network node may also be implemented across or comprise multiple devices or modules. As such, a network node may in particular be implemented in or be a stationary device. Multiple network nodes may in particular establish a wireless communication system or network, which may in particular be an NR or 5G system (5GS) or any other wireless communications system defined by a past or future standard, in particular successors of the present 3 GPP standards. Network nodes may be capable of being in direct and / or indirect communication with user equipment.

[0015] According to each of the example aspects, a respective method is also disclosed.

[0016] Thus, according to the first example aspect, there is disclosed a method performed by an apparatus. The method may comprise receiving, from a network node, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the network node. The method may further comprise performing the uplink transmission to the network node based on the received frequency-domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus. The method may further comprise indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus.

[0017] The apparatus by which the method according to the first example aspect is performed may be or may comprise a user equipment (UE).

[0018] According to the second example aspect, there is disclosed a method performed by an apparatus. The method may comprise transmitting, to a user equipment, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the apparatus. The method may further comprise receiving the uplink transmission from the user equipment. The method may further comprise receiving, from the user equipment, an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed. The method may further comprise, based on the indication, determining at least one of: a duration of the uplink transmission; a length of the uplink transmission; an end of the uplink transmission; a number of symbols of the uplink transmission; a number of slots of the uplink transmission; a number of Transmission Time Intervals, TTIs, of the uplink transmission; or a Transport Block Size, TBS, of the uplink transmission.

[0019] The apparatus by which the method according to the second example aspect is performed may be or may comprise a network entity such as, e.g., a network node. According to the example aspects of the present disclosure, there is in each case also disclosed a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform the method of the respective aspect.

[0020] The computer program may in each case be stored on a computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer readable storage medium could for example be a disk or a memory or the like. The computer program could be stored in the computer readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer readable storage medium may be intended for taking part in the operation of a device, like an internal or external memory, for instance a Read-Only Memory (ROM) or hard disk of a computer, or be intended for distribution of the program, like an optical disc.

[0021] Thus, according to the example aspects of the present disclosure, there is in each case also disclosed a computer- readable storage medium having stored thereon the computer program of the respective aspect.

[0022] Any disclosure herein relating to any example aspect is to be understood to be equally disclosed with respect to any subject-matter according to the respective example aspect, e.g. relating to an apparatus, a method, a computer program, and a computer-readable storage medium. For example, any passage describing at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform a step is to be understood as disclosing the step as a method step itself. The same holds the other way around, i.e., any passage describing a method or method step is to be understood as disclosing at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method or method step. The disclosure of a method or a method step shall also be considered as a disclosure of means for performing and / or causing to perform the respective method or method step. Likewise, the disclosure of means for performing and / or causing to perform a method or method step shall also be considered as a disclosure of the method or method step itself.

[0023] Specifically, an apparatus (e.g., the apparatus according to the first example aspect and / or the apparatus according to the second example aspect) is disclosed, configured to carry out, perform and / or control or comprising respective means for performing and / or controlling the method according to any of the above-mentioned example aspects. Further, an apparatus (e.g., the apparatus according to the first example aspect and / or the apparatus according to the second example aspect) is disclosed comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method according to any aspect.

[0024] The apparatus according to any aspect may comprise means for performing the specified method or steps.

[0025] In general, the means or functionality of any of the disclosed devices or apparatuses (e.g., the apparatus according to the first example aspect and / or the apparatus according to the second example aspect) may be implemented in hardware and / or software. They may comprise one or multiple modules or units providing the respective functionality. They may for instance comprise at least one processor for executing computer program code for performing the required functions, at least one memory storing the program code, or both. They could comprise for instance circuitry that is designed to implement the required functions, for instance implemented in a chipset or a chip, like an integrated circuit. In general, the means may comprise for instance one or more processing means or processors.

[0026] Specific means may be used to implement specific functions / functionalities / features, e.g. receiving means for receiving, from a network node, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the network node, performing means for performing the uplink transmission to the network node based on the received frequency -domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus, and / or indicating means for indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus (said means may for example be comprised by the apparatus according to the first example aspect).

[0027] Further examples of specific means may comprise, e.g., transmitting means for transmitting, to a user equipment, a frequency-domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the apparatus, receiving means for receiving the uplink transmission from the user equipment, receiving means for receiving, from the user equipment, an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed, and / or determining means for determining, based on the indication, at least one of: a duration of the uplink transmission; a length of the uplink transmission; an end of the uplink transmission; a number of symbols of the uplink transmission; a number of slots of the uplink transmission; a number of Transmission Time Intervals, TTIs, of the uplink transmission; or a Transport Block Size, TBS, of the uplink transmission (said means may for example be comprised by the apparatus according to the second example aspect).

[0028] Thus, according to the respective example aspects of the present disclosure, there is in each case also disclosed a respective apparatus comprising means for performing a method according to the respective aspect of the present disclosure.

[0029] Any of the above-disclosed example aspects may, however, in general be performed by an apparatus, which may be a module or a component for a device, for example a chip.

[0030] The apparatus according to any aspect may comprise only (i.e., consist of) the disclosed components, for instance means, processor, memory, circuitry, or may further comprise one or more additional components.

[0031] The described aspects may be advantageous in terms of at least one of speed, efficiency, or power consumption associated with an SDT uplink transmission. More specifically, by reducing a number of required uplink transmissions, in particular to a single transmission, an amount of power consumed by an apparatus performing the uplink transmission may advantageously be reduced. Further, network resources (e.g., network overhead and / or over allocated resources) may advantageously be saved, e.g. minimized. Further, an overall time required for the uplink transmission may advantageously be reduced, e.g. minimized. The aforementioned advantages may in particular be achieved by performing the uplink transmission based on a time-domain resource allocation determined at least in part by the apparatus performing the uplink transmission (e.g., a UE). It has been found that in particular letting the apparatus performing the uplink transmission at least in part determine the time-domain resource allocation for performing the uplink transmission advantageously allows the number of required uplink transmissions (e.g. for completely sending an UL message) to be reduced, in particular to a single transmission. With respect to the second aspect (e.g., on the network side), the aforementioned advantages may in particular be achieved by receiving an indication indicating a time-domain resource allocation based on which an uplink transmission is performed.

[0032] In this way, the described aspects and in particular a time-domain resource allocation in accordance with the described aspects may allow for an improved SDT uplink transmission, e.g. for loT applications in 6G.

[0033] The apparatuses, methods, computer programs and / or storage media in accordance with the described aspects may for instance correspond to apparatuses, methods, computer programs and / or storage media for 6G (e.g. standardized in 3GPP Rel-21 or beyond), for instance for a 6G Low Power Wide Area (LPWA) network.

[0034] An uplink transmission in accordance with the described aspects, e.g. an uplink transmission performed based on a time-domain resource allocation determined at least in part by the apparatus performing the uplink transmission, may for instance be referred to as a flexible (or autonomous), in particular flexible-duration, uplink transmission. By contrast, an uplink transmission performed based on a time-domain resource allocation determined solely by the network and, thus, not at least in part by the apparatus performing the uplink transmission may be referred to as a fixed-duration uplink transmission.

[0035] The frequency -domain resource allocation may for instance comprise or correspond to a frequency range, a carrier frequency, one or more frequency bands, and / or one or more bandwidth parts (BWPs). The frequency -domain resource allocation may for instance comprise or correspond to a plurality of, e.g. consecutive, Resource Blocks (RBs). The frequency -domain resource allocation may be received from, e.g. indicated by, the network node. The frequency-domain resource allocation may be received as part of uplink transmission configuration information or uplink transmission scheduling information, as further described herein.

[0036] The received frequency -domain resource allocation may be allocated for performing the uplink transmission. In other words, the received frequency -domain resource allocation may comprise or correspond to one or more frequency-domain resources where the uplink transmission is to be performed, e.g. where performing the uplink transmission is allowed, e.g. scheduled, by the network. The frequency-domain resource allocation may be part of or comprised by a time-frequency resource allocation.

[0037] The frequency -domain resource allocation may be an allocation for performing the uplink transmission as part of a Small Data Transmission (SDT) procedure. In an example, the uplink transmission may thus be performed as part of an SDT procedure. Performing an uplink transmission as part of an SDT procedure may for instance mean that the uplink transmission is performed during the SDT procedure and / or that the SDT procedure comprises performing the uplink transmission. As used herein, an SDT procedure may be understood to refer to any procedure of any present or future radio access technology (e.g. standardized in 3GPP Rel-21 or beyond) that enables an uplink transmission (e.g. of user data or user-plane data) in some sort of inactive or idle communication state, e.g. without transitioning to a Radio Resource Control (RRC) connected state, and is in particular not to be understood as limiting the described aspects to 4G and / or 5G / NR radio access technology, unless explicitly stated otherwise. As used herein, an SDT procedure may thus comprise or correspond to transmitting data, in particular in the uplink direction, in an inactive communication state, e.g. in RRC Inactive or RRC Idle state. Thus, the uplink transmission may for instance be performed by the apparatus without the apparatus being in an active communication state. The data transmission may be performed using predefined signaling and / or one or more predefined resource allocations, e.g. configured for an uplink transmission of one or more small data packets. As used herein, the size of a small data packet may be predetermined, e.g. configured, by the network. For example, as used herein, a small data packet may comprise at most 1000 bytes, in particular at most 200 bytes, in particular at most 100 bytes. Notwithstanding the foregoing, the SDT procedure referred to in the example aspects may for instance correspond to an SDT procedure in 5G / NR, e.g. as specified in section 18 of 3GPP Technical Specification (TS) 38.300.

[0038] The uplink transmission may in particular comprise or correspond to a Physical Uplink Shared Channel (PUSCH) transmission. Performing the uplink transmission may thus comprise or correspond to performing a PUSCH transmission.

[0039] Performing the uplink transmission based on the received frequency -domain resource allocation may for instance comprise performing the uplink transmission using the received frequency -domain resource allocation. Similarly, performing the uplink transmission based on the time-domain resource allocation may for instance comprise performing the uplink transmission using the time-domain resource allocation. Thus, performing the uplink transmission based on the received frequency -domain resource allocation and based on the time-domain resource allocation determined at least in part by the apparatus may for instance comprise performing the uplink transmission using the received frequency -domain resource allocation and the determined time-domain resource allocation.

[0040] Alternatively or in addition, performing the uplink transmission based on the received frequency -domain resource allocation may for instance comprise performing the uplink transmission in, e.g. direct, response to and / or after receiving the frequency -domain resource allocation from the network node.

[0041] The time-domain resource allocation may comprise or correspond to one or more values indicating a time-domain resource, e.g. a time-domain resource being allocated for performing the uplink transmission.

[0042] The time-domain resource allocation determined at least in part by the apparatus may correspond to at least one of: o a duration of the uplink transmission; o a length of the uplink transmission; o an end of the uplink transmission; o a number of symbols of the uplink transmission; o a number of slots of the uplink transmission; o a number of Transmission Time Intervals, TTIs, of the uplink transmission; or o a Transport Block Size, TBS, of the uplink transmission.

[0043] In other words, the time-domain resource allocation may be defined at least in part by one or more of the above elements. The time-domain resource allocation may correspond to and / or may be defined, at least in part, by multiple of the above elements. The time-domain resource allocation may correspond to and / or may be fully defined by a single one of the above elements.

[0044] A duration of an uplink transmission may comprise or correspond to a time interval for which or during which the uplink transmission is performed. A length of an uplink transmission may comprise or correspond to a number of, e.g. consecutive, time resource units, e.g. symbols or TTIs, used for performing the uplink transmission. An end of an uplink transmission may comprise or correspond to a final symbol or slot used for the uplink transmission, e.g. marking a last symbol or slot used for the uplink transmission.

[0045] A number of symbols of an uplink transmission may comprise or correspond to a number of Orthogonal Frequency Division Multiplexing (OFDM) symbols used for the uplink transmission. A number of slots of an uplink transmission may comprise or correspond to a length of a sequence of, e.g. consecutive, time units used for the uplink transmission. A number of Transmission Time Intervals (TTIs) of an uplink transmission may comprise or correspond to a number of, e.g. contiguous, time periods used for the uplink transmission. A TTI may for instance be defined by a predefined duration and / or a predefined number of slots. A Transport Block Size (TBS) of an uplink transmission may comprise or correspond to a size, e.g. a number of bits, of a Transport Block (TB) associated with, e.g. comprised by, the uplink transmission.

[0046] As mentioned, the time-domain resource allocation may be determined at least in part by the apparatus according to the first aspect (e.g. a UE). The time-domain resource allocation may for instance be determined in part by the apparatus or may for instance be determined completely by the apparatus. The instructions, when executed by the at least one processor, may thus further cause the apparatus to perform: determining, at least in part, the time-domain resource allocation.

[0047] The time-domain resource allocation determined at least in part by the apparatus may for instance comprise or correspond to a time-domain resource allocation (e.g., at least one of a duration, a length, an end, a number of symbols, a number of slots, a number of TTIs or a TBS) required for transmitting an amount of data to be transmitted by the apparatus as part of the uplink transmission, in particular by means of a single transmission. As one example, the time-domain resource allocation determined at least in part by the apparatus may correspond to a required transmission duration (e.g., a duration required for transmitting an amount of data to be transmitted by the apparatus as part of the uplink transmission).

[0048] In this way, network resources may advantageously be saved and an amount of power consumed by the apparatus may advantageously be reduced, e.g. minimized, as described above.

[0049] The time-domain resource allocation may for example be determined based on at least one of: o a coverage enhancement level associated with the apparatus; o a data buffer status of a data buffer of the apparatus; o an energy level of the apparatus; o at least one characteristic of one or more further uplink transmissions performed by the apparatus prior to the uplink transmission to the network node; o a latency requirement or priority level associated with uplink data to be transmitted as part of the uplink transmission to the network node; o a duplex capability of the apparatus; o a time-frequency tracking performance of the apparatus; or o a Reference Signal Received Power, RSRP, measured by the apparatus.

[0050] The coverage enhancement (CE) level associated with the apparatus may comprise or correspond to a level indicating a quality of a radio link between the apparatus (e.g. a UE) and the network. Employing different CE levels may allow UEs to maintain a radio link also in challenging radio conditions.

[0051] The data buffer status of the data buffer of the apparatus may indicate an amount of data awaiting transmission or reception, e.g. represented by a value indicating the amount of data stored (e.g. temporarily) in the data buffer of the apparatus at a given time. In other words, the data buffer status of the data buffer may indicate a (e.g. current) size of the data buffer. Determining the time-domain resource allocation based on the data buffer status of the data buffer of the apparatus may for instance comprise determining the time-domain resource allocation such that the data buffer may be emptied if the uplink transmission is performed based on the time-domain resource allocation. In other words, the time-domain resource allocation may be determined such as to correspond to a TBS necessary to empty the data buffer.

[0052] The energy level, or battery level, of the apparatus may comprise or correspond to a remaining battery power or charge state, e.g. represented by a value indicating a remaining energy of the apparatus at a given time.

[0053] The latency requirement associated with uplink data to be transmitted as part of the uplink transmission (which may also be referred to as an uplink traffic) may indicate a time constraint for transmitting the uplink data, e.g. to the network node. Such time constraint may for instance be defined by a time interval between an initiation of the uplink transmission of the uplink data and a reception of the uplink data by the network.

[0054] The priority level associated with uplink data to be transmitted as part of the uplink transmission may indicate an order of importance of the uplink data, e.g. relative to other data to be transmitted. The priority level may for instance be low, medium, or high, or any intermediate level thereof.

[0055] The duplex capability of the apparatus may indicate if the apparatus supports a bidirectional communication, e.g. with the network node. For instance, the duplex capability of the apparatus may indicate if the apparatus supports a frequency division duplex (FDD) or a time division duplex (TDD) configuration for transmitting and receiving data to and from a network node. The time-frequency tracking performance of the apparatus may indicate a capability of the apparatus of maintaining a synchronization with a carrier signal with respect to time and / or frequency. As mentioned, the time-domain resource allocation may be determined based on the duplex capability of the apparatus and based on the time-frequency tracking performance of the apparatus. In particular, depending on the duplex capability of the apparatus, the apparatus may need to switch from an uplink transmission to a downlink transmission after a certain amount of time in order to perform a time -frequency tracking, thus limiting a maximum amount of time for performing the uplink transmission. The latter may for instance apply to an apparatus having half-duplex capability.

[0056] The Reference Signal Received Power (RSRP) measured, or observed, by the apparatus may indicate an average power of one or more reference signals (e.g. transmitted via the 5G / NR Un interface) received by the apparatus from a network node (e.g. in a serving cell of the apparatus). Determining the time-domain resource allocation based on the measured RSRP may for instance comprise comparing the measured RSRP to an RSRP threshold and determining the time-domain resource allocation based on a result of this comparison. The RSRP threshold may for instance be an RSRP threshold for an SDT having a time-domain resource allocation (e.g. duration) which is predefined or fixed and / or determined solely by the network. The time-domain resource allocation may be determined based on a maximum TBS corresponding to such a predefined or fixed time-domain resource allocation (e.g. duration).

[0057] The apparatus may further determine that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus. The instructions, when executed by the at least one processor, may thus further cause the apparatus to perform: determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus.

[0058] Determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus may be based on one or more of the aforementioned elements such as coverage enhancement level, data buffer status, etc.

[0059] The instructions, when executed by the at least one processor, may thus further cause the apparatus to perform: determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on at least one of: o a coverage enhancement level associated with the apparatus; o a data buffer status of a data buffer of the apparatus; o an energy level of the apparatus; o at least one characteristic of one or more further uplink transmissions performed by the apparatus prior to the uplink transmission to the network node; o a latency requirement or priority level associated with uplink data to be transmitted as part of the uplink transmission to the network node; o a duplex capability of the apparatus; o a time-frequency tracking performance of the apparatus; or o a Reference Signal Received Power, RSRP, measured by the apparatus. Determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on a CE level may for instance comprise determining, based on the CE level, a supported TBS; determining if the supported TBS is below a predefined threshold; and, based on determining that the supported TBS is below the predefined threshold, determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus. If, on the other hand, it is determined that the supported TBS is not below the predefined threshold, it may be determined that the uplink transmission to the network node does not need to be performed based on a time-domain resource allocation determined at least in part by the apparatus.

[0060] In other words, considering that a supported TBS may be relatively small for certain CE levels (e.g. in relatively bad radio conditions), it may be desirable for such CE levels to use a time-domain resource allocation determined at least in part by the apparatus in order to reduce a number of required transmissions, in particular to a single transmission. Conversely, considering that a supported TBS may be relatively large for certain other CE levels (e.g. in relatively good radio conditions), it may not be necessary to use a time-domain resource allocation determined at least in part by the apparatus and, e.g., a fixed duration transmission may be used instead. For instance, in relatively good radio conditions, the network may be able to use a higher Modulation and Coding Scheme (MCS) and may allocate larger packet sizes. In this way, the CE level may advantageously be used to determine whether a flexibleduration uplink transmission shall be performed.

[0061] Alternatively or in addition to the CE level associated with the apparatus, the RSRP measured by the apparatus may be used. Thus, determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on an RSRP may for instance comprise determining, based on the RSRP, a supported TBS; determining if the supported TBS is below a predefined threshold; and, based on determining that the supported TBS is below the predefined threshold, determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus. In this way, the measured RSRP may advantageously be used to determine whether a flexible-duration uplink transmission shall be performed.

[0062] Determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on a data buffer status of a data buffer of the apparatus may for instance comprise determining that a size of the data buffer, which may be indicated by the data buffer status, is larger than a predetermined threshold and, based thereon, determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus. In other words, it may be determined that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus if the size of the data buffer is determined to be larger than the threshold.

[0063] Determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on the data buffer status may further comprise determining, based on the received frequency -domain resource allocation, that the apparatus would not be able to transmit the data contained in the data buffer of the apparatus in a single transmission if the uplink transmission would not be performed based on a time-domain resource allocation determined at least in part by the apparatus. In this way, the data buffer status of the data buffer of the apparatus may advantageously be used to determine whether a flexible-duration uplink transmission shall be performed.

[0064] Alternatively or in addition, determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus may be based on a maximum duration of the uplink transmission and / or a maximum TBS of the uplink transmission. For instance, in 5G / NR, an apparatus performing an uplink transmission in Frequency Range 2 (FR2) may be able to transmit an amount of data within a single frequency-domain resource allocation that is larger than an amount of data transmitted within a single frequencydomain resource allocation in Frequency Range 1 (FR1). In this way, the maximum duration of the uplink transmission and / or the maximum TBS of the uplink transmission, e.g. depending on the particular Frequency Range (FR1 or FR2) used, may advantageously be used to determine whether a flexible-duration uplink transmission shall be performed.

[0065] Determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on the energy level of the apparatus may for instance comprise determining that the energy level of the apparatus is below a predefined threshold and, based thereon, determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus. In other words, it may be determined that uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus if the energy level of the apparatus is below the predefined threshold. In this way, the energy level of the apparatus may advantageously be used to determine whether a flexible-duration uplink transmission shall be performed.

[0066] The at least one characteristic of one or more further uplink transmissions performed by the apparatus prior to the uplink transmission to the network node may comprise or correspond to a respective number and / or a respective duration of the one or more further uplink transmissions having been required for transmitting a predefined data type in one or more further transmissions having been performed prior to the uplink transmission. Determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus based on the at least one characteristic of one or more further uplink transmissions may thus for instance comprise determining that a number of (e.g. consecutive) prior uplink transmissions having required more than one, e.g. fixed-duration, transmission for transmitting a predefined data type exceeds a predefined threshold. In other words, it may be determined that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus if the number of (e.g. consecutive) prior, or previous, uplink transmissions having required more than one, e.g. fixed-duration, transmission for transmitting a predefined data type exceeds a predefined threshold. In this way, it may advantageously be determined that fixed-duration transmissions are not suitable for said predefined data type and that instead a flexible-duration uplink transmission shall be performed.

[0067] Alternatively or in addition, the apparatus may receive an indication from the network node that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus. Thus, the instructions, when executed by the at least one processor, may further cause the apparatus to perform: receiving, from the network node, an indication that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus.

[0068] In other words, alternatively or in addition to the apparatus determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus, it may be indicated to the apparatus by the network (node) to perform the uplink transmission based on a time-domain resource allocation determined at least in part by the apparatus. Yet put differently, it may in particular be the network that may eventually allow or disallow the apparatus to perform the uplink transmission based on a timedomain resource allocation determined at least in part by the apparatus.

[0069] Alternatively or in addition, the network node may to this end indicate to the apparatus one or more request criteria, wherein the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus if, in particular only if, the one or more request criteria are satisfied. Correspondingly, the apparatus according to the second aspect may for instance indicate said one or more request criteria to the user equipment. Thus, the instructions, when executed by the at least one processor, may further cause the apparatus to perform: obtaining an indication of at least one request criterion, wherein the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus if, in particular only if, the at least one request criterion is satisfied.

[0070] The one or more request criteria may for instance be based on an RSRP (e.g. of the 5G / NR Un interface) measured by the apparatus, a Logical Channel Group (LCG) of uplink data (e.g. buffered by the apparatus) to be transmitted as part of the uplink transmission, a Packet Delay Budget (PDB) of such uplink data, an energy level of the apparatus, and / or an availability of an indirect path for the uplink transmission. The one or more request criteria may for instance include at least one of the following: o the RSRP measured by the apparatus being below a predefined RSRP threshold; o the energy level of the apparatus being below a predefined energy threshold; o the uplink data belonging to a certain predefined LCG group; o the uplink data having a certain predefined priority; o the uplink data being above certain predefined bits; o an indirect path being unavailable for the uplink transmission; or o an indirect path being available for the uplink transmission and the uplink data being above a certain predefined number of bits.

[0071] The one or more request criteria may allow the apparatus according to the second aspect (e.g., a network node) to control which UEs are allowed to use flexible-duration uplink transmission.

[0072] Indicating the time-domain resource allocation to the network node may for instance comprise or correspond to providing information indicative of the time-domain resource allocation to the network node. The information may for example comprise one or more values representing the time-domain resource allocation. Said one or more values may for instance comprise or correspond to at least one of a duration, a length, a number of symbols, a number of slots, a number of TTIs, or a TBS of the uplink transmission. Alternatively or in addition, indicating the timedomain resource allocation to the network node may comprise or correspond to indicating an end of the uplink transmission to the network node. The time-domain resource allocation may be indicated at least in part to the network node. Thus, the time-domain resource allocation may for instance be indicated to the network node in part or may for instance be indicated to the network node completely.

[0073] The time-domain resource allocation determined at least in part by the apparatus may be indicated to the network node by means of at least one of: o a transmission pre-amble transmitted prior to the uplink transmission; o a transmission mid-amble transmitted during the uplink transmission; o a transmission post-amble transmitted after the uplink transmission; o a Medium Access Control, MAC, sub-header associated with the uplink transmission; o uplink control information; or o a Sounding Reference Signal, SRS.

[0074] Alternatively or in addition to being transmitted prior to the uplink transmission, the transmission pre-amble may be transmitted at the beginning of the uplink transmission. The transmission pre-amble may for instance indicate the time-domain resource allocation using one or more predefined sequences, wherein each of the one or more predefined sequences may correspond to a time-domain resource allocation. For example, predefined sequences indexed 1,2, 3, 4 may respectively indicate a number of TTIs used for the uplink transmission being 1,2, 4, 8.

[0075] Alternatively or in addition to being transmitted during the uplink transmission, the transmission mid-amble may be transmitted as part of the uplink transmission. The transmission mid-amble may for instance indicate an end of a first repetition of the uplink transmission, e.g. prior to one or more further repetitions of the uplink transmission. In other words, the transmission mid-amble may be appended to the first repetition of the uplink transmission, e.g. before one or more further repetitions are transmitted. In this way, the network may determine the time-domain resource allocation (e.g. a length) of the uplink transmission prior to the one or more further repetitions, thereby saving an amount of data buffering required by the network.

[0076] Alternatively or in addition to being transmitted after the uplink transmission, the transmission post-amble may be transmitted at the end of the uplink transmission. In other words, the transmission post-amble may be appended to the uplink transmission. The transmission post-amble may for instance be detected by the network node and, based thereon, the network node may determine the time-domain resource allocation of (e.g. the end of) the uplink transmission.

[0077] The MAC sub-header may for instance use a predefined number of bits to indicate the time-domain resource allocation, e.g. a number of TTIs used for the uplink transmission. For example, two bits may be used to indicate 1, 2, 4 or 8 TTIs being used for the uplink transmission.

[0078] The uplink control information may for instance be prepended to the uplink transmission. The uplink control information may use an existing uplink control information format. In other words, an existing Uplink Control Information (UCI) format, e.g. CSI reporting, may be (re-)used for indicating the time-domain resource allocation. The uplink control information may for instance indicate the time-domain resource allocation using one or more predefined sequences, as described above for the transmission pre-amble.

[0079] Alternatively or in addition, an SRS may be used for indicating the time-domain resource allocation to the network node.

[0080] Alternatively or in addition to the time-domain resource allocation being indicated to the network node, the network node may determine the time-domain resource allocation based on a Demodulation Reference Signal (DMRS) and / or based on an energy detection. Determining the time-domain resource allocation without an indication from the apparatus performing the uplink transmission, e.g. solely based on a DMRS and / or an energy detection, may be referred to as a blind detection. Thus, in an example, the network node may determine the time-domain resource allocation blindly.

[0081] The instructions, when executed by the at least one processor, may further cause the apparatus to perform: receiving, from the network node, an indication that the network node is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at least in part by a user equipment.

[0082] In other words, the apparatus may receive an indication that the network node supports an uplink transmission performed based on a time-domain resource allocation determined at least in part by a user equipment. In this way, the apparatus performing the uplink transmission may advantageously be informed whether a particular network node to which the uplink transmission shall be performed supports flexible-duration uplink transmissions or not.

[0083] The apparatus may further obtain an indication of at least one predetermined condition to be satisfied by the timedomain resource allocation.

[0084] The instructions, when executed by the at least one processor, may further cause the apparatus to perform: obtaining an indication of at least one predetermined condition to be satisfied by the time-domain resource allocation, wherein the at least one predetermined condition corresponds to at least one of: o a maximum duration of the uplink transmission; o a maximum length of the uplink transmission; o a latest end of the uplink transmission; o a maximum number of symbols of the uplink transmission; o a maximum number of slots of the uplink transmission; o a maximum number of Transmission Time Intervals, TTIs, of the uplink transmission; or o a maximum Transport Block Size, TBS, of the uplink transmission.

[0085] In other words, the at least one predetermined condition may be defined at least in part by one or more of the above elements. The maximum duration of the uplink transmission may comprise or correspond to a maximum time interval for which or during which the uplink transmission is performed. The maximum length of the uplink transmission may comprise or correspond to a maximum number of, e.g. consecutive, time resource units, e.g. OFDM symbols or slots, used for performing the uplink transmission. The latest end of the uplink transmission may comprise or correspond to a latest final symbol or slot used for the uplink transmission, e.g. marking a latest last symbol or slot used for the uplink transmission.

[0086] The maximum number of symbols of the uplink transmission may comprise or correspond to a maximum number of OFDM symbols used for the uplink transmission. The maximum number of slots of the uplink transmission may comprise or correspond to a maximum length of a sequence of, e.g. consecutive, time units used for the uplink transmission. The maximum number of TTIs of the uplink transmission may comprise or correspond to a maximum number of, e.g. contiguous, time periods used for the uplink transmission. The maximum TBS of the uplink transmission may comprise or correspond to a maximum size, e.g. a maximum number of bits, of a TB associated with, e.g. comprised by, the uplink transmission.

[0087] The time-domain resource allocation may in particular be determined based on the at least one predetermined condition. The instructions, when executed by the at least one processor, may thus further cause the apparatus to perform: determining the time-domain resource allocation based on the at least one predetermined condition.

[0088] Determining the time-domain resource allocation based on the at least one predetermined condition may in particular mean that the time-domain resource allocation is determined such as to satisfy the at least one predetermined condition.

[0089] The time-domain resource allocation may for instance be understood to satisfy a respective predetermined condition if a respective value (e.g. a duration, a length, a number of symbols, a number of slots, a number of TTIs, and / or a TBS) of the time-domain resource allocation corresponding to a respective predetermined condition (e.g. a maximum duration, a maximum length, a maximum number of symbols, a maximum number of slots, a maximum number of TTIs, and / or a maximum TBS) is less than or equal to the respective maximum value (e.g. the maximum duration, the maximum length, the maximum number of symbols, the maximum number of slots, the maximum number of TTIs, and / or the maximum TBS). Further, the time-domain resource allocation may be understood to satisfy a corresponding predetermined condition if the end of the uplink transmission is prior to or equal the latest end of the uplink transmission.

[0090] Determining the time-domain resource allocation based on at least one predetermined condition may advantageously take account of limitations associated with a particular radio access technology and / or may increase compatibility between apparatuses involved in performing and receiving the uplink transmission.

[0091] The instructions, when executed by the at least one processor, may further cause the apparatus to perform: obtaining an indication of a starting time-domain resource to be used for performing the uplink transmission, wherein the starting time-domain resource corresponds to a starting symbol, a starting slot or a starting TTI to be used for performing the uplink transmission.

[0092] The uplink transmission may be performed based on the starting time-domain resource. For example, the uplink transmission may be started at the starting time-domain resource. Yet put differently, the starting time-domain resource may be used when starting to perform the uplink transmission. The indication of the starting time-domain resource may for instance be received by the apparatus from the network node. Obtaining the indication of the starting time-domain resource may thus comprise or correspond to receiving the starting time-domain resource from the network node.

[0093] By obtaining, by the apparatus performing the uplink transmission, the indication of the starting time-domain resource, and in particular by performing the uplink transmission based on the starting time-domain resource the network may advantageously be able to determine the time-domain resource allocation based on which the uplink transmission is performed.

[0094] The indication that the network node is configured for receiving an uplink transmission performed based on a timedomain resource allocation determined at least in part by a user equipment, the indication of at least one predetermined condition to be satisfied by the time-domain resource allocation and / or the indication of a starting time-domain resource to be used for performing the uplink transmission may be obtained as part of at least one of: o a Small Data Transmission, SDT, configuration; o a Random Access, RA, configuration; o a Configured Grant, CG, configuration; or o uplink transmission scheduling information.

[0095] Any or all of said configurations may be received from the network node. Obtaining one or more of said indications may thus comprise or correspond to receiving the one or more indications from the network node.

[0096] The SDT configuration may for instance comprise or correspond to a configuration indicating one or more parameters for performing an SDT uplink transmission, as further described herein.

[0097] The Random Access (RA) configuration may for instance comprise or correspond to a configuration indicating one or more parameters for performing a RA procedure. The RA procedure may be understood as a procedure comprising a set of signaling exchanges initiated by a UE to establish a radio connection with a network node. The set of signaling exchanges may for instance include a RA Preamble transmission (also referred to as Msgl or MsgA), a RA Response (also referred to as Msg2 or MsgB), a PUSCH transmission (also referred to as Msg3 or MsgA), and a Contention Resolution message (also referred to as Msg4 or MsgB). Alternatively or in addition, the set of signaling exchanges may include a RA Preamble Assignment, a RA Preamble transmission, and a RA Response. The Configured Grant (CG) configuration may for instance comprise or correspond to a configuration indicating one or more parameters for defining a CG. A CG may be understood to comprise or correspond to a predefined set of resource allocations for an uplink transmission.

[0098] The uplink transmission scheduling information may for instance comprise or correspond to information relating to a scheduling of the uplink transmission. The scheduling of the uplink transmission may for instance comprise or correspond to a Dynamic Scheduling, e.g. by means of Downlink Control Information (DCI) or by means of an UL grant in a RA response, or to a Configured Scheduling (CS), e.g. by means of RRC signaling.

[0099] The uplink transmission to the network node may further be performed based on uplink transmission configuration information or uplink transmission scheduling information received from the network node, wherein the uplink transmission configuration information or the uplink transmission scheduling information indicates at least one of: o the frequency -domain resource allocation for performing the uplink transmission; o a Modulation and Coding Scheme, MCS, to be used for the uplink transmission; or o a number of repetitions to be used for the uplink transmission.

[0100] The Modulation and Coding Scheme (MCS) to be used for the uplink transmission may for instance comprise or correspond to a scheme for modulating and / or coding the uplink transmission. The number of repetitions to be used for the uplink transmission may for instance indicate a number of repetitions that shall be transmitted. Repetitions of an uplink transmission may refer to transmitting a same data unit multiple times. Repetitions may improve a reliability of the uplink transmission in challenging radio conditions.

[0101] The uplink transmission configuration information may for instance comprise or correspond to information relating to a configuration of the uplink transmission. The uplink transmission scheduling information may for instance comprise or correspond to information relating to a scheduling of the uplink transmission. The scheduling of the uplink transmission may for instance comprise or correspond to a Dynamic Scheduling, e.g. by means of Downlink Control Information (DCI) or by means of an UL grant in a RA response, or to a Configured Scheduling (CS), e.g. by means of RRC signaling.

[0102] The uplink transmission configuration information and / or the uplink transmission scheduling information may for instance comprise (e.g. use) a Downlink Control Information (DCI) format (also) used for fixed-duration uplink transmissions. For example, an (e.g. reserved) field and / or an (e.g. unused) state of said DCI format may be used to indicate flexible-duration uplink transmissions. Alternatively or in addition, a DCI format different from one or more DCI formats used for fixed-duration uplink transmissions may be used for flexible-duration uplink transmissions.

[0103] The frequency -domain resource allocation transmitted by the apparatus according to the second aspect may in particular correspond to the frequency -domain resource allocation received by the apparatus according to the first aspect. Further, the uplink transmission received by the apparatus according to the second aspect may in particular correspond to the uplink transmission performed by the apparatus according to the first aspect. Further, the indication indicating a time-domain resource allocation received by the apparatus according to the second aspect may in particular correspond to the time-domain resource allocation indicated by the apparatus according to the first aspect.

[0104] As mentioned, the indication received by the apparatus according to the second aspect may indicate a time-domain resource allocation determined at least in part by the user equipment. Further, the uplink transmission received by the apparatus according to the second aspect may be or may have been performed based on the time-domain resource allocation.

[0105] Based on the indication indicating the time-domain resource allocation determined at least in part by the user equipment, the apparatus according to the second aspect may determine at least one of a duration of the uplink transmission; a length of the uplink transmission; an end of the uplink transmission; a number of symbols of the uplink transmission; a number of slots of the uplink transmission; a number of Transmission Time Intervals, TTIs, of the uplink transmission; or a Transport Block Size, TBS, of the uplink transmission.

[0106] In this way, the apparatus according to the second aspect may advantageously be able to obtain uplink data being transmitted as part of a flexible-duration uplink transmission, as described herein.

[0107] As used herein, performing a second step based on a first step may for example mean that the second step may be performed, e.g. directly, in response to the first step, e.g. without any intermediate steps in between the first step and the second step. Alternatively, performing a second step based on a first step may mean that the second step may be performed (merely) after the first step, e.g. such that there may be at least one intermediate step in between the first step and the second step.

[0108] It is to be understood that the presentation of the embodiments disclosed herein is merely by way of examples and non-limiting.

[0109] Herein, the disclosure of a method step shall also be considered as a disclosure of means for performing the respective method step. Likewise, the disclosure of means for performing a method step shall also be considered as a disclosure of the method step itself.

[0110] Other features of the present disclosure will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are designed solely for purposes of illustration and not as a definition of the limits of the present disclosure, for which reference should be made to the appended claims. It should be further understood that the drawings are not drawn to scale and that they are merely intended to conceptually illustrate the structures and procedures described herein.

[0111] BRIEF DESCRIPTION OF THE FIGURES

[0112] Some example embodiments will now be described with reference to the accompanying drawings in which

[0113] FIG. 1 exemplarily illustrates a user equipment and a network node in wireless communication; FIG. 2 shows an example embodiment of a method according to the present disclosure;

[0114] FIG. 3 shows a further example embodiment of a method according to the present disclosure;

[0115] FIG. 4 shows an example of a signaling flow chart according to example embodiments of the present disclosure;

[0116] FIG. 5 shows a further example of a signaling flow chart according to example embodiments of the present disclosure;

[0117] FIGS. 6A-6C show schematic illustrations of various examples for indicating a time-domain resource allocation according to example embodiments of the present disclosure;

[0118] FIG. 7 shows a block diagram of an example of an apparatus according to the first aspect;

[0119] FIG. 8 shows a block diagram of an example of an apparatus according to the second aspect;

[0120] FIG. 9 shows a schematic illustration of examples of tangible and non-transitory computer-readable storage media.

[0121] DETAILED DESCRIPTION OF THE FIGURES

[0122] The following description serves to deepen the understanding of the present disclosure and shall be understood to complement and be read together with the description of example embodiments of the present disclosure as provided in the above SUMMARY section of this specification.

[0123] In the following, an example wireless communication system, within which the present disclosure may be applied, is described. While the radio system in the examples below is a 5G / NR system, this is only to be considered a nonlimiting example.

[0124] FIG. 1 exemplarily illustrates a UE 100 (an example of the apparatus according to the first aspect) in wireless communication with a gNB 110 (an example of the apparatus according to the second aspect) via a radio link 10. Radio link 10 may enable transmitting / receiving information and / or signals in between the UE 100 and the gNB 110.

[0125] For example, UE 100 may receive, from gNB 110 (an example of a network node), a frequency-domain resource allocation for performing, as part of an SDT procedure, an uplink transmission to the gNB 110. Further, UE 100 may perform an uplink transmission to gNB 110 based on the received frequency -domain resource allocation and based on a time-domain resource allocation determined at least in part by UE 100. Further, UE 100 may indicate, to gNB 110, the time-domain resource allocation determined at least in part by UE 100. Further, UE 100 may receive, from gNB 110, an indication that gNB 110 is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at least in part by a UE. Further, UE 100 may receive, from gNB 110, an indication of at least one predetermined condition to be satisfied by the timedomain resource allocation (an example of obtaining an indication of at least one predetermined condition to be satisfied by the time-domain resource allocation). Further, UE 100 may receive, from gNB 110, an indication of a starting time-domain resource to be used for performing the uplink transmission (an example of obtaining an indication of a starting time-domain resource to be used for performing the uplink transmission). Further, UE 100 may receive, from gNB 110, an SDT configuration, a RA configuration and / or a CG configuration (an example of obtaining such configurations).

[0126] Further, gNB 110 may transmit, to UE 100, a frequency-domain resource allocation for performing, as part of an SDT procedure, an uplink transmission to gNB 110. Further, gNB 110 may receive the uplink transmission from UE 100. Further, gNB 110 may receive, from UE 100, an indication indicating a time-domain resource allocation determined at least in part by UE 100 and based on which the uplink transmission is performed. Further, gNB 110 may determine, based on the indication, at least one of: a duration of the uplink transmission; a length of the uplink transmission; an end of the uplink transmission; a number of symbols of the uplink transmission; a number of slots of the uplink transmission; a number of TTIs of the uplink transmission; or a TBS of the uplink transmission.

[0127] FIG. 2 shows an example embodiment 200 of a method according to the first aspect. Method 200 may for example be performed by an apparatus according to the first aspect (e.g., a UE). First, a frequency -domain resource allocation for performing, as part of an SDT procedure, an uplink transmission to a network node may be received from the network node (action 210). Further, the uplink transmission to the network node may be performed based on the received frequency -domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus performing method 200 (action 220). Further, the time-domain resource allocation determined at least in part by the apparatus performing method 200 may be indicated to the network node (action 230).

[0128] Example implementations of method 200 will be described in detail further below.

[0129] FIG. 3 shows an example embodiment 300 of a method according to the second aspect. Method 300 may for example be performed by an apparatus according to the second aspect (e.g., a network node). First, a frequencydomain resource allocation for performing, as part of an SDT procedure, an uplink transmission to the apparatus performing method 300 may be transmitted to a user equipment (action 310). Further, the uplink transmission may be received from the user equipment (action 320). Further, an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed may be received from the user equipment (action 330). Further, at least one of a duration, a length, an end, a number of symbols, a number of slots, a number of TTIs, or a TBS of the uplink transmission may be determined based on the indication (action 340).

[0130] Example implementations of method 300 will be described in detail further below. Internet of Things (loT) may in particular refer to the interconnection and the autonomous exchange of data between devices. Three main loT categories may include massive loT, critical loT, and broadband loT. Of the three loT categories, massive loT may be considered to have the widest application with use cases such as smart meter, asset tracking and management, fleet management, sensors, remote monitoring, smart cities, etc. In cellular systems, massive loT deployment may be supported via Low Power Wide Area (LPWA) network. LPWA networks may have at least one of the following characteristics: o Low device complexity / cost; o Low device power consumption enabling long battery life, e.g. of greater than 10 years; o Enhanced coverage compared to broadband services, e.g. up to 20-25 dB enhanced coverage; o Support for massive number of devices; o Delay tolerant data transmission, e.g. up to 10 seconds to transmit a data packet; or o Infrequent data transmissions. loT traffic (e.g. sensor measurement reports, usage reports, location reports, etc.) may be generally delay -tolerant. In 5G / NR Technical Report (TR) 38.913, a latency requirement for massive loT applications is given in Section 7.6 as shown below:

[0131] “For infrequent application layer small packet / message transfer, the time it takes to successfully deliver an application layer packet / message from the radio protocol layer 2 / 3 SDU ingress point at the mobile device to the radio protocol layer 2 / 3 SDU egress point in the RAN, when the mobile device starts from its most "battery efficient" state.

[0132] For the definition above, the latency shall be no worse than 10 seconds on the uplink for a 20 byte application packet (with uncompressed IP header corresponding to 105 bytes physical layer) measured at the maximum coupling loss (MaxCL) of 164dB.”

[0133] For infrequent data transmission of small packet, Small Data Transmission (SDT) procedure has been defined in 5G / NR to support data transmission in RRC INACTIVE state without having to transition to RRC CONNECTED state. This may save significant RRC overhead as well as reduce data transmission latency. In addition, power consumption at the UE may be reduced. For 6G, it may be expected that SDT or a similar procedure will be supported. This procedure may be a basis for loT traffic transmission.

[0134] Typical loT data packet size may be small. For instance, in TR 38.900, 20 byte application packet (with uncompressed IP header corresponding to 105 bytes physical layer packet) is used as a reference for evaluation purpose. However, loT packet size may vary based on applications and reporting types.

[0135] For SDT, it may be most beneficial if the network is able to allocate sufficient UL resources for the UE to successfully send its UL report in a single transmission. This may allow the UE to complete the SDT procedure quickly and be released, thereby reducing UE power consumption. In addition, network resource may be saved as additional scheduling grants are not needed. However, as the network may not know the size of the UE data buffer when it schedules the first transmission, the network may over or under allocate the resources. Under allocation in the UL grant may result in multiple subsequent transmissions which may consume power. Over allocation may require the UE to transmit longer than necessary (i.e. UE may have to pad its data) which may waste power and / or network resources.

[0136] It may be considered a second issue in SDT that a UE in poor coverage may only be allocated small data packet size. This may be due to the design of the UL transmission in the specification (e.g. TBS table based on maximum time allocation). For instance, in NB-IoT, at the lowest MCS value, the UE may only be able to transmit at most 256 bits at a time. Therefore, the UE may need to transmit several packets. For instance, for a packet size of 105 bytes (840 bits), the UE may need to transmit 4 packets.

[0137] Therefore, a method (e.g. a method in accordance with the described aspects) may be needed to allow loT UE to, e.g., completely send its UL message in one transmission via SDT. This may be beneficial when (1) the network does not know an amount of data to be transmitted by the UE or when (2) the UE is only able to transmit a small amount of data in poor coverage due to an MCS / TBS design.

[0138] It may be considered an idea of the present disclosure for the network to, e.g., indicate an MCS and / or a frequency allocation in the UL scheduling grant, but let the UE transmit, e.g., as long as needed to send its message. That is, the network may only indicate the starting symbol, but the duration may be up to the UE. As a result, the UE may be able to determine a transmission duration that may correspond to a TBS necessary to empty its data buffer. This flexible or autonomous duration UL transmission configuration may be indicated as part of an SDT configuration (e.g., a RA-SDT or CG-SDT configuration). As part of its UL transmission, the UE may indicate to the network the length or the stopping point of its transmission e.g. via pre-amble / mid-amble / post-amble or via control message at the beginning of its transmission.

[0139] The proposed solution may provide a way for a UE to minimize a number of transmissions needed for its UL data transmission. This may reduce UE power consumption and minimize network overhead. In this way, the described aspects may expand use cases for 6G LPWA.

[0140] In the following, two example implementations of methods 200, 300 are described in detail. Said example implementations may, e.g., relate to blocks and / or actions of signaling flow charts 400, 500.

[0141] RA-SDT

[0142] For RA-SDT, the process may for instance be implemented as follows:

[0143] 1. The network may indicate support and configuration for flexible (or autonomous) duration UL transmission in SDT configuration (an example of an indication from a network node that the network node is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at least in part by a user equipment).

[0144] • Flexible-duration UL transmission may mean that the UE may transmit in the UL as long as necessary subject to conditions defined in the configuration. • The configuration may indicate the maximum time (e.g. number of symbols, slots or TTIs) or TBS that is supported using flexible-duration UL transmission (an example of the at least one predetermined condition to be satisfied by the time-domain resource allocation).

[0145] • The configuration may indicate the frequency resources (e.g., frequency range, carrier frequency, frequency bands, bandwidth parts, etc.) where flexible-duration UL transmissions are allowed (an example of the frequency -domain resource allocation received from the network node).

[0146] • The configuration may indicate the number of repetitions for UEs in coverage enhancement.

[0147] • The configuration may indicate the specific symbol(s) and slot(s) (or in general, time resources) that NW has pre-allocated for the start of flexible-duration UL transmissions (an example of an indication of a starting time-domain resource to be used for performing the uplink transmission), i.e., in which UE might be scheduled to start its transmission. In a variant, this may be indicated as a bitmap, e.g., for a bit map of (00010001000100), flexible-duration UL transmission may be scheduled at every 4th, 8th or 12th symbol in a slot of 14 symbols. This may allow more flexibility at the network side to efficiently use the radio resources, e.g., to distribute the UE traffic load across time resources, and may also assist the UE to decide between using a fixed vs flexible duration UL transmission depending on the latency requirement of its UL transmission.

[0148] • In an embodiment, UEs that have both direct and indirect connection to the network (e.g. multi-path connection using a UE-to-Network relay) may not be permitted by the network to use the configuration for flexible (or autonomous) duration UL transmission in SDT configuration because those UEs have already additional throughput and robustness using the multi-path connection. However, as an additional configuration, the NW may permit UEs with multi-path connection to use flexible (or autonomous) duration UL transmission if the amount of data to be transmitted may be above a certain number of bits.

[0149] • Network may provide a way for UE to select flexible-duration UL transmission and fixed-duration UL transmission (an example of determining that determining that the uplink transmission shall be performed based on a time-domain resource allocation determined at least in part by the apparatus). Examples may be preamble or PRACH resource partitioning for Msgl.

[0150] • In a variant, the network may configure the UE to use fixed vs flexible-duration UL transmission (an example of the network indicating to the apparatus to perform the uplink transmission based on a timedomain resource allocation determined at least in part by the apparatus) based on UE buffer status. For instance, UE with less than X bytes to transmit may use fixed duration UL transmission while UE with X or more bytes may use flexible duration UL transmission. o In a further embodiment, network may configure the UE to use flexible-duration UL for data belonging to only certain logical channel group (LCG) in the buffer. For example, the UE may use flexibleduration UL for LCG associated with high priority.

[0151] • In a variant, network may configure the UE to use flexible-duration UL transmission based on establishment cause or services (e.g. emergency access).

[0152] • In a variant, flexible-duration UL transmission may be only configured for UE in coverage enhancement.

[0153] • In embodiments, the configuration may target multiple UEs, e.g., any LPWA loT type of device, all UEs in a cell, etc., and may be broadcast / groupcast, or it may target a single UE and may be provided via dedicated signaling. In a further embodiment, in case of massive deployment of LPWA loT UEs, the configuration may permit only one / few LPWA loT UEs per a group of them to use flexible (or autonomous) UL transmissions for managing UL transmissions when LPWA loT UEs are massively deployed.

[0154] 2. UE may access the network and indicate its UL transmission preference (fixed or flexible-duration) in Msgl (if configured).

[0155] • UE may determine whether to use fixed or flexible duration transmission (an example of determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus), e.g.: o Based on its coverage enhancement level (or RSRP or other signal quality measurements) - UE may determine to use flexible-duration transmission. Since the supported TBS may be small for UE in coverage enhancement, it may want to select flexible-duration transmission to avoid having to transmit multiple times. Conversely, UE in good radio conditions may opt for fixed duration transmission since the network may be able to use higher MCS and allocate larger packet size. o Based on its data buffer status - UE may select the mode based on how much data it has to transmit (e.g. select flexible duration transmission if buffer size may be larger than a threshold). o In a variant, preference may be based on whether UE is able to transmit its data with a single allocation, given the configuration in Step 1. For this, UE may take into account the frequency resources indicated in Step 1, together with maximum duration / TBS to determine if it is able to transmit its data with a single allocation, e.g., in FR2, UE may transmit higher amount of data with a single allocation as compared to FR1. o Based on its battery or energy level - UE may select the mode based on how much energy it has left (e.g. select flexible-duration transmission if energy level is smaller than a threshold). o Based on comparison with previous UL SDT transmissions. For example, UE may opt for using flexible-duration transmission if at least X number of previous (consecutive) UL SDT attempts of the same data type with fixed duration (e.g., in case of periodic measurement reporting) resulted in multiple transmissions. In this way the UE may realize that fixed duration is not suitable for the particular type of operation it performs. o Based on the latency requirement of its UL traffic, depending on the slots and / or symbols that are preallocated for flexible-duration UL transmissions indicated in the configuration in Step 1.

[0156] • Additionally or alternatively, the network may provide the UE with one or more request criteria that UE must meet to request for the flexible UL (an example of the indication of the at least one request criterion). The criteria may be based on Un RSRP measurement, LCG of the buffered data, packet delay budget of the buffered data, energy level at the UE, availability of an indirect path. This may allow the network to control which UEs are allowed to use flexible UL. Examples of the criteria to request flexible UL include: o The RSRP being below a certain RSRP threshold, o Energy level being below a certain energy threshold, o Buffered data belonging to certain LCG group, o Buffered data belonging to certain priority, and / or o Buffered data is being above certain bits or threshold, etc. o Not having also an indirect path or having buffered data above a certain number of bits in case an indirect path is also available. 3. Network may provide corresponding UL grant in Msg2 (an example of the network allowing the apparatus to perform the uplink transmission based on a time-domain resource allocation determined at least in part by the apparatus).

[0157] • UL grant for flexible duration transmission may indicate MCS (an example of an MCS to be used for the uplink transmission) and frequency domain resource (an example of the frequency -domain resource allocation for performing the uplink transmission), number of repetition (an example of a number of repetitions to be used for the uplink transmission), starting symbol for time domain resource (an example of a starting time-domain resource to be used for performing the uplink transmission) but not time domain duration.

[0158] • One DCI format may be used for both modes (an example of the uplink transmission configuration information and / or the uplink transmission scheduling information using a DCI format (also) used for fixed-duration uplink transmissions). For instance, a reserved field or unused state may be used to indicate flexible duration.

[0159] • In a variant, two DCI formats may be supported - one for fixed and one for flexible duration UL allocation (an example of a DCI format being used for flexible-duration uplink transmissions being different from one or more DCI formats being used for fixed-duration uplink transmissions). UE will monitor for the format according to its indication in Msgl.

[0160] • In a variant, UE requesting flexible-duration UL transmission may be scheduled using fixed duration UL transmission. This may allow the network to fallback to normal UL transmission for UE requesting flexible duration UL transmission.

[0161] • In a further variant, the NW may indicate the time characteristics of such fallback-to-normal UL transmission. For example, the NW may indicate a cutoff time, such that the UE may request again flexible duration UL transmission only after this time has passed - but continue with fixed duration UL transmission meanwhile.

[0162] • In a further variant, the NW may indicate the permitted buffer characteristics for the UE to be able to request again flexible duration UL transmission. For example, upon scheduling fixed duration UL transmission, the NW may indicate to UE the minimum buffer volume of data-to -be -transmitted that must be met at the UE, for the UE to request again flexible duration UL transmission.

[0163] • In a variant, grant for flexible duration UL transmission may also include a method for UE to indicate its transmission duration (e.g. pre-amble or control information).

[0164] 4. UE scheduled with flexible-duration UL transmission may determine the duration of its transmission (an example of determining, at least in part, the time-domain resource allocation).

[0165] • UE may determine its UL transmission duration, e.g.: o Based on its data buffer status - UE may determine the duration based on the amount of data in its buffer, the allocated MCS, and the allocated frequency resources. o Based on its duplex capability and time-frequency tracking performance - half-duplex UE would need to switch from UL to DL after a while to perform time -frequency tracking. Therefore, the maximum duration may be determined by this time. o Based on observed RSRP - UE may compare its measured serving cell RSRP with the RSRP threshold for fixed duration SDT and may determine transmission duration in comparison with fixed duration’s TBS limit.

[0166] 5. UE may transmit in the allocated frequency resource (an example of performing the uplink transmission to the network node based on the received frequency -domain resource allocation). UE may indicate the length or end of transmission to the network (an example of indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus).

[0167] • Indication may be pre-amble / mid-amble / post-amble, MAC sub-header or via control message at the beginning of its transmission. o For pre-amble based indication, several sequences may be predefined corresponding to various transmission lengths. For example, sequence indices { 1,2, 3, 4} may be mapped to { 1,2, 4, 8} TTIs, respectively. o Mid-amble may be used to indicate the end of the first transmission prior to any repetition. o MAC sub-header may indicate the transmission length in TTIs. For example, 2 bits may be used to indicate one of { 1,2, 4, 8} TTIs. o In a variant, sounding reference signal may be used instead of pre- / mid- / post-amble signal.

[0168] • In a variant, the network may blindly determine the end of the transmission e.g. through detecting the DMRS or through energy detection (an example of the network node blindly determining the time-domain resource allocation).

[0169] Examples of UE indications are shown in and described with reference to FIGS. 6A-6C.

[0170] 6. After receiving UL transmission (an example of receiving the uplink transmission from the user equipment), network may determine the TBS of the UL transmission based on (1) allocated MCS in UL grant, (2) allocated frequency domain resource in UL grant, (3) allocated number of repetition and (4) transmission time indicated by the UE (an example of an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed).

[0171] An example implementation of a RA-SDT process is shown in and described with respect to FIG. 4.

[0172] CG-SDT

[0173] For CG-SDT, the process may be implemented in a similar manner as for RA-SDT except that the UE may be configured to use flexible-duration UL grant as part of the CG-SDT configuration (an example of a CG configuration). Subsequent to data arrival at the UE, the UE may transmit in the allocated frequency resource (1) UL data (an example of performing the uplink transmission to the network node based on the received frequencydomain resource allocation) and (2) an indication of a length or of an end of the transmission (an example of indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus).

[0174] An example implementation of a CG-SDT process is shown in and described with respect to FIG. 5. FIG. 4 shows an example of a signaling flow chart 400 between a UE 100 and a gNB 110 according to example embodiments of the present disclosure. In particular, FIG. 4 shows an example of a signaling diagram for a flexibleduration UL transmission via RA-SDT. This may include indicating a flexible-duration UL transmission configuration as part of an SDT configuration and a determination by the UE which UL transmission method to use. The flexible-duration UL transmission may be configured as part of an SDT configuration with a preamble partitioning used to indicate an UL transmission mode request. In detail:

[0175] Block 401: UE 100 is in RRC INACTIVE state (an example of an inactive communication state).

[0176] Action 402: gNB 110 transmits to UE 100, e.g. as a part of a System Information Block (SIB), an SDT configuration including a flexible-duration uplink configuration (an example of an indication that the network node is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at least in part by a user equipment), e.g. at least one of a PRACH preamble, a maximum TBS, a maximum number of symbols, a coverage enhancement level, etc.

[0177] Action 403: UE 100 determines that a flexible uplink transmission should be used (an example of determining that the uplink transmission to the network node shall be performed based on a time-domain resource allocation determined at least in part by the apparatus).

[0178] Action 404: UE 100 transmits to gNB 110, e.g. as part of a Msgl, a preamble indicating a flexible-duration UL transmission request.

[0179] Action 405: gNB 110 transmits to UE 100, e.g. as part of a Msg2, an UL grant for a flexible-duration UL transmission.

[0180] Action 406: UE 100 determines a length of the UL transmission (an example of determining, at least in part, the time-domain resource allocation).

[0181] Action 407: UE 100 transmits to gNB 110, e.g. as part of a Msg3, an RRCResumeRequest, UL data (an example of performing the uplink transmission to the network node) and an indication of the UL transmission length and / or of an end of the UL transmission (an example of indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus).

[0182] Action 408: the network determines an end of the transmission and a TBS of an uplink data packet associated with the uplink transmission (an example of determining an end of the uplink transmission and a TBS of the uplink transmission).

[0183] Action 409: gNB 110 transmits to UE 100 an RRCRelease message.

[0184] Block 410: UE 100 is in RRC IN ACTIVE state. In particular by the UE 100 determining the length of the UL transmission in action 406, the number of required uplink transmissions may advantageously be reduced to the single transmission in action 407, thereby reducing an amount of power consumed by UE 100 and saving potential excess network resources, as described in detail above. Further, in particular by the UE 100 indicating to the gNB 110 the UL transmission length and / or of an end of the UL transmission in action 407, in action 408 the gNB 110 may advantageously be able to obtain the uplink data, as described in detail above.

[0185] FIG. 5 shows a further example of a signaling flow chart 500 according to example embodiments of the present disclosure. In particular, FIG. 5 shows an example of a signaling diagram for a flexible-duration UL transmission via CG-SDT. This may include configuring a flexible-duration UL transmission as part of a CG configuration before releasing the UE into RRC inactive state. In detail:

[0186] Block 501: UE 100 is in RRC Connected state.

[0187] Action 502: UE 100 transmits to gNB 110, e.g. as a part of UE Assistance Information, a CG request.

[0188] Action 503: gNB 110 transmits to UE 100, e.g. as a part of an RRC Release message with a suspend indication, a CG configuration including a flexible-duration uplink configuration (an example of an indication that the network node is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at least in part by a user equipment), e.g. at least one of a maximum TBS, a maximum number of symbols, a coverage enhancement level, etc.

[0189] Block 504: UE 100 is in RRC INACTIVE state (an example of an inactive communication state).

[0190] Block 505: Data arrives at UE 100.

[0191] Action 506: UE 100 determines a length of the UL transmission (an example of determining, at least in part, the time-domain resource allocation).

[0192] Action 507: UE 100 transmits to gNB 110 an RRCResumeRequest, UL data (an example of performing the uplink transmission to the network node) and an indication of the UL transmission length (and / or of an end of the UL transmission) (an example of indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus).

[0193] Action 508: the network determines an end of the transmission and a TBS of an uplink data packet associated with the uplink transmission (an example of determining an end of the uplink transmission and a TBS of the uplink transmission).

[0194] Action 509: gNB 110 transmits to UE 100 an RRCRelease message.

[0195] Block 510: UE 100 is in RRC INACTIVE state. In particular by the UE 100 determining the length of the UL transmission in action 506, the number of required uplink transmissions may advantageously be reduced to the single transmission in action 507, thereby reducing an amount of power consumed by UE 100 and saving potential excess network resources, as described in detail above. Further, in particular by the UE 100 indicating to the gNB 110 the UL transmission length (and / or of an end of the UL transmission) in action 507, in action 508 the gNB 110 may advantageously be able to obtain the uplink data, as described in detail above.

[0196] FIGS. 6A-6C show schematic illustrations of various examples for indicating a time-domain resource allocation according to example embodiments of the present disclosure. In said examples, a time is respectively indicated by the direction from left to right and a frequency is respectively indicated by the direction from bottom to top, as indicated by the respective coordinate axes included in each of FIGS. 6A-6C.

[0197] In FIG. 6 A, a post-amble 610 (an example of a transmission post-amble) is appended to the end of a PUSCH transmission 600. The network may detect the post-amble to advantageously determine an end of the PUSCH transmission 600 and the number of symbols used for the PUSCH transmission 600, as described above.

[0198] In FIG. 6B, a mid-amble 620 (an example of a transmission mid-amble) is added to the PUSCH transmission 600. The mid-amble 620 is added to the end of the first PUSCH transmission 600, before the three repetitions 600a, 600b, 600c are transmitted. This may advantageously allow the network to determine the length of the transmission prior to any repetition, e.g. up to mid-amble 620, which may save an amount of data buffering required by the network.

[0199] In FIG. 6C, uplink control information 630 (an example of a transmission pre-amble and / or of uplink control information) is prepended to the PUSCH transmission 600 to indicate the length of the PUSCH transmission 600. The control information 630 may reuse an existing UCI format (e.g. CSI reporting) to indicate the length of the PUSCH transmission 600. In this case, some values may be predefined. This may advantageously allow the network to determine the length of the following PUSCH transmission 600.

[0200] FIG. 7 shows a block diagram of an example of an apparatus 100 according to the first aspect (e.g., a UE). For example, apparatus 100 may be one of a smartphone, a tablet computer, a notebook computer, a smart watch, a smart band, an loT device or a vehicle or a part thereof.

[0201] Apparatus 100 comprises a processor 101. Processor 101 may represent a single processor or two or more processors, which are for instance at least partially coupled, for instance via a bus. Processor 101 executes a program code stored in program memory 102 (for instance program code causing apparatus 100 in connection with an apparatus 110 according to the second aspect to perform one or more of the example embodiments of a method according to the present disclosure or parts thereof, when executed on processor 101, and interfaces with a main memory 103. Program memory 102 may also contain an operating system for processor 101. Some or all of memories 102 and 103 may also be included into processor 101. One of or both of a main memory and a program memory of a processor (e.g. program memory 102 and main memory 103) could be fixedly connected to the processor (e.g. processor 101) or at least partially removable from the processor, for instance in the form of a memory card or stick.

[0202] A program memory (e.g. program memory 102) may for instance be a non-volatile memory. It may for instance be a FLASH memory (or a part thereof), any of a ROM, PROM, EPROM, MRAM or a FeRAM (or a part thereof) or a hard disc (or a part thereof), to name but a few examples. For example, a program memory may for instance comprise a first memory section that is fixedly installed, and a second memory section that is removable from, for instance in the form of a removable SD memory card.

[0203] A main memory (e.g. main memory 103) may for instance be a volatile memory. It may for instance be a DRAM memory, to give non-limiting example. It may for instance be used as a working memory for processor 101 when executing an operating system, an application, a program, and / or the like.

[0204] Processor 101 further controls a communication interface 104 (e.g. radio interface) configured to receive and / or transmit data and / or information. For instance, communication interface 104 may be configured to transmit and / or receive radio signals from a network node, in particular as described herein. It is to be understood that any computer program code based processing required for receiving and / or evaluating radio signals may be stored in an own memory of communication interface 104 and executed by an own processor of communication interface 104 and / or it may be stored for example in memory 103 and executed for example by processor 101.

[0205] Communication interface 104 may in particular be configured to communicate according to a cellular communication system like a 2G / 3G / 4G / 5G or future generation cellular communication system, e.g. 6G. Apparatus 100 may use radio interface 104 to communicate with a network node.

[0206] For example, the communication interface 104 may further comprise a BLE and / or Bluetooth radio interface including a BLE transmitter, receiver or transceiver. For example, radio interface 104 may additionally or alternatively comprise a WLAN radio interface including at least a WLAN transmitter, receiver or transceiver.

[0207] The components 102 to 104 of apparatus 100 may for instance be connected with processor 101 by means of one or more serial and / or parallel busses.

[0208] It is to be understood that apparatus 100 may comprise various other components. For example, apparatus 100 may optionally comprise a user interface (e.g. a touch-sensitive display, a keyboard, a touchpad, a display, etc.).

[0209] FIG. 8 shows a block diagram of an example of an apparatus 110 according to the second aspect (e.g., a network node, for instance a base station or gNB). For instance, apparatus 110 may be configured for scheduling and / or transmitting signals to the apparatus 100, as described above.

[0210] Apparatus 110 comprises a processor 111. Processor 111 may represent a single processor or two or more processors, which are for instance at least partially coupled, for instance via a bus. Processor 111 executes a program code stored in program memory 112 (for instance program code causing apparatus 110 to perform alone or together with apparatus 100 example embodiments according to the present disclosure or parts thereof), and interfaces with a main memory 113.

[0211] Program memory 112 may also comprise an operating system for processor 111. Some or all of memories 112 and 113 may also be included into processor 111.

[0212] Moreover, processor 111 controls a communication interface 114 which is for example configured to communicate according to a cellular communication system like a 2G / 3G / 4G / 5G or future generation cellular communication system, e.g. 6G. Communication interface 114 of apparatus 110 may be realized by radio heads for instance and may be provided for communication between a network node and a user equipment.

[0213] The components 112 to 114 of apparatus 110 may for instance be connected with processor 111 by means of one or more serial and / or parallel busses.

[0214] It is to be understood that apparatuses 100, 110 may comprise various other components.

[0215] FIG. 9 shows a schematic illustration of examples of tangible and non-transitory computer-readable storage media according to the present disclosure that may for instance be used to implement memory 102 of FIG. 7 or memory 112 of FIG. 8. To this end, FIG. 9 displays a flash memory 1000, which may for instance be soldered or bonded to a printed circuit board, a solid-state drive 1001 comprising a plurality of memory chips (e.g. Flash memory chips), a magnetic hard drive 1002, a Secure Digital (SD) card 1003, a Universal Serial Bus (USB) memory stick 1004, an optical storage medium 1005 (such as for instance a CD-ROM or DVD) and a magnetic storage medium 1006.

[0216] Any presented connection in the described embodiments is to be understood in a way that the involved components are operationally coupled. Thus, the connections can be direct or indirect with any number or combination of intervening elements, and there may be merely a functional relationship between the components.

[0217] As used in this text, the term ‘circuitry’ may refer to one or more or all of the following:

[0218] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0219] (b) combinations of hardware circuits and software (and / or firmware), such as (as applicable):

[0220] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and

[0221] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

[0222] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0223] This definition of ‘circuitry’ applies to all uses of this term in this text, including in any claims. As a further example, as used in this text, the term ‘circuitry’ also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term ‘circuitry’ also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0224] Any of the processors mentioned in this text, in particular but not limited to processors 101 and 111 of FIGS. 7 and 8, could be a processor of any suitable type. Any processor may comprise but is not limited to one or more microprocessors, one or more processors) with accompanying digital signal processor(s), one or more processor(s) without accompanying digital signal processors), one or more special-purpose computer chips, one or more field- programmable gate arrays (FPGAS), one or more controllers, one or more application-specific integrated circuits (ASICS), or one or more computer(s). The relevant structure / hardware has been programmed in such a way to carry out the described function.

[0225] Moreover, any of the actions or steps described or illustrated herein may be implemented using executable instructions in a general-purpose or special-purpose processor and stored on a computer-readable storage medium (e.g., disk, memory, or the like) to be executed by such a processor. References to ‘computer-readable storage medium’ should be understood to encompass specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices.

[0226] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0227] The wording “A, or B, or C, or a combination thereof’ or “at least one of A, B and C” or “at least one of A, B or C” or “A, B, and / or C” may be understood to be not exhaustive and to include at least the following: (i) A, or (ii) B, or (iii) C, or (iv) A and B, or (v) A and C, or (vi) B and C, or (vii) A and B and C.

[0228] It will be understood that the embodiments disclosed herein are only example, and that any feature presented for a particular example embodiment may be used with any aspect of the present disclosure on its own or in combination with any feature presented for the same or another particular example embodiment and / or in combination with any other feature not mentioned. It will further be understood that any feature presented for an example embodiment in a particular category may also be used in a corresponding manner in an example embodiment of any other category.

[0229] List of abbreviations

[0230] B WP Bandwidth Part

[0231] CE Coverage Enhancement

[0232] CG-SDT Configured Grant Small Data Transmission

[0233] DL Downlink

[0234] DMRS Demodulation Reference Signal

[0235] FR1 Frequency Range 1

[0236] FR2 Frequency Range 2 gNB Next generation Node-B loT Internet of things

[0237] LCG Logical Channel Group

[0238] LPWA Low Power Wide Area

[0239] MCS Modulation and Coding Scheme

[0240] NB-IoT Narrowband Internet of Things

[0241] NR New Radio

[0242] NW Network

[0243] PRACH Physical Random Access Channel

[0244] RA-SDT Random Access Small Data Transmission

[0245] RSRP Reference Signal Received Power

[0246] SDT Small Data Transmission

[0247] SIB System Information Block

[0248] SRS Sounding Reference Signal

[0249] TBS Transport Block Size

[0250] TTI Transmission Time Interval

[0251] UE User Equipment

[0252] UL Uplink

Claims

C l i m s1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from a network node, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the network node; performing the uplink transmission to the network node based on the received frequency-domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus; and indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus.

2. The apparatus of claim 1, wherein the time-domain resource allocation determined at least in part by the apparatus corresponds to at least one of: o a duration of the uplink transmission; o a length of the uplink transmission; o an end of the uplink transmission; o a number of symbols of the uplink transmission; o a number of slots of the uplink transmission; o a number of Transmission Time Intervals, TTIs, of the uplink transmission; or o a Transport Block Size, TBS, of the uplink transmission.

3. The apparatus of any of claims 1 or 2, wherein the time-domain resource allocation determined at least in part by the apparatus is indicated to the network node by means of at least one of: o a transmission pre-amble transmitted prior to the uplink transmission; o a transmission mid-amble transmitted during the uplink transmission; o a transmission post-amble transmitted after the uplink transmission; o a Medium Access Control, MAC, sub-header associated with the uplink transmission; o uplink control information; or o a Sounding Reference Signal, SRS.

4. The apparatus of any of claims 1 to 3, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform:35determining that the uplink transmission to the network node shall be performed based on a timedomain resource allocation determined at least in part by the apparatus based on at least one of: o a coverage enhancement level associated with the apparatus; o a data buffer status of a data buffer of the apparatus; o an energy level of the apparatus; o at least one characteristic of one or more further uplink transmissions performed by the apparatus prior to the uplink transmission to the network node; o a latency requirement or priority level associated with uplink data to be transmitted as part of the uplink transmission to the network node; o a duplex capability of the apparatus; o a time-frequency tracking performance of the apparatus; or o a Reference Signal Received Power, RSRP, measured by the apparatus.

5. The apparatus of any of claims 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform: receiving, from the network node, an indication that the network node is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at least in part by a user equipment.

6. The apparatus of any of claims 1 to 5, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform: obtaining an indication of at least one predetermined condition to be satisfied by the time-domain resource allocation, wherein the at least one predetermined condition corresponds to at least one of: o a maximum duration of the uplink transmission; o a maximum length of the uplink transmission; o a latest end of the uplink transmission; o a maximum number of symbols of the uplink transmission; o a maximum number of slots of the uplink transmission; o a maximum number of Transmission Time Intervals, TTIs, of the uplink transmission; or o a maximum Transport Block Size, TBS, of the uplink transmission.

7. The apparatus of any of claims 1 to 6, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform: obtaining an indication of a starting time-domain resource to be used for performing the uplink transmission, wherein the starting time-domain resource corresponds to a starting symbol, a starting slot or a starting TTI to be used for performing the uplink transmission.

8. The apparatus of any of claims 5 to 7, wherein the indication that the network node is configured for receiving an uplink transmission performed based on a time-domain resource allocation determined at36least in part by a user equipment, the indication of at least one predetermined condition to be satisfied by the time-domain resource allocation and / or the indication of a starting time-domain resource to be used for performing the uplink transmission is obtained as part of at least one of: o a Small Data Transmission, SDT, configuration; o a Random Access, RA, configuration; o a Configured Grant, CG, configuration; or o uplink transmission scheduling information.

9. The apparatus of any of claims 1 to 8, wherein the uplink transmission to the network node is further performed based on uplink transmission configuration information or uplink transmission scheduling information received from the network node, wherein the uplink transmission configuration information or the uplink transmission scheduling information indicates at least one of: o the frequency -domain resource allocation for performing the uplink transmission; o a Modulation and Coding Scheme, MCS, to be used for the uplink transmission; or o a number of repetitions to be used for the uplink transmission.

10. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: transmitting, to a user equipment, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the apparatus; receiving the uplink transmission from the user equipment; receiving, from the user equipment, an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed; and- based on the indication, determining at least one of: o a duration of the uplink transmission; o a length of the uplink transmission; o an end of the uplink transmission; o a number of symbols of the uplink transmission; o a number of slots of the uplink transmission; o a number of Transmission Time Intervals, TTIs, of the uplink transmission; or o a Transport Block Size, TBS, of the uplink transmission.

11. A method, performed by an apparatus, the method comprising: receiving, from a network node, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the network node;performing the uplink transmission to the network node based on the received frequency -domain resource allocation and based on a time-domain resource allocation determined at least in part by the apparatus; and indicating, to the network node, the time-domain resource allocation determined at least in part by the apparatus.

12. A method, performed by an apparatus, the method comprising: transmitting, to a user equipment, a frequency -domain resource allocation for performing, as part of a Small Data Transmission, SDT, procedure, an uplink transmission to the apparatus; receiving the uplink transmission from the user equipment; receiving, from the user equipment, an indication indicating a time-domain resource allocation determined at least in part by the user equipment and based on which the uplink transmission is performed; and- based on the indication, determining at least one of: o a duration of the uplink transmission; o a length of the uplink transmission; o an end of the uplink transmission; o a number of symbols of the uplink transmission; o a number of slots of the uplink transmission; o a number of Transmission Time Intervals, TTIs, of the uplink transmission; or o a Transport Block Size, TBS, of the uplink transmission.

13. A computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform the method of any of claims 11 or 12.

14. A computer-readable storage medium having stored thereon the computer program of claim 13.

Images