WO2022269126A1

WO2022269126A1 - Small data transmission adaptation

Info

Publication number: WO2022269126A1
Application number: PCT/FI2022/050402
Authority: WO
Inventors: Daniela Laselva; Jorma Johannes KAIKKONEN
Original assignee: Nokia Technologies Oy
Priority date: 2021-06-23
Filing date: 2022-06-10
Publication date: 2022-12-29
Also published as: EP4360394A1; CN117546591A

Abstract

Devices, methods and computer programs for adapting a small data transmission are disclosed. An SDT adaptation parameter is received at a client device (200) from a network node device (210) during an ongoing small data transmission, SDT, procedure with the network node device (210). The client device (200) determines a preconfigured SDT adaptation operation associated with the received SDT adaptation parameter, and the client device (200) adapts the ongoing SDT procedure in accordance with the determined SDT adaptation operation.

Description

SMALL DATA TRANSMISSION ADAPTATION

TECHNICAL FIELD

The disclosure relates generally to communica tions and, more particularly but not exclusively, to small data transmission adaptation.

BACKGROUND

Fifth generation (5G) new radio (NR) wireless networks allow so called small data transmissions (SDTs) to convey packet data transmissions while a client de vice or a user equipment (UE) is in a radio resource control (RRC) inactive state. Furthermore, it is possi ble for the client device to send multiple uplink, UL, and/or downlink, DL, subsequent transmissions after a first UL SDT without transitioning the client device to an RRC connected state, i.e. as part of a same ongoing SDT procedure or transaction.

However, at least in some situations, the SDT procedure may currently not be as power efficient as might be desirable. For example, during an SDT proce dure, after the client device has performed a first UL SDT in the RRC inactive state, the client device may have to perform continuous physical downlink control channel, PDCCH, monitoring e.g., in a random access com mon search space (RA-CSS), i.e. type 1 PDCCH common search space, because the client device may receive, e.g., a DL acknowledgment for an UL payload that the client device has sent, and/or a UL/DL scheduling grant for subsequent UL/DL data transmissions as part of the same SDT procedure without transition to the RRC con nected mode, and/or an RRC release message to end the ongoing SDT procedure. Such continuous PDCCH monitoring consumes client device power and, thus, is not desirable for the RRC inactive state, which is designed to be a power efficient state. SUMMARY

The scope of protection sought for various ex ample embodiments of the invention is set out by the independent claims. The example embodiments and fea tures, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various example embodiments of the invention.

An example embodiment of a client device com prises at least one processor, and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the client device to at least perform: during an ongoing small data transmission, SDT, procedure with a network node device, receiving from the network node device an SDT adaptation parameter; determining a preconfigured SDT adaptation op eration associated with the received SDT adaptation pa rameter; and adapting the ongoing SDT procedure in accord ance with the determined SDT adaptation operation.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the SDT adaptation parameter comprises a scheduling slot offset value or time domain resource assignment infor mation.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the scheduling slot offset value comprises a value of an uplink scheduling slot offset K2 or a value of a downlink scheduling slot offset K0.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the time domain resource assignment information comprises an indication of a row index of a time domain resource assignment table.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the adapting of the ongoing SDT procedure comprises adapting physical downlink control channel, PDCCH, monitoring used by the client device during the ongoing SDT proce dure.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the adapting of the PDCCH monitoring used by the client device during the ongoing SDT procedure comprises using by the client device at least one of: a dedicated search space, a dedicated search space group, or a dedicated PDCCH monitoring skipping configuration.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the adapting of the ongoing SDT procedure comprises switch ing to a separate SDT bandwidth part for the ongoing SDT procedure.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the determining of the preconfigured SDT adaptation opera tion associated with the received SDT adaptation param eter comprises performing a search for the received SDT adaptation parameter in a data structure comprising map pings between SDT adaptation parameters and associated SDT adaptation operations.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the client device to perform the receiving of the SDT adaptation parameter by receiving the SDT adaptation parameter in one of: link scheduling grant information, downlink control information, or a control element of medium access control. An example embodiment of a client device com prises means for performing: during an ongoing small data transmission, SDT, procedure with a network node device, causing the client device to receive from the network node device an SDT adaptation parameter; determining a preconfigured SDT adaptation op eration associated with the received SDT adaptation pa rameter; and adapting the ongoing SDT procedure in accord ance with the determined SDT adaptation operation.

An example embodiment of a method comprises: during an ongoing small data transmission, SDT, procedure with a network node device, receiving at a client device from the network node device an SDT adap tation parameter; determining, by the client device, a precon figured SDT adaptation operation associated with the received SDT adaptation parameter; and adapting, by the client device, the ongoing SDT procedure in accordance with the determined SDT adapta tion operation.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the time domain resource assignment information comprises an indication of a row index of a time domain resource assignment table. In an example embodiment, alternatively or in addition to the above-described example embodiments, the adapting of the ongoing SDT procedure comprises adapting physical downlink control channel, PDCCH, monitoring used by the client device during the ongoing SDT proce dure.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the method further comprises performing the receiving of the SDT adaptation parameter by receiving the SDT adaptation parameter in one of: link scheduling grant information, downlink control information, or a control element of medium access control.

