US6049528A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Trunking ethernet-compatible networks
Assignee: Oracle America Inc
•
Filing: 1997-06-30
•
Granted: 2000-04-11
•
Expires: 2017-06-30
Abstract
Abstract A network system dynamically controls data flow between physical links by logically combining multiple physical links into a single logical channel trunk, preferably to balance data flow carried by each link. Each link in the trunk has identical physical layer and identical media access control layer characteristics. A system server assigns a single media access control layer address to the single trunked logical channel, preferably randomly by hashing destination media access control layer addresses for the links. The system server includes, in addition to a physical layer and a network layer, a pseudo-driver software layer disposed therebetween, which pseudo-driver software layer functions as a multiplexer in a receive path and functions as a de-multiplexer in a transmit path. The resultant preferably Ethernet-compatible network system operates in full-duplex mode and distributes packets from the server to the links to preserve temporal order of data flow.
Inventors
- 👤 Ariel Hendel
- 👤 Leo A. Hejza
- 👤 Sampath H. K. Kumar
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 01:00
CPC Classifications
H; H04; H04L; H04L47/00; H04L47/10; H04L61/00; H04L69/00; H04L69/14
Claims Analysis
Total Claims: 33
Claim 1
Independent Claim
54 words
A method of dynamically controlling data flow between physical links of a network system, the method comprising the step of: logically combining multiple said physical links into a single logical channel referred to as a trunk; and a server in said system assigning a single media access control (MAC) layer address to said trunk.
Claim 2
Independent Claim
54 words
A method of dynamically controlling data flow between physical links of a network system, the method comprising the step of: logically combining multiple said physical links into a single logical channel referred to as a trunk; and a server in said system assigning a single media access control (MAC) layer address to said trunk.
Claim 3
Dependent Claim
25 words
The method of claim 1, wherein: each of said physical links comprising said trunk is representable by identical physical layer and identical MAC layer characteristics.
Claim 4
Dependent Claim
27 words
The method of claim 1, further comprising: dynamically controlling said data flow to substantially balance data flow carried by each of said physical links comprising said trunk.
Claim 5
Dependent Claim
20 words
The method of claim 1, further comprising: constructing said single MAC layer address using map-table information available to said system.
Claim 6
Dependent Claim
18 words
The method of claim 1, further comprising: randomly selecting a destination address for one of said physical links.
Claim 7
Dependent Claim
19 words
The method of claim 5, wherein said randomly selecting includes hashing destination MAC layer addresses for said physical links.
Claim 8
Dependent Claim
32 words
The method of claim 1, further comprising: distributing data packets from a server in said system to chosen ones of said physical links such that temporal order of data flow is preserved.
Claim 9
Dependent Claim
20 words
The method of claim 7, further comprising: said server distributing said data packets over a common segment of said trunk.
Claim 10
Dependent Claim
42 words
The method of claim 1, further comprising: defining, for a server in said system representable by a multi-layer model including at least a physical layer and a network layer, a pseudo-driver software layer disposed intermediate said physical layer and said network layer.
Claim 11
Dependent Claim
27 words
The method of claim 9, wherein: said pseudo-driver software layer functions as a multiplexer in a receive path and functions as a de-multiplexer in a transmit path.
Claim 12
Dependent Claim
10 words
The method of claim 1, wherein said network is Ethernet-compatible.
Claim 13
Dependent Claim
12 words
The method of claim 1, wherein said network functions in full-duplex mode.
Claim 14
Dependent Claim
60 words
A network system, comprising: a first physical link, coupleable to said network system; a second physical link, coupleable to said network system; a server having a server interface that dynamically combines the first and second physical links into a single logical channel referred to as a trunk by assigning a single media access control (MAC) layer address to said trunk.
Claim 15
Dependent Claim
60 words
A network system, comprising: a first physical link, coupleable to said network system; a second physical link, coupleable to said network system; a server having a server interface that dynamically combines the first and second physical links into a single logical channel referred to as a trunk by assigning a single media access control (MAC) layer address to said trunk.
Claim 16
Dependent Claim
26 words
The network system of claim 13, wherein: each of said physical links comprising said trunk is representable by identical physical layer and identical MAC layer characteristics.
Claim 17
Dependent Claim
58 words
The network system of claim 13, wherein said MAC layer address is generated with an address generator selected from a group consisting of (i) a map-table, (ii) a random selector of destination media access control layer addresses for said physical links, and (iii) a hash unit that hashes destination medial access control layer addresses for said physical links.
Claim 18
Dependent Claim
24 words
The network system of claim 13, wherein said server interface dynamically balances data flow carried by each of said physical links comprising said trunk.
Claim 19
Dependent Claim
28 words
The network system of claim 13, wherein said server distributes data packets to chosen ones of said physical links such that temporal order of data flow is preserved.
Claim 20
Dependent Claim
47 words
The network system of claim 13, wherein: said interface includes a pseudo-driver software layer disposed intermediate a physical layer and a network layer in said server; said pseudo-driver software layer functioning as a multiplexer in a receive path and functioning as a de-multiplexer in a transmit path.
Claim 21
Dependent Claim
41 words
The network system of claim 13, wherein said network system has at least one characteristic selected from a group consisting of (i) said network functions in full-duplex mode, (ii) said network is an Ethernet network, and (iii) said network is Ethernet-compatible.
Claim 22
Dependent Claim
41 words
The method of claim 1, wherein said server assigns said MAC layer address by selecting one of the said multiple physical links as the trunk-head and using the MAC address of the trunk head as the MAC address of the trunk.
Claim 23
Dependent Claim
64 words
A server comprising: a first physical port to provide a physical link to a network; a second port to provide a second physical link to the network; and a server interface that dynamically combines the first port and the second port into a single logical channel referred to as a trunk by assigning a single media access control (MAC) layer address to said trunk.
Claim 24
Dependent Claim
64 words
A server comprising: a first physical port to provide a physical link to a network; a second port to provide a second physical link to the network; and a server interface that dynamically combines the first port and the second port into a single logical channel referred to as a trunk by assigning a single media access control (MAC) layer address to said trunk.
Claim 25
Dependent Claim
25 words
The server of claim 21, wherein each of said physical links comprising said trunk is representable by identical physical layer and identical MAC layer characteristics.
Claim 26
Dependent Claim
28 words
The server of claim 21, wherein said server dynamically controls said data flow to substantially balance data flow carried by each of said physical links comprising said trunk.
Claim 27
Dependent Claim
21 words
The server of claim 21, wherein said server constructs said single MAC layer address using map-table information available to said system.
Claim 28
Dependent Claim
19 words
The server of claim 21, wherein said server randomly selects a destination address for one of said physical links.
Claim 29
Dependent Claim
19 words
The server of claim 25, wherein said randomly selection includes hashing destination MAC layer addresses for said physical links.
Claim 30
Dependent Claim
24 words
The server of claim 21, wherein said server distributes data packets over said physical links such that temporal order of data flow is preserved.
Claim 31
Dependent Claim
19 words
The server of claim 27, wherein said server distributes said data packets over a common segment of said trunk.
Claim 32
Dependent Claim
22 words
The server of claim 21, wherein said server defines a pseudo-driver software layer disposed intermediate the physical layer and the network layer.
Claim 33
Dependent Claim
27 words
The server of claim 29, wherein said pseudo-driver software layer functions as a multiplexer in a receive path and functions as a de-multiplexer in a transmit path.
References Cited (Backward Citations)
US4539637A
Cited
US4627052A
Cited
US4652874A
Cited
US4641302A
Cited
US4935869A
Cited
US4737953A
Cited
US4850042A
Cited
US4807111A
Cited
US4811337A
Cited
US4899333A
Cited
US4922503A
Cited
US4933938A
Cited
US5220562A
Cited
US5130977A
Cited
US5278830A
Cited
US5163046A
Cited
US5159685A
Cited
US5210746A
Cited
US5301333A
Cited
US5309437A
Cited
US5231633A
Cited
US5150358A
Cited
US5481540A
Cited
US5251205A
Cited
US5353412A
Cited
US5490260A
Cited
US5293379A
Cited
US5420862A
Cited
US5500860A
Cited
US5392432A
Cited
US5623489A
Cited
US5875464A
Cited
US5461624A
Cited
US5675714A
Cited
US5313454A
Cited
US5343471A
Cited
US5432907A
Cited
US5742760A
Cited
US5720032A
Cited
US5457681A
Cited
US5517488A
Cited
US5425028A
Cited
US5291482A
Cited
US5490252A
Cited
US5410540A
Cited
US5649109A
Cited
US5404538A
Cited
US5425026A
Cited
US5410722A
Cited
US5459714A
Cited
US5365514A
Cited
US5485578A
Cited
US5386413A
Cited
US5477537A
Cited
US5402415A
Cited
US5455820A
Cited
US5426736A
Cited
US5396602A
Cited
US5553067A
Cited
US5394402A
Cited
US5450399A
Cited
US5555405A
Cited
US5610905A
Cited
US5515376A
Cited
US5473607A
Cited
US5422838A
Cited
US5574861A
Cited
US5790546A
Cited
US5485455A
Cited
US5570365A
Cited
US5535202A
Cited
US5761435A
Cited
US5509123A
Cited
US5459717A
Cited
US5493564A
Cited
US5602841A
Cited
US5572522A
Cited
US5592476A
Cited
US5557610A
Cited
US5689518A
Cited
US5606669A
Cited
US5461611A
Cited
US5617421A
Cited
US5583981A
Cited
US5600641A
Cited
US5615340A
Cited
US5751967A
Cited
US5640605A
Cited
US5619500A
Cited
US5594727A
Cited
US5490139A
Cited
US5784573A
Cited
US5931980A
Cited
US5726977A
Cited
US5566170A
Cited
US5550816A
Cited
US5734651A
Cited
US5563878A
Cited
US5745048A
Cited
US5706472A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-04-11 | 2003-10-11 | 2004-04-11 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-04-11 | 2007-10-11 | 2008-04-11 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-04-11 | 2011-10-11 | 2012-04-11 | $7700.00 | Window Closed / Lapsed |