throbber

`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`PROVISIONAL APPLICATION FOR LETTERS PATENT
`
`EV1883905 3.6
`
`A Wireless Data Packet Communications System
`
`Inventor(s):
`Marcusda Silva
`William J. Crilly, Jr.
`James Brennan
`Robert J. Conley
`Siavash Alamouti
`
`Edward Casas
`
`ATTORNEY'S DOCKET NO. MNI-010USP1
`
`1
`
`AMAZON.COM,INC., et al.
`EXHIBIT 1009
`
`1
`
`

`

`
`
`TECHNICALFIELD
`
`This invention relates to wireless communications and more particularly to
`
`methods and apparatuses for use in wircless data packet communications systems
`
`capable of supporting multiple point-to-point links, packet-by-packetsteering, and
`
`the like.
`
`BACKGROUND
`
`Conventional wircless local area network (LAN) systems typically employ
`a micro-cellular arrangement, wherein, for cxample, a small base station, often
`
`referred to as an Access Point (AP), is configured to communicate with wireless
`
`devices attached to computing devices, such as, laptops or other portable data
`
`appliances. These APs have a limited range, typically 20 to 200 feet for an IEEE
`
`802.11(b) system. Thus, to covera large area a system may require a plurality of
`
`APs. This can be costly and tends to complicate the wireless system.
`
`There is a need for improved methods and apparatuses that can provide
`
`wireless communications.
`
`DESCRIPTION
`
`The following description sets forth a specific embodiment of a wireless
`
`communications
`
`system that
`
`incorporates elements
`
`recited in the appended
`
`exemplary claims and others. The embodiments are described herein and in the
`
`attached documentation. However, the description itself is not intended to limit
`
`the scope of this patent. Rather,
`
`the inventors have contemplated that
`
`the
`
`invention might also be embodied in other ways, to include different elements or
`
`20
`
`21
`
`22
`
`24
`
`25
`
`Ine@hayespie
`
`509-224-9256
`
`]
`
`1102022220 MN1-O10USPLPATAPP_DOC
`
`2
`
`

`

`
`
`combinations of elements similar to the ones described in this document,
`
`in
`
`conjunction with other present or future technologies.
`
`With this in mind, methods, apparatuses, and systems are provided for a
`
`project code-named “Little Joc” developed by Vivato Incorporated (formally
`
`known as Mabuhay Networks) having research and development offices in
`
`Spokane, WA, and headquarters in San Francisco, CA.
`
`Incorporated herein are the following appendices:
`
`A.
`
`B.
`
`C.
`
`D.
`
`E.
`| F,
`
`Document: Little Joe Functional Specification (113 Pages)
`
`Document: Behavior of 802.11 Networks With Mabuhay Access
`
`Points (15 Pages)
`
`Document: Beamforming for Little Joe (25 Pages)
`
`Document: Little Joe Link Budget (15 Pages)
`
`HTML Document: SimpleMAC(1 Page)
`Presentation Slides: Prototype Story Board (17 Pages)
`
`G.
`
`Copy of various lab notebook pages 2-3,45-49, 57, 89-93, 106-107
`
`H.
`
`L.
`
`J.
`
`(15 Pages)
`
`Drawings: System Diagram (9 Pages)
`
`Document: Quickfacts - DirectedPacket 1 (5 Pages)
`
`Document: Conceptual Proposal for Little Joe Antenna (3 Pages)
`
`Presentation Slides: DirectedPacket™ 1 Logical View (7 Pages)
`
`L.
`
`Presentation Slides: Little Joe Digital Block (5 Pages)
`
`21
`
`22
`
`23
`
`25
`
`lee@nayespe cooazesa00
`
`2
`
`1102022120 bINT-OLOUSPI PATAPP.DOC
`
`3
`
`

`

`
`
`EXEMPLARY CLAIMS
`
`1.
`
`A method comprising:
`
`using at least one electronically steerable phase array antenna in a wireless
`
`data packet communications system.
`
`2.
`
`The method as recited in Claim 1, wherein using said at least one
`
`electronically steerable phase array antenna in said wireless data packet
`
`communications system further includes:
`
`using said at least one electronically steerable phase array antenna indoors.
`
`3.
`
`The method as recited in Claim 1, wherein said wireless data packet
`
`communications system uses packet-by-packet steering.
`
`4.
`
`The method as recited in Claim 1, wherein said wireless data packet
`
`communications system implements a CSMA scheme.
`
`5.|The method asrecited in Claim 1, wherein said wireless data packet
`
`communications system includes a scanning recciver.
`
`6.
`
`The method as recited in Claim 1, wherein said wireless data packet
`
`communications system uses array windowing.
`
`7.
`
`The method as recited in Claim |, wherein said wireless data packet
`
`communications system includes a Butler Matrix.
`
`20
`
`21
`
`22
`
`23
`
`25
`
`lee@hayespic
`
`509-324-9256
`
`3
`
`1102022220 MNIT-OLOUSPT PAT. APP.DOC
`
`4
`
`

`

