IP Library Granted Patent US 7,417,948
Granted Patent B2
US 7,417,948 · App. 09/903,863 · Granted Aug 26, 2008

Controlled data network error recovery

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 7,417,948
App. No.
09/903,863
Granted
Aug 26, 2008
Kind
B2
Abstract

A method, a system and network nodes using indication of possible duplicates (IPD) of units, so that these units can be handled differently than other units. The unit is indicated to be a possible duplicate to the entity to which it is resent because no response was received from the entity it was sent to.

Claims (68)

1. A method comprising:

sending a unit to a first receiving entity in a telecommunications system;

in the event that no response is received from the first receiving entity, resending said unit to a second receiving entity;

indicating that said unit was resent because no response was received when resending said unit to the second receiving entity by marking the resent unit as a possible duplication with an indication of a possible duplicate (IPD);

noticing that the first receiving entity is operating;

checking whether the first receiving entity received said unit;

sending a release message to the second receiving entity when said unit was not received in the first receiving entity; and

sending a cancel message to the second receiving entity when said unit was received in the first receiving entity.

2. The method of claim 1 , wherein the IPD is indicated in the unit when resending said unit to the second receiving entity.

3. The method of claim 1 , further comprising:

receiving said unit in the second receiving entity;

storing said unit in response to said indication; and

sending said unit in response to said release message from the first receiving entity; or

deleting said unit in response to said cancel message.

4. The method of claim 1 , further comprising:

receiving said unit in an end system; and

checking only in response to said IPD whether the unit is a duplicate.

5. The method of claim 1 , further comprising indicating the possible duplication by adding said IPD to the unit before resending the unit.

6. A transmission system comprising:

a first receiving entity;

a second receiving entity; and

a sending entity that is configured to:

resend, to the second receiving entity, a unit including an indication of a possible duplicate (IPD) relating to said unit in the event that no response is received from the first receiving entity, the IPD indicating that said unit was resent because no response was received from the first receiving entity;

notice that the first receiving entity is operating

check whether the first receiving entity received said unit;

send a release message to the second receiving entity when said unit was not received in the first receiving entity: and

send a cancel message to the second receiving entity when said unit was received in the first receiving entity.

7. The system of claim 6 , wherein said sending entity is further configured to indicate also the sending entity when sending said IPD.

8. The system of claim 6 , further comprising an end system which is configured to check from a recieved unit whether it includes said IPD and, IPD, to check whether said unit is a duplicate in response to said IPD.

9. The system of claim 6 , further comprising an end system which is configured to check from a received unit whether it includes said IPD and, to check whether said unit is a duplicate in response to said IPD.

10. A network node comprising:

a memory; and

a processor operatively connected to the memory and, in the absence of receiving a response from a first entity to which a unit was sent, said processor being configured to:

resend said unit with an indication of a possible duplicate (IPD) to another entity, the IPD indicating that said unit was resent because no response was received from the first entity;

notice that the first entity is operating;

check whether the first entity received said unit;

send a release message to the other entity when said unit was not received in the first entity; and

send a cancel message to the other entity when said unit was received in the first entity.

11. The network node of claim 10 , wherein the processor is further configured to indicate the sending entity when sending said IPD.

12. The network node of claim 10 , wherein the processor is further configured to include said IPD when resending said unit to another entity.

13. The network node of claim 12 , further comprising a memory comprising a data structure containing a priority list of entities to which units may be sent and wherein the processor is further configured to resend the unit to the entity having a next lowest priority.

14. A method comprising:

sending a unit to a first receiving entity;

in the event that no response is received from the first receiving entity, resending the unit to another entity;

noticing that the first receiving entity is operating;

checking whether the first receiving entity received said unit;

if said unit was not received in the first receiving entity, sending a release message to the other entity; and

otherwise, sending a cancel message to the other entity,

wherein the resending of the unit differs from the sending of the unit in that a sending entity specifically provides an indication of a possible duplicate (IPD) relating to said unit when resending the unit, the IPD indicating that said unit was resent because no response was received.

15. The method of claim 14 wherein the IPD is included in the unit when resending said unit to a second receiving entity.

16. A network node comprising:

sending means for sending a unit to a first receiving entity, and

resending means, for resending said unit with an indication of a possible duplicate (IPD) to another receiving entity, the IPD indicating that said unit was resent because no response was received,

noticing that the first receiving entity is operating

checking whether the first receiving entity received said unit, if said unit was not received in the first receiving entity,

sending a release message to the other receiving entity and otherwise,

sending a cancel message to the other receiving entity,

wherein the resending means differ from the sending means in that the resending means are configured to specifically indicate a possible duplication of said unit by including the IPD when the unit is resent.

17. The network node of claim 16 , wherein the resending means are further configured to include said IPD when resending said unit to another entity.

18. The network node of claim 17 , further comprising:

a memory comprising a data structure that stores a priority list of entities to which the sending means and the resending means are capable of sending units, wherein the resending means are further configured to resend the unit to the entity having a next lowest priority.

19. A computer readable medium encoded with computer-executable code thereon which, when executed by a computer, causes the computer to:

send a unit to a first receiving entity in a telecommunications system;

in the event that no response is received from the first receiving entity, resend said unit with an indication a possible duplicate (IPD) to a second receiving entity, the IPD indicating that said unit was resent because no response was received from the first receiving entity;

notice that the first receiving entity is operating;

check whether the first receiving entity received said unit;

send a release message to the second receiving entity when said unit was not received in the first receiving entity; and

send a cancel message to the second receiving entity when said unit was received in the first receiving entity.

Assignments (10)
REDACTED PURCHASE AND SALE AGREEMENT Recorded Mar 10, 2017
From: 2011 INTELLECTUAL PROPERTY TRUST
To: CORE WIRELESS LICENSING S.A.R.L.
Reel/Frame 041941/0662 →
UCC FINANCING STATEMENT AMENDMENT - DELETION OF SECURED PARTY Recorded Aug 30, 2016
From: NOKIA CORPORATION
To: MICROSOFT CORPORATION
Reel/Frame 039872/0112 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2016
From: CORE WIRELESS LICENSING SARL,
To: MICROSOFT TECHNOLOGY LICENSING LLC,
Reel/Frame 037468/0953 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 15, 2011
From: 2011 INTELLECTUAL PROPERTY ASSET TRUST
To: CORE WIRELESS LICENSING S.A.R.L.
Reel/Frame 027395/0650 →
CHANGE OF NAME Recorded Oct 26, 2011
From: NOKIA 2011 PATENT TRUST
To: 2011 INTELLECTUAL PROPERTY ASSET TRUST
Reel/Frame 027121/0353 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2011
From: NOKIA CORPORATION
To: NOKIA 2011 PATENT TRUST
Reel/Frame 027120/0608 →
SHORT FORM PATENT SECURITY AGREEMENT Recorded Sep 13, 2011
From: CORE WIRELESS LICENSING S.A.R.L.
To: NOKIA CORPORATION; MICROSOFT CORPORATION
Reel/Frame 026894/0665 →
CHANGE OF NAME Recorded Jun 24, 2008
From: NOKIA NETWORKS OY
To: NOKIA CORPORATION
Reel/Frame 021144/0428 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR NAME, PREVIOSULY RECORDED AT REEL 012143, FRAME 0704. Recorded Aug 9, 2002
From: SJOBLOM, KAI
To: NOKIA NETWORKS OY
Reel/Frame 013183/0908 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 7, 2001
From: SJOBLOM, KARI
To: NOKIA NETWORKS OY
Reel/Frame 012143/0704 →