IP Library Granted Patent US 9,281,869
Granted Patent B2
US 9,281,869 · App. 13/902,283 · Granted Mar 8, 2016

Network repeater

Inventors: Veronica Romero (Barcelona, ES); David Ruiz Lopez (Barcelona, ES)
Assignee: BROADCOM NETWORKS SPAIN, S.L.
H04B3/58H04L12/46
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 9,281,869
App. No.
13/902,283
Granted
Mar 8, 2016
Kind
B2
Abstract

A network repeater is configured to repeat data packets in a broadcast mode without generating a significant broadcast storm. The network repeater is configured to detect a characteristic of a received data packet. The data packet characteristic is compared with valid copies of packet characteristics previously stored in a packet registry. During a delay period, if a valid copy of the detected characteristic is found in the packet registry, then it is assumed that the packet is being received for the second time and the data packet is not repeated in the broadcast mode. If a valid copy of the detected characteristic of the data packet is not found in the packet registry, then the characteristic is stored in the packet registry and the data packet is repeated in a broadcast mode.

Claims (51)

1. A repeater comprising:

an input/output interface;

a packet registry storing packet characteristics of data packets received within a delay time, wherein the delay time represents a threshold amount of elapsed time;

logic configured to

receive data packets from the input/output interface;

select particular data packets from among data packets determined not to be copies of previously received data packets, wherein the copies of previously received data packets are received within a predetermined time measured from a time of receipt of the previously received data packet has elapsed;

repeat the particular data packets; and

refresh the packet registry, wherein refreshing the packet registry includes removing packet characteristics of data packets received outside the delay time.

2. The repeater of claim 1 , wherein the logic is configured to operate in a broadcast mode.

3. The repeater of claim 1 , wherein the logic is further configured to determine whether a received data packet is a copy of a previously received data packet based on comparing a characteristic of the received data packet to a characteristic stored in the packet registry.

4. The repeater of claim 3 , wherein the characteristic of the received data packet comprises a source identifier.

5. The repeater of claim 3 , wherein the characteristic of the received data packet comprises a tag added by logic associated with a network device other than the repeater.

6. The repeater of claim 1 , wherein the predetermined time is set based on a rebroadcast interval.

7. The repeater of claim 1 , further comprising:

the packet registry configured to store data packet characteristics of the previously received data packets; and

a registry manager configured to remove the data packet characteristics from the packet registry after the predetermined time.

8. The repeater of claim 1 , wherein the logic is configured to select the particular data packets based upon a search of the packet registry for valid data packet characteristics.

9. The repeater of claim 8 , further comprising:

a registry manager configured to determine a validity status of the data packet characteristics stored in the packet registry.

10. A repeater comprising:

a packet registry configured to store a valid characteristic of a previously received data packet, at least until a predetermined delay expires;

an input/output configured to receive a current data packet;

logic configured to:

detect a characteristic of the current data packet,

drop the current data packet if the characteristic of the current data packet corresponds to the valid characteristic stored in the packet registry; and

refresh the packet registry, wherein refreshing the packet registry includes removing packet characteristics of data packets after the packet characteristics become invalid due to expiration of the predetermined delay.

11. The repeater of claim 10 , wherein the logic is configured to operate in a broadcast mode.

12. The repeater of claim 10 , further comprising:

a registry manager configured to determine a validity status of data packet characteristics stored in the packet registry.

13. The repeater of claim 12 , further comprising:

the registry manager configured to remove invalid data packet characteristics from the packet registry.

14. The repeater of claim 12 , further comprising:

the registry manager configured to associate validity indications with respective data packet characteristics stored in the packet registry.

15. The repeater of claim 10 , wherein the predetermined delay is selected to be less than a retransmission time associated with one or more nodes on a network.

16. A method comprising:

storing a first characteristic of a first data packet in a packet registry, the first data packet received at a first time from a first communication network;

repeating the first data packet over a second communication network;

receiving a second data packet from the first communication network within a delay time after the first data packet was received, the second packet having a second characteristic matching the first characteristic;

dropping the second data packet in response to a search of the packet registry finding the second characteristic in the packet registry;

receiving a third data packet from the first communication network within the delay time after the first data packet was received, the third data packet having a third characteristic different from the first characteristic;

repeating the third data packet over the second communication network in response to a search of the packet registry indicating that the third characteristic is absent from the packet registry; and

refreshing the packet registry to remove the first characteristic of the first data packet from the registry after the delay time.

17. The method of claim 16 , further comprising:

receiving a fourth data packet from the first communication network outside of the delay time after the first data packet was received, the fourth data packet having a fourth characteristic different from the first characteristic; and

dropping the fourth packet.

18. The method of claim 16 , further comprising;

removing the first characteristic from storage in response to determining that the first characteristic is invalid.

19. The method of claim 16 , further comprising:

dynamically adjusting the delay time.

20. The method of claim 19 , further comprising:

dynamically adjusting the delay time based on at least one of: network latency, a number of dropped packets, and a volume of network traffic.

Assignments (5)
CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT NUMBER 9,385,856 TO 9,385,756 PREVIOUSLY RECORDED AT REEL: 47349 FRAME: 001. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER. Recorded Mar 22, 2019
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 051144/0648 →
CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE PREVIOUSLY RECORDED ON REEL 047229 FRAME 0408. ASSIGNOR(S) HEREBY CONFIRMS THE THE EFFECTIVE DATE IS 09/05/2018. Recorded Oct 29, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047349/0001 →
MERGER Recorded Oct 4, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047229/0408 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2017
From: BROADCOM CORPORATION
To: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
Reel/Frame 041706/0001 →
CHANGE OF NAME Recorded Aug 23, 2013
From: GIGLE NETWORKS IBERIA, S.L.
To: BROADCOM NETWORKS SPAIN, S.L.
Reel/Frame 031076/0242 →
Continuity (3)
Continuation 12874404 · Sep 2, 2010
Continuation 11562380 · Nov 21, 2006
Related Publication 20130259096A1 · Oct 3, 2013