`
`
`8.
`
`The method as recited in Claim 1, wherein said wireless data packet
`
`communications system includes at least one Little Joe device.
`
`9.
`
`A Little Joe device.
`
`10.
`
`A communications system having at least one Little Joc device.
`
`11.
`
`A propagatedsignal from a Little Joc device.
`
`
`
`lee@hayes pu
`
`s0%224-02nA
`
`4
`
`1102022220 MNI-ULUUSPLPATL.APP.DOC
`
`5
`
`

`

`
`
`Little Joe Functional Specification
`
`6
`
`

`

`Little Joe Functional Specification
`
`
`
`Document History
`
`
`Contributor(s)
`
`
`
`Description Date
`
`
`
`
`
`
`
`
`
`
`7
`
`

`

`
`
`Table of Contents
`
`
`
`Contents.
`
`
`Part |: Radio and MAC.
`Introduction... ccc ecccene eee cee neces seen eneeeeeceaaeaenseeeeuscssneeseeeaaeeeceeaaaereseceageseseausaeeeesenane ees 7
`L.
`2.
`System Architecture ........ccc cece sseereeeesrerersreeeeereseessecereeseneeees teeeeceeerteaesneeeenaseeseaeeceea 8
`
`2.1. SYSHOM ooo. ee cececceeceeeeeeneeaneeenseeescaaeeeennaneeeeneeeeeeeneesnseeeeseaasseesesssenennensaaaseseeneeeeee 8
`
`
`Deployment Sccnarios...............
`10
`2.2.
`‘Typical Building Structure....
`12
`2.2.2.
`
`Traffic Load Assumptions ............0...000.cceens cece cece cece e cee cee ce ten vnneeerenecteeeeteneeens 12
`2.2.3.
`2.3.
`Interference effects ........ec e
`i eee ce cee eter nee cece ened nine cte cee seterepeee sneesceaeeesseeeeee 13
`2.4.
`Coverage requirements .................
`13
`2.5.
`Throughput and delay requirements.
`15
`lS
`2.5.1.
`Performance Metrics .............
`
`Performance limiting issues ......0. 0...c cece eee c cece eee e ee ce eee c ata e ena eeceeeeteeeeeseeeeees 15
`2.6.
`2.7.
` Technology.........eeeseesecccecccceee cece econ eee c esate sone saaceee sna sea eens eeepc cn case gas eeeenersereerseneennree 16
`2.8.
`System Block Diagram..
`16
`The Beamforming Network...
`19
`3.1.
`The Butler Matnx..........
`1D
`3.2.
`Ideal BeamPatterns ....... cece cece sence reece see nnee eee e re eennnaeseeeeeeerer nega sea neereesereneegs 20
`3.3.
`Receive WindoOwiIng............ececceeeseeceesecccecencetteeec crete ene cee cor ces eens nen ensteeer tree ceeteeeeceeeees 23
`3.3.1.
`The Hamming Window.........
`23
`
`3.4. Complementary Transmit Beamformiung..........0..eeeeercreeereeeereeeteee 26
`A.csnenssneeeerenesneeteesesseeaasssanecerseseeecerensinaceeees 28Link Budgets ...... eee eececceee cee eee creer ene aee nese
`
`
`
`Link Power Budget... cece cc cece cee cece cree caesar anes ce neee se eane cece ga ave raven reper sneneeeeeeenees 28
`4.1.
`4.2.
`Link Budget Pararmeters......... cece cern creer ener re cnee neenne cape eeerer spree reves se ereeenean ines 30
`we
`4.2.1.
`Panel Transmit Power: FCC EIRP Power Limits...
`
`4.3.|Characteristics of Conventional 802.1 1b Equipment oo...eee 31
`4.3.1,
`Pancl Antemma Gain .......ccccccccceeceenececeneceeenerseeeeeeeeersceeteneneeenenag eve rrregeteneecrees 33
`4.3.2.
`Gain Reduction due to Scattering ..........cccccecceeececeeeeeceeeeeeectnessescerceseeeseeenerees 33
`4.3.3.
`Client Antena Gait... ccc cece cccec cee ceecceeeeceneeeceneeceageuseneesaaeeneepeceeeaesenersneas 34
`Client and Panel Noise Figures
`34
`4.3.4.
`
`Effect of Shadow Fading .0.............ccscecceeeeseseerceeesesensnereeeeeeserseerseevnscaseaeeaseeseees 35
`4.3.5.
`
`4.3.6. Effect of Rayleigh Fading ........0...cccceeececeeeeenereeeenseeeceeeeerseneneeeseeeeseseeeeees 36
`
`
`4.4.—Path Loss Models 0000.00.02... cccccecccceccseececeeeceneneneacerseeeeeceaeeuseeanegensrenesesenesamausaaeaasoeas 36
`44.1.
`Propagation in Free Space (LOS)uo... ccc cess ccseeseeaerseesteeesessesseeesspeerenees 37
`vee
`4.4.2.
`Propagation by Diffraction (NLOS) ....
`
`Propagation by Transmission (OBS) .........0....cce: cescsceececseeeereneeseeensnneeeennnteeees 37
`4.4.3.
`4.4.4,
`Outdoor-Indoor Path Loss... cece ees ee eeerceenseseeecneneesseresrnenseeasreees 38
`445.
`Indoor-Indoor Path LOSS.............c cee ceeeeeeeeeeneneteeeneneeeneneeeeeeeeeresescnees teceecteeerreees 39
`4.5.
`Link Budget Results 200.0000... ecee ccc ce cece sce eeee centr cere eeeeerceeectenesaaeecnaseeaseageees 39
`:
`Transmit Power Control...........
`
`Power Control Requirements..........0.0.0 cece eee eee creer cence esate ceaeseteeeeteaee 42
`5.1.
`5.2.
`Power Control State Transition Diagram........0......cee ccc ceeeeeeeeeeecee centre ete te teeeeaaaae 4B
`5.3.
`Power Control SNR Measurement.....00.......0..00ccccccceeeee cee c cee e eee eee tees ceeeeaaseseeaeaenaees 44
`
`
`
`
`
`3.
`
`5.
`
`8
`
`

