IP Library Granted Patent US 8,031,714
Granted Patent B2
US 8,031,714 · App. 12/511,673 · Granted Oct 4, 2011

Using a cache of outgoing packet identifiers to recover from a protocol error in GTP-u

Assignee: Nokia Siemens Networks GmbH & Co. KG
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,031,714
App. No.
12/511,673
Granted
Oct 4, 2011
Kind
B2
Abstract

A process of using a cache of outgoing packet identifiers to recover from a protocol error includes assigning a receive identifier associated with a user entity to a traffic stream at a receive node. The receive identifier is sent to a transmit node. The transmit node is instructed to associate the receive identifier with a receive plurality of data packets of the traffic stream. The transmit identifier associated with the user entity is assigned to the traffic stream at the transmit node. The transmit node identifier, the receive node identifier, and the address of the receive node are stored in a transmit cache at the transmit node for each of the receive plurality of data packets. The receive plurality of data packets is sent from the transmit node to the receive node. An error message is received at the transmit node from the receive node, indicating that the receive identifier was not recognized. The transmit cache is searched for the transmit node identifier using the receive node identifier and the address of the receive node. The user entity associated with the transmit node identifier is identified, and the user entity is removed.

Claims (47)

1. A method of using a cache of outgoing packet identifiers to recover from a protocol error, comprising:

assigning a first identifier associated with a user entity to a traffic stream at a first node;

forwarding the first identifier to a second node;

instructing the second node to associate the first identifier with a first plurality of data packets of the traffic stream;

storing the first node identifier, the second node identifier, and the address of the first node in a second cache at the second node for each of the first plurality of data packets;

sending the first plurality of data packets from the second node to the first node;

assigning a second identifier associated with the user entity to the traffic stream at the second node;

sending the second identifier to the first node;

instructing the first node to associate the second identifier with a second plurality of data packets of the traffic stream;

storing the first node identifier, the second node identifier, and the address of the second node in a first cache at the first node for each of the second plurality of data packets;

sending the second plurality of data packets from the first node to the second node;

receiving an error message from the second node at the first node, indicating that the second identifier was not recognized;

searching the first cache for the first node identifier using the second node identifier and the address of the second node;

identifying the user entity associated with the first node identifier; and

removing the user entity.

2. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 1 , wherein the first cache is dedicated to the traffic stream being sent to the first node.

3. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 1 , wherein the second cache is dedicated to the traffic stream being sent to the second node.

4. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 1 , wherein the first cache or the second cache is shared by a plurality of nodes.

5. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 1 , wherein each of a plurality of nodes has a separate cache.

6. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 1 , wherein the first cache or the second cache is a first-in-first-out cache.

7. A method of using a cache of outgoing packet identifiers to recover from a protocol error, comprising:

assigning a receive identifier associated with a user entity of a traffic stream at a receive node;

sending the receive identifier to a transmit node;

instructing the transmit node to associate the receive identifier with a receive plurality of data packets of the traffic stream;

assigning a transmit identifier associated with the user entity to the traffic stream at the transmit node;

storing the transmit node identifier, the receive node identifier, and the address of the receive node in a transmit cache at the transmit node for each of the receive plurality of data packets;

sending the receive plurality of data packets from the transmit node to the receive node;

receiving an error message at the transmit node from the receive node, indicating that the receive identifier was not recognized;

searching the transmit cache for the transmit node identifier using the receive node identifier and the address of the receive node;

identifying the user entity associated with the transmit node identifier; and

removing the user entity.

8. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 7 , wherein the transmit cache is dedicated to the traffic stream being sent to the transmit node.

9. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 7 , wherein the transmit cache is shared by a plurality of nodes.

10. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 9 , wherein each of the plurality of nodes has a separate cache.

11. The method of using a cache of outgoing packet identifiers to recover from a protocol error of claim 7 , wherein the transmit cache is a first-in-first-out cache.

12. An apparatus using a cache of outgoing packet identifiers to recover from a protocol error, comprising:

a receive node;

the receive node assigning a receive identifier associated with a user entity of a traffic stream, and sending the receive identifier to the transmit node;

the receive node instructing the transmit node to associate the receive identifier with a receive plurality of data packets of the traffic stream;

a transmit node having a transmit cache;

the transmit node assigning a transmit identifier associated with the user entity to the traffic stream;

the transmit node storing the transmit node identifier, the receive node identifier, and the address of the receive node in the transmit cache for each of the receive plurality of data packets;

the transmit node sending the receive plurality of data packets to the receive node;

the transmit node receiving an error message from the receive node, indicating that the receive identifier was not recognized;

the transmit node searching the transmit cache for the transmit node identifier using the receive node identifier and the address of the receive node;

the transmit node identifying the user entity associated with the transmit node identifier; and

the transmit node removing the user entity from the transmit cache.

Assignments (12)
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
CHANGE OF NAME Recorded Apr 30, 2019
From: NOKIA SIEMENS NETWORKS GMBH & CO. KG
To: NOKIA SOLUTIONS NETWORKS GMBH & CO. KG
Reel/Frame 049028/0190 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 30, 2019
From: NOKIA SIEMENS NETWORKS GMBH & CO. KG
To: NOKIA SOLUTIONS NETWORKS GMBH & CO. KG
Reel/Frame 049028/0220 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
CHANGE OF NAME Recorded Nov 19, 2014
From: NOKIA SIEMENS NETWORKS OY
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 034294/0603 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 14, 2009
From: SAIRANEN, JUSSI-PEKKA
To: NOKIA SIEMENS NETWORKS GMBH & CO. KG
Reel/Frame 023669/0990 →
Continuity (2)
Provisional Application 61105511 · Oct 15, 2008
Related Publication 20100103935A1 · Apr 29, 2010