# US 2023/0403703 A1 · Optimizing small data transmission for a client device

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0403703 A1
- Document ID: US20230403703A1
- Status: Published application
- Kind: A1
- Application number: 18/250,135
- Filed: 2020-10-22
- Published: 2023-12-14
- Earliest claimed: 2020-10-22
- Assignees: Nokia Technologies Oy
- Applicants: Nokia Technologies Oy
- Inventors: Nuno Manuel KIILERICH PRATAS; Daniela LASELVA; Samuli Heikki TURTINEN
- Web page: https://patentgrep.com/patent/US20230403703A1

## CPC

- H04W 24/02: Arrangements for optimising operational condition
- H04W 72/1268: of uplink data flows
- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Devices, methods and computer programs for optimizing small data transmission for a client device are disclosed. Configuration information for a small data transmission procedure is received at the client device from a network node device. The configuration information comprises set(s) of resources for a configured uplink scheduling grant for small data transmissions. The client device carries out one or more small data transmissions based on the received configuration information for the small data transmission procedure and/or subsequently received updated configuration information for the small data transmission procedure.

## Claims

### Claim 1

A network node 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 network node device (200) to at least perform:
generating configuration information for a small data transmission procedure of a client device (210), the configuration information for the small data transmission procedure comprising at least one set of resources for a configured uplink scheduling grant for small data transmissions, wherein the configuration information is generated based on unavailability information regarding the client device (210), the unavailability information being about at least one unavailability time period; and
transmitting the generated configuration information to the client device (210).

### Claim 2 (depends on 1)

The network node device (200) according to claim 1, wherein the at least one unavailability time period is due to an overlapping activity of the client device (210).

### Claim 3 (depends on 1)

The network node device (200) according to claim 1, 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 network node device (200) to at least perform:
after transmitting the generated configuration information to the client device (210), receiving from the client device (210) an update request for the configuration information based on a detected overlap in the transmitted configuration information with an overlapping activity of the client device (210);
generating updated configuration information for the small data transmission procedure based on the received update request for the configuration information; and
transmitting the generated updated configuration information to the client device (210).

### Claim 4 (depends on 3)

The network node device (200) according to claim 3, wherein the transmitted configuration information comprises at least two sets of the resources for the configured uplink scheduling grant and the received update request for the configuration information comprises a selection indication about a selected non-overlapping one of the transmitted at least two sets of the resources for the configured uplink scheduling grant, and 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 network node device (200) to perform the generating of the updated configuration information for the small data transmission procedure based on the selected non-overlapping one of the transmitted at least two sets of the resources for the configured uplink scheduling grant.

### Claim 5 (depends on 1)

The network node device (200) according to claim 1,
wherein:
the client device (210) further comprises a first subscriber identity module (217) and a second subscriber identity module (218); and
the at least one memory (204) and the computer program code are further configured to, with the at least one processor (202), cause the network node device (200) to at least perform the generating of the configuration information for small data transmissions for the second subscriber identity module (218).

### Claim 6 (depends on 5)

The network node device (200) according to claim 5, wherein the overlapping activity is due to one or more operations related to at least one of the first subscriber identity module (217) or the second subscriber identity module (218).

### Claim 7 (depends on 5)

The network node device (200) according to claim 5, wherein the overlapping activity comprises a paging monitoring activity related to at least one of the first subscriber identity module (217) and the second subscriber identity module (218).

### Claim 8 (depends on 1)

The network node device (200) according to claim 1, wherein the unavailability information is received from the client device (210) as part of a request for the configuration information for the small data transmission procedure.

### Claim 9

A method, comprising:
generating, by a network node device, configuration information for a small data transmission procedure of a client device, the configuration information for the small data transmission procedure comprising at least one set of resources for a configured uplink scheduling grant for small data transmissions, wherein the configuration information is generated based on unavailability information regarding the client device, the unavailability information being about at least one unavailability time period; and
transmitting (303A, 304B, 302C, 306C) the generated configuration information from the network node device to the client device.

### Claim 10

(canceled)