`

`a
`

`
`Little Joe Functional Specification
`
`
`
`
`
`8.
`
`9.
`
`6. Media Access Control (MAC).o0..... i... cceecce cee cceeceeceeenee cease sees csececsaneesceeecsaeesnieeseneeseeees 44
`6.1.
` ViVATO Panel MACOperation...
`.
`6.1.1.
`MAC Modesof Operation.....
`7, Multi-Radio Transmit Controloe eer ete vpn a ree aae case eneeeesecees 46
`7.4. MultitMAC Control (MMC)... ccc ccccccee cee cee cc ccceeceeeeeeecasacenaseaaaieesseneeeteeeeceseeeenees 47
`7.2.) MMC OVErVICW.L.. eee cccetceee cece cece eee ecreeensneeeerensueennnrereccnterersieeececsrnneesenterensngaess 47
`7.3. MMC Provisioned Parametert.............0......eeeeeeeecceceeeeesecnesaceeeecceeccteeetnaaneceeseneenee 48
`Intra-Panel Roaming.......0000.00.000.
`.
`
`Roaming Requirements. .......0.. cee eee cee nee en edad nee reece renee ae ea tee 49
`8.1.
`8.2.
`Beam-Switching Algorithm ©... eee eee ee eee eceeenae nee sees eeneeesaaaaeeeeeeeaes 49
`8.2.1.
`Beam-Switching State Transition Diagram...ee ee ee eer eeeee eee OO
`8.3.
` IAPP (Seamless Roaming).....0..0.........222::ccccceecceccee eee eeeeeereeecceceereecenecnenaereeeeseeees 52
`.
`Channel Assignment.......0.... 0 ce etereeereees
`
`Channel Assignment Provisioned Parametetrs.............00000000 tees cece eenerrnceteeetes 53
`9.1.
`9.2.
`Channel Assignment Internal Parameters.......0...00.eee eee cent reeees 53
`9.3.
`Channel Assignment Metrics...0...00.0.ccc nee cere eee anette ee tees 53
`9.4.
`Channel Assignment Algorithm 2.00.00... eee e eect eet eeeeeee en tte etna ee eeeetee 55
`9.4.1.
`Channet Assignment Preprocessing......
`
`Block-based Channel Assignment Algonthm 2000.00.00...ee DO
`9.4.2.
`9.4.3.
`Emergency €Xit
`..... 2... ce eeeeeceec cee cere eencee cece ee rennet eee een n net ene e tte e cee enaeeeeeeeeeeenea 60
`
`Downlink Traffic-Shaping .............. 00... ceccceseseec sees cece ee seeeeeee spac cau neeenegeeeteeeeceeeseeeeerpentee 61 10.1.
`
`10.
`
`Traffic-Shaping Requirement.............0..2ccee cece cece eet e tee c cece ecee cee cen tne ecneeesteetdnneenes 61
`Traffic-Shaping Architecture .............
`61
`10.2.
`Traffic-Shaping Functional Description ........0....00..ceee ceeeeeeeceeen ree etree eeeeneeteeeeeee 63
`10.3.
`Leaky Bucket Algorithin........ 2... ce cece cece eee e rece reece erence case eeenerebenereneneneeess 63
`10.3.1.
`64
`10.3.2. Granularity of Operation .............
`
`10.3.3. Dynamic Parameter Update...............
`..64
`
`10.3.4. Operating Point Estimation Algorithm.
`65
`
`Provisioned and Internal Parameters...................ccecceeecceeeeeeeeeeeeer tree ceeteneteecteeetees 66
`10.4.
`1.
`The Scanning Radio ...........ccceeeeeeeeeceeeeecececeeeeeeeeesceececeeeeteeeeeeeeeeeteeereeeseneesiseeesneeenneetees 67
`67
`HH.
`Scan Mode........
`
`
`Roaming ...........
`68
`11.2.
`68
`14.3.
`State Transitions ..
`
`RE PEPeN eS «2... c cece cece cece ec eeneneceeteeeeenereceeaatteneeeeaeassaenetenssaaestsaetteeesageseneasenen eens 69
`12.
`Part 2: Software System Architecture .......eee ccee cease ccccesseeneennevseeseuanesueuseserneneeenneeeees 72
`72
`13.
`Introduction..............: eee
`
`Software Overview .............cceeeceeeeceeeee
`74
`14.
`
`Software not covered by this Document.
`74
`14.1.
`
`Software Module Overview .........ccccccccccececccecsccenecceceeseeenseeeeceeeeceeeesqaeaienenenentneeesnee 75
`14.2.
`Control Plane... ccc ccececccccneeeeceeeean sees ceceeeeeeaa beeeteeeataneseeeeessteneseneae sees ssaaeeeeteainensnns 76
`15.
`16.
`Drivers«0.2.0.0...
`
`Console Driver.....
`16.1.
`
`Ethernet Drivers............
`16.2.
`
`
`Secure Management.................
`16.2.1.
`Backhaul / Daisy-chain for the Next Pancl......... eee ceceeeenereeeneeeeenereeees 78
`16.2.2.
`
`ao
`
`9
`
`

`

