# US 2026/0101412 A1 · Transmission of application data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2026/0101412 A1 - Document ID: US20260101412A1 - Status: Published application - Kind: A1 - Application number: 19/115,239 - Filed: 2022-09-29 - Published: 2026-04-09 - Earliest claimed: 2022-09-29 - Assignees: Nokia Technologies Oy - Applicants: Nokia Technologies Oy - Inventors: Srinivasan SELVAGANAPATHY; Mads LAURIDSEN; Jeroen WIGARD; Ping YUAN; Xiang XU - Web page: https://patentgrep.com/patent/US20260101412A1 ## CPC - H04L 1/1854: {Scheduling and prioritising arrangements} - H04W 76/30: Connection release - H04L 1/18: Automatic repetition systems, e.g. Van Duuren systems - H04L 1/188: {Time-out mechanisms} - H04L 1/1887: {Scheduling and prioritising arrangements} - H04L 1/1896: {ARQ related signaling} - H04W 76/28: Discontinuous transmission [DTX]; Discontinuous reception [DRX] - H04W 76/27: Transitions between radio resource control [RRC] states - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Embodiments of the present disclosure relate to data transmission for discontinuous connectivity. A terminal device receives, from an access network device, an indication that an acknowledgement for application data from the terminal device is to be deferred. The terminal device avoids retransmitting the application data based on the indication. As such, redundant retransmissions of the application data can be avoided. ## Claims ### Claim at position 1 1-36. (canceled) ### Claim 37 A terminal device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from an access network device, an indication that an acknowledgement for application data from the terminal device is to be deferred; and avoid retransmitting the application data based on the indication. ### Claim 38 (depends on 37) The terminal device of claim 37, wherein the access network device has discontinuous connectivity with a core network. ### Claim 39 (depends on 38) The terminal device of claim 38, wherein the indication comprises at least one of: information indicating that the access network device is in a store-and-forward mode, information indicating that a packet from the terminal device is stored in the access network device for forwarding, a resume time indicating a time for delivery of the acknowledgement, or a token generated based on a number of previous data transmissions between the terminal device and the core network. ### Claim 40 (depends on 37) The terminal device of claim 37, wherein the terminal device is caused to receive the indication via at least one of: a radio resource control, RRC, connection release message, system information, a random access response, RAR, message or a contention resolution message. ### Claim 41 (depends on 37) The terminal device of claim 37, wherein the terminal device is further caused to perform, prior to retransmission of the application data, at least one of the following based on receiving a RRC connection release message comprising the indication: indicating, to an application layer of the terminal device, delivery confirmations for a plurality of packets for the application data given to an access stratum, AS, layer of the terminal device, or indicating the application layer to wait for the deferred acknowledgement. ### Claim 42 (depends on 37) The terminal device of claim 37, wherein the terminal device is further caused to perform at least one of the following based on receiving a RRC connection release message comprising the indication: indicating, to an application layer of the terminal device, a delivery confirmation for each packet data convergence protocol service data unit, PDCP SDU, for the application data with an indication to wait for the deferred acknowledgement. ### Claim 43 (depends on 38) The terminal device of claim 38, wherein the terminal device is caused to perform one or both of: receive the indication by: receiving system information or a RAR message indicating that the access network device is in a store-and-forward mode, prior to transmitting the application data to the access network device; or transmitting, to the access network device, release assistance information, RAI, indicating that a final packet for the application data is transmitted and the acknowledgement is pending; and receiving, from the access network device, a RRC connection release message comprising a resume time indicating a time for delivery of the acknowledgement. ### Claim 44 (depends on 43) The terminal device of claim 43, wherein the terminal device is further caused to perform one or both of: generate, by an AS layer of the terminal device, the RAI with a flag indicating that the final packet for the application data is transmitted and the acknowledgement is pending; or receive, from the access network device and prior to receiving the RRC connection release message, pending downlink data received from the core network during last connectivity between the core network and the access network device. ### Claim 45 (depends on 37) The terminal device of claim 37, wherein the terminal device is further caused to: transmit, to the access network device, a RRC connection resume request comprising the application data and RAI indicating that a downlink packet is expected, prior to receiving the indication via a RRC connection release message or via a contention resolution message. ### Claim 46 (depends on 38) The terminal device of claim 38, wherein the terminal device is further caused to: transmit, to the access network device, an early data transmission request comprising the application data as a non-access stratum, NAS, message, prior to receiving a contention resolution message comprising an token generated based on a number of previous early data transmissions between the terminal device and the core network, wherein the number of previous early data transmissions are associated with an attach procedure or a previous NAS message. ### Claim 47 (depends on 46) The terminal device of claim 46, wherein one or both of the following is utilized by the terminal device: the number of previous early data transmissions are associated with an attach procedure or a previous NAS message, or the token is generated based on an s-temporary mobile subscription identifier, S-TMSI, for the terminal device and the number of previous early data transmissions between the terminal device and the core network. ### Claim 48 (depends on 37) The terminal device of claim claims 37, wherein the terminal device is further caused to perform one or both of: receive, from the access network device, auto resume information indicating the terminal device to trigger an early data transmission, EDT, procedure or a RRC connection procedure to obtain the acknowledgement during next connectivity with the access network device without waiting for paging; or receive a duration from the access network device; and trigger the EDT procedure or the RRC connection procedure to obtain the acknowledgement after the duration from receipt of the acknowledgement. ### Claim 49 (depends on 48) The terminal device of claim 48, wherein the terminal device is caused to receive the auto resume information via a RRC connection release message or system information. ### Claim 50 An access network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the access network device at least to: determine, at the access network device, that an acknowledgement for application data from a terminal device is to be deferred; and transmit, to the terminal device, an indication that the acknowledgement is to be deferred, the terminal device being configured to avoid retransmitting the application data based on the indication. ### Claim 51 (depends on 50) The access network device of claim 50, wherein the access network device has discontinuous connectivity with a core network. ### Claim 52 (depends on 51) The access network device of claim 51, wherein the indication comprises at least one of: information indicating that the access network device is in a store-and-forward mode, information indicating that a packet from the terminal device is stored in the access network device for forwarding, a resume time indicating a time for delivery of the acknowledgement, or a token generated based on a number of previous data transmissions between the terminal device and the core network. ### Claim 53 (depends on 50) The access network device of claim 50, wherein the access network device is caused to transmit the indication via at least one of: a radio resource control, RRC, connection release message, system information, a random access response, RAR, message or a contention resolution message. ### Claim 54 (depends on 50) The access network device of claim 50, wherein the access network device is further caused to: receive, from the terminal device, the application data in a RRC connected mode, prior to transmitting the indication to the terminal device via a RRC connection release message indicating at least one of information indicating that a packet from the terminal device is stored in the access network device for forwarding, or a resume time indicating a time for delivery of the acknowledgement. ### Claim 55 (depends on 51) access network device of claim 51, wherein the access network device is caused to transmit the indication by: transmitting, to the terminal device, system information or a RAR message indicating that the access network device is in a store-and-forward mode prior to receiving the application data from the terminal device. ### Claim 56 (depends on 55) The access network device of claim 55, wherein the access network device is further caused to: receive, from the terminal device, release assistance information, RAI, indicating that a final packet for the application data is transmitted and the acknowledgement is pending; and transmit, to the terminal device, a RRC connection release message comprising a resume time indicating a time for delivery of the acknowledgement.