An example embodiment of a computer program comprises instructions for causing a client device to perform at least the following: during an ongoing small data transmission, SDT, procedure with a network node device, receiving from the network node device an SDT adaptation parameter; determining a preconfigured SDT adaptation op eration associated with the received SDT adaptation pa rameter; and adapting the ongoing SDT procedure in accord ance with the determined SDT adaptation operation.

An example embodiment of a network node device comprises at least one processor, and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the network node device to at least perform: detecting a need to adapt an ongoing small data transmission, SDT, procedure with a client device; selecting a preconfigured SDT adaptation oper ation for the detected need; and transmitting to the client device an SDT adap tation parameter associated with the selected SDT adap tation operation.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the detecting of the need to adapt the ongoing SDT procedure is performed based on information about at least one of: network load, downlink traffic, or uplink traffic.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the selecting of the preconfigured SDT adaptation operation is performed by selecting the preconfigured SDT adapta tion operation from a data structure comprising mappings between SDT adaptation operations and associated SDT adaptation parameters.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network node device to perform: transmitting to the client device SDT config uration information comprising the data structure.

An example embodiment of a network node device comprises means for performing: detecting a need to adapt an ongoing small data transmission, SDT, procedure with a client device; selecting a preconfigured SDT adaptation oper ation for the detected need; and causing the network node device to transmit to the client device an SDT adaptation parameter associated with the selected SDT adaptation operation.

An example embodiment of a method comprises: detecting, by a network node device, a need to adapt an ongoing small data transmission, SDT, procedure with a client device; selecting, by the network node device, a pre configured SDT adaptation operation for the detected need; and transmitting, by the network node device, to the client device an SDT adaptation parameter associated with the determined SDT adaptation operation.

In an example embodiment, alternatively or in addition to the above-described example embodiments, the selecting of the preconfigured SDT adaptation operation is performed by selecting the preconfigured SDT adapta tion operation from a data structure comprising mappings between SDT adaptation operations and associated SDT adaptation parameters. In an example embodiment, alternatively or in addition to the above-described example embodiments, the method further comprises: transmitting to the client device SDT config uration information comprising the data structure.

An example embodiment of a computer program comprises instructions for causing a network node device to perform at least the following detecting a need to adapt an ongoing small data transmission, SDT, procedure with a client device; selecting a preconfigured SDT adaptation oper ation for the detected need; and transmitting to the client device an SDT adap tation parameter associated with the determined SDT ad aptation operation.

DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the embodiments and constitute a part of this specification, illustrate embodiments and together with the description help to explain the principles of the embodiments. In the draw ings:

FIG. 1 shows an example embodiment of the sub ject matter described herein illustrating an example system, where various embodiments of the present dis closure may be implemented;

FIG. 2A shows an example embodiment of the sub ject matter described herein illustrating a client de vice;

FIG. 2B shows an example embodiment of the sub ject matter described herein illustrating a network node device;

FIG. 3 shows an example embodiment of the sub ject matter described herein illustrating a method; and FIG. 4 shows an example embodiment of the sub ject matter described herein illustrating another method.

Like reference numerals are used to designate like parts in the accompanying drawings.

DETAILED DESCRIPTION

Reference will now be made in detail to embod iments, examples of which are illustrated in the accom panying drawings. The detailed description provided be low in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the pre sent example may be constructed or utilized. The de scription sets forth the functions of the example and the sequence of steps for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.

Fig. 1 illustrates an example system 100, where various embodiments of the present disclosure may be implemented. The system 100 may comprise a fifth gener ation (5G) new radio (NR) network 110. An example rep resentation of the system 100 is shown depicting a cli ent device 200 and a network node device 210. At least in some embodiments, the 5G NR network 110 may comprise one or more massive machine-to-machine (M2M) network(s), massive machine type communications (mMTC) network(s), internet of things (IoT) network(s), industrial inter- net-of-things (IIoT) network(s), enhanced mobile broad band (eMBB) network(s), ultra-reliable low-latency com munication (URLLC) network(s), and/or the like. In other words, the 5G NR network 110 may be configured to serve diverse service types and/or use cases, and it may log ically be seen as comprising one or more networks.

Small data transmissions (SDTs) may be used in the 5G NR wireless network 110 to convey packet data transmissions while the client device 200 is in an in active state of RRC. An SDT can be used during the RRC inactive state without need for a state transition to a connected state of RRC. Alternatively/additionally, in at least some embodiments an SDT can be used during an RRC idle state and/or in yet another non-connected RRC state without need for a state transition to a connected state of RRC. Herein, RRC states include the connected state of RRC, an idle state of RRC, and the inactive state of RRC. For example, the inactive state of RRC may comprise RRC_INACTIVE state of 5G NR, the idle state of RRC may comprise RRC_IDLE state of 5G NR, and the con nected state of RRC may comprise RRC_CONNECTED state of 5G NR. The RRC_INACTIVE state of 5G NR is designed to complement the existing states, RRC_CONNECTED and RRC_IDLE, with the goal of lean signalling and energy- efficient support of NR services. The RRC_INACTIVE state currently allows to more quickly resume the connection and start the transmission of small or sporadic data with a much lower initial access delay and associated signalling overhead as compared to the RRC_IDLE state. This is achieved, e.g., via reduced control signalling required for requesting and obtaining the resumption of a suspended RRC connection, which results in client de vice power saving. At the same time, a client device in RRC_INACTIVE is able to achieve similar power savings as in RRC_IDLE, benefiting from e.g., a much larger period of physical downlink control channel (PDCCH) mon itoring (e.g., infrequent paging monitoring as per net work configuration) and relaxed radio resource manage ment (RRM) measurements of the serving cell / neighbor cells compared to RRC_CONNECTED.