`
`
`Source for Wireless Drivers.................:.0 00s sc ceeeseeeee tence cent eee cee ene scte cee cesaesaaeeenenenees 719
`16.3.
`Searcher and Merlin Interfaces and Functions .............00... cece ee ee erence ates 79
`16.4.
`
`Scheduler / Shaper.........0....ceeeseeeeeees
`16.5.
`RRM (Radio Resource Managemen
`16.6.
`
`FLASH 0... ccccececceeeeceeecceeeneeeereveceececeeteseeeeeeetieennneeeneeerttetcteectees
`16.7.
`This table showsinitial estimations of management module resource usage. Need clarification
`of data items in the table. Some of these items are daemons, running all of the time. Others
`are one instance per invocation. Cish is dependent onlots of other elements, such as ipchains,
`bretl and ifconfig. ...........2.. 0 eee cca
`
`17.
`ManagementInterfaces
`- 83
`
`VP HEP ieee ce eee eeeEEE ena e ea eee nese nen enna camer ete eeenaee 85
`17.2
`CISH (COD Looe eee ceecceee ce cece cece eee cenee cere een ctteseacee snes scaaaeensaeseaaseeesseneesneesenneenenes 86
`87
`17.3 User Manager .......... 00. eee eeeec cece eee c cence nee tect teteeeneeaeeneeees
`
`SSHD occe cence ec cnec tesa etenee tae eteneeeeneesreeeereeeecnneees
`87
`17.4
`
`87
`Telnet...
`17.5
`
`SNMPD.... oo. ccccccceeccecececeeceeecesececeaeentneceeeeecesecneeespeesceneecasecasassaaseneastanecseeecaeeciesers 87
`17.6
`18.
`Environmental Control] 20.00.2000... cece eec cece eee eeecen acne cert epee epee ce scene state cnsenseaesseeecnnaseeness 87
`88
`18.1
`Temperature and Fan Control .............00.00...
`
`19, Wireless Control .....0.... 0... cece certs
`..88
`
`88
`19.1 Wireless Bridging.......
`
`19.2 Centralized Bridging .........22....2..ccccceee cece cee erect eee ec eet acca cones canes aeeeeneneceeae 89
`19.4
`Radio Configuration Manager...............ccc cece cece eter er crete cette tenes eee e eee tnnteee ones 90
`19.4
`Inter-card Roaming Manager...................-
`90
`Mabuhay Enhanced Performance System (MEPS)....
`..90
`90
`SOQCUIILY 0c eee ee eet tnee eee eee ce renee nnceeaaeeee reer rerrceeeaeee
`
`19.4 Authentication Managet....... 02... eceeceeccccccee cece cet tee ce ee ees canaaseaeeceeescenecisceseseeereatenenaees 90
`19.4 Authentication ........... cece cece cee cence e tere ten rete eee teeta ne es eeeeecenreneaeeeeeeennnenaeaeee 90
`19.4
`802.1x / EAP Authentication Mechanism.
`
`19,
`Other Control.....
`
`19.4. DHCP Client 2.0.0... cee eset ceseeeesenecneanteeeereeens
`19.
`DHCPServer and Network Address Translation (NAT) .............. es 92
`19.
`Typical Packet Walk (Bridged)... ces ceecscsssecesseeeecree tenes teecenecnceeeciseecaeetesenseeeenees 93
`19,
`Typical Packct Walk (NAT and DHCP Server) .
`.93
`
`
`
`
`
`19. DiagnOsliCs 00.0.0... cece eeeeeceeesseeeecececenaeeencneansneneeeseeneeeregnnsonsireeeesonneeregirecerseressenneees 95
`
`
`19. Out-of-the-Box Power-up SCQUence .........eeciesceeeteeterteertteeeceeeesenee ces eeecneereneeetee 95
`
`19. HERES.ec ccceee een eceee cere reece cece teens cneceseeeereeeesesessmeeesesaesaeuananssaneasanaecrrisssenenes 95
`19.4
`FTP Client (for downloading new Images)... cece cece eeeneenee nee eee centres ieee 95
`FTP Server (for Serving images to otherpanels)..
`19.
`95
`
`19. Data Packet Interfaces 2.0.0.0... ccc cet eece cece beetsreneeeececeee eeneceeeseeseecenneseenecensecersneeeeres: 96
`
`
`Appendix A — PCI / PCI Bridge Support in Linux
`.........:cec eee teeter ere ceree eres ennetenes 97
`19.
`Example PCI Based System oe... cece cere ceeesseeeecneeesensseeescsesceneseeersneeessaeeeees 97
`19.4
`19.4
`PCD Address Spaces 2.0.2... cece cceere cence ce eae scene cenecceeeeseees cng eeaaaeeeeeesenerisnnereneesnes 97
`ven
`19.4
`PCI Configuration Headers..........0......
`
`Layout of the 256 byte PCI configuration header.............cc:ccceeeee tees eete ere reees 99
`19.4
`19.
`Vendor Identification 0.0... cececcece cece ee tee nets ee ae csaae sta cae aesneeeegererenenreess 99
`
`
`
`
`
`10
`
`10
`
`

`

`L
`
`Little Joe Functional Specification
`
`
`
`Device Identification... cee cece ete ce ccc a cece tere ceea nee eaaaee ces teaeeeg gas eeeeenpnernpngaees 99
`19.
`SUAS 200 cece cece eneee eee ee neuen eee seen ee ereeeeneeycetessepeuee ges seeeseeteere cen eesteateaeeeeeeeeeeees 99
`19.
`COmmanhhd 00... .cccccceecccesessen cen eeeeeesceneeceee cee ceeceeecesvenseceeeeesseeeceenceveeee gee seeeirecerecereeees 99
`19.
`2299
`Class Code...
`19,
`
`Base Address Registers 20.0.0... cece cee cee ereeesneceeceeeerneecceer tetas ceeeeceentieeeeeeeesenenree 100
`19.4
`Interrupt Pin...ec cece eee cen tee ceeneeneeecsennnsaeessaeesanesseeannanecnenesnegerieeees 100
`19.4
`... 100
`Interrupt Line... ee
`19.4
`
`PCI I/O and PC] Memory Addresses... cece eee cee cece cece cet cece eet nnne tees teeeeees 100
`19.
`PCLISA Bridges ............cccceceescceeeeee cess eee cneneeeeececeecencecaeeseeaseeeesseeestenseseesieasscnaeees 100
`19.
`
`101
`PCE-PCI Bridges .......0.. eee eeece cee ce eee tesseeteneteeeetiees
`19.
`
`PCI-PCI Bridges: PCI /O and PC] Memory Windows........000.000::cectetteeteeeeeee 101
`19.
`PCI-PCI Bridges - PCI Configuration Cycles and PCI Bus Numbering................ 101
`19.
`
`Type 0 PCI Configuration Cycle Figure: 2.0.0... eee ceeeteerneeeretieteiete:
`101
`... 102
`Type | PCI Configuration Cycle Figure: .....
`... 103
`19.
`Linux PCI Initialization 0.0.0.0.
`.. 103
`The Linux Kemel PCI Data Structures ......0.... eee
`.
`19.4.
`
`The PCI Device Driver... ccs cee senentee ee ceeeseererineeeeees
`.. LO4
`19.4
`
`... 105
`19.
`Configuring PCI-PCI Bridges - Assigning PCI Bus Numbers
`
`PCT I/O and PCI Memory Windows 0.0... ce ece ec eeeeceeeeceee cere renee eee eee ete
`... 106
`b.
`
`.. 106
`a.
`PCI-PCI] Bridge Numbering: Step 1 ou... cesses cere rent ceeerreneeeseetenees
`
`b.
`PCI-PCI Bridge Numbering: Step 2...
`... 106
`d.
`PCI-PCI Bridge Numbering: Step 4.0.0.0... cc cece cee cece seen tene tree e terre ere tere eeeeeeen eres 107
`€.
`PCI BIOS Functions 00.0... eeeeeceeecceenseeceseneeeeeeeeesenecereseneenneecengeseneeniensceeeeteneenn es 108
`
`fo
`PCT FIXUp 2... ccc eee ccteseeeeerenseeessenenreesceeeneeesserensceeceerecesenscecssensaeeaaaas
`108
` Hinding Out How Much PCT I/O and PCI Memory Space a Device Needs............... 108
`g.
`PCI Configuration Header: Base Address Registers ............ccceeccceeceerteere ete 109
`a.
`b. Allocating PCI I/O and PCI Memory to PCI-PCI Bridges and Devices................ 109
`
`11
`
`11
`
`

`

`
`
`Part 1: Radio and MAC
`
`Overview
`
`This document describes the LittleJoe 802.11b WiFi switch (WS) from a functional point-of-
`view. The document includes system description, the beamforming functions, radio resource
`management (RRM), and the media access control (MAC)functionality. Higher layer
`functionality, network managementand other functions are described in separate documents M.
`Brewer, D. Lohman,et. al. “Software System Architecture Document’, V1.
`
`The functional descriptions in this document provide details of the functions performed by any
`subsystem. Thefinal architectural design is discussed in separate documents including the
`control and interface functions between the subsystems.
`
`The product concept is discussed in Introduction.
`
`The highlevel system architecture is presented in
`
`System Architecture
`
`. The beamforming network whichis the core technology ofthis product is described in ‘The
`Beamforming Network.
`
`Theradio link budgets are presented in Link Budgets
`
`‘The transmit power control schemeis described in Transmit Power
`Control. The media access contro! (MAC)is described in Media Access
`Control (MAC). The multi-radio transmit control, multi-MAC Control
`(MMC)and roaming are discussed in
`
`Multi-Radio ‘Transmit Control
`
`Multi-MAC Control, and Intra-Panel Roaming respectively. The channel
`assignment and tratfic shaping algorithmsare described in Channel
`
`12
`
`12
`
`

`

`1
`
`Little Joc Functional Specification
`
`
`
`Assignment and Dowrespectively. The scanning radio functions are
`described in
`
`The Scanning Radio
`
`1. Introduction
`
`LittleJoe is ViVATO’s first-generation long-range packet switch built according to the 802.11
`standard. It seamlessly supports 802.11b clients. ‘he LittleJoe Wifi switch features:
`
`linear array of 16 antennas providing up to 29 dBi of gain

`* Butler-matrix beamforming
`= Complementary beamtorming
`*« Multi-MAC controller
`
`« Multi-channel operation
`* a high sensitivity RF front end
`« Agere 802.11b MAC and baseband processor chips
`* Custom logic and software for integration
`+ Security enhancements
`
`There are two configurations:
`
`+ DirectedPacket™ 1 (DP2310) transmits on one channelat a time
`* DirectedPacket™ 3 (DP2330) transmits up to 3 channels at a time
`
`Thesecan befit into two types of antennas/enclosures:
`
`« Indoor half height: Im wide by 0.5 m high
`* Outdoorfull height: 1m wide by Im high
`
`2. System Architecture
`
`In this section we review the ViVATO Packet Switch concept and it’s advantages comparcd to
`existing APs in the market. We also describe ViVA1T0’s high-level system block diagram. The
`details of the subsystems are then described in different sections within the document.
`
`13
`
`13
`
`

`

`
`
`17.3
`
`System Concept
`
`Figure 2 A typical deployment for conventional 802.11 APs is shown in Reference deploymentfor
`802.11 networks.. The example deployment scenario assumes a 10,000 m coverage area covered
`by 9 conventional APs each with a celiular coverage radius of 20 m. The assumed coverage cells
`are circular each with a radius of 20 m. The reference LittleJoe deployment is shown in Reference
`LittleJoe indoor deployment.
`
`One LittleJoe panel (with a range of about 140 m)is used (typically at the corner of a building
`indoors or mounted ona tall structure outdoors) to provide service to the whole coverage area. In
`some deployment scenarios, there are regions where LittleJoe cannot provide service due to
`shadowingorsevere scattering. This is represented by the gray shadedcircle in Reference
`LittleJoe indoor deployment.
`
`Such areas will be covered using ViVATO APs. In the above example, 9 regular APs have been
`replaced by one LittleJoe Packet Switch and one ViVATOAP. This reduces the cost of network
`deployment. Ln addition,it is possible to provide outdoor coverage by deploying the unit
`outdoors.
`
`100 m
`
`
`100m
`
`Ls 802.116 AP on channel 1, 2 or 3 (not-to-scale}.
`
`14
`
`14
`
`

`

`Little Joe Functional Specification
`
`
`
`Figure 1 Reference deploymentfor 802.11
`
`
`4 be
`
`100m
`
`networks.
`
`HBLittleJoe WS (not-to-scale).
`Ln 802.11b AP on channe? 1, 2 or 3 (not-te-scale).
`
`Figure 2 Reference LittleJoe indoor deployment.
`
`17.3
`
`Deployment Scenarios
`
`LittleJoe is a long-range WiFi switch and therefore it can support many different applications.
`Nevertheless, there are five reference deployment scenarios identified:
`+
`Indoor Office
`* Indoor Warehouse
`
`+ Outdoor Campus
`* OutdoorHotel
`+ Outdoor ISP
`
`17.1
`
`Typical Mounting Conditions
`
`There are two types of LittlcJoc units: half height indoor and full height outdoor.
`
`A-te
`
`15
`
`15
`
`

`

`
`
`2...1.
`
`Indoor Deployment
`
`A LittleJoe WSis placed inside the building to provide coverage throughout the whole building.
`
`Typically a half height LittleJoe panel is installed on a comer wall inside an office building or a
`warehouse. The ceiling height is typically between 3 to 4m for the office building and 4 to 8m in
`a warchousc.
`
`The center of the panel is typically installed at 0.25m below theceiling. The unit should be
`mounted away from nearby scatterers or obstructions.
`
`2...2. Outdoor Deployment
`
`Typically one to four co-located full height LittleJoe panels are installed in a desirable location
`on campus grounds, each panel providing 100° coverage. The typical antenna hcightis 4 to 20m.
`The furthest building to LittheJoe installation site is no more than 200m away. The buildings are
`low-rise (6 stories or less). The scatterers are mostly local to the client and not close to the
`LittleJoe panel.
`
`For the Outdoor Hotel model, the typical antenna heights would be about 4 - 8m and the building
`would be no more than 20m away from the panel.
`
`The typical ranges and mounting conditions for the different deployment scenarios are
`summarized in The range and antenna dimensions and heightsfor different de.
`
`indoor
`office
`
`indoor
`warehouse
`
`outdoor
`office
`
`outdoor
`Hotel
`
`outdoor
`ISP
`
`range 2km < 150m 300m
`
`
`
`antenna
`tm x 0.5m
`Im x lm
`Im x 1m
`size
`
`height
`
`
`
`antenna 4 to 20m|4mto 8m|10 to 50m3 to 4m 4 to 8m
`
`
`
`
`
`A-U
`
`16
`
`16
`
`

`

`Little Joe Functional Specification
`
`
`
`Table 1
`
`The range and antenna
`dimensions and heights for
`different deployment scenarios.
`
`1.1.1
`
`17.1. Typical Building Structure
`
`The exterior walls are typically concrete or other hard construction material.There are usually
`many windows and metal on the exterior of the building.
`
`Theinterior walls are not hard structures. They are typically made of drywall with woodor metal
`studs. The floors are typically made of concrete. The interior of the building has mostly open
`offices with soft enclosed cubicles. There may be some dry-wall enclosedoffices and conference
`rooms with or without interior windows.
`
`The unit is built with sufficient link budget to operate with the assumptions above. However, a
`site may have areas of exceptionally high path loss. These poor coverage areas may be serviced
`using ViVATO APs' connectedto the LittleJoe panel through the backbone network or in-band
`802.11 signalling.
`
`1.1.2
`
`17.1 Traffic Load Assumptions
`
`There may be more than 200 associated users inside the building. Most users are connected to a
`wired network and hence do not generate any traffic unless when they require portable
`connectivity. Nevertheless, they may send probe request frames regularly. The network is
`expected to perform well with a maximum of 50 active users each with a profile of a “typical”
`LANuser. Thetraffic load assumptions for the different deployment scenarios are summarized
`in Traffic load assumptions fordifferent deployment scenarios..
`
`
`outdoor
`indoor
`indoor
`outdoor
`outdoor
`
`
`
`warehouse
`office
`Hotel
`ISP
`office
`
`
`
`
`> 200
`
`
`associated
`> 200
`400 >200 >200
`
`users
`
`
`'A ViVATO AP(also known asthe Pollen8) is an open-source AP whose software has
`been updated to work effectively with the LittleJoe WPS. The details will be described in
`separate documents.
`
`17
`
`17
`
`

`

`
`
`
`
`users
`
`profile
`
`office
`LAN
`
`short
`transactions
`
`office
`LAN
`
`home
`LAN
`
`home
`LAN
`
`active | 20 50 40 10 40
`
`
`
`
`
`
`
`
`Table 2
`
`Traffic load assumptions for
`different deployment scenarios.
`
`17.3
`
`Interference effects
`
`The following are the major sources of interference to the ViVATO network:
`
`* Microwaveovens: create a coverage hole of 5-10 mwhile they are transmitting.It is
`recommended that the panel be placed as far away as possible from microwave ovens.It is
`also advisuble to shicld the microwave ovens to reduce interference to the network.
`
`Cordless phones: many operate on the same band and can henceinterfere severely with
`both the panel and client transmissions. It is advised that cordless phones in office and
`warehouse deployments not be used. For the ISP deployment scenario, the cordless phones
`will be a significant source of interference and may reduce the networks performance to
`unacceptable levels.
`802.11 private LANs: the ViVATO network shares the frequency resources with other
`802.11 networks.
`
`17.3
`
`Coverage requirements
`
`Coverage is defined as a packet error rate of 10% or better at a specified data rate. LittleJoe
`should have an indoor coverage of 85% coverage at
`|1 Mbits/s and 95% at 5.5 Mbits/sec.
`ViVATO APsare used tofill in large coverage holes in rare places (no more than 10% of the
`coverage area) due to severe deploymentconditions.
`
`The nominal expected coverage for the different deployment scenarios are summarized in
`Coverage for different deployment scenarios..
`indoor
`indoor
`outdoor
`outdoor
`outdoor
`office
`warehouse
`office
`Hotel
`ISP
`
`
`
`85%
`
`1] Mb/s
`coverage
`
`
`85%
`
`85%
`
`85%
`
`TS%
`
`“15
`
`18
`
`18
`
`

`

`‘
`
`#
`fad? Hall a
`
`Little Joe Functional Specification
`
`B%
`
`95%
`
`95%
`
`95%
`
`5.5 Mb/s
`coverage
`
`coverage
`holes
`
`5-15%
`
`
`
`
`
`$-15%
`
`5-15%
`
`5-15%
`
`19
`
`19
`
`

`

`
`
`Table 3
`
`Coveragefordifferent
`deployment scenarios.
`
`1.2
`
`17.3
`
`Throughput and delay requirements
`
`The user experience should be similar to that of a deployment of multiple low-range access
`points shown in Reference deploymentfor 802.11 networks..
`
`17.1 Performance Metrics
`
`The following performance metrics measure the quality of service provided by LittleJoe
`compared to conventional 802.11 deployments. These are non-real-time traffic measures G.
`Anastasi, et. al., “MAC Protocols for Wideband Wireless Local Access: Ev:
`
`Packet queuing delay: the time elapsed fromthe time a packet is generated until it is ready
`to contend for access to the channel
`
`Packet MAC delay: the time elapsed between the time a packet is ready to contend until the
`beginning ofits successful transmission
`Packet access delay: the sum ofthe queueing delay and MAC delay
`Packet transmission time: the time betweenthe start of a transmission to its successtul
`completion.
`Packet throughput: the numberof bits transmitted in a packet divided by packet
`transmission time.
`
`Packet loss rate: the number of packets whose transmissiontime exceeds TCP time-out.
`
`17.3
`
`Performancelimiting issues
`
`The following effects are the most detrimental to LittleJoe performance:
`
`+ Nearby large scatterers
`« hard structures (hard walls, metal objects, etc.)
`* competing $02.11 networks
`+ high angle spread environment
`* microwave ovens
`
`+ 2.4 GHz cordless phones
`
`20
`
`20
`
`

`

`
`
`Little Joe Functional Specification
`
`1.3
`
`17.3
`
`Technology
`
`The technologies enabling the increased coverage for LittleJoe are:
`
`« Phased Arrays
`- vertical antenna gain
`- directional receive and transmit patterns using a Butler matrix
`-
`taking advantage of point-to-point power limits
`* Technologies to enable directional antennas with 802.11
`- complementary beamforming
`- Multi-Radio Transmit Control
`- Multi-MACcontrol
`
`Additiona! capacity gain is obtained using:
`
`+ multi-channel operation
`* seamless roamimg
`*
`traffic-shaping
`
`1.4
`
`17.3
`
`System Block Diagram
`
`This section includes the functional block diagram of LittleJoe. The single channel product
`(DP2310) can operate on a single channel at any time. The 3 channel product call DP2330 can
`operate on three different channels simultaneously.
`
`Figure 3 The block diagram for The DP2330 product is shown in The DP2330
`high-level block diagram.
`
`. There are 16 antenna elements each with its own RF front-end. The receive port of each
`circulator is followed by an LNA before the Butler matrix. The circulators ensure that:
`
`* signals arriving at the antenna elements are directed to the receive chain and tsolated from
`the transmit chain
`
`* signals transmitted through the transmit chain are directed to the antenna elements and
`isolated from the receive chain.
`
`21
`
`21
`
`

`

`switch
`
`Butter
`matrix
`
`13x3
`crosspoint
`
`
`
`13x3
`crosspoint
`switch
`
`Figure 3. The DP2330 high-level biock diagram.
`
`Each PAis followed by a ceramic bandpassfilter. To allow for simultancous transmit and
`receive on adjacent channels the LNA can handle strong input signal with no distortion and the
`post-PA bandpassfilters have high adjacent-channelrejection.
`
`The PA output powers can be reduced from thcir maximum levels in by least 24 dB (4 steps of 6
`dB).
`
`A single-channel cost-rcduced model (DP2310) may use switches instead ofcirculators and
`eliminate the crosspoint switches andfilters.
`
`7.5
`
`The Butler Matrix described in detail in
`
`The Butler Matrix
`
`22
`
`22
`
`

`

`
`
`Little Joe Functional Specification
`
`is a networkof passive hybrid power dividers and fixed phase shifters with 16 inputs and 16
`outputs. The Butler matrix produces 16 orthogonal beams eachpointingin a different direction.
`However, since the patternis distorted at the extreme angles, only 13 ports of the Butler matrix
`on the radios side are used.
`
`Figure 3 Each Butler matrix port at the radio side is connected to a splitter which
`splits the signal to a WLAN radio and a 13-way switch whichis connected to a
`scanning radio (not shown in The DP2330high-level block diagram.
`
`Figure 3 ).
`
`1.6 Each WLAN radiois built using the Agere 802.11b chipset’. The
`Agere MAC controller is used and runs AP firmware. See
`
`ViV for more details.
`
`The receive ports of the 13 radios are connected to 13 ports of the receive Butler matrix and the
`transmit ports are cormected te a 13x3 switch that can connecteach radio to any of the 3 PAs.
`The PA outputs are connected to a second 3x13 switch that connects each of the 3 PAs to any of
`the transmit Butler matnx ports.
`
`The beampatterns and

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket