US 12,717,609 B2Granted

Enforcement of end-to-end transaction latency

AssigneeNokia Technologies Oy

InventorsEdward Grinshpun, Bilgehan Erman, Catello Di Martino

Life of this patent

Estimating the term…

Loading patent…

Abstract

Various example embodiments for supporting enforcement of end-to-end transaction latency for transaction-based applications and services are presented herein. The enforcement of a total end-to-end transaction latency for a transaction of a transaction-based application or service may be supported by associating a transaction latency budget with the transaction data of the transaction and updating the transaction latency budget during execution of the transaction to ensure that the transaction is completed within the total end-to-end transaction latency permitted for the transaction-based application or service. The enforcement of end-to-end transaction latency for transaction-based applications and services may be configured to enforce end-to-end transaction latency without the need for use of network-wide time synchronization (rather, all of the timing may be measured locally using local clocks of the elements in the end-to-end path of the application or service transaction).

Claims17

Dependent claims

An apparatus, comprising:

at least one processor;
and
at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to:
initialize, by a node, a transaction including transaction data and having associated therewith a transaction identifier, a transaction start time, and an end-to-end transaction latency budget indicative of a length of time allotted for completion of the transaction;
generate, by the node, a transaction packet including at least a portion of the transaction data and a transaction header, wherein the transaction header includes the transaction identifier and a transaction latency budget indicative of a length of time remaining for completion of the transaction, wherein the transaction latency budget is based on the end-to-end transaction latency budget, a local handling time of the transaction packet that is determined based on the transaction start time at the node, and a propagation delay from the node to a next-hop node;
and
send, by the node toward the next-hop node, the transaction packet;
wherein the local handling time of the transaction packet at the node is computed by the node based on a difference between the transaction start time and a local time of successfully sending the transaction packet from the node toward the next-hop node.

5 more elements

An apparatus, comprising:

at least one processor;
and
at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to:
receive, by a node, a transaction packet associated with a transaction, wherein the transaction packet includes a transaction header and transaction data for the transaction, wherein the transaction header includes a transaction latency budget indicative of a length of time remaining for completion of the transaction;
determine, by the node, an outgoing interface toward a next-hop node for the transaction packet;
determine, by the node based on the transaction latency budget, scheduling of the transaction packet for transmission via the outgoing interface toward the next-hop node;
update, by the node, the transaction latency budget in the transaction header of the transaction packet, wherein the transaction latency budget is updated to remove a local handling time of the transaction packet at the node, wherein the local handling time of the transaction packet at the node is computed by the node based on a difference between a time at which the transaction packet was received at the node and a time at which the transaction packet is sent by the node toward the next-hop node;
and
send, by the node toward the next-hop node via the outgoing interface toward the next-hop node, the transaction packet.

6 more elements

An apparatus, comprising:

at least one processor;
and
at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to:
receive a set of transaction packets associated with a transaction, wherein the transaction packets include respective portions of transaction data of the transaction and respective transaction latency budgets for the respective packets;
compute, based on the transaction latency budgets for the respective packets and information indicative of delays associated with receipt of the set of transaction packets, a first updated transaction latency budget for the transaction;
compute, based on the first updated transaction latency budget for the transaction, a scheduling priority for processing of the transaction data and an amount of compute resources for processing of the transaction data;
process, based on the scheduling priority and the amount of compute resources, the transaction data of the transaction to produce updated transaction data of the transaction;
compute, based on the first updated transaction latency budget for the transaction and information indicative of delays associated with processing of the transaction data of the transaction to produce the updated transaction data of the transaction, a second updated transaction latency budget for the transaction;
segment the new transaction data into a set of new transaction packets associated with the transaction, wherein the new transaction packets include respective portions of the updated transaction data of the transaction and the second updated transaction latency budget for the transaction;
schedule, based on the second updated transaction latency budget for the transaction, sending of the new transaction packets;
compute, based on the second updated transaction latency budget for the transaction and information indicative of delays associated with sending of the new transaction packets, respective new transaction latency budgets for the new packets;
and
send the new transaction packets associated with the transaction, wherein the new transaction packets include respective portions of the updated transaction data of the transaction and the respective new transaction latency budgets for the new packets.

10 more elements

Dependencies are inferred from the claim text.