SDTs may be used, e.g., for traffic from smartphone applications, including traffic from instant messaging (IM) services, heart-beat/keep-alive traffic from IM/email clients and other applications, push no tifications from various applications, and/or traffic from wearable devices (such as periodic positioning in formation, etc.)_/ traffic from sensors (such as indus trial wireless sensor networks transmitting tempera ture, pressure readings, etc. periodically or in an event triggered manner), traffic from smart meters and smart meter networks sending periodic meter readings, and the like.

The client device 200 may include, e.g., a mo bile phone, a smartphone, a tablet computer, a smart watch, or any hand-held or portable device. The client device 200 may also be referred to as a user equipment (UE). The network node device 210 may be a base station. The base station may include, e.g., a fifth-generation base station (gNB) or any such device suitable for providing an air interface for client devices to connect to a wireless network via wireless transmissions.

Herein, SDTs may include RA-SDTs (a client de vice in an RRC inactive state can transmit UL data as part of random access (RA)) and/or CG-SDTs (a client device in an RRC inactive state can transmit UL data on preconfigured physical uplink shared channel (PUSCH) resources (i.e., configured grant (CG) type 1 based PUSCH resources) without a random access procedure when the client device has a valid timing advance (TA)).

Herein, scheduling slot offset values relate to cross-slot scheduling for 5G NR, defining that a downlink control information (DCI) carrying the resource allocation for a DL data reception and a UL data trans mission may have a "slot offset" to its allocation in a physical downlink data shared channel (PDSCH) (i.e., DL scheduling slot offset K0) and in a physical uplink data shared channel (PUSCH) (i.e., UL scheduling slot offset K2). Minimum values for the scheduling slot offsets K0 (KO_rain) and K2 (K2_min) may be determined, e.g., via RRC signalling as: o minimumSchedulingOf fsetKO-rl6 in a PDSCH-Config information element (IE); and o minimumSchedulingOf fsetK2-rl6 in a PUSCH-Config IE.

Herein, a single-shot SDT procedure refers to an SDT procedure that includes only a single UL data transmission. Optionally, the single-shot SDT procedure may also include a single DL data transmission. A multi shot SDT procedure refers to an SDT procedure that in cludes multiple subsequent UL/DL data transmissions (oc curring in RRC_Inactive without transitioning to RRC_CONNECTED) . A two-shot SDT procedure is an example of a multi-shot SDT procedure.

In the following, various example embodiments will be discussed. At least some of these example em bodiments may allow adapting a small data transmission. More specifically, at least some of these example em bodiments may allow a network-based adaptation of SDTs (e.g., adaptation of a PDCCH monitoring pattern) that the client device 200 is to use during an SDT procedure, such that the network (e.g., the network node device 210) can adapt the PDCCH monitoring pattern implicitly, based on a scheduling slot offset (e.g., K0, K2) value and/or time domain resource assignment information. Herein, implicitly means that the network does not need to send an explicit command, thereby allowing avoiding additional network node device 210 transmissions and client device 200 receptions during SDTs for the SDT adaptation. The network decision on the SDT adaptation may be based, e.g., on network load and DL/UL traffic knowledge. Likewise, the scheduling slot offset value and time domain resource assignment information may be used to command the client device 200 to switch to a separate UL bandwidth part (BWP) or to a separate DL BWP for the SDT(s).

Fig. 2A is a block diagram of the client device 200, in accordance with an example embodiment. The client device 200 comprises one or more processors 202 and one or more memories 204 that com prise computer program code. The client device 200 may also include other elements, such as a transceiver 206 configured to enable the client device 200 to transmit and/or receive information to/from other devices, as well as other elements not shown in Fig. 2A. In one example, the client device 200 may use the transceiver 206 to transmit or receive signaling information and data in accordance with at least one cellular communi cation protocol. The transceiver 206 may be configured to provide at least one wireless radio connection, such as for example a 3GPP mobile broadband connection (e.g., 5G). The transceiver 206 may comprise, or be configured to be coupled to, at least one antenna to transmit and/or receive radio frequency signals.

Although the client device 200 is depicted to include only one processor 202, the client device 200 may include more processors. In an embodiment, the memory 204 is capable of storing instructions, such as an operating system and/or various applications. Fur thermore, the memory 204 may include a storage that may be used to store, e.g., at least some of the information and data used in the disclosed embodiments.

Furthermore, the processor 202 is capable of executing the stored instructions. In an embodiment, the processor 202 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core pro cessors. For example, the processor 202 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for ex ample, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a mi crocontroller unit (MCU), a hardware accelerator, a spe cial-purpose computer chip, or the like. In an embodi ment, the processor 202 may be configured to execute hard-coded functionality. In an embodiment, the proces sor 202 is embodied as an executor of software instruc tions, wherein the instructions may specifically con figure the processor 202 to perform the algorithms and/or operations described herein when the instructions are executed.

The memory 204 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For ex ample, the memory 204 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

The client device 200 may comprise any of var ious types of devices used directly by an end user entity and capable of communication in a wireless network, such as user equipment (UE). Such devices include but are not limited to smartphones, tablet computers, smart watches, lap top computers, internet-of-things (IoT) devices, massive machine-to-machine (M2M) devices, massive ma chine type communications (mMTC) devices, industrial internet-of-things (IIoT) devices, enhanced mobile broadband (eMBB) devices, ultra-reliable low-latency communication (URLLC) devices, etc.

The at least one memory 204 and the computer program code are configured to, with the at least one processor 202, cause the client device 200 to at least perform receiving from the network node device 210 an SDT adaptation parameter, during an ongoing SDT proce dure with the network node device 210. In at least some embodiments, the at least one memory 204 and the computer program code may be further configured to, with the at least one processor 202, cause the client device 200 to perform the receiving of the SDT adaptation parameter by receiving the SDT adaptation parameter in one of link scheduling grant information, downlink con trol information (DCI), or a control element (CE) of medium access control (MAC).

For example, the SDT adaptation parameter may comprise a scheduling slot offset value or time domain resource assignment information. In at least some em bodiments, the scheduling slot offset value may comprise a value of an uplink scheduling slot offset K2 or a value of a downlink scheduling slot offset K0. In at least some embodiments, the time domain resource as signment information comprises an indication of a row index of a time domain resource assignment table.

The at least one memory 204 and the computer program code are further configured to, with the at least one processor 202, cause the client device 200 to perform determining a preconfigured SDT adaptation op eration that is associated with the received SDT adap tation parameter.

For example, the determining of the preconfig ured SDT adaptation operation associated with the re ceived SDT adaptation parameter may comprise performing a search for the received SDT adaptation parameter in a data structure comprising mappings between SDT adapta tion parameters and associated SDT adaptation opera tions.

In other words, an association between given UL scheduling slot offset K2 values and given PDCCH monitoring patterns and/or an association between given DL scheduling slot offset K0 values and given PDCCH monitoring patterns may be predefined (e.g., by the net work node device 210, by some other network entity) and provided as the data structure to the client device 200 and/or the network node device 210. Alternatively, the association (s) may be stored as the data structure at the client device 200 and/or the network node device 210 at manufacturing or deployment.

The at least one memory 204 and the computer program code are further configured to, with the at least one processor 202, cause the client device 200 to perform adapting the ongoing SDT procedure in accordance with the determined SDT adaptation operation.

For example, the adapting of the ongoing SDT procedure may comprise adapting physical downlink con trol channel, PDCCH, monitoring used by the client de vice 200 during the ongoing SDT procedure. Alterna tively, the adapting of the ongoing SDT procedure may comprise switching to a separate SDT bandwidth part for the ongoing SDT procedure.

In at least some embodiments, the adapting of the PDCCH monitoring used by the client device 200 during the ongoing SDT procedure may comprise using by the client device 200 at least one of: a dedicated search space, a dedicated search space group, or a dedicated PDCCH monitoring skipping configuration.

In at least some embodiments, the PDCCH moni toring may be performed according to a PDCCH monitoring pattern. The PDCCH monitoring pattern may comprise a search space (SS), a search space set, and/or a search space group dedicated to SDT or configured to be used during SDT.

In other words, the provisioning to the client device 200 of, e.g., an UL grant DCI during the SDT including a scheduling offset K2 value may trigger the client device 200 to apply the associated PDCCH moni toring pattern. Similarly, the provisioning to the cli ent device 200 of, e.g., a DL grant DCI during the SDT including a scheduling offset K0 value may trigger the client device 200 to apply the associated PDCCH moni toring pattern.

In at least some embodiments, the K2 may have up to, e.g., 16 (32) values, and up to 16 (32) search space configurations may be mapped in total. Similarly, in at least some embodiments, the K0 may have up to, e.g., 16 (32) values, and up to 16 (32) search space configurations may be mapped in total.

For example, the first value of K2 (e.g., slot 1) may be mapped to a PDCCH monitoring pattern 1, the second value of K2 (e.g., slot 2) may be mapped to a PDCCH monitoring pattern 2, and so on. For example, the lower values of K2 may be associated to PDCCH monitoring patterns having shorter monitoring period and vice- versa.

For example, the first value of K0 (e.g., slot 0) may be mapped to a PDCCH monitoring pattern 1, the second value of K0 (e.g., slot 2) may be mapped to a PDCCH monitoring pattern 2, and so on. For example, the lower values of K0 may be associated to PDCCH monitoring patterns having shorter monitoring period and vice- versa.

In at least some embodiments, K2=N may implic itly indicate that no PDCCH transmissions are to be expected for M consecutive slots (e.g., M³N), thus the client device 200 may skip monitoring for the M consec utive slots. For example, K2=N may be mapped to a PDCCH monitoring skipping configuration indicating the skip ping of M slots.

In at least some embodiments, K0=N may implic itly indicate that no PDCCH transmissions are to be expected for M consecutive slots (e.g., M³N), thus the client device 200 may skip monitoring for the M consec utive slots. For example, K0=N may be mapped to a PDCCH monitoring skipping configuration indicating the skip ping of M slots.

In at least some embodiments, a default value of minimumSchedulingOffsetK2-rl6 may be used for SDT (e.g., slots > 1) and may be mapped to a default PDCCH monitoring pattern. For example, the client device 200 may apply such a default pattern upon sending a physical random access channel (PRACH) preamble specific to SDT.

In at least some embodiments, a default value of minimumSchedulingOffsetKO-rl6 may be used for SDT (e.g., slots > 1) and may be mapped to a default PDCCH monitoring pattern. For example, the client device 200 may apply such a default pattern upon sending a PRACH preamble specific to SDT.

In at least some embodiments, the K2 value cho sen and sent by the network node device 210 may depend on the DL/UL traffic knowledge. For example, if no fur ther UL data is present (i.e., the current UL grant is able to accommodate all the UL data indicated in a buffer status report (BSR)) but the network node device 210 decides not to terminate the SDT procedure yet (e.g., due to waiting for potential DL data to arrive), the network node device 210 may indicate to the client de vice 200 to switch to a monitoring pattern allowing for a sparser monitoring to save power by using a larger K2 value as configured/defined. As another example, if fur ther UL data is present (i.e., the current UL grant cannot accommodate all the UL data indicated in the BSR), the network node device 210 may select and send a lower K2 value such that the client device 200 may apply an SS with a short(er) periodicity.

In at least some embodiments, the K0 value cho sen and sent by the network node device 210 may depend on the DL/UL traffic knowledge. For example, if no fur ther UL data is present (i.e., no BSR was provided by the client device 200) and no further DL data is present (all the DL data can be accommodated with the current DL grant) but the network node device 210 decides not to terminate the SDT procedure yet (e.g., due to waiting for potential DL data to arrive), the network node de vice 210 may indicate to the client device 200 to switch to a monitoring pattern allowing for a sparser monitor ing to save power by using a larger K0/K2 value as configured/defined .

In at least some embodiments, the K2 value cho sen and sent by the network node device 210 may depend on the network load. For example, at a higher load, a lower K2 value may be used resulting in more frequent PDCCH monitoring in order to have larger scheduling flexibility, and vice versa.

In at least some embodiments, the K0 value cho sen and sent by the network node device 210 may depend on the network load. For example, at a higher load, a lower K0 value may be used resulting in more frequent PDCCH monitoring in order to have larger scheduling flexibility, and vice versa.

In at least some embodiments, the association between given scheduling slot offset K0/K2 values and given PDCCH monitoring patterns may be defined dedicat- edly for CG-SDT and RA-SDT.

In at least some embodiments, the PDSCH / PUSCH time domain resource assignment values (e.g., the row indexes pointing to sets of values in a time domain resource assignment (TDRA) table) may be associated with given PDCCH search space configurations. If a corre sponding time domain allocation value is indicated by a DCI (via a time domain resource assignment field), the client device 200 may apply a corresponding PDCCH search space configuration. For example, dedicated row indexes and/or search space parameters may be predefined in the TDRA tables to be used for SDT if indicated by the network / network node device 210. In one example, de fault search space parameters may be predefined for SDT.

In at least some embodiments, a subset of the scheduling offsets (K0 and/or K2) or time domain resource assignment row indexes may be associated to given search space configurations, while other schedul ing offsets may not be associated to any specific search space configurations. If the client device 200 is pro vided an indication via a DCI (e.g., a K0 corresponding to a given search space configuration), the client de vice 200 may apply it. On the other hand, if the client device 200 is provided, e.g., a K0 that is not specif ically associated to any search space configuration, the client device 200 may keep the search space configura tion unchanged.

In at least some embodiments, given scheduling offsets (K0 and/or K2) and/or a time domain resource assignment row index may be associated to, and trigger, the switch to a separate UL BWP / DL BWP to be used during SDT, e.g., a BWP larger than an initial BWP for the transmission of larger payloads. Alternatively or additionally, certain scheduling offsets (K0 and/or K2) and/or time domain resource assignment row index may be associated to, and trigger, both the switch to the sep arate UL BWP / DL BWP dedicated to SDT and the switch to a given search space configuration to be applied by the client device 200.

Fig. 2B is a block diagram of a network node device 210, in accordance with an example embodiment.

The network node device 210 comprises at least one processor 212 and at least one memory 214 including computer program code. The network node device 210 may also include other elements, such as a transceiver 216 configured to enable the network node device 210 to transmit and/or receive information to/from other de vices, as well as other elements not shown in Fig. 2B. In one example, the network node device 210 may use the transceiver 216 to transmit or receive signaling infor mation and data in accordance with at least one cellular communication protocol. The transceiver 216 may be con figured to provide at least one wireless radio connec tion, such as for example a 3GPP mobile broadband con nection (e.g., 5G). The transceiver 216 may comprise, or be configured to be coupled to, at least one antenna to transmit and/or receive radio frequency signals.