### Claim 11

A client 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 client device (210) to at least perform:
receiving, from a network node device (200), configuration information for a small data transmission procedure, the configuration information for the small data transmission procedure comprising at least one set of resources for a configured uplink scheduling grant for small data transmissions, the configuration information generated based on unavailability information regarding the client device (210), the unavailability information being about at least one unavailability time period; and
carrying out one or more small data transmissions based on at least one of the received configuration information for the small data transmission procedure or subsequently received updated configuration information for the small data transmission procedure.

### Claim 12 (depends on 11)

The client device (210) according to claim 11, further comprising a first subscriber identity module (217) and a second subscriber identity module (218).

### Claim 13 (depends on 12)

The client device (210) according to claim 12, wherein the configuration information for the small data transmission procedure is received when the first subscriber identity module (217) is not in a connected state of radio resource control, RRC.

### Claim 14 (depends on 13)

The client device (210) according to claim 13, wherein the first subscriber identity module (217) not being in the connected state of RRC comprises the first subscriber identity module (217) being in an idle state of RRC or in an inactive state of RRC.

### Claim 15 (depends on 11)

The client device (210) according to claim 11, 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 client device (210) to at least perform:
prior to or after receiving the configuration information, transmitting to the network node device (200) the unavailability information about the at least one unavailability time period.

### Claim 16 (depends on 15)

The client device (210) according to claim 15, wherein the at least one unavailability time period is due to an overlapping activity of the client device (210).

### Claim 17 (depends on 11)

The client device (210) according to claim 11, 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 client device (210) to at least perform:
detecting an overlap in the received configuration information with an overlapping activity of the client device (210), before carrying out the one or more small data transmissions;
transmitting to the network node device (200) an update request for the configuration information based on the detected overlap; and
receiving, from the network node device (200), updated configuration information for the small data transmission procedure.

### Claim 18 (depends on 17)

The client device (210) according to claim 17, wherein the received configuration information comprises at least two sets of the resources for the configured uplink scheduling grant, and the at least one memory (214) and the computer program code are further configured to, with the at least one processor (212), cause the client device (210) to at least perform:
in response to detecting the overlap in the received configuration information, selecting a non-overlapping one of the received at least two sets of the resources for the configured uplink scheduling grant,
wherein the transmitted update request for the configuration information comprises a selection indication about the selected non-overlapping one of the received at least two sets of the resources for the configured uplink scheduling grant.

### Claim 19 (depends on 11)

The client device (210) according to claim 11, 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 client device (210) to at least perform:
detecting an overlap in the received configuration information with an overlapping activity of the client device (210), after carrying out at least one of the one or more small data transmissions;
transmitting to the network node device (200) an update request for the configuration information based on the detected overlap; and
receiving, from the network node device (200), updated configuration information for the small data transmission procedure.

### Claim 20 (depends on 19)

The client device (210) according to claim 19, wherein the first subscriber identity module (217) not being in the connected state of RRC further comprises the first subscriber identity module (217) being deactivated when first receiving the configuration information.

### Claim 21 (depends on 16)

The client device (210) according to claim 16, wherein the overlapping activity comprises a paging monitoring activity related to at least one of the first subscriber identity module (217) and the second subscriber identity module (218).

### Claim 22

A method, comprising:
receiving (303A, 302B, 302C), at a client device from a network node device, configuration information for a small data transmission procedure, the configuration information for the small data transmission procedure comprising at least one set of resources for a configured uplink scheduling grant for small data transmissions, the configuration information generated based on unavailability information regarding the client device, the unavailability information being about at least one unavailability time period; and
carrying out, by the client device, one or more small data transmissions (304A, 305A, 305B, 306B, 303C, 307C) based on at least one of the received (303A, 302C) configuration information for the small data transmission procedure or subsequently received (304B, 306C) updated configuration information for the small data transmission procedure.

### Claim 23 (depends on 22)

The method according to claim 22, wherein the client device comprises a first subscriber identity module and a second subscriber identity module.

### Claim at position 24

24-25. (canceled)