Although the network node device 210 is de picted to include only one processor 212, the network node device 210 may include more processors. In an em bodiment, the memory 214 is capable of storing instruc tions, such as an operating system and/or various ap plications. Furthermore, the memory 214 may include a storage that may be used to store, e.g., at least some of the information and data used in the disclosed embodiments.

Furthermore, the processor 212 is capable of executing the stored instructions. In an embodiment, the processor 212 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core pro cessors. For example, the processor 212 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for ex ample, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a mi crocontroller unit (MCU), a hardware accelerator, a spe cial-purpose computer chip, or the like. In an embodi ment, the processor 212 may be configured to execute hard-coded functionality. In an embodiment, the proces sor 212 is embodied as an executor of software instruc tions, wherein the instructions may specifically con figure the processor 212 to perform the algorithms and/or operations described herein when the instructions are executed.

The memory 214 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For ex ample, the memory 214 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

The network node device 210 may comprise a base station. The base station may include, e.g., a fifth- generation base station (gNB) or any such device provid ing an air interface for client devices to connect to the wireless network via wireless transmissions.

The at least one memory 214 and the computer program code are configured to, with the at least one processor 212, cause the network node device 210 to at least perform detecting a need to adapt an ongoing SDT procedure with the client device 200.

For example, the detecting of the need to adapt the ongoing SDT procedure may be performed based on information about network load, downlink traffic, and/or uplink traffic.

The at least one memory 214 and the computer program code are further configured to, with the at least one processor 212, cause the network node device 210 to perform selecting a preconfigured SDT adaptation operation for the detected need.

For example, the selecting of the preconfigured SDT adaptation operation may be performed by selecting the preconfigured SDT adaptation operation from a data structure comprising mappings between SDT adaptation operations and associated SDT adaptation parameters.

The at least one memory 214 and the computer program code are further configured to, with the at least one processor 212, cause the network node device 210 to perform transmitting to the client device 200 an SDT adaptation parameter associated with the selected SDT adaptation operation. As discussed above, the SDT adaptation parameter may be transmitted, e.g., in one of link scheduling grant information, downlink control information (DCI), or a control element (CE) of medium access control (MAC).

In at least some embodiments, the at least one memory 214 and the computer program code may be further configured to, with the at least one processor 212, cause the network node device 210 to perform transmit ting to the client device 200 SDT configuration infor mation comprising the data structure.

Further features (such as those related to the SDT adaptation parameter, the scheduling slot offset value, the data structure, and the time domain resource assignment information) of the network node device 210 directly result from the functionalities and parameters of the client device 200 and thus are not repeated here.

Fig. 3 illustrates an example signalling dia gram 300 of a method, in accordance with an example embodiment.

At optional operation 301, the network node device 210 may transmit to the client device 200 SDT configuration information that comprises a data struc ture. The data structure comprises mappings between SDT adaptation operations and associated SDT adaptation parameters. The network node device 210 may retain a copy of the data structure for later use, e.g., in op erations 304 and/or 306 below.

At optional operation 302, client device 200 may start an SDT procedure.

At operation 303, the network node device 210 detects a need to adapt the ongoing SDT procedure (e.g., the SDT procedure started at operation 302) with the client device 200.

At operation 304, the network node device 210 selects a preconfigured SDT adaptation operation for the detected need, e.g., by selecting the preconfigured SDT adaptation operation from the data structure comprising the mappings between the SDT adaptation operations and the associated SDT adaptation parameters. At operation 305, the network node device 210 transmits to the client device 200 an SDT adaptation parameter associated with the determined SDT adaptation operation. Further at operation 305, the client device 200 receives the transmitted SDT adaptation parameter.

At operation 306, the client device 200 deter mines the preconfigured SDT adaptation operation asso ciated with the received SDT adaptation parameter, e.g., by performing a search for the received SDT adaptation parameter in a data structure comprising mappings between SDT adaptation parameters and associated SDT adaptation operations (such as the data structure re ceived at operation 301).

At operation 307, the client device 200 adapts the ongoing SDT procedure in accordance with the deter mined SDT adaptation operation.

The method of diagram 300 may be performed by the client device 200 of Fig. 2A and the network node device 210 of Fig. 2B. The operations 301, 303-305 can, for example, be performed by the at least one processor 212 and the at least one memory 214. The operations 301- 302, 305-307 can, for example, be performed by the at least one processor 202 and the at least one memory 204. Further features of the method of diagram 300 directly result from the functionalities and parameters of the client device 200 and the network node device 210, and thus are not repeated here. The method of diagram 300 can be performed by computer program (s).

Fig. 4 illustrates an example signalling dia gram 400 of another method, in accordance with an exam ple embodiment. More specifically, diagram 400 of Fig. 4 illustrates a case in which the client device initi ates a two-shot SDT (with subsequent UL data) in a last serving cell.

At first, the client device 200 is in an RRC connected state. At optional operation 401, the network node device 210 may transmit to the client device 200 SDT configuration information that comprises a data struc ture comprising mappings between SDT adaptation operations (e.g., PDCCH monitoring patterns) and associated SDT adaptation parameters (e.g. K2/K0 values).

Then, the client device 200 transitions to an RRC inactive state.

At optional operation 402, the client device 200 may perform a first SDT, including an UL payload and a BSR.

At optional operation 403, the network node device 210 may decode a medium access control (MAC) protocol data unit (PDU) and send an early contention resolution (CR).

At optional operation 404, the network node device 210 may transmit to the client device 200 an SDT specific search space (SDT-SS) in a system information block (SIB).

At optional operation 405, the network node device 210 may transmit the early contention resolution to the client device 200.

At optional operation 406, the client device 200 may apply a common search space for SDT (SDT-CSS) upon the CR.

At optional operation 407, the network node device 210 may account for the SDT-CSS upon the CR.

At operation 408, the network node device 210 transmits to the client device 200 an SDT adaptation parameter (K2=N) associated with the determined SDT ad aptation operation (PDCCH monitoring skipping M slots).

At operation 409, the client device 200 applies PDCCH monitoring skipping for M slots, as associated with the received K2 value. After the M slots, the client device 200 may apply, e.g., a default search space for SDT as predefined/configured by the network node device 210 during operation 401.

At optional operation 410, the network node device 210 may take into account the PDCCH monitoring skipping of M slots, i.e., the network node device 210 may not transmit scheduling grants during this skipping period.

At optional operation 411, the client device 200 may perform a subsequent SDT, including a second UL payload.

At optional operation 412, the network node device 210 may transmit to the client device 200 an RRC release message to end the ongoing SDT procedure.

The method of diagram 400 may be performed by the client device 200 of Fig. 2A and the network node device 210 of Fig. 2B. The operations 401, 403-405, 407- 408, 410, 412 can, for example, be performed by the at least one processor 212 and the at least one memory 214. The operations 402, 406, 409, 411 can, for example, be performed by the at least one processor 202 and the at least one memory 204. Further features of the method of diagram 400 directly result from the functionalities and parameters of the client device 200 and the network node device 210, and thus are not repeated here. The method of diagram 400 can be performed by computer program (s).

At least some of the embodiments described herein may allow a client device in an RRC inactive state of 5G NR to perform an SDT in a power-efficient manner.

At least some of the embodiments described herein may allow a network node device to control the PDCCH monitoring pattern during the SDT while avoiding a switching command DCI and its drawbacks. That is, if the switching among the configured search spaces was controlled by the network node device by using dynamic signalling, i.e., a PDCCH DCI of a given format includ- ing a bit indicating the search space (group) to acti vate, and if such a DCI was reused for controlling the search space adaptation during the SDT, it would result in a need for an additional network transmission of a dedicated DCI (and its reception at the client device) during SDT, which is undesired as it consumes additional radio resources and UE power, and/or it would result in a need to use a DCI having additional bits for the search space (group) identification (ID), thus having a larger size, and in turn consuming more radio resources (con trol channel elements (CCEs)) and having a larger like lihood of PDCCH decoding failures.

At least some of the embodiments described herein may allow the client device to make use of the most suitable SS on a per client device needs basis, and thereby to obtain the highest client device power sav ings.

At least some of the embodiments described herein may allow the network node device to avoid having dedicated signalling for the SDT adaptation, thereby keeping the signalling overhead low.

The client device 200 may comprise means for performing at least one method described herein. In one example, the means may comprise the at least one pro cessor 202, and the at least one memory 204 including program code configured to, when executed by the at least one processor, cause the client device 200 to perform the method.

The network node device 210 may comprise means for performing at least one method described herein. In one example, the means may comprise the at least one processor 212, and the at least one memory 214 including program code configured to, when executed by the at least one processor, cause the network node device 210 to perform the method.

The functionality described herein can be per formed, at least in part, by one or more computer program product components such as software components. Accord ing to an embodiment, the network node device 210 and/or the client device 200 may comprise a processor or pro cessor circuitry, such as for example a microcontroller, configured by the program code when executed to execute the embodiments of the operations and functionality de scribed. Alternatively, or in addition, the functional ity described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-pro grammable Gate Arrays (FPGAs), Program-specific Inte grated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Com plex Programmable Logic Devices (CPLDs), and Graphics Processing Units (GPUs).

Any range or device value given herein may be extended or altered without losing the effect sought. Also, any embodiment may be combined with another em bodiment unless explicitly disallowed.

Although the subject matter has been described in language specific to structural features and/or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims and other equiv alent features and acts are intended to be within the scope of the claims.

It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It will further be un derstood that reference to 'an' item may refer to one or more of those items. The steps of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the spirit and scope of the subject matter de scribed herein. Aspects of any of the embodiments de scribed above may be combined with aspects of any of the other embodiments described to form further embodiments without losing the effect sought.

The term 'comprising' is used herein to mean including the method, blocks or elements identified, but that such blocks or elements do not comprise an exclu sive list and a method or apparatus may contain addi tional blocks or elements.

It will be understood that the above descrip tion is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exem plary embodiments. Although various embodiments have been described above with a certain degree of particu larity, or with reference to one or more individual embodiments, those skilled in the art could make numer ous alterations to the disclosed embodiments without departing from the spirit or scope of this specifica tion.

Claims

CLAIMS:

1. A client device (200), comprising: at least one processor (202); and at least one memory (204) including computer program code; the at least one memory (204) and the computer program code configured to, with the at least one processor (202), cause the client device (200) to at least perform: during an ongoing small data transmission, SDT, procedure with a network node device (210), receiving from the network node device (210) an SDT adaptation parameter; determining a preconfigured SDT adaptation operation associated with the received SDT adaptation parameter; and adapting the ongoing SDT procedure in accordance with the determined SDT adaptation operation.

2. The client device (200) according to claim

1, wherein the SDT adaptation parameter comprises a scheduling slot offset value or time domain resource assignment information.

3. The client device (200) according to claim

2, wherein the scheduling slot offset value comprises a value of an uplink scheduling slot offset K2 or a value of a downlink scheduling slot offset K0.

4. The client device (200) according to claim 2, wherein the time domain resource assignment information comprises an indication of a row index of a time domain resource assignment table.

5. The client device (200) according to any of claims 1 to 4, wherein the adapting of the ongoing SDT procedure comprises adapting physical downlink control channel, PDCCH, monitoring used by the client device (200) during the ongoing SDT procedure.

6. The client device (200) according to claim 5, wherein the adapting of the PDCCH monitoring used by the client device (200) during the ongoing SDT procedure comprises using by the client device (200) at least one of: a dedicated search space, a dedicated search space group, or a dedicated PDCCH monitoring skipping configuration.

7. The client device (200) according to any of claims 1 to 4, wherein the adapting of the ongoing SDT procedure comprises switching to a separate SDT bandwidth part for the ongoing SDT procedure.

8. The client device (200) according to any of claims 1 to 7, wherein the determining of the preconfigured SDT adaptation operation associated with the received SDT adaptation parameter comprises performing a search for the received SDT adaptation parameter in a data structure comprising mappings between SDT adaptation parameters and associated SDT adaptation operations.

9. The client device (200) according to any of claims 1 to 8, wherein the at least one memory (204) and the computer program code are further configured to, with the at least one processor (202), cause the client device (200) to perform the receiving of the SDT adaptation parameter by receiving the SDT adaptation parameter in one of: link scheduling grant information, downlink control information, or a control element of medium access control.

10. A method, comprising: during an ongoing small data transmission, SDT, procedure with a network node device (210), receiving (305) at a client device (200) from the network node device (210) an SDT adaptation parameter; determining (306), by the client device (200), a preconfigured SDT adaptation operation associated with the received SDT adaptation parameter; and adapting (307), by the client device (200), the ongoing SDT procedure in accordance with the determined SDT adaptation operation.

11. A computer program comprising instructions for causing a client device to perform at least the following: during an ongoing small data transmission, SDT, procedure with a network node device, receiving from the network node device an SDT adaptation parameter; determining a preconfigured SDT adaptation operation associated with the received SDT adaptation parameter; and adapting the ongoing SDT procedure in accordance with the determined SDT adaptation operation.

12. A network node device (210), comprising: at least one processor (212); and at least one memory (214) including computer program code; the at least one memory (214) and the computer program code configured to, with the at least one processor (212), cause the network node device (210) to at least perform: detecting a need to adapt an ongoing small data transmission, SDT, procedure with a client device (200); selecting a preconfigured SDT adaptation operation for the detected need; and transmitting to the client device (200) an SDT adaptation parameter associated with the selected SDT adaptation operation.

13. The network node device (210) according to claim 12, wherein the detecting of the need to adapt the ongoing SDT procedure is performed based on information about at least one of: network load, downlink traffic, or uplink traffic.

14. The network node device (210) according to claim 12 or 13, wherein the selecting of the preconfigured SDT adaptation operation is performed by selecting the preconfigured SDT adaptation operation from a data structure comprising mappings between SDT adaptation operations and associated SDT adaptation parameters.

15. The network node device (210) according to claim 14, wherein the at least one memory (214) and the computer program code are further configured to, with the at least one processor (212), cause the network node device (210) to perform: transmitting to the client device (200) SDT configuration information comprising the data structure.

16. A method, comprising: detecting (303), by a network node device (210), a need to adapt an ongoing small data transmission, SDT, procedure with a client device (200); selecting (304), by the network node device (210), a preconfigured SDT adaptation operation for the detected need; and transmitting (305), by the network node device (210), to the client device (200) an SDT adaptation parameter associated with the determined SDT adaptation operation.

17. A computer program comprising instructions for causing a network node device to perform at least the following: detecting a need to adapt an ongoing small data transmission, SDT, procedure with a client device (200); selecting a preconfigured SDT adaptation operation for the detected need; and transmitting to the client device (200) an SDT adaptation parameter associated with the determined SDT adaptation